HIGH Introduced in 6.9
net/ipa WakeQueue Race
CVE-2026-80997
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
KernelScan AI4.7MEDIUM
01Description
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.
02KernelScan AI Analysis
Risk summary
A race condition in the Qualcomm IPA modem driver can permanently stall the cellular data path when a transmit coincides with a runtime power-resume cycle. Any local process sending network traffic through the modem interface can trigger it, and the stall disables both TX and RX with no automatic recovery. Devices without Qualcomm IPA modem hardware are unaffected.
Vulnerability analysis
A race condition in the Qualcomm IPA cellular modem driver can leave the transmit queue permanently stopped. When a transmit happens while the modem is resuming from a low-power state, the scheduled queue wake-up can run before the resume finishes. The restarted transmit then stops the queue again, but because the power-management resume is still in progress, no further wake-up is scheduled. Once the resume completes, nothing remains to restart the queue, so all outbound traffic stalls indefinitely. Without a transmit timeout handler registered, the kernel cannot auto-recover, and the cellular data path becomes completely unresponsive until reboot. The fix ensures the wake-up waits until the resume has fully completed before allowing the queue to restart, so every stop is paired with a valid restart. Any local process that can send network traffic through the cellular modem interface can trigger this, and it only affects devices using a Qualcomm SoC with an integrated IPA modem.
Lifecycle
03Fix Versions
| Branch | Introduced | Fixed in | Patch commit |
|---|---|---|---|
| 7.2 | 6.9 | 7.2.4 | 30cef9c1229a |
| 6.12 | 6.9 | 6.12.109 | 30d5226bac52 |
| mainline | 6.9 | 7.3-rc1 | 3cbfd627ee72 |
| 6.18 | 6.9 | 6.18.50 | 62da38b4b3a0 |
| cip/6.12 | 6.9 | 6.12.111-cip32 | 30d5226bac52 |