In the Linux kernel, the following vulnerability has been resolved: net: ipa: fix stalled modem TX queue after runtime resume ipa_start_xmit()… (CVE-2026-80997)
A vulnerability in the Linux kernel's IPA network driver caused the modem transmit (TX) queue to stall permanently after a runtime resume operation. This issue occurs because the TX queue stop and wake sequence is misaligned with the device's power state transitions, leading to a transmit queue that never restarts. The problem was observed on specific hardware (SM7635/Fairphone 6) where cellular data transmission and reception would cease after hours of operation. The fix ensures the wake work waits for the device to reach an active power state before restarting the queue, preventing permanent stalls.
AI Analysis
Technical Summary
The Linux kernel IPA network driver had a flaw where ipa_start_xmit() stopped the TX queue before calling pm_runtime_get(), expecting a wake scheduled by runtime resume to restart it. However, the wake work was queued before the device reached the RPM_ACTIVE power state, causing the wake to be consumed too early and the TX queue to stall permanently. This led to packets piling up and the device runtime suspending without recovery, as no transmit timeout handler was registered. The patch changes the wake work to wait for pm_runtime_get_sync() to complete, ensuring the queue restarts only after the device is fully resumed, preventing transmit stalls.
Potential Impact
The vulnerability causes the modem's transmit queue to stall permanently after a runtime resume, effectively disabling cellular data transmission and reception on affected devices. This results in a loss of network connectivity until the device is rebooted or the issue is otherwise resolved. The issue was specifically observed on the SM7635 platform (Fairphone 6). There are no known exploits in the wild.
Mitigation Recommendations
A patch has been applied to the Linux kernel to fix this issue by making the wake work wait for the device to fully resume before restarting the TX queue. Users and administrators should update to a kernel version that includes this fix once available. Since this is a kernel-level issue, applying the official kernel update is the recommended remediation. No other mitigations are indicated.
In the Linux kernel, the following vulnerability has been resolved: net: ipa: fix stalled modem TX queue after runtime resume ipa_start_xmit()… (CVE-2026-80997)
Description
A vulnerability in the Linux kernel's IPA network driver caused the modem transmit (TX) queue to stall permanently after a runtime resume operation. This issue occurs because the TX queue stop and wake sequence is misaligned with the device's power state transitions, leading to a transmit queue that never restarts. The problem was observed on specific hardware (SM7635/Fairphone 6) where cellular data transmission and reception would cease after hours of operation. The fix ensures the wake work waits for the device to reach an active power state before restarting the queue, preventing permanent stalls.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The Linux kernel IPA network driver had a flaw where ipa_start_xmit() stopped the TX queue before calling pm_runtime_get(), expecting a wake scheduled by runtime resume to restart it. However, the wake work was queued before the device reached the RPM_ACTIVE power state, causing the wake to be consumed too early and the TX queue to stall permanently. This led to packets piling up and the device runtime suspending without recovery, as no transmit timeout handler was registered. The patch changes the wake work to wait for pm_runtime_get_sync() to complete, ensuring the queue restarts only after the device is fully resumed, preventing transmit stalls.
Potential Impact
The vulnerability causes the modem's transmit queue to stall permanently after a runtime resume, effectively disabling cellular data transmission and reception on affected devices. This results in a loss of network connectivity until the device is rebooted or the issue is otherwise resolved. The issue was specifically observed on the SM7635 platform (Fairphone 6). There are no known exploits in the wild.
Mitigation Recommendations
A patch has been applied to the Linux kernel to fix this issue by making the wake work wait for the device to fully resume before restarting the TX queue. Users and administrators should update to a kernel version that includes this fix once available. Since this is a kernel-level issue, applying the official kernel update is the recommended remediation. No other mitigations are indicated.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-4hqp-w86v-96hh
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-80997"]
Threat ID: 6aa4a02b55bf5e2cf5a86b47
Added to database: 09/12/2026, 00:43:23 UTC
Last enriched: 09/12/2026, 01:22:13 UTC
Last updated: 09/12/2026, 01:22:13 UTC
Views: 2
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.