CyberSecBulletin
CVE-2026-64148NVD status: Analyzed

Linux: Loop with Unreachable Exit Condition

CVE-2026-64148 is a high-severity loop with unreachable exit condition vulnerability in Linux, with a CVSS 3.1 base score of 7.5 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. The record lists versions 3231aff8ab26111c54e630b1a200fc43a729dd14, 10ae3180095bbe2d378c5b1d6f2f2fd74dda3cc2, 784dd2bdc622ed3cc6ef8e113aa1852e252de36f as the first without the flaw, so updating Linux to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.47% chance of exploitation within 30 days, which is low compared with other CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Update Linux to 3231aff8ab26111c54e630b1a200fc43a729dd14 or 10ae3180095bbe2d378c5b1d6f2f2fd74dda3cc2 or 784dd2bdc622ed3cc6ef8e113aa1852e252de36f or 560d559324169fe0583d54c475b5329550a86f71, whichever matches your release line, or a later version.
  2. Update Linux Kernel to 6.6.142 or 6.12.92 or 6.18.34 or 7.0.11, whichever matches your release line, or a later version.
  3. Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.

Affected products and versions

VendorProductAffected versionsFixed in
LinuxLinux45d76f492938cdc27ddadc16e1e75103f4cfbf56 up to, but not including, 3231aff8ab26111c54e630b1a200fc43a729dd14; 45d76f492938cdc27ddadc16e1e75103f4cfbf56 up to, but not including, 10ae3180095bbe2d378c5b1d6f2f2fd74dda3cc2; 45d76f492938cdc27ddadc16e1e75103f4cfbf56 up to, but not including, 784dd2bdc622ed3cc6ef8e113aa1852e252de36f; 45d76f492938cdc27ddadc16e1e75103f4cfbf56 up to, but not including, 560d559324169fe0583d54c475b5329550a86f71; 45d76f492938cdc27ddadc16e1e75103f4cfbf56 up to, but not including, 0e46b6635b03d29807f810c3b415c4755a3f958d; 6.43231aff8ab26111c54e630b1a200fc43a729dd14, 10ae3180095bbe2d378c5b1d6f2f2fd74dda3cc2, 784dd2bdc622ed3cc6ef8e113aa1852e252de36f, 560d559324169fe0583d54c475b5329550a86f71, 0e46b6635b03d29807f810c3b415c4755a3f958d
LinuxLinux Kernel6.4 up to, but not including, 6.6.142; 6.7 up to, but not including, 6.12.92; 6.13 up to, but not including, 6.18.34; 6.19 up to, but not including, 7.0.11; 7.16.6.142, 6.12.92, 6.18.34, 7.0.11

Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
NetworkCan be exploited remotely over a network, including the internet.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
NoneNo account or login is needed.
User interaction
NoneNo action by a victim is required.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
NoneNo data is disclosed.
Integrity
NoneNothing can be modified.
Availability
HighThe component can be taken down completely.

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H. Scored by CNA.

Official description

In the Linux kernel, the following vulnerability has been resolved: pds_core: fix error handling in pdsc_devcmd_wait Fix two cases where pdsc_devcmd_wait() returns stale success from the completion register instead of an error: 1. FW crash: If firmware stops running, the wait loop breaks early with running=false. The condition "if ((!done || timeout) && running)" is false, so error handling is bypassed and stale status is returned. Check !running first and return -ENXIO. 2. Timeout: If a command times out, err is set to -ETIMEDOUT but then overwritten by pdsc_err_to_errno(status) which reads stale status. Return -ETIMEDOUT immediately after cleaning up. Both errors now propagate to pdsc_devcmd_locked() which queues health_work for recovery.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Loop with Unreachable Exit Condition

The product contains an iteration or loop with an exit condition that cannot be reached, i.e., an infinite loop.

More Loop with Unreachable Exit Condition vulnerabilities (CWE-835)

Timeline

  1. CVE record published.
  2. Record last changed materially (score, affected products, status or references).

References

Recent Loop with Unreachable Exit Condition vulnerabilities

Spotted an error? Tell us.