Kernel memory corruption via stale interrupt-controller entry
Published Dec 27, 2024 · Updated Aug 5, 2026
Use-after-free in the Linux SuperH interrupt controller allows local users to read or corrupt kernel memory after an early-boot error. register_intc_controller() adds d to intc_list before initialization finishes, then frees d after an allocation or mapping failure without removing the list entry. A vulnerable SuperH kernel with CONFIG_SH_INTC must encounter that early-boot failure; later traversal can disclose or corrupt kernel memory or panic the host.
Summary
What happened
Use-after-free in the Linux SuperH interrupt controller allows local users to read or corrupt kernel memory after an early-boot error. register_intc_controller() adds d to intc_list before initialization finishes, then frees d after an allocation or mapping failure without removing the list entry. A vulnerable SuperH kernel with CONFIG_SH_INTC must encounter that early-boot failure; later traversal can disclose or corrupt kernel memory or panic the host.
The record
- CVE
- CVE-2024-53165
- Published
- Dec 27, 2024
- Updated
- Aug 5, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-416
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 27, 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=2.6.30
- Affected versionversion=2dcec7a988a1895540460a0bf5603bab63d5a3ed <3c7c806b3eafd94ae0f77305a174d63b69ec187c
- Affected versionversion=2dcec7a988a1895540460a0bf5603bab63d5a3ed <588bdec1ff8b81517dbae0ae51c9df52c0b952d3
- Affected versionversion=2dcec7a988a1895540460a0bf5603bab63d5a3ed <63e72e551942642c48456a4134975136cdcb9b3c
- Affected versionversion=2dcec7a988a1895540460a0bf5603bab63d5a3ed <6ba6e19912570b2ad68298be0be1dc779014a303
- Affected versionversion=2dcec7a988a1895540460a0bf5603bab63d5a3ed <971b4893457788e0e123ea552f0bb126a5300e61
- Affected versionversion=2dcec7a988a1895540460a0bf5603bab63d5a3ed <b8b84dcdf3ab1d414304819f824b10efba64132c
- Affected versionversion=2dcec7a988a1895540460a0bf5603bab63d5a3ed <c3f4f4547fb291982f5ef56c048277c4d5ccc4e4
- Affected versionversion=2dcec7a988a1895540460a0bf5603bab63d5a3ed <c43df7dae28fb9fce96ef088250c1e3c3a77c527
- Affected versionversion=2dcec7a988a1895540460a0bf5603bab63d5a3ed <d8de818df12d86a1a26a8efd7b4b3b9c6dc3c5cc
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