CVE-2022-50013

f2fs: fix to avoid use f2fs_bug_on() in f2fs_new_node_page()

MEDIUM
5.5
CVSS Score
Published: June 18, 2025 at 11:01 AM UTC
Updated: August 15, 2026 at 01:36 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM5.5
Exploit prediction
EPSS 0.2%

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

3.8 ≤ v < 4.19.2564.11 ≤ v < 4.19.2564.11 ≤ v < 5.10.1384.11 ≤ v < 5.15.634.11 ≤ v < 5.19.44.11 ≤ v < 5.4.2114.11 ≤ v < 6.04.20 ≤ v < 5.4.2115.11 ≤ v < 5.15.635.16 ≤ v < 5.19.45.5 ≤ v < 5.10.13822ad0b6ab46683975c6da032f1c2593066c7b3bd4.11
Vendor states this is fixed in 141170b759e03958f296033bb7001be62d1d363b (fixed)
Vendor states this is fixed in 29e734ec33ae4bd7de4018fb0fb0eec808c36b92 (fixed)
Vendor states this is fixed in 43ce0a0bda2c54dad91d5a1943554eed9e050f55 (fixed)
Vendor states this is fixed in 5a01e45b925a0bc9718eccd33e5920f1a4e44caf (fixed)
Vendor states this is fixed in 800ba8979111184d5194f4233cc83afe683efc54 (fixed)
Vendor states this is fixed in fbfad62b29e9f8f1c1026a806c9e064ec2a7c342 (fixed)
Vendor states this is fixed in 4.11 (unaffected)
Vendor states this is fixed in 4.19.256 (unaffected)
Vendor states this is fixed in 5.10.138 (unaffected)
Vendor states this is fixed in 5.15.63 (unaffected)
Vendor states this is fixed in 5.19.4 (unaffected)
Vendor states this is fixed in 5.4.211 (unaffected)
Vendor states this is fixed in 6.0 (unaffected)

References (6)

Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/141170b759e03958f296033bb7001be62d1d363b
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/29e734ec33ae4bd7de4018fb0fb0eec808c36b92
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/43ce0a0bda2c54dad91d5a1943554eed9e050f55
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/5a01e45b925a0bc9718eccd33e5920f1a4e44caf
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/800ba8979111184d5194f4233cc83afe683efc54
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/fbfad62b29e9f8f1c1026a806c9e064ec2a7c342

CVSS

Attack Vector
LOCAL
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusANALYZED
CWE
NVD-CWE-noinfo

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card