CVE-2022-49363f2fs: fix to do sanity check on block address in f2fs_do_zero_range()
- 7.8HighCVSS base score
- 0.28%Exploitation in 30 daysEPSS · top 80% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
In the Linux kernel, the following vulnerability has been resolved: f2fs: fix to do sanity check on block address in f2fs_do_zero_range() As Yanming reported in bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=215894 I have encountered a bug in F2FS file system in kernel v5.17. I have uploaded the system call sequence as case.c, and a fuzzed image can be found in google net disk The kernel should enable CONFIG_KASAN=y and CONFIG_KASAN_INLINE=y. You can reproduce the bug by running the following commands: kernel BUG at fs/f2fs/segment.c:2291! Call Trace: f2fs_invalidate_blocks+0x193/0x2d0 f2fs_fallocate+0x2593/0x4a70 vfs_fallocate+0x2a5/0xac0 ksys_fallocate+0x35/0x70 __x64_sys_fallocate+0x8e/0xf0 do_syscall_64+0x3b/0x90 entry_SYSCALL_64_after_hwframe+0x44/0xae The root cause is, after image was fuzzed, block mapping info in inode will be inconsistent with SIT table, so in f2fs_fallocate(), it will cause panic when updating SIT with invalid blkaddr. Let's fix the issue by adding sanity check on block address before updating SIT table with it.
Timeline
ID reserved
By Linux
Published
- 18 months later
· 18 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| LinuxCNA (assigner) | 3.1 | High7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVDNVD · Modified | 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.28% · top 80% of all CVEs (17 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.
Affected products
- affected 75cd4e098d178433436abce08146a21647bb4585 – < 7361c9f2bd6a8f0cbb41cdea9aff04765ff23f67
- affected 75cd4e098d178433436abce08146a21647bb4585 – < a34d7b49894b0533222188a52e2958750f830efd
- affected 75cd4e098d178433436abce08146a21647bb4585 – < f2e1c38b5ac64eb1a16a89c52fb419409d12c25b
- affected 75cd4e098d178433436abce08146a21647bb4585 – < 470493be19a5730ed432e3ac0f29a2ee7fc6c557
- affected 75cd4e098d178433436abce08146a21647bb4585 – < 805b48b234a2803cb7daec7f158af12f0fbaefac
- affected 75cd4e098d178433436abce08146a21647bb4585 – < 25f8236213a91efdf708b9d77e9e51b6fc3e141c
- affected 4.2
- unaffected < 4.2
- unaffected 5.4.198 – ≤ 5.4.*
- unaffected 5.10.121 – ≤ 5.10.*
- unaffected 5.15.46 – ≤ 5.15.*
- unaffected 5.17.14 – ≤ 5.17.*
- unaffected 5.18.3 – ≤ 5.18.*
- unaffected 5.19 – ≤ *
References
References6
- https://git.kernel.org/stable/c/7361c9f2bd6a8f0cbb41cdea9aff04765ff23f67 (opens in a new tab)
- https://git.kernel.org/stable/c/a34d7b49894b0533222188a52e2958750f830efd (opens in a new tab)
- https://git.kernel.org/stable/c/f2e1c38b5ac64eb1a16a89c52fb419409d12c25b (opens in a new tab)
- https://git.kernel.org/stable/c/470493be19a5730ed432e3ac0f29a2ee7fc6c557 (opens in a new tab)
- https://git.kernel.org/stable/c/805b48b234a2803cb7daec7f158af12f0fbaefac (opens in a new tab)
- https://git.kernel.org/stable/c/25f8236213a91efdf708b9d77e9e51b6fc3e141c (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)
- EUVD EUVD-2022-54866 (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://cveledger.app/cve/CVE-2022-49363)Record last updated .