CVE-2022-50013 [Medium] | Security Vulnerability in Linux Kernel

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.

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2026-04-14	0.02%	0.06%	+0.04%
2	2025-06-18	—	0.02%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2026-04-14

0.02%

0.06%

+0.04%

2025-06-18

—

0.02%

—

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
5.5	3.1	MEDIUM	`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H` Click to expand Attack vector (AV:L) They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by. Attack complexity (AC:L) Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup. Privileges required (PR:L) A normal user session is enough; they don’t have to be admin. User interaction (UI:N) Nobody has to click “OK” or open a trap file; it can work without a victim helping. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:N) Doesn’t really leak secrets in a meaningful way. Integrity (I:N) Data isn’t meaningfully altered or forged. Availability (A:H) Could take the service down hard or make it unusable for people who depend on it.	1.8	3.6	[email protected]

Base score

Version

Severity

Vector

Exploitability

Impact

Score source

5.5

3.1

MEDIUM

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H Click to expand

Attack vector (AV:L): They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L): Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L): A normal user session is enough; they don’t have to be admin.
User interaction (UI:N): Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N): Doesn’t really leak secrets in a meaningful way.
Integrity (I:N): Data isn’t meaningfully altered or forged.
Availability (A:H): Could take the service down hard or make it unusable for people who depend on it.

1.8

3.6

[email protected]

OS Trackers for CVE-2022-50013

vendor	priority	summary	link
`debian`	not yet assigned	CVE-2022-50013 not yet assigned priority: Debian including 1 source packages (linux), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5.	https://security-tracker.debian.org/tracker/CVE-2022-50013
`redhat`	—	—	https://access.redhat.com/security/cve/CVE-2022-50013
`suse`	medium	CVE-2022-50013 severity moderate: SUSE including 26 source package names (cluster-md-kmp-default, dlm-kmp-default, …), 266 product×package rows across 52 product lines (SLES-LTSS-TERADATA 15 SP2, SUSE Linux Enterprise High Availability Extension 15 SP7, … (52 product lines)): Known Not Affected 266.	https://www.suse.com/security/cve/CVE-2022-50013/
`ubuntu`	medium	CVE-2022-50013 medium priority: Ubuntu including 158 source packages (linux, linux-allwinner-5.19, …), 1551 status rows across 10 suites (bionic, focal, jammy, noble, oracular, plucky, questing, trusty, upstream, xenial): DNE 1145, ignored 151, released 135, not-affected 99, needed 20, needs-triage 1.	https://ubuntu.com/security/CVE-2022-50013

Affected software / configurations for CVE-2022-50013

Vendor	Product	Version	Raw CPE
linux	linux_kernel	>= 3.8, < 4.19.256	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 4.20, < 5.4.211	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 5.5, < 5.10.138	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 5.11, < 5.15.63	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 5.16, < 5.19.4	cpe:2.3:o:linux:linux_kernel::::::::

References for CVE-2022-50013

URL	Tags
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

URL

CVE-2022-50013 | f2fs: fix to avoid use f2fs_bug_on() in f2fs_new_node_page()

Exploit prediction scoring system (EPSS) score for CVE-2022-50013

Common vulnerability scoring system (CVSS) metrics for CVE-2022-50013

Weakness enumeration for CVE-2022-50013

OS Trackers for CVE-2022-50013

Affected software / configurations for CVE-2022-50013

References for CVE-2022-50013