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

In the Linux kernel, the following vulnerability has been resolved: f2fs: fix to do sanity check on inline_dots inode As Wenqing reported in bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=215765 It will cause a kernel panic with steps: - mkdir mnt - mount tmp40.img mnt - ls mnt folio_mark_dirty+0x33/0x50 f2fs_add_regular_entry+0x541/0xad0 [f2fs] f2fs_add_dentry+0x6c/0xb0 [f2fs] f2fs_do_add_link+0x182/0x230 [f2fs] __recover_dot_dentries+0x2d6/0x470 [f2fs] f2fs_lookup+0x5af/0x6a0 [f2fs] __lookup_slow+0xac/0x200 lookup_slow+0x45/0x70 walk_component+0x16c/0x250 path_lookupat+0x8b/0x1f0 filename_lookup+0xef/0x250 user_path_at_empty+0x46/0x70 vfs_statx+0x98/0x190 __do_sys_newlstat+0x41/0x90 __x64_sys_newlstat+0x1a/0x30 do_syscall_64+0x37/0xb0 entry_SYSCALL_64_after_hwframe+0x44/0xae The root cause is for special file: e.g. character, block, fifo or socket file, f2fs doesn't assign address space operations pointer array for mapping->a_ops field, so, in a fuzzed image, if inline_dots flag was tagged in special file, during lookup(), when f2fs runs into __recover_dot_dentries(), it will cause NULL pointer access once f2fs_add_regular_entry() calls a_ops->set_dirty_page().

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2026-04-06	0.03%	0.14%	+0.11%
2	2025-11-21	0.06%	0.03%	-0.03%
3	2025-11-18	—	0.06%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2026-04-06

0.03%

0.14%

+0.11%

2025-11-21

0.06%

0.03%

-0.03%

2025-11-18

—

0.06%

—

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-49428

vendor	priority	summary	link
`debian`	not yet assigned	CVE-2022-49428 not yet assigned priority: Debian including 1 source packages (linux), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 4, open 1.	https://security-tracker.debian.org/tracker/CVE-2022-49428
`redhat`	medium	—	https://access.redhat.com/security/cve/CVE-2022-49428
`suse`	medium	CVE-2022-49428 severity moderate: SUSE including 26 source package names (cluster-md-kmp-default, dlm-kmp-default, …), 270 product×package rows across 54 product lines (SLES-LTSS-TERADATA 15 SP2, SUSE Linux Enterprise High Availability Extension 12 SP5, … (54 product lines)): Known Not Affected 270.	https://www.suse.com/security/cve/CVE-2022-49428/
`ubuntu`	medium	CVE-2022-49428 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 149, released 114, not-affected 102, needed 41.	https://ubuntu.com/security/CVE-2022-49428

Affected software / configurations for CVE-2022-49428

Vendor	Product	Version	Raw CPE
linux	linux_kernel	>= 4.1, < 5.15.46	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 5.16, < 5.17.14	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 5.18, < 5.18.3	cpe:2.3:o:linux:linux_kernel::::::::

References for CVE-2022-49428

URL	Tags
https://git.kernel.org/stable/c/12662d19467b391b5b509ac5e9ab4f583c6dde16	Patch
https://git.kernel.org/stable/c/250e5a6be52a6b9d82fe91976c83cc158868b4e9	Patch
https://git.kernel.org/stable/c/2f46160d0a19b13bfe96c0dd50eed5c5d253ab7a	Patch
https://git.kernel.org/stable/c/34f48ce5d5936eea33e3b6415403e57eb84aff97	Patch

URL

CVE-2022-49428 | f2fs: fix to do sanity check on inline_dots inode

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

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

Weakness enumeration for CVE-2022-49428

OS Trackers for CVE-2022-49428

Affected software / configurations for CVE-2022-49428

References for CVE-2022-49428