CVE-2023-53503
Last modified
CVE-2023-53503 is a medium-severity vulnerability rated 5.5/10 on the CVSS scale. In the Linux kernel, the following vulnerability has been resolved: ext4: allow ext4_get_group_info() to fail Previously, ext4_get_group_info() would treat an invalid group number as BUG(), since in theory it should never happen. However, if a malicious attaker (or fuzzer) modifies the superblock via the block device while it is the file system is mounted, it is possible for s_first_data_block to get set to a very large number. EPSS estimates a 0.14% chance of exploitation in the next 30 days.
Description
In the Linux kernel, the following vulnerability has been resolved: ext4: allow ext4_get_group_info() to fail Previously, ext4_get_group_info() would treat an invalid group number as BUG(), since in theory it should never happen. However, if a malicious attaker (or fuzzer) modifies the superblock via the block device while it is the file system is mounted, it is possible for s_first_data_block to get set to a very large number. In that case, when calculating the block group of some block number (such as the starting block of a preallocation region), could result in an underflow and very large block group number. Then the BUG_ON check in ext4_get_group_info() would fire, resutling in a denial of service attack that can be triggered by root or someone with write access to the block device. For a quality of implementation perspective, it's best that even if the system administrator does something that they shouldn't, that it will not trigger a BUG. So instead of BUG'ing, ext4_get_group_info() will call ext4_error and return NULL. We also add fallback code in all of the callers of ext4_get_group_info() that it might NULL. Also, since ext4_get_group_info() was already borderline to be an inline function, un-inline it. The results in a next reduction of the compiled text size of ext4 by roughly 2k.
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Linux | Linux Kernel | >= 3.11, < 5.10.181 | — |
| Linux | Linux Kernel | >= 5.11, < 5.15.113 | — |
| Linux | Linux Kernel | >= 5.16, < 6.1.30 | — |
| Linux | Linux Kernel | >= 6.2, < 6.3.4 | — |
| Linux | Linux Kernel | 6.4 | Rc1 |
References
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2023-53503?
How severe is CVE-2023-53503?
How do I fix CVE-2023-53503?
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 2023
- CVE-2023-53498In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2023-53499In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2023-5350 SQL Injection in GitHub repository salesagility/suitecrm pr…9.1
- CVE-2023-53500In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2023-53501In the Linux kernel, the following vulnerability has been re…4.7
- CVE-2023-53502Rejected reason: This CVE ID has been rejected or withdrawn …
- CVE-2023-53504In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2023-53505In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2023-53506In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2023-53507In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2023-53508In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2023-53509In the Linux kernel, the following vulnerability has been re…5.5
Are you affected by CVE-2023-53503?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
