Local service interruption via nested IRQ unlocking
Published Jun 21, 2024 · Updated May 23, 2026
Improper locking in the Linux kernel allows local users to interrupt service through access to the sw-sync debugfs interface. The sync_print_obj() path calls spin_unlock_irq() while nested inside sync_debugfs_show(), which already manages IRQ state, producing an inconsistent lock state. Exploitation requires local low-privileged access and reaches availability only; no confidentiality or integrity impact is reported.
Summary
What happened
Improper locking in the Linux kernel allows local users to interrupt service through access to the sw-sync debugfs interface. The sync_print_obj() path calls spin_unlock_irq() while nested inside sync_debugfs_show(), which already manages IRQ state, producing an inconsistent lock state. Exploitation requires local low-privileged access and reaches availability only; no confidentiality or integrity impact is reported.
The record
- CVE
- CVE-2024-38780
- Published
- Jun 21, 2024
- Updated
- May 23, 2026
- Vendor
- Siemens
- Product
- SIPLUS S7-1500 CPU 1518-4 PN/DP MFP
- Classifications
- CWE-667, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 21, 2024CVE publishedPublication date reported by the CVE source.
- May 23, 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=V3.1.0 <V3.1.5
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