CVE-2022-49428
f2fs: fix to do sanity check on inline_dots inode
- Published
- Updated
- Reserved
- Assigned by
- Linux
Description
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().
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 (7 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.
Weakness
Affected products
- affected 510022a85839a8409d1e6a519bb86ce71a84f30a – < 250e5a6be52a6b9d82fe91976c83cc158868b4e9
- affected 510022a85839a8409d1e6a519bb86ce71a84f30a – < 34f48ce5d5936eea33e3b6415403e57eb84aff97
- affected 510022a85839a8409d1e6a519bb86ce71a84f30a – < 2f46160d0a19b13bfe96c0dd50eed5c5d253ab7a
- affected 510022a85839a8409d1e6a519bb86ce71a84f30a – < 12662d19467b391b5b509ac5e9ab4f583c6dde16
- affected 4.1
- unaffected < 4.1
- unaffected 5.15.46 – ≤ 5.15.*
- unaffected 5.17.14 – ≤ 5.17.*
- unaffected 5.18.3 – ≤ 5.18.*
- unaffected 5.19 – ≤ *
References (4)
- https://git.kernel.org/stable/c/250e5a6be52a6b9d82fe91976c83cc158868b4e9 (opens in a new tab)
- https://git.kernel.org/stable/c/34f48ce5d5936eea33e3b6415403e57eb84aff97 (opens in a new tab)
- https://git.kernel.org/stable/c/2f46160d0a19b13bfe96c0dd50eed5c5d253ab7a (opens in a new tab)
- https://git.kernel.org/stable/c/12662d19467b391b5b509ac5e9ab4f583c6dde16 (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)
- 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://trackcve.app/cve/CVE-2022-49428)Record last updated .