Linux: Use After Free
CVE-2024-56602 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 1d5fe782c0ff068d80933f9cfd0fd39d5434bbc9, 14959fd7538b3be6d7617d9e60e404d6a8d4fd1f, 2b46994a6e76c8cc5556772932b9b60d03a55cd8 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 1d5fe782c0ff068d80933f9cfd0fd39d5434bbc9 or 14959fd7538b3be6d7617d9e60e404d6a8d4fd1f or 2b46994a6e76c8cc5556772932b9b60d03a55cd8 or e8bd6c5f5dc2234b4ea714380aedeea12a781754, whichever matches your release line, or a later version.
- Update Linux Kernel to 5.4.287 or 5.10.231 or 5.15.174 or 6.1.120, whichever matches your release line, or a later version.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Linux | Linux | 9ec7671603573ede31207eb5b0b3e1aa211b2854 up to, but not including, 1d5fe782c0ff068d80933f9cfd0fd39d5434bbc9; 9ec7671603573ede31207eb5b0b3e1aa211b2854 up to, but not including, 14959fd7538b3be6d7617d9e60e404d6a8d4fd1f; 9ec7671603573ede31207eb5b0b3e1aa211b2854 up to, but not including, 2b46994a6e76c8cc5556772932b9b60d03a55cd8; 9ec7671603573ede31207eb5b0b3e1aa211b2854 up to, but not including, e8bd6c5f5dc2234b4ea714380aedeea12a781754; 9ec7671603573ede31207eb5b0b3e1aa211b2854 up to, but not including, b4982fbf13042e3bb33e04eddfea8b1506b5ea65; 9ec7671603573ede31207eb5b0b3e1aa211b2854 up to, but not including, 03caa9bfb9fde97fb53d33decd7364514e6825cb; 9ec7671603573ede31207eb5b0b3e1aa211b2854 up to, but not including, b4fcd63f6ef79c73cafae8cf4a114def5fc3d80d; 2.6.31 | 1d5fe782c0ff068d80933f9cfd0fd39d5434bbc9, 14959fd7538b3be6d7617d9e60e404d6a8d4fd1f, 2b46994a6e76c8cc5556772932b9b60d03a55cd8, e8bd6c5f5dc2234b4ea714380aedeea12a781754, b4982fbf13042e3bb33e04eddfea8b1506b5ea65, 03caa9bfb9fde97fb53d33decd7364514e6825cb |
| Linux | Linux Kernel | before 5.4.287; 5.5 up to, but not including, 5.10.231; 5.11 up to, but not including, 5.15.174; 5.16 up to, but not including, 6.1.120; 6.2 up to, but not including, 6.6.66; 6.7 up to, but not including, 6.12.5 | 5.4.287, 5.10.231, 5.15.174, 6.1.120, 6.6.66, 6.12.5 |
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 |
| CVSS 3.1 | 7.8 | High | CISA (ADP) |
Official description
In the Linux kernel, the following vulnerability has been resolved: net: ieee802154: do not leave a dangling sk pointer in ieee802154_create() sock_init_data() attaches the allocated sk object to the provided sock object. If ieee802154_create() fails later, the allocated sk object is freed, but the dangling pointer remains in the provided sock object, which may allow use-after-free. Clear the sk pointer in the sock object on error.
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.
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Patches and release notes
- git.kernel.org/stable/c/03caa9bfb9fde97fb53d33decd7364514e6825cb
- git.kernel.org/stable/c/14959fd7538b3be6d7617d9e60e404d6a8d4fd1f
- git.kernel.org/stable/c/1d5fe782c0ff068d80933f9cfd0fd39d5434bbc9
- git.kernel.org/stable/c/2b46994a6e76c8cc5556772932b9b60d03a55cd8
- git.kernel.org/stable/c/b4982fbf13042e3bb33e04eddfea8b1506b5ea65
- git.kernel.org/stable/c/b4fcd63f6ef79c73cafae8cf4a114def5fc3d80d
- git.kernel.org/stable/c/e8bd6c5f5dc2234b4ea714380aedeea12a781754
Other references
Recent Use After Free vulnerabilities
- 7.8 High severity
- 7.0 High severity
- 7.8 High severity
- 7.8 High severity
- 7.8 High severity
- 7.8 High severity
Spotted an error? Tell us.