CVE-2026-80997
Received Received - Intake

Kernel TX Queue Stall Fix in Linux IPA Driver

Vulnerability report for CVE-2026-80997, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-09-11

Last updated on: 2026-09-13

Assigner: kernel.org

Description

In the Linux kernel, the following vulnerability has been resolved: net: ipa: fix stalled modem TX queue after runtime resume ipa_start_xmit() unconditionally stops the TX queue before calling pm_runtime_get(), relying on the wake scheduled by runtime resume (ipa_modem_wake_queue_work()) to restart it once power is ACTIVE. But that work is queued from within the runtime resume callback, before the device's power state reaches RPM_ACTIVE, so it can run while the device is still RPM_RESUMING. The wake is then consumed too early: the transmit it restarts stops the queue again, pm_runtime_get() returns -EINPROGRESS without arranging any future wake (deferred_resume exists only for RPM_SUSPENDING), and after the resume completes nothing is left to wake the queue. Transmit stalls permanently: packets pile up in the qdisc behind the stopped queue, the device runtime-suspends, and since the netdev registers no ndo_tx_timeout the watchdog never fires. Observed on SM7635 (Fairphone 6) as the cellular data path going permanently deaf within hours, RX included, since nothing resumes the suspended endpoints. Close the window by making the wake work wait for the resume to complete (pm_runtime_get_sync()) before waking the queue. Every queue stop is then guaranteed a later wake that happens while power is ACTIVE; a transmit racing a new suspend/resume cycle re-schedules the work. If the device could not be resumed, wake the queue anyway so pending packets are dropped by the transmit path rather than stranded. The STARTED power flag used to narrow this window: a wake running before the transmit path's stop suppressed that stop, but only once, as the flag was cleared by the first stop it absorbed. Removing the flag made a single transmit during an in-flight resume sufficient to strand the queue, which is the form observed. With an accelerated reproducer (autosuspend delay shortened to 5 ms, ~20 packets/s of TX), an unpatched kernel stalled three times in 230 s / 4380 packets; with this patch the same test ran 3601 s / 70298 packets without a stall.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-09-11
Last Modified
2026-09-13
Generated
2026-10-02
AI Q&A
2026-09-12
EPSS Evaluated
2026-10-01
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
linux linux_kernel *

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-UNKNOWN

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability in the Linux kernel causes the modem's TX queue to stall permanently after a runtime resume. The issue occurs because the TX queue is stopped before power is fully restored, but the resume process does not properly restart it. This leads to packets piling up and the device eventually suspending, with no mechanism to recover the queue.

Detection Guidance

This vulnerability affects the Linux kernel's IPA (IP Accelerator) driver, specifically related to modem TX queue stalling after runtime resume. Detection requires checking kernel logs for TX queue stalls or modem-related errors during network activity. Monitor dmesg or journalctl for IPA-related errors or watchdog timeouts.

Impact Analysis

If affected, your device's cellular data connection may stop working after a short period. You might experience loss of mobile data, dropped calls, or inability to send/receive messages. The issue was observed on the Fairphone 6 but could affect other devices using the IPA modem driver.

Compliance Impact

This vulnerability affects compliance with standards like GDPR and HIPAA by potentially causing data transmission failures in systems handling sensitive information. If the TX queue stalls, data packets may not be transmitted, leading to incomplete or delayed data processing, which could violate data integrity and availability requirements under these regulations.

Mitigation Strategies

Apply the kernel patch that fixes the IPA TX queue stall issue. Update to a patched kernel version where pm_runtime_get_sync() is used instead of pm_runtime_get() to ensure proper queue wake handling. If immediate patching is not possible, disable runtime power management for the IPA device as a temporary workaround.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-80997. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart