Kernel memory disclosure and crash via OCFS2 listxattr
Published Jun 24, 2026 · Updated Jun 24, 2026
Out-of-bounds read in Linux Kernel OCFS2 listxattr handling allows local users to disclose kernel memory or crash the system. After inline attribute names exactly consume the supplied buffer, ocfs2_xattr_list_entry() treats the zero remaining size as probe mode, skips its bounds check, counts block-stored names, and makes listxattr() copy beyond the allocated list buffer. Exploitation requires a writable OCFS2 file with both inline and block-based user attributes; network wrappers allocate the full size and do not expose the trigger.
Summary
What happened
Out-of-bounds read in Linux Kernel OCFS2 listxattr handling allows local users to disclose kernel memory or crash the system. After inline attribute names exactly consume the supplied buffer, ocfs2_xattr_list_entry() treats the zero remaining size as probe mode, skips its bounds check, counts block-stored names, and makes listxattr() copy beyond the allocated list buffer. Exploitation requires a writable OCFS2 file with both inline and block-based user attributes; network wrappers allocate the full size and do not expose the trigger.
The record
- CVE
- CVE-2026-53041
- Published
- Jun 24, 2026
- Updated
- Jun 24, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-787, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 24, 2026CVE publishedPublication date reported by the CVE source.
- Jun 24, 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=2.6.28
- Affected versionversion=936b8834366ec05f2a6993f73afd8348cac9718e <2323084c17370304f49c84b354fe7b3edbb264fe
- Affected versionversion=936b8834366ec05f2a6993f73afd8348cac9718e <2685df8577a38d83b367c8cf52eda9dc286959ff
- Affected versionversion=936b8834366ec05f2a6993f73afd8348cac9718e <46e66fefb83811958127bc9ad736983ec629d82b
- Affected versionversion=936b8834366ec05f2a6993f73afd8348cac9718e <50033ec1350fe68abdc63b950ced7ae57364b77a
- Affected versionversion=936b8834366ec05f2a6993f73afd8348cac9718e <6f702b00b8124c5d3525f19172934544826a114d
- Affected versionversion=936b8834366ec05f2a6993f73afd8348cac9718e <a35a1c2b170b5b578b1b3fecb95694796552af9a
- Affected versionversion=936b8834366ec05f2a6993f73afd8348cac9718e <d12f558e6200b3f47dbef9331ed6d115d2410e59
- Affected versionversion=936b8834366ec05f2a6993f73afd8348cac9718e <d919b905939eda93393e3572900ff70dbad2b47f
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.
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