Kernel task hang via self-referential xattr inode
Published May 2, 2025 · Updated May 11, 2026
Denial of service in affected Linux kernel releases allows local users to hang a kernel task by mounting a crafted ext4 filesystem image. During ext4 orphan cleanup, ext4_xattr_delete_inode follows an extended-attribute inode number that matches the inode being deleted and waits for that same I_FREEING inode to finish, creating an infinite self-wait. Triggering the condition requires local access sufficient to mount the crafted image; the resulting task hang interrupts availability without reported data disclosure or modification.
Summary
What happened
Denial of service in affected Linux kernel releases allows local users to hang a kernel task by mounting a crafted ext4 filesystem image. During ext4 orphan cleanup, ext4_xattr_delete_inode follows an extended-attribute inode number that matches the inode being deleted and waits for that same I_FREEING inode to finish, creating an infinite self-wait. Triggering the condition requires local access sufficient to mount the crafted image; the resulting task hang interrupts availability without reported data disclosure or modification.
The record
- CVE
- CVE-2023-53089
- Published
- May 2, 2025
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 2, 2025CVE publishedPublication date reported by the CVE source.
- May 11, 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=4.13
- Affected versionversion=e50e5129f384ae282adebfb561189cdb19b81cee <0f7bfd6f8164be32dbbdf36aa1e5d00485c53cd7
- Affected versionversion=e50e5129f384ae282adebfb561189cdb19b81cee <1aec41c98cce61d19ce89650895e51b9f3cdef13
- Affected versionversion=e50e5129f384ae282adebfb561189cdb19b81cee <2c96c52aeaa6fd9163cfacdd98778b4a0398ef18
- Affected versionversion=e50e5129f384ae282adebfb561189cdb19b81cee <64b72f5e7574020dea62ab733d88a54d903c42a1
- Affected versionversion=e50e5129f384ae282adebfb561189cdb19b81cee <73f7987fe1b82596f1a380e85cd0097ebaae7e01
- Affected versionversion=e50e5129f384ae282adebfb561189cdb19b81cee <94fd091576b12540924f6316ebc0678e84cb2800
- Affected versionversion=e50e5129f384ae282adebfb561189cdb19b81cee <a98160d8f3e6242ca9b7f443f26e7ef3a61ba684
- Affected versionversion=e50e5129f384ae282adebfb561189cdb19b81cee <efddc7e106fdf8d1f62d45e79de78f63b7c04fba
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
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