Service interruption via uncleared DMA parity status
Published Apr 2, 2024 · Updated May 11, 2026
Denial of service in Linux allows local users to interrupt service when an XGMAC DMA channel reports a Data Path Parity Error. The XGMAC safety interrupt handler checks other safety conditions but fails to check and clear DMA_DPP_Interrupt_Status, so the asserted condition continually retriggers interrupts. Exposure requires a system using the stmmac XGMAC driver and a DMA Data Path Parity Error; the documented consequence is an interrupt storm that consumes service availability.
Summary
What happened
Denial of service in Linux allows local users to interrupt service when an XGMAC DMA channel reports a Data Path Parity Error. The XGMAC safety interrupt handler checks other safety conditions but fails to check and clear DMA_DPP_Interrupt_Status, so the asserted condition continually retriggers interrupts. Exposure requires a system using the stmmac XGMAC driver and a DMA Data Path Parity Error; the documented consequence is an interrupt storm that consumes service availability.
The record
- CVE
- CVE-2024-26684
- Published
- Apr 2, 2024
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 2, 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.4
- Affected versionversion=56e58d6c8a5640eb708e85866e9d243d0357ee54 <2fc45a4631ac7837a5c497cb4f7e2115d950fc37
- Affected versionversion=56e58d6c8a5640eb708e85866e9d243d0357ee54 <3b48c9e258c8691c2f093ee07b1ea3764caaa1b2
- Affected versionversion=56e58d6c8a5640eb708e85866e9d243d0357ee54 <46eba193d04f8bd717e525eb4110f3c46c12aec3
- Affected versionversion=56e58d6c8a5640eb708e85866e9d243d0357ee54 <6609e98ed82966a1b3168c142aca30f8284a7b89
- Affected versionversion=56e58d6c8a5640eb708e85866e9d243d0357ee54 <7e0ff50131e9d1aa507be8e670d38e9300a5f5bf
- Affected versionversion=56e58d6c8a5640eb708e85866e9d243d0357ee54 <e42ff0844fe418c7d03a14f9f90e1b91ba119591
- Affected versionversion=56e58d6c8a5640eb708e85866e9d243d0357ee54 <e9837c83befb5b852fa76425dde98a87b737df00
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