Kernel panic via OCFS2 transaction-credit exhaustion
Published Jul 29, 2024 · Updated May 11, 2026
Transaction-credit exhaustion in Linux OCFS2 allows local users to trigger a filesystem abort and kernel panic through direct I/O. ocfs2_dio_end_io_write() uses ocfs2_calc_extend_credits() without accounting for arbitrarily large I/O containing many extents, so repeated ocfs2_replace_extent_rec() calls can consume all journal credits. The failure requires write access to a heavily fragmented OCFS2 filesystem and a direct-I/O request spanning many single-block extents; the bounded consequence is an OCFS2 abort and possible host crash.
Summary
What happened
Transaction-credit exhaustion in Linux OCFS2 allows local users to trigger a filesystem abort and kernel panic through direct I/O. ocfs2_dio_end_io_write() uses ocfs2_calc_extend_credits() without accounting for arbitrarily large I/O containing many extents, so repeated ocfs2_replace_extent_rec() calls can consume all journal credits. The failure requires write access to a heavily fragmented OCFS2 filesystem and a direct-I/O request spanning many single-block extents; the bounded consequence is an OCFS2 abort and possible host crash.
The record
- CVE
- CVE-2024-42077
- Published
- Jul 29, 2024
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Jul 29, 2024CVE publishedPublication date reported by the CVE source.
- May 11, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=4.6
- Affected versionversion=c15471f79506830f80eca0e7fe09b8213953ab5f <320273b5649bbcee87f9e65343077189699d2a7a
- Affected versionversion=c15471f79506830f80eca0e7fe09b8213953ab5f <331d1079d58206ff7dc5518185f800b412f89bc6
- Affected versionversion=c15471f79506830f80eca0e7fe09b8213953ab5f <9ea2d1c6789722d58ec191f14f9a02518d55b6b4
- Affected versionversion=c15471f79506830f80eca0e7fe09b8213953ab5f <a68b896aa56e435506453ec8835bc991ec3ae687
- Affected versionversion=c15471f79506830f80eca0e7fe09b8213953ab5f <be346c1a6eeb49d8fda827d2a9522124c2f72f36
- Affected versionversion=c15471f79506830f80eca0e7fe09b8213953ab5f <c05ffb693bfb42a48ef3ee88a55b57392984e111
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo