Linux: Double Free
CVE-2024-26930 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 f14cee7a882cb79528f17a2335f53e9fd1848467, b7deb675d674f44e0ddbab87fee8f9f098925e73, 825d63164a2e6bacb059a9afb5605425b485413f 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.23% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update Linux to f14cee7a882cb79528f17a2335f53e9fd1848467 or b7deb675d674f44e0ddbab87fee8f9f098925e73 or 825d63164a2e6bacb059a9afb5605425b485413f or e288285d47784fdcf7c81be56df7d65c6f10c58b, whichever matches your release line, or a later version.
- Update Linux Kernel to 6.6.24 or 6.7.12 or 6.8.3, whichever matches your release line, or a later version.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Linux | Linux | 430eef03a763e5e76a371ba6d02779ae4a64b6ea up to, but not including, f14cee7a882cb79528f17a2335f53e9fd1848467; 430eef03a763e5e76a371ba6d02779ae4a64b6ea up to, but not including, b7deb675d674f44e0ddbab87fee8f9f098925e73; 430eef03a763e5e76a371ba6d02779ae4a64b6ea up to, but not including, 825d63164a2e6bacb059a9afb5605425b485413f; 430eef03a763e5e76a371ba6d02779ae4a64b6ea up to, but not including, e288285d47784fdcf7c81be56df7d65c6f10c58b; 6.3 | f14cee7a882cb79528f17a2335f53e9fd1848467, b7deb675d674f44e0ddbab87fee8f9f098925e73, 825d63164a2e6bacb059a9afb5605425b485413f, e288285d47784fdcf7c81be56df7d65c6f10c58b |
| Linux | Linux Kernel | 6.3 up to, but not including, 6.6.24; 6.7 up to, but not including, 6.7.12; 6.8 up to, but not including, 6.8.3; 6.9 | 6.6.24, 6.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.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 7.0 | High | CNA |
| CVSS 3.1 | 7.8 | High | NVD |
Official description
In the Linux kernel, the following vulnerability has been resolved: scsi: qla2xxx: Fix double free of the ha->vp_map pointer Coverity scan reported potential risk of double free of the pointer ha->vp_map. ha->vp_map was freed in qla2x00_mem_alloc(), and again freed in function qla2x00_mem_free(ha). Assign NULL to vp_map and kfree take care of NULL.
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.
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: partial).
- Record last changed materially (score, affected products, status or references).
References
Patches and release notes
Recent Double Free vulnerabilities
- 7.8 High severity
- 7.8 High severity
- 7.8 High severity
- 8.2 High severity
- 7.8 High severity
- 7.8 High severity
Spotted an error? Tell us.