Kernel memory corruption via stale JFS inode pointer
Published Mar 6, 2024 · Updated Aug 5, 2026
Use-after-free in the JFS mount path in Linux before 6.8 allows local users to trigger stale kernel-memory access via a failed JFS mount. When diMount(ipimap) fails, jfs_evict_inode leaves sbi->ipimap pointing to an object that RCU later frees, and diFreeSpecial dereferences it. Reaching the flaw requires low-privilege local access and a JFS mount failure; published sources do not demonstrate a specific crash or privilege gain.
Summary
What happened
Use-after-free in the JFS mount path in Linux before 6.8 allows local users to trigger stale kernel-memory access via a failed JFS mount. When diMount(ipimap) fails, jfs_evict_inode leaves sbi->ipimap pointing to an object that RCU later frees, and diFreeSpecial dereferences it. Reaching the flaw requires low-privilege local access and a JFS mount failure; published sources do not demonstrate a specific crash or privilege gain.
The record
- CVE
- CVE-2023-52600
- Published
- Mar 6, 2024
- Updated
- Aug 5, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-416
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 6, 2024CVE publishedPublication date reported by the CVE source.
- Aug 5, 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=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <1696d6d7d4a1b373e96428d0fe1166bd7c3c795e
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <32e8f2d95528d45828c613417cb2827d866cbdce
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <81b4249ef37297fb17ba102a524039a05c6c5d35
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <8e44dc3f96e903815dab1d74fff8faafdc6feb61
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <93df0a2a0b3cde2d7ab3a52ed46ea1d6d4aaba5f
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <bacdaa04251382d7efd4f09f9a0686bfcc297e2e
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <bc6ef64dbe71136f327d63b2b9071b828af2c2a8
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <e0e1958f4c365e380b17ccb35617345b31ef7bf3
- Affected versionversion=2.6.12
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