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.
Published: 2026-09-11
Score: 7.5 High
EPSS: < 1% Very Low
KEV: No
Impact: Denial of Service (network connectivity loss)
Action: Patch Kernel
AI Analysis

Impact

The ipa driver in the Linux kernel contains a flaw that can cause the transmit queue to stall during a runtime resume. When a packet transmission initiates, the queue is stopped and a wake work is scheduled before the device reaches an active power state. The work then consumes the wake too early, leaving the queue stopped and queued packets stranded. As a result, the cellular data path becomes permanently deaf, packets pile in the queue, and the device eventually runtime‑suspends without a watchdog timeout. This loss of connectivity manifests as a denial of service to the affected network interface.

Affected Systems

This issue exists in the Linux kernel’s ipa network subsystem, affecting any device that relies on that driver, such as the Fairphone 6’s SM7635 modem. The vulnerability is tied to the kernel’s runtime power management and is present in all current kernels that have not yet applied the corrective commit. Both Linux vendors are listed as affected, so any installation of an unpatched kernel on a Linux host with an ipa‑enabled modem is susceptible.

Risk and Exploitability

The CVSS score of 4.7 places the flaw in the moderate range, and the EPSS score is not available, suggesting a low to moderate exploitation probability. The vulnerability is not listed in the CISA KEV catalog. The flaw does not rely on remote code execution; a local or potentially remote attacker would need to trigger a resume cycle on the device for the issue to manifest. Due to its nature as a kernel bug and the lack of a documented exploit, the risk is moderate but could lead to significant service disruption in production environments.

Generated by OpenCVE AI on September 12, 2026 at 01:53 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Apply the kernel patch that fixes the ipa TX queue stall, such as the commit 30cef9c1229a36a9c80edb29296459849a2fbaa3 or a later stable kernel release that includes the work.
  • If updating the kernel is not immediately possible, restart the modem interface or reboot the system to clear any stalled queues, as the bug results from a transient state.
  • Enable monitoring of network traffic and runtime power state to detect stalled queues early; consider disabling or delaying IPA runtime autosuspend if the device frequently experiences this issue.

Generated by OpenCVE AI on September 12, 2026 at 01:53 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Sun, 13 Sep 2026 06:45:00 +0000

Type Values Removed Values Added
Metrics cvssV3_1

{'score': 4.7, 'vector': 'CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H'}

cvssV3_1

{'score': 7.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H'}


Sat, 12 Sep 2026 00:15:00 +0000

Type Values Removed Values Added
Weaknesses CWE-821
References
Metrics threat_severity

None

cvssV3_1

{'score': 4.7, 'vector': 'CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H'}

threat_severity

Moderate


Fri, 11 Sep 2026 23:45:00 +0000

Type Values Removed Values Added
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.
Title net: ipa: fix stalled modem TX queue after runtime resume
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References

Subscriptions

Linux Linux Kernel
cve-icon MITRE

Status: PUBLISHED

Assigner: Linux

Published:

Updated: 2026-09-13T06:29:00.065Z

Reserved: 2026-08-26T14:34:25.812Z

Link: CVE-2026-80997

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-09-11T20:19:06.740

Modified: 2026-09-13T07:17:06.347

Link: CVE-2026-80997

cve-icon Redhat

Severity : Moderate

Publid Date: 2026-09-11T19:42:52Z

Links: CVE-2026-80997 - Bugzilla

cve-icon OpenCVE Enrichment

Updated: 2026-09-12T09:45:11Z

Weaknesses
  • CWE-821

    Incorrect Synchronization