Memory disclosure and crash via unbounded xattr walk
Published Sep 16, 2025 · Updated Sep 16, 2025
An out-of-bounds read in the ext4 inline-data path in Linux allows local users to read adjacent kernel memory or crash the system. get_max_inline_xattr_value_size() follows inline inode xattr entries without verifying that the next entry remains inside the allocated inode buffer. Reachability requires a crafted ext4 image or write access to an underlying block device while its filesystem is mounted, followed by a file write through the local VFS path.
Summary
What happened
An out-of-bounds read in the ext4 inline-data path in Linux allows local users to read adjacent kernel memory or crash the system. get_max_inline_xattr_value_size() follows inline inode xattr entries without verifying that the next entry remains inside the allocated inode buffer. Reachability requires a crafted ext4 image or write access to an underlying block device while its filesystem is mounted, followed by a file write through the local VFS path.
The record
- CVE
- CVE-2023-53285
- Published
- Sep 16, 2025
- Updated
- Sep 16, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 16, 2025CVE publishedPublication date reported by the CVE source.
- Sep 16, 2025Record 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=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <1d2caddbeeee56fbbc36b428c5b909c3ad88eb7f
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <2220eaf90992c11d888fe771055d4de330385f01
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <3d7b8fbcd2273e2b9f4c6de5ce2f4c0cd3cb1205
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <4597554b4f7b29e7fd78aa449bab648f8da4ee2c
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <486efbbc9445dca7890a1b86adbccb88b91284b0
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <5a229d21b98d132673096710e8281ef522dab1d1
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <88a06a94942c5c0a896e9da1113a6bb29e36cbef
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <e780058bd75614b66882bc02620ddbd884171560
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <f22b274429e88d3dc7e79d375b56ce4f2f59f0b4
What conditions does exploitation require?
What is affected?
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
- syzbot ext4 out-of-bounds-read reproducerproof of concept · demonstrated
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