CVE-2022-49363 Details
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.
A vulnerability has been identified in the Linux kernel's F2FS (Flash-Friendly File System) implementation, specifically in versions through 5.17. The issue arises in the 'f2fs_do_zero_range()' function, where a lack of proper validation on block addresses can lead to inconsistencies between the inode's block mapping information and the Segment Information Table (SIT). This discrepancy can cause the kernel to panic when the F2FS fallocate function attempts to update the SIT with an invalid block address. The vulnerability can be reproduced by enabling Kernel Address Sanitizer (KASAN) and running a specific sequence of system calls that trigger the bug, as reported in the Linux kernel bugzilla.
Users can upgrade to a patched version of the Linux kernel where this vulnerability has been addressed. The specific commit fixing this issue is available in the Linux kernel's official Git repository.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
No SSVC data is available for this CVE.
References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://git.kernel.org/stable/c/25f8236213a91efdf708b9d77e9e51b6fc3e141c | kernel.org | Patch |
| https://git.kernel.org/stable/c/470493be19a5730ed432e3ac0f29a2ee7fc6c557 | kernel.org | Patch |
| https://git.kernel.org/stable/c/7361c9f2bd6a8f0cbb41cdea9aff04765ff23f67 | kernel.org | Patch |
| https://git.kernel.org/stable/c/805b48b234a2803cb7daec7f158af12f0fbaefac | kernel.org | Patch |
| https://git.kernel.org/stable/c/a34d7b49894b0533222188a52e2958750f830efd | kernel.org | Patch |
| https://git.kernel.org/stable/c/f2e1c38b5ac64eb1a16a89c52fb419409d12c25b | kernel.org | Patch |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| NVD-CWE-noinfo | Insufficient Information to Classify Weakness | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| linux linux kernel | >= 3.8, < 5.4.198 >= 5.5, < 5.10.121 >= 5.11, < 5.15.46 >= 5.16, < 5.17.14 >= 5.18, < 5.18.3 |
CPE
Remediation
| |
Change History
5 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Aug 15, 2026 | CVE Modified | kernel.org |
| Aug 4, 2026 | CVE Modified | kernel.org |
| Jun 17, 2026 | CVE Modified | kernel.org |
| Oct 21, 2025 | Initial Analysis | [email protected] |
| Feb 26, 2025 | New CVE Received | kernel.org |