Service interruption via repeated platform timer lookup
Published Sep 27, 2024 · Updated May 11, 2026
Availability flaw in the MIPS clock-event driver in Linux allows local users to interrupt service during secondary CPU initialization. r4k_clockevent_init calls get_c0_compare_int on every CPU before checking cp0_timer_irq_installed, causing a secondary CPU to enter code that can sleep from invalid context. Reachability requires a MIPS multiprocessor system with its timer IRQ already installed; public sources identify no separate user-controlled input.
Summary
What happened
Availability flaw in the MIPS clock-event driver in Linux allows local users to interrupt service during secondary CPU initialization. r4k_clockevent_init calls get_c0_compare_int on every CPU before checking cp0_timer_irq_installed, causing a secondary CPU to enter code that can sleep from invalid context. Reachability requires a MIPS multiprocessor system with its timer IRQ already installed; public sources identify no separate user-controlled input.
The record
- CVE
- CVE-2024-46832
- Published
- Sep 27, 2024
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 27, 2024CVE 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=2.6.24
- Affected versionversion=38760d40ca61b18b2809e9c28df8b3ff9af8a02b <189d3ed3b25beee26ffe2abed278208bece13f52
- Affected versionversion=38760d40ca61b18b2809e9c28df8b3ff9af8a02b <32ee0520159f1e8c2d6597c19690df452c528f30
- Affected versionversion=38760d40ca61b18b2809e9c28df8b3ff9af8a02b <50f2b98dc83de7809a5c5bf0ccf9af2e75c37c13
- Affected versionversion=38760d40ca61b18b2809e9c28df8b3ff9af8a02b <b1d2051373bfc65371ce4ac8911ed984d0178c98
- Affected versionversion=38760d40ca61b18b2809e9c28df8b3ff9af8a02b <d3ff0f98a52f0aafe35aa314d1c442f4318be3db
- Affected versionversion=38760d40ca61b18b2809e9c28df8b3ff9af8a02b <e6cd871627abbb459d0ff6521d6bb9cf9d9f7522
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
No sourced classifications are available.
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