Severity by source
AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Race condition requires precise timing during runtime resume (AC:H); network traffic triggers it without privileges, but only on specific Qualcomm IPA hardware; availability-only impact.
Primary rating from Vendor (Linux).
CVSS VectorVendor: Linux
Lifecycle Timeline
6DescriptionCVE.org
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.
AnalysisAI
Race condition in the Linux kernel's IPA (IP Accelerator) network driver permanently stalls the cellular modem TX queue on Qualcomm Snapdragon-based devices after a runtime power management resume cycle. The flaw occurs because the queue-wake work is dispatched during RPM_RESUMING state before RPM_ACTIVE is reached; the wake is consumed prematurely by a racing transmit, pm_runtime_get() returns -EINPROGRESS with no future wake scheduled, and the TX queue never recovers - blocking both outbound packets queued in qdisc and, through suspended endpoints, inbound RX as well. …
Unlock full vulnerability intelligence
- Risk assessment & exploitation conditions
- Attack chain visualization
- Remediation with exact patch versions
- Threat intelligence from 22 sources
- Personal watchlist & email alerts
Free forever · No credit card required
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata
Vulnerability AssessmentAI
| Exploitation | Requires a Linux system with Qualcomm IPA (IP Accelerator) hardware - specifically Snapdragon SoCs where the net/ipa kernel driver is active. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | The supplied CVSS vector AV:N/AC:L/PR:N/UI:N overstates exploitability. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | Full exploit scenario with step-by-step reproduction available after sign-in. |
| Remediation | Update the Linux kernel to a patched stable release: 6.12.109 or later for the 6.12.x series, 6.18.50 or later for the 6.18.x series, or 7.2.4 or later for the 7.2.x series. … Detailed patch versions, workarounds, and compensating controls in full report. |
Recommended ActionAI
Within 24 hours: Identify all Qualcomm Snapdragon devices in your fleet (phones, tablets, IoT) and verify their current kernel versions against vendor advisory baselines. …
Sign in for detailed remediation steps and compensating controls.
Threat intelligence, references, and detailed analysis are available after sign-in.
Share
External POC / Exploit Code
Leaving vuln.today
EUVD-2026-76320
GHSA-4hqp-w86v-96hh