CyberSecBulletin
CVE-2024-26723NVD status: Analyzed

Linux: Uncontrolled Resource Consumption

Published Updated By the CyberSecBulletin desk

CVE-2024-26723 is a high-severity uncontrolled resource consumption vulnerability in Linux, with a CVSS 3.1 base score of 7.8 out of 10. It can be exploited with local access to the system by an attacker with a low-privileged account, without any action from a user. The record lists versions b9357489c46c7a43999964628db8b47d3a1f8672, 48fae67d837488c87379f0c9f27df7391718477c, 2a492f01228b7d091dfe38974ef40dccf8f9f2f1 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.24% 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 b9357489c46c7a43999964628db8b47d3a1f8672 or 48fae67d837488c87379f0c9f27df7391718477c or 2a492f01228b7d091dfe38974ef40dccf8f9f2f1 or 15faa1f67ab405d47789d4702f587ec7df7ef03e, whichever matches your release line, or a later version.
  2. Update linux_kernel to b9357489c46c or 48fae67d8374 or 2a492f01228b or 15faa1f67ab4, whichever matches your release line, or a later version.

Affected products and versions

VendorProductAffected versionsFixed in
LinuxLinuxcabc9d49333df72fe0f6d58bdcf9057ba341e701 up to, but not including, b9357489c46c7a43999964628db8b47d3a1f8672; cabc9d49333df72fe0f6d58bdcf9057ba341e701 up to, but not including, 48fae67d837488c87379f0c9f27df7391718477c; cabc9d49333df72fe0f6d58bdcf9057ba341e701 up to, but not including, 2a492f01228b7d091dfe38974ef40dccf8f9f2f1; cabc9d49333df72fe0f6d58bdcf9057ba341e701 up to, but not including, 15faa1f67ab405d47789d4702f587ec7df7ef03e; 6.1b9357489c46c7a43999964628db8b47d3a1f8672, 48fae67d837488c87379f0c9f27df7391718477c, 2a492f01228b7d091dfe38974ef40dccf8f9f2f1, 15faa1f67ab405d47789d4702f587ec7df7ef03e
Linuxlinux_kernelcabc9d49333d up to, but not including, b9357489c46c; cabc9d49333d up to, but not including, 48fae67d8374; cabc9d49333d up to, but not including, 2a492f01228b; cabc9d49333d up to, but not including, 15faa1f67ab4; 6.1b9357489c46c, 48fae67d8374, 2a492f01228b, 15faa1f67ab4

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
LocalThe attacker needs local access or must trick a user into running something.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
LowA basic user account is enough.
User interaction
NoneNo action by a victim is required.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
HighAll data handled by the component can be read.
Integrity
HighData or code can be modified at will.
Availability
HighThe component can be taken down completely.

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

Official description

In the Linux kernel, the following vulnerability has been resolved: lan966x: Fix crash when adding interface under a lag There is a crash when adding one of the lan966x interfaces under a lag interface. The issue can be reproduced like this: ip link add name bond0 type bond miimon 100 mode balance-xor ip link set dev eth0 master bond0 The reason is because when adding a interface under the lag it would go through all the ports and try to figure out which other ports are under that lag interface. And the issue is that lan966x can have ports that are NULL pointer as they are not probed. So then iterating over these ports it would just crash as they are NULL pointers. The fix consists in actually checking for NULL pointers before accessing something from the ports. Like we do in other places.

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

The underlying weakness: Uncontrolled Resource Consumption

The product does not properly control the allocation and maintenance of a limited resource.

How developers prevent this class of flaw

  • Ensure that protocols have specific limits of scale placed on them.
  • Ensure that all failures in resource allocation place the system into a safe posture.

More Uncontrolled Resource Consumption vulnerabilities (CWE-400)

Timeline

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

References

Recent Uncontrolled Resource Consumption vulnerabilities

Spotted an error? Tell us.