CVE-2023-52786
Last modified
CVE-2023-52786 is a medium-severity vulnerability rated 4.7/10 on the CVSS scale. In the Linux kernel, the following vulnerability has been resolved: ext4: fix racy may inline data check in dio write syzbot reports that the following warning from ext4_iomap_begin() triggers as of the commit referenced below: if (WARN_ON_ONCE(ext4_has_inline_data(inode))) return -ERANGE; This occurs during a dio write, which is never expected to encounter an inode with inline data. To enforce this behavior, ext4_dio_write_iter() checks the current inline state of the inode and clears the MAY_INLINE_DATA state flag to either fall back to buffered writes, or enforce that any other writers in progress on the inode are not allowed to create inline data. The problem is that the check for existing inline data and the state flag can span a lock cycle. EPSS estimates a 0.18% chance of exploitation in the next 30 days.
Description
In the Linux kernel, the following vulnerability has been resolved: ext4: fix racy may inline data check in dio write syzbot reports that the following warning from ext4_iomap_begin() triggers as of the commit referenced below: if (WARN_ON_ONCE(ext4_has_inline_data(inode))) return -ERANGE; This occurs during a dio write, which is never expected to encounter an inode with inline data. To enforce this behavior, ext4_dio_write_iter() checks the current inline state of the inode and clears the MAY_INLINE_DATA state flag to either fall back to buffered writes, or enforce that any other writers in progress on the inode are not allowed to create inline data. The problem is that the check for existing inline data and the state flag can span a lock cycle. For example, if the ilock is originally locked shared and subsequently upgraded to exclusive, another writer may have reacquired the lock and created inline data before the dio write task acquires the lock and proceeds. The commit referenced below loosens the lock requirements to allow some forms of unaligned dio writes to occur under shared lock, but AFAICT the inline data check was technically already racy for any dio write that would have involved a lock cycle. Regardless, lift clearing of the state bit to the same lock critical section that checks for preexisting inline data on the inode to close the race.
Metrics
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux Kernel | >= 6.5, < 6.5.13 |
| Linux | Linux Kernel | >= 6.6, < 6.6.3 |
References
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2023-52786?
How severe is CVE-2023-52786?
How do I fix CVE-2023-52786?
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-52780In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2023-52781In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2023-52782In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2023-52783In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2023-52784In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2023-52785In the Linux kernel, the following vulnerability has been re…4.7
- CVE-2023-52787In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2023-52788In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2023-52789In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2023-5279A vulnerability has been found in SourceCodester Engineers O…9.8
- CVE-2023-52790In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2023-52791In the Linux kernel, the following vulnerability has been re…5.5
Are you affected by CVE-2023-52786?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
