← All Advisories
Reported from OT-Advisories.com as of

CVE-2026-80997

Last refreshed2026-10-19

Status: UPDATED  |  Advisory ID: CVE-2026-80997

Key Details

CVECVE-2026-80997
CVSS Score / Version
7.5 (High) / CVSS v3.1
Updated2026-10-19
CVSS Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
CVSS Prose
attack vector is network; attack complexity is low; privileges required is none; user interaction is none; scope is unchanged; confidentiality impact is none; integrity impact is none; availability impact is high.
Affected products
Linux Kernel

Affected Products, Subsystems & Sectors

VendorProductAffected VersionsPatch Status
LinuxLinux Kernel
SubsystemsOT Supporting Infrastructure
SectorsAll Sectors

What to Know

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. (NVD)

What to Do

Monitor Linux's web page for any future patch releases.

References

SourceReference
NVDhttps://nvd.nist.gov/vuln/detail/CVE-2026-80997
CVEhttps://www.cve.org/CVERecord?id=CVE-2026-80997
Report compilation © 2026 OT-Advisories.com  ·  CC BY 4.0  ·  Source materials remain the property of their respective publishers as cited.