CyberSecBulletin
CVE-2024-26653NVD status: Analyzed

Linux: Double Free

CVE-2024-26653 is a high-severity double free 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 420babea4f1881a7c4ea22a8e218b8c6895d3f21, 8a9f653cc852677003c23ee8075e3ed8fb4743c9, 7c9631969287a5366bc8e39cd5abff154b35fb80 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 420babea4f1881a7c4ea22a8e218b8c6895d3f21 or 8a9f653cc852677003c23ee8075e3ed8fb4743c9 or 7c9631969287a5366bc8e39cd5abff154b35fb80, whichever matches your release line, or a later version.
  2. Update Linux Kernel to 6.7.12 or 6.8.3, whichever matches your release line, or a later version.

Affected products and versions

VendorProductAffected versionsFixed in
LinuxLinuxacd6199f195d6de814ac4090ce0864a613b1580e up to, but not including, 420babea4f1881a7c4ea22a8e218b8c6895d3f21; acd6199f195d6de814ac4090ce0864a613b1580e up to, but not including, 8a9f653cc852677003c23ee8075e3ed8fb4743c9; acd6199f195d6de814ac4090ce0864a613b1580e up to, but not including, 7c9631969287a5366bc8e39cd5abff154b35fb80; 6.7420babea4f1881a7c4ea22a8e218b8c6895d3f21, 8a9f653cc852677003c23ee8075e3ed8fb4743c9, 7c9631969287a5366bc8e39cd5abff154b35fb80
LinuxLinux Kernel6.7 up to, but not including, 6.7.12; 6.8 up to, but not including, 6.8.3; 6.96.7.12, 6.8.3

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

Official description

In the Linux kernel, the following vulnerability has been resolved: usb: misc: ljca: Fix double free in error handling path When auxiliary_device_add() returns error and then calls auxiliary_device_uninit(), callback function ljca_auxdev_release calls kfree(auxdev->dev.platform_data) to free the parameter data of the function ljca_new_client_device. The callers of ljca_new_client_device shouldn't call kfree() again in the error handling path to free the platform data. Fix this by cleaning up the redundant kfree() in all callers and adding kfree() the passed in platform_data on errors which happen before auxiliary_device_init() succeeds .

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

The underlying weakness: Double Free

The product calls free() twice on the same memory address.

How developers prevent this class of flaw

  • Choose a language that provides automatic memory management.
  • Ensure that each allocation is freed only once. After freeing a chunk, set the pointer to NULL to ensure the pointer cannot be freed again. In complicated error conditions, be sure that clean-up routines respect the state of allocation properly. If the language is object oriented, ensure that object destructors delete each chunk of memory only once.
  • Use a static analysis tool to find double free instances.

More Double Free vulnerabilities (CWE-415)

Timeline

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

References

Recent Double Free vulnerabilities

Spotted an error? Tell us.