RT kernel interruption via sleeping atomic-context lock
Published Jul 12, 2024 · Updated Aug 5, 2026
Improper locking in Linux 2.6.31 and later allows local users to interrupt RT kernels through drop-monitor packet tracing. The trace_drop_common function acquires a sleeping spin_lock while preemption is disabled, performing an operation that is invalid in atomic context on RT builds. The condition requires an RT configuration and execution of the packet-drop tracing path; its bounded consequence is an invalid-context failure and service interruption.
Summary
What happened
Improper locking in Linux 2.6.31 and later allows local users to interrupt RT kernels through drop-monitor packet tracing. The trace_drop_common function acquires a sleeping spin_lock while preemption is disabled, performing an operation that is invalid in atomic context on RT builds. The condition requires an RT configuration and execution of the packet-drop tracing path; its bounded consequence is an invalid-context failure and service interruption.
The record
- CVE
- CVE-2024-40980
- Published
- Jul 12, 2024
- Updated
- Aug 5, 2026
- Vendor
- Siemens
- Product
- SIMATIC S7-1500 TM MFP - GNU/Linux subsystem
- Classifications
- CWE-20, CWE-667
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 12, 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=0 <*
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.
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