Local service interruption via OCFS2 credit exhaustion
Published May 27, 2026 · Updated May 27, 2026
Resource exhaustion in affected Linux Kernel OCFS2 releases allows local users to interrupt service by completing direct I/O writes. ocfs2_dio_end_io_write() processes too many extents in one JBD2 transaction, so journal restart requests can exceed the transaction credit limit; it also removed the orphan inode before the extent-tree update completed. Exploitation requires low-privileged local access and an OCFS2 direct-I/O write path, and a mid-update crash can leave stale blocks beyond end-of-file.
Summary
What happened
Resource exhaustion in affected Linux Kernel OCFS2 releases allows local users to interrupt service by completing direct I/O writes. ocfs2_dio_end_io_write() processes too many extents in one JBD2 transaction, so journal restart requests can exceed the transaction credit limit; it also removed the orphan inode before the extent-tree update completed. Exploitation requires low-privileged local access and an OCFS2 direct-I/O write path, and a mid-update crash can leave stale blocks beyond end-of-file.
The record
- CVE
- CVE-2026-46080
- Published
- May 27, 2026
- Updated
- May 27, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 27, 2026CVE publishedPublication date reported by the CVE source.
- May 27, 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=0 <6.12.86
- Affected versionversion=0 <6.18.27
- Affected versionversion=0 <6.6.140
- Affected versionversion=0 <7.0.4
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <069c3fb310e9336cf48cfdf8748a32c29fd0193d
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <3c636a3edca9c3f180b3079f94fe7e115730d9c6
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <886f97fa59d0bbfa9859fb1a66dd9e014b522d89
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <d647c5b2fbf81560818dacade360abc8c00a9665
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <ea5bb1d20da756e4f41a48dad42b2e7d6e73f71e
What conditions does exploitation require?
What is affected?
Published CVSS scores
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