Kernel memory corruption via ext4 double unlock
Published Oct 7, 2025 · Updated Oct 7, 2025
Memory corruption in Linux ext4 5.4.237, 5.10.175, 5.15.103, 6.1.20, and 6.2.7 allows local users to read or write kernel memory. The ext4_rename error path releases the moved directory inode's i_rwsem after ext4_rename_dir_prepare has already released it, breaking exclusion during concurrent directory mutation. Exploitation requires a locally mounted crafted ext4 filesystem and a rename operation; the resulting corruption can expose or modify kernel memory or hang the directory and its unmount.
Summary
What happened
Memory corruption in Linux ext4 5.4.237, 5.10.175, 5.15.103, 6.1.20, and 6.2.7 allows local users to read or write kernel memory. The ext4_rename error path releases the moved directory inode's i_rwsem after ext4_rename_dir_prepare has already released it, breaking exclusion during concurrent directory mutation. Exploitation requires a locally mounted crafted ext4 filesystem and a rename operation; the resulting corruption can expose or modify kernel memory or hang the directory and its unmount.
The record
- CVE
- CVE-2023-53626
- Published
- Oct 7, 2025
- Updated
- Oct 7, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 7, 2025CVE publishedPublication date reported by the CVE source.
- Oct 7, 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=0813299c586b175d7edb25f56412c54b812d0379 <70e42feab2e20618ddd0cbfc4ab4b08628236ecd
- Affected versionversion=0c440f14558bfacd22c6935ae1fd4b2a09e96b5d <020166bc6669ca9fb267ebd96bd88c4fb64a5d46
- Affected versionversion=291cd19d107e197306869cb3237c1bba62d13182 <43ce288ab5d7274a4a141d7f5e3ed2ab7b41f8a2
- Affected versionversion=5.10.175 <5.10.176
- Affected versionversion=5.15.103 <5.15.104
- Affected versionversion=5.4.237 <5.4.238
- Affected versionversion=6.1.20 <6.1.21
- Affected versionversion=6.2.7 <6.2.8
- Affected versionversion=8dac5a63cf79707b547ea3d425fead5f4482198f <c16cbd8233d6c58fc488545393e49b5d55729990
- Affected versionversion=b0bb13612292ca90fa4c2a7e425375649bc50d3e <e71eb4dca41f0f36823724ced0406bb2dbdd5506
- Affected versionversion=c50fc503ee1b97f12c98e26afc39fdaebebcf04f <1c93c42c7bb23057bde8a0a2ab834927ff64d20c
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