Linux: Use After Free
CVE-2024-42280 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 70db2c84631f50e02e6b32b543700699dd395803, d3e4d4a98c5629ccdcb762a0ff6c82ba9738a0c3, 9460ac3dd1ae033bc2b021a458fb535a0c36ddb2 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.
High severity with no evidence of exploitation so far.
What to do
- Update Linux to 70db2c84631f50e02e6b32b543700699dd395803 or d3e4d4a98c5629ccdcb762a0ff6c82ba9738a0c3 or 9460ac3dd1ae033bc2b021a458fb535a0c36ddb2 or 8f4030277dfb9dbe04fd78566b19931097c9d629, whichever matches your release line, or a later version.
- Update Linux Kernel to 4.19.320 or 5.4.282 or 5.10.224 or 5.15.165, whichever matches your release line, or a later version.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Linux | Linux | af69fb3a8ffa37e986db00ed93099dc44babeef4 up to, but not including, 70db2c84631f50e02e6b32b543700699dd395803; af69fb3a8ffa37e986db00ed93099dc44babeef4 up to, but not including, d3e4d4a98c5629ccdcb762a0ff6c82ba9738a0c3; af69fb3a8ffa37e986db00ed93099dc44babeef4 up to, but not including, 9460ac3dd1ae033bc2b021a458fb535a0c36ddb2; af69fb3a8ffa37e986db00ed93099dc44babeef4 up to, but not including, 8f4030277dfb9dbe04fd78566b19931097c9d629; af69fb3a8ffa37e986db00ed93099dc44babeef4 up to, but not including, 4d8b642985ae24f4b3656438eb8489834a17bb80; af69fb3a8ffa37e986db00ed93099dc44babeef4 up to, but not including, ddc79556641ee070d36be0de4a1f0a16a71f1fc7; af69fb3a8ffa37e986db00ed93099dc44babeef4 up to, but not including, 7e4a539bca7d8d20f2c5d93c18cce8ef77cd78e0; af69fb3a8ffa37e986db00ed93099dc44babeef4 up to, but not including, 61ab751451f5ebd0b98e02276a44e23a10110402; and 1 more ranges | 70db2c84631f50e02e6b32b543700699dd395803, d3e4d4a98c5629ccdcb762a0ff6c82ba9738a0c3, 9460ac3dd1ae033bc2b021a458fb535a0c36ddb2, 8f4030277dfb9dbe04fd78566b19931097c9d629, 4d8b642985ae24f4b3656438eb8489834a17bb80, ddc79556641ee070d36be0de4a1f0a16a71f1fc7 |
| Linux | Linux Kernel | 2.6.27 up to, but not including, 4.19.320; 4.20 up to, but not including, 5.4.282; 5.5 up to, but not including, 5.10.224; 5.11 up to, but not including, 5.15.165; 5.16 up to, but not including, 6.1.103; 6.2 up to, but not including, 6.6.44; 6.7 up to, but not including, 6.10.3 | 4.19.320, 5.4.282, 5.10.224, 5.15.165, 6.1.103, 6.6.44 |
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.8 | High | CNA |
| CVSS 3.1 | 7.8 | High | NVD |
Official description
In the Linux kernel, the following vulnerability has been resolved: mISDN: Fix a use after free in hfcmulti_tx() Don't dereference *sp after calling dev_kfree_skb(*sp).
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: partial).
- Record last changed materially (score, affected products, status or references).
References
Patches and release notes
- git.kernel.org/stable/c/4d8b642985ae24f4b3656438eb8489834a17bb80
- git.kernel.org/stable/c/61ab751451f5ebd0b98e02276a44e23a10110402
- git.kernel.org/stable/c/70db2c84631f50e02e6b32b543700699dd395803
- git.kernel.org/stable/c/7e4a539bca7d8d20f2c5d93c18cce8ef77cd78e0
- git.kernel.org/stable/c/8f4030277dfb9dbe04fd78566b19931097c9d629
- git.kernel.org/stable/c/9460ac3dd1ae033bc2b021a458fb535a0c36ddb2
- git.kernel.org/stable/c/d3e4d4a98c5629ccdcb762a0ff6c82ba9738a0c3
- git.kernel.org/stable/c/ddc79556641ee070d36be0de4a1f0a16a71f1fc7
Other references
Recent Use After Free vulnerabilities
- 7.8 High severity
- 7.8 High severity
- 7.8 High severity
- 7.8 High severity
- 7.8 High severity
- 7.8 High severity
Spotted an error? Tell us.