VDB

CVE-2026-80997

CVE-2026-80997 PUBLISHED CVSS 7.5 HIGH

net: ipa: fix stalled modem TX queue after runtime resume

Reported by linux · Published September 11, 2026

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.

EPSS 0.61% · 50.2th percentile

Risk scores

CVSS 3.1
7.5
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS Score
0.61%
50.2th percentile

Affected products

VendorProductVersions
LinuxLinux688de12f080f10dff8f3ddc80103e432ad8deb0b, 688de12f080f10dff8f3ddc80103e432ad8deb0b, 688de12f080f10dff8f3ddc80103e432ad8deb0b
LinuxLinux6.9, 0, 6.12.109
linuxlinux_kernel6.9, 6.9, 6.9
LinuxLinux688de12f080f10dff8f3ddc80103e432ad8deb0b, 688de12f080f10dff8f3ddc80103e432ad8deb0b, 688de12f080f10dff8f3ddc80103e432ad8deb0b

Timeline

  • Sep 11, 2026 CVE Published
  • Sep 12, 2026 EPSS Score (29 in total, the first dated here)
  • Sep 12, 2026 Coalition ESS Score
  • Oct 19, 2026 CVE Updated

Query this with the API

The same record, from the CLI:

vulnetix vdb vuln CVE-2026-80997
vulnetix vdb fixes CVE-2026-80997

Or with curl, using the org id and key from your account page:

curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
  "https://api.vdb.vulnetix.com/v2/vuln/CVE-2026-80997/fixes/registry"

The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart

References

Look up in the Resolve Platform →
$ Lookup Community · 50/day Open Lookup ›