Service interruption via uncleared UART timeout interrupts
Published Jul 29, 2024 · Updated May 23, 2026
Denial of service in the Linux 8250 OMAP serial driver allows local users to cause an interrupt storm via a UART timeout. On affected K3 SoCs, RHR, MSR, or LSR register reads can spuriously assert a receive-timeout interrupt, while omap8250_irq lacks the erratum sequence that raises the timeout counters, changes timeout mode, and reads IIR to clear it. Reachability requires a TI K3 processor using the affected OMAP UART path; an uncleared interrupt can monopolize processing and interrupt service.
Summary
What happened
Denial of service in the Linux 8250 OMAP serial driver allows local users to cause an interrupt storm via a UART timeout. On affected K3 SoCs, RHR, MSR, or LSR register reads can spuriously assert a receive-timeout interrupt, while omap8250_irq lacks the erratum sequence that raises the timeout counters, changes timeout mode, and reads IIR to clear it. Reachability requires a TI K3 processor using the affected OMAP UART path; an uncleared interrupt can monopolize processing and interrupt service.
The record
- CVE
- CVE-2024-42095
- Published
- Jul 29, 2024
- Updated
- May 23, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 29, 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=5.10.50 <5.10.221
- Affected versionversion=5.12.17 <5.13
- Affected versionversion=5.13.2 <5.14
- Affected versionversion=5.14
- Affected versionversion=9443acbd251f366804b20a27be72ba67df532cb1 <cb879300669881970eabebe64bd509dbbe42b9de
- Affected versionversion=b67e830d38fa9335d927fe67e812e3ed81b4689c <6270051f656004ca5cde644c73cb1fa4d718792e
- Affected versionversion=b67e830d38fa9335d927fe67e812e3ed81b4689c <87257a28271c828a98f762bf2dd803c1793d2b5b
- Affected versionversion=b67e830d38fa9335d927fe67e812e3ed81b4689c <98840e410d53329f5331ecdce095e740791963d0
- Affected versionversion=b67e830d38fa9335d927fe67e812e3ed81b4689c <9d141c1e615795eeb93cd35501ad144ee997a826
- Affected versionversion=b67e830d38fa9335d927fe67e812e3ed81b4689c <e67d7f38008e56fb691b6a72cadf16c107c2f48b
- Affected versionversion=bf1bcca53c35a40976afbdd40aaea9424154f57b
- Affected versionversion=ed87ec89b7f6071de06380a0216e6aa420eb9742
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