CVE-2022-50013

  1. OpenCVE
  2. Vulnerabilities (CVE)
  3. CVE-2022-50013
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.

5.5 /10

CVSS v3 : MEDIUM

V3 Legend

Vector :

Exploitability : 1.8 / Impact : 3.6

Attack Vector LOCAL

Attack Complexity LOW

Privileges Required LOW

User Interaction NONE

Confidentiality Impact NONE

Integrity Impact NONE

Availability Impact HIGH

Scope UNCHANGED

References
Link Resource
https://git.kernel.org/stable/c/141170b759e03958f296033bb7001be62d1d363b Patch
https://git.kernel.org/stable/c/29e734ec33ae4bd7de4018fb0fb0eec808c36b92 Patch
https://git.kernel.org/stable/c/43ce0a0bda2c54dad91d5a1943554eed9e050f55 Patch
https://git.kernel.org/stable/c/5a01e45b925a0bc9718eccd33e5920f1a4e44caf Patch
https://git.kernel.org/stable/c/800ba8979111184d5194f4233cc83afe683efc54 Patch
https://git.kernel.org/stable/c/fbfad62b29e9f8f1c1026a806c9e064ec2a7c342 Patch
Configurations

Configuration 1 (hide)

OR cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
History

14 Nov 2025, 17:00

Type Values Removed Values Added
Summary
  • (es) En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: f2fs: corrección para evitar el uso de f2fs_bug_on() en f2fs_new_node_page() Como informó Dipanjan Das , syzkaller encontró un error de f2fs como el siguiente: RIP: 0010:f2fs_new_node_page+0x19ac/0x1fc0 fs/f2fs/node.c:1295 Seguimiento de llamadas: write_all_xattrs fs/f2fs/xattr.c:487 [en línea] __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 [en línea] __se_sys_lsetxattr fs/xattr.c:649 [en línea] __x64_sys_lsetxattr+0xbd/0x150 fs/xattr.c:649 do_syscall_x64 arch/x86/entry/common.c:50 [en línea] do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x46/0xb0 La entrada NAT y el mapa de bits NAT pueden ser inconsistentes, por ejemplo, un nid está libre en el mapa de bits NAT y blkaddr en su entrada NAT no es NULL_ADDR, puede activar BUG_ON() en f2fs_new_node_page(), arréglelo.
First Time Linux
Linux linux Kernel
CVSS v2 : unknown
v3 : unknown 		v2 : unknown
v3 : 5.5
CPE cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
CWE NVD-CWE-noinfo
References () https://git.kernel.org/stable/c/141170b759e03958f296033bb7001be62d1d363b - () https://git.kernel.org/stable/c/141170b759e03958f296033bb7001be62d1d363b - Patch
References () https://git.kernel.org/stable/c/29e734ec33ae4bd7de4018fb0fb0eec808c36b92 - () https://git.kernel.org/stable/c/29e734ec33ae4bd7de4018fb0fb0eec808c36b92 - Patch
References () https://git.kernel.org/stable/c/43ce0a0bda2c54dad91d5a1943554eed9e050f55 - () https://git.kernel.org/stable/c/43ce0a0bda2c54dad91d5a1943554eed9e050f55 - Patch
References () https://git.kernel.org/stable/c/5a01e45b925a0bc9718eccd33e5920f1a4e44caf - () https://git.kernel.org/stable/c/5a01e45b925a0bc9718eccd33e5920f1a4e44caf - Patch
References () https://git.kernel.org/stable/c/800ba8979111184d5194f4233cc83afe683efc54 - () https://git.kernel.org/stable/c/800ba8979111184d5194f4233cc83afe683efc54 - Patch
References () https://git.kernel.org/stable/c/fbfad62b29e9f8f1c1026a806c9e064ec2a7c342 - () https://git.kernel.org/stable/c/fbfad62b29e9f8f1c1026a806c9e064ec2a7c342 - Patch

18 Jun 2025, 11:15

Type Values Removed Values Added
New CVE
Information

Published : 2025-06-18 11:15

Updated : 2025-11-14 17:00

NVD link : CVE-2022-50013

Mitre link : CVE-2022-50013

CVE.ORG link : CVE-2022-50013

JSON object : View

Products Affected

linux

  • linux_kernel
CWE
NVD-CWE-noinfo