CVE-2022-50013 json
f2fs: fix to avoid use f2fs_bug_on() in f2fs_new_node_page()
published last yr. modified 3mo ago also EUVD-2022-55198
- cvss
- 5.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 17%
- public exploits
- 0
- none known
Summary
In the Linux kernel, the following vulnerability has been resolved:
f2fs: fix to avoid use f2fs_bug_on() in f2fs_new_node_page()
As Dipanjan Das <mail.dipanjan.das@gmail.com> reported, syzkaller found a f2fs bug as below:
RIP: 0010:f2fs_new_node_page+0x19ac/0x1fc0 fs/f2fs/node.c:1295 Call Trace: write_all_xattrs fs/f2fs/xattr.c:487 [inline] __f2fs_setxattr+0xe76/0x2e10 fs/f2fs/xattr.c:743 f2fs_setxattr+0x233/0xab0 fs/f2fs/xattr.c:790 f2fs_xattr_generic_set+0x133/0x170 fs/f2fs/xattr.c:86 __vfs_setxattr+0x115/0x180 fs/xattr.c:182 __vfs_setxattr_noperm+0x125/0x5f0 fs/xattr.c:216 __vfs_setxattr_locked+0x1cf/0x260 fs/xattr.c:277 vfs_setxattr+0x13f/0x330 fs/xattr.c:303 setxattr+0x146/0x160 fs/xattr.c:611 path_setxattr+0x1a7/0x1d0 fs/xattr.c:630 __do_sys_lsetxattr fs/xattr.c:653 [inline] __se_sys_lsetxattr fs/xattr.c:649 [inline] __x64_sys_lsetxattr+0xbd/0x150 fs/xattr.c:649 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x46/0xb0
NAT entry and nat bitmap can be inconsistent, e.g. one nid is free in nat bitmap, and blkaddr in its NAT entry is not NULL_ADDR, it may trigger BUG_ON() in f2fs_new_node_page(), fix it.
Patch / fix
- Linux Linux 4.19.256, 5.4.211, 5.10.138, 5.15.63, 5.19.4, 6.0
- linux Debian 14, Debian 13, Debian 12 6.0.2-1
debian advisories DEBIAN-CVE-2022-50013
- linux Ubuntu 20.04 LTS 5.4.0-132.148
- linux Ubuntu 22.04 LTS 5.15.0-53.59
- linux-aws Ubuntu 20.04 LTS 5.4.0-1089.97
- linux-aws Ubuntu 22.04 LTS 5.15.0-1023.27
- linux-gcp Ubuntu 20.04 LTS 5.4.0-1093.102
- linux-gcp Ubuntu 22.04 LTS 5.15.0-1022.29
- linux-gke Ubuntu 22.04 LTS 5.15.0-1020.25
- linux-ibm Ubuntu 20.04 LTS 5.4.0-1037.42
ubuntu advisories UBUNTU-CVE-2022-50013
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- git.kernel.org/stable/c/fbfad62b29e9f8f1c1026a806c9e064ec2a7c342 commit
- git.kernel.org/stable/c/29e734ec33ae4bd7de4018fb0fb0eec808c36b92 commit
- git.kernel.org/stable/c/800ba8979111184d5194f4233cc83afe683efc54 commit
- git.kernel.org/stable/c/5a01e45b925a0bc9718eccd33e5920f1a4e44caf commit
- git.kernel.org/stable/c/43ce0a0bda2c54dad91d5a1943554eed9e050f55 commit
- git.kernel.org/stable/c/141170b759e03958f296033bb7001be62d1d363b commit
Is CVE-2022-50013 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2022-50013 updated
kernel: f2fs: fix to avoid use f2fs_bug_on() in f2fs_new_node_page()
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more Red Hat Enterprise Linux 10 kernelnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
0.26% chance of exploitation in the next 30 days, higher than 17% of all scored CVEs (FIRST EPSS, 2026-11-18).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
Affected products
- Linux Linux
Classification
- Technology feeds
References
-
git.kernel.org
/stable/c/fbfad62b29e9f8f1c1026a806c9e064ec2a7c342
patch
-
git.kernel.org
/stable/c/29e734ec33ae4bd7de4018fb0fb0eec808c36b92
patch
-
git.kernel.org
/stable/c/800ba8979111184d5194f4233cc83afe683efc54
patch
-
git.kernel.org
/stable/c/5a01e45b925a0bc9718eccd33e5920f1a4e44caf
patch
-
git.kernel.org
/stable/c/43ce0a0bda2c54dad91d5a1943554eed9e050f55
patch
-
git.kernel.org
/stable/c/141170b759e03958f296033bb7001be62d1d363b
patch
Sources
- CVE List CVE-2022-50013
- NVD CVE-2022-50013
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.