Host panic via static-call allocation warning
Published Oct 21, 2024 · Updated May 11, 2026
Denial of service in affected Linux kernel releases from 5.10 allows local users to crash hosts during static-call module loading. static_call_module_notify() invokes WARN_ON when __static_call_add_module() cannot allocate memory, despite propagating the recoverable error to userspace. Exploitation requires low-privileged local access, a module operation that reaches the allocation failure, and panic_on_warn enabled; the bounded consequence is a host panic.
Summary
What happened
Denial of service in affected Linux kernel releases from 5.10 allows local users to crash hosts during static-call module loading. static_call_module_notify() invokes WARN_ON when __static_call_add_module() cannot allocate memory, despite propagating the recoverable error to userspace. Exploitation requires low-privileged local access, a module operation that reaches the allocation failure, and panic_on_warn enabled; the bounded consequence is a host panic.
The record
- CVE
- CVE-2024-49954
- Published
- Oct 21, 2024
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 21, 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=5.10
- Affected versionversion=9183c3f9ed710a8edf1a61e8a96d497258d26e08 <85a104aaef1f56623acc10ba4c42d5f046ba65b7
- Affected versionversion=9183c3f9ed710a8edf1a61e8a96d497258d26e08 <b83bef74c121a3311240fc4002d23486b85355e4
- Affected versionversion=9183c3f9ed710a8edf1a61e8a96d497258d26e08 <bc9356513d56b688775497b7ac6f2b967f46a80c
- Affected versionversion=9183c3f9ed710a8edf1a61e8a96d497258d26e08 <e67534bd31d79952b50e791e92adf0b3e6c13b8c
- Affected versionversion=9183c3f9ed710a8edf1a61e8a96d497258d26e08 <ea2cdf4da093d0482f0ef36ba971e2e0c7673425
- Affected versionversion=9183c3f9ed710a8edf1a61e8a96d497258d26e08 <fe513c2ef0a172a58f158e2e70465c4317f0a9a2
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