CyberSecBulletin
CVE-2024-58002NVD status: Modified

Linux: Use After Free

CVE-2024-58002 is a high-severity use after 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 2a29413ace64627e178fd422dd8a5d95219a2c0b, 653993f46861f2971e95e9a0e36a34b49dec542c, 117f7a2975baa4b7d702d3f4830d5a4ebd0c6d50 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.26% 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 2a29413ace64627e178fd422dd8a5d95219a2c0b or 653993f46861f2971e95e9a0e36a34b49dec542c or 117f7a2975baa4b7d702d3f4830d5a4ebd0c6d50 or ac18d781466252cd35a3e311e0a4b264260fd927, whichever matches your release line, or a later version.
  2. Update Linux Kernel to 6.6.80 or 6.12.14 or 6.13.3, whichever matches your release line, or a later version.

Affected products and versions

VendorProductAffected versionsFixed in
LinuxLinuxe5225c820c057537dc780244760e2e24c7d27366 up to, but not including, 2a29413ace64627e178fd422dd8a5d95219a2c0b; e5225c820c057537dc780244760e2e24c7d27366 up to, but not including, 653993f46861f2971e95e9a0e36a34b49dec542c; e5225c820c057537dc780244760e2e24c7d27366 up to, but not including, 117f7a2975baa4b7d702d3f4830d5a4ebd0c6d50; e5225c820c057537dc780244760e2e24c7d27366 up to, but not including, ac18d781466252cd35a3e311e0a4b264260fd927; e5225c820c057537dc780244760e2e24c7d27366 up to, but not including, 4dbaa738c583a0e947803c69e8996e88cf98d971; e5225c820c057537dc780244760e2e24c7d27366 up to, but not including, 438bda062b2c40ddd7df23b932e29ffe0a448cac; e5225c820c057537dc780244760e2e24c7d27366 up to, but not including, 9edc7d25f7e49c33a1ce7a5ffadea2222065516c; e5225c820c057537dc780244760e2e24c7d27366 up to, but not including, 221cd51efe4565501a3dbf04cc011b537dcce7fb; and 1 more ranges2a29413ace64627e178fd422dd8a5d95219a2c0b, 653993f46861f2971e95e9a0e36a34b49dec542c, 117f7a2975baa4b7d702d3f4830d5a4ebd0c6d50, ac18d781466252cd35a3e311e0a4b264260fd927, 4dbaa738c583a0e947803c69e8996e88cf98d971, 438bda062b2c40ddd7df23b932e29ffe0a448cac
SiemensSIMATIC S7-1500 TM MFP - GNU/Linux subsystemall versionsNot stated
LinuxLinux Kernel4.19 up to, but not including, 6.6.80; 6.7 up to, but not including, 6.12.14; 6.13 up to, but not including, 6.13.36.6.80, 6.12.14, 6.13.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.

Scoring systemScoreSeverityScored by
CVSS 3.17.8HighCNA
CVSS 3.17.8HighNVD

Official description

In the Linux kernel, the following vulnerability has been resolved: media: uvcvideo: Remove dangling pointers When an async control is written, we copy a pointer to the file handle that started the operation. That pointer will be used when the device is done. Which could be anytime in the future. If the user closes that file descriptor, its structure will be freed, and there will be one dangling pointer per pending async control, that the driver will try to use. Clean all the dangling pointers during release(). To avoid adding a performance penalty in the most common case (no async operation), a counter has been introduced with some logic to make sure that it is properly handled.

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

The underlying weakness: Use After Free

The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory belongs to the code that operates on the new pointer.

How developers prevent this class of flaw

  • Choose a language that provides automatic memory management.
  • When freeing pointers, be sure to set them to NULL once they are freed. However, the utilization of multiple or complex data structures may lower the usefulness of this strategy.

More Use After Free vulnerabilities (CWE-416)

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 Use After Free vulnerabilities

Spotted an error? Tell us.