CVE-2022-49363
Last modified
CVE-2022-49363 is a medium-severity vulnerability rated 5.5/10 on the CVSS scale. 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.. EPSS estimates a 0.26% chance of exploitation in the next 30 days.
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.
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux Kernel | >= 3.8, < 5.4.198 |
| Linux | Linux Kernel | >= 5.5, < 5.10.121 |
| Linux | Linux Kernel | >= 5.11, < 5.15.46 |
| Linux | Linux Kernel | >= 5.16, < 5.17.14 |
| Linux | Linux Kernel | >= 5.18, < 5.18.3 |
References
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2022-49363?
How severe is CVE-2022-49363?
How do I fix CVE-2022-49363?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2022
- CVE-2022-49358In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2022-49359In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2022-4936The WCFM Marketplace plugin for WordPress is vulnerable to C…8.8
- CVE-2022-49360In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2022-49361In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2022-49362In the Linux kernel, the following vulnerability has been re…9.8
- CVE-2022-49364In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2022-49365In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2022-49366In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2022-49367In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2022-49368In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2022-49369In the Linux kernel, the following vulnerability has been re…5.5
Are you affected by CVE-2022-49363?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
