In the Linux kernel, the following vulnerability has been resolved: stmmac: Clear variable when destroying workqueue Currently when suspending… (CVE-2024-26802)
A vulnerability in the Linux kernel's stmmac driver can cause a kernel or module panic due to improper handling of a workqueue variable during driver suspend and resume operations. The issue arises because the workqueue variable is not set to NULL after being destroyed, which can lead to a NULL pointer dereference if the DMA engine initialization fails and the workqueue is skipped. This results in a transmit queue timeout and a 'Reset adapter' error, potentially crashing the kernel.
AI Analysis
Technical Summary
The Linux kernel stmmac driver has a vulnerability where the workqueue variable is not cleared (set to NULL) after destroy_workqueue() is called during driver suspend. If the DMA engine initialization fails during resume, the workqueue may not be initialized but the resume process continues, leading to a scenario where the driver attempts to destroy a non-initialized workqueue. This causes a kernel NULL pointer dereference and panic. The vulnerability is tracked as CVE-2024-26802 and is related to improper handling of workqueue lifecycle in the stmmac driver, causing a denial of service via kernel crash.
Potential Impact
This vulnerability can cause a denial of service by crashing the kernel or module due to a NULL pointer dereference when the stmmac driver attempts to destroy a workqueue that was never initialized. This results in network interface malfunction, transmit queue timeouts, and 'Reset adapter' errors, disrupting normal operation of affected systems.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. The described fix involves setting the workqueue variable to NULL after destroying it to prevent kernel panic. Until an official patch is available, avoid scenarios that trigger the DMA engine initialization failure or suspend/resume cycles on affected drivers if possible.
In the Linux kernel, the following vulnerability has been resolved: stmmac: Clear variable when destroying workqueue Currently when suspending… (CVE-2024-26802)
Description
A vulnerability in the Linux kernel's stmmac driver can cause a kernel or module panic due to improper handling of a workqueue variable during driver suspend and resume operations. The issue arises because the workqueue variable is not set to NULL after being destroyed, which can lead to a NULL pointer dereference if the DMA engine initialization fails and the workqueue is skipped. This results in a transmit queue timeout and a 'Reset adapter' error, potentially crashing the kernel.
CVSS v3.1
Score 5.5medium
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The Linux kernel stmmac driver has a vulnerability where the workqueue variable is not cleared (set to NULL) after destroy_workqueue() is called during driver suspend. If the DMA engine initialization fails during resume, the workqueue may not be initialized but the resume process continues, leading to a scenario where the driver attempts to destroy a non-initialized workqueue. This causes a kernel NULL pointer dereference and panic. The vulnerability is tracked as CVE-2024-26802 and is related to improper handling of workqueue lifecycle in the stmmac driver, causing a denial of service via kernel crash.
Potential Impact
This vulnerability can cause a denial of service by crashing the kernel or module due to a NULL pointer dereference when the stmmac driver attempts to destroy a workqueue that was never initialized. This results in network interface malfunction, transmit queue timeouts, and 'Reset adapter' errors, disrupting normal operation of affected systems.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. The described fix involves setting the workqueue variable to NULL after destroying it to prevent kernel panic. Until an official patch is available, avoid scenarios that trigger the DMA engine initialization failure or suspend/resume cycles on affected drivers if possible.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-r7p6-cff4-g6q4
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2024-26802"]
- Ecosystems
- []
- Database Specific Severity
- MODERATE
- Cvss Version
- 3.1
Threat ID: 6a71feebbf8831d539ff1300
Added to database: 08/04/2026, 15:02:03 UTC
Last enriched: 08/04/2026, 15:20:09 UTC
Last updated: 08/04/2026, 15:21:00 UTC
Views: 4
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.