CyberSecBulletin
CVE-2026-64003NVD status: Modified

Linux: Missing Release of Resource after Effective Lifetime

Published Updated By the CyberSecBulletin desk

CVE-2026-64003 is a high-severity missing release of resource after effective lifetime 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 15fb19af49f2073ed77fad16aaabc648b0ca6800, d4dddfecdbb5467bef158d4e1486459808357fef, 475f2b37a78f4c698967a7f14f325f04e24c9175 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.44% 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 15fb19af49f2073ed77fad16aaabc648b0ca6800 or d4dddfecdbb5467bef158d4e1486459808357fef or 475f2b37a78f4c698967a7f14f325f04e24c9175 or c740e13e7fe32d8e4d9a1699f65b8daf6709895a, whichever matches your release line, or a later version.
  2. Update Linux Kernel to 6.6.143 or 6.12.93 or 6.18.35 or 7.0.12, 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
LinuxLinux8b566edbdbfb5cde31a322c57932694ff48125ed up to, but not including, 15fb19af49f2073ed77fad16aaabc648b0ca6800; 8b566edbdbfb5cde31a322c57932694ff48125ed up to, but not including, d4dddfecdbb5467bef158d4e1486459808357fef; 8b566edbdbfb5cde31a322c57932694ff48125ed up to, but not including, 475f2b37a78f4c698967a7f14f325f04e24c9175; 8b566edbdbfb5cde31a322c57932694ff48125ed up to, but not including, c740e13e7fe32d8e4d9a1699f65b8daf6709895a; 8b566edbdbfb5cde31a322c57932694ff48125ed up to, but not including, 7205b58702273baf21d6ba7992e6ba15852325f7; 6.515fb19af49f2073ed77fad16aaabc648b0ca6800, d4dddfecdbb5467bef158d4e1486459808357fef, 475f2b37a78f4c698967a7f14f325f04e24c9175, c740e13e7fe32d8e4d9a1699f65b8daf6709895a, 7205b58702273baf21d6ba7992e6ba15852325f7
LinuxLinux Kernel6.5 up to, but not including, 6.6.143; 6.7 up to, but not including, 6.12.93; 6.13 up to, but not including, 6.18.35; 6.19 up to, but not including, 7.0.12; 7.16.6.143, 6.12.93, 6.18.35, 7.0.12

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: scsi: core: Run queues for all non-SDEV_DEL devices from scsi_run_host_queues While a SCSI host is in a recovery state, scsi_mq_requeue_cmd() will not set the requeue list for a requeued command to be kicked in the future. The expectation is a call to scsi_run_host_queues() will kick all SCSI devices once the recovery state is cleared. However, scsi_run_host_queues() uses shost_for_each_device() which uses scsi_device_get() and so will ignore devices in a partially removed state like SDEV_CANCEL. But these devices may also have requeued requests, leaving their requests stuck from not being kicked and causing the removal process of the device to hang. scsi_run_host_queues() needs to run against more devices than the macro shost_for_each_device() allows. Instead of using the too limiting scsi_device_get() state checks, only ignore devices in SDEV_DEL state or when unable to acquire a reference. Attempt to run the queues for all other devices when scsi_run_host_queues() is called.

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

The underlying weakness: Missing Release of Resource after Effective Lifetime

The product does not release a resource after its effective lifetime has ended, i.e., after the resource is no longer needed.

How developers prevent this class of flaw

  • Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, languages such as Java, Ruby, and Lisp perform automatic garbage collection that releases memory for objects that have been deallocated.
  • It is good practice to be responsible for freeing all resources you allocate and to be consistent with how and where you free resources in a function. If you allocate resources that you intend to free upon completion of the function, you must be sure to free the resources at all exit points for that function including error conditions.

More Missing Release of Resource after Effective Lifetime vulnerabilities (CWE-772)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: none, automatable: yes, technical impact: partial).
  3. Record last changed materially (score, affected products, status or references).

References

Recent Missing Release of Resource after Effective Lifetime vulnerabilities

Spotted an error? Tell us.