CVE-2022-50013f2fs: fix to avoid use f2fs_bug_on() in f2fs_new_node_page()
- 5.5MediumCVSS base score
- 0.26%Exploitation in 30 daysEPSS · top 82% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
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 <[email protected]> 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.
Timeline
ID reserved
By Linux
Published
- 14 months later
· 14 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| NVDNVD · Analyzed | 3.1 | Medium5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
- EPSS (exploitation in 30 days)
- 0.26% · top 82% of all CVEs (18 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.
Affected products
- affected 22ad0b6ab46683975c6da032f1c2593066c7b3bd – < fbfad62b29e9f8f1c1026a806c9e064ec2a7c342
- affected 22ad0b6ab46683975c6da032f1c2593066c7b3bd – < 29e734ec33ae4bd7de4018fb0fb0eec808c36b92
- affected 22ad0b6ab46683975c6da032f1c2593066c7b3bd – < 800ba8979111184d5194f4233cc83afe683efc54
- affected 22ad0b6ab46683975c6da032f1c2593066c7b3bd – < 5a01e45b925a0bc9718eccd33e5920f1a4e44caf
- affected 22ad0b6ab46683975c6da032f1c2593066c7b3bd – < 43ce0a0bda2c54dad91d5a1943554eed9e050f55
- affected 22ad0b6ab46683975c6da032f1c2593066c7b3bd – < 141170b759e03958f296033bb7001be62d1d363b
- affected 4.11
- unaffected < 4.11
- unaffected 4.19.256 – ≤ 4.19.*
- unaffected 5.4.211 – ≤ 5.4.*
- unaffected 5.10.138 – ≤ 5.10.*
- unaffected 5.15.63 – ≤ 5.15.*
- unaffected 5.19.4 – ≤ 5.19.*
- unaffected 6.0 – ≤ *
References
References6
- https://git.kernel.org/stable/c/fbfad62b29e9f8f1c1026a806c9e064ec2a7c342 (opens in a new tab)
- https://git.kernel.org/stable/c/29e734ec33ae4bd7de4018fb0fb0eec808c36b92 (opens in a new tab)
- https://git.kernel.org/stable/c/800ba8979111184d5194f4233cc83afe683efc54 (opens in a new tab)
- https://git.kernel.org/stable/c/5a01e45b925a0bc9718eccd33e5920f1a4e44caf (opens in a new tab)
- https://git.kernel.org/stable/c/43ce0a0bda2c54dad91d5a1943554eed9e050f55 (opens in a new tab)
- https://git.kernel.org/stable/c/141170b759e03958f296033bb7001be62d1d363b (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2022-55198 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2022-50013)Record last updated .