Linux: Uncontrolled Resource Consumption
CVE-2024-39479 is a high-severity uncontrolled resource consumption 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 cfa73607eb21a4ce1d6294a2c5733628897b48a2, ce5a22d22db691d14516c3b8fdbf69139eb2ea8f, 5bc9de065b8bb9b8dd8799ecb4592d0403b54281 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.22% 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 cfa73607eb21a4ce1d6294a2c5733628897b48a2 or ce5a22d22db691d14516c3b8fdbf69139eb2ea8f or 5bc9de065b8bb9b8dd8799ecb4592d0403b54281, whichever matches your release line, or a later version.
- Update linux_kernel to cfa73607eb21 or ce5a22d22db6 or 5bc9de065b8b, whichever matches your release line, or a later version.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Linux | Linux | b3b088e28183b84080b7f0a0b8da84ec42b4b0e8 up to, but not including, cfa73607eb21a4ce1d6294a2c5733628897b48a2; b3b088e28183b84080b7f0a0b8da84ec42b4b0e8 up to, but not including, ce5a22d22db691d14516c3b8fdbf69139eb2ea8f; b3b088e28183b84080b7f0a0b8da84ec42b4b0e8 up to, but not including, 5bc9de065b8bb9b8dd8799ecb4592d0403b54281; 6.2 | cfa73607eb21a4ce1d6294a2c5733628897b48a2, ce5a22d22db691d14516c3b8fdbf69139eb2ea8f, 5bc9de065b8bb9b8dd8799ecb4592d0403b54281 |
| Linux | linux_kernel | 1da177e4c3f4 up to, but not including, cfa73607eb21; 1da177e4c3f4 up to, but not including, ce5a22d22db6; 1da177e4c3f4 up to, but not including, 5bc9de065b8b | cfa73607eb21, ce5a22d22db6, 5bc9de065b8b |
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 | NVD |
| CVSS 3.1 | 7.8 | High | CISA (ADP) |
Official description
In the Linux kernel, the following vulnerability has been resolved: drm/i915/hwmon: Get rid of devm When both hwmon and hwmon drvdata (on which hwmon depends) are device managed resources, the expectation, on device unbind, is that hwmon will be released before drvdata. However, in i915 there are two separate code paths, which both release either drvdata or hwmon and either can be released before the other. These code paths (for device unbind) are as follows (see also the bug referenced below): Call Trace: release_nodes+0x11/0x70 devres_release_group+0xb2/0x110 component_unbind_all+0x8d/0xa0 component_del+0xa5/0x140 intel_pxp_tee_component_fini+0x29/0x40 [i915] intel_pxp_fini+0x33/0x80 [i915] i915_driver_remove+0x4c/0x120 [i915] i915_pci_remove+0x19/0x30 [i915] pci_device_remove+0x32/0xa0 device_release_driver_internal+0x19c/0x200 unbind_store+0x9c/0xb0 and Call Trace: release_nodes+0x11/0x70 devres_release_all+0x8a/0xc0 device_unbind_cleanup+0x9/0x70 device_release_driver_internal+0x1c1/0x200 unbind_store+0x9c/0xb0 This means that in i915, if use devm, we cannot gurantee that hwmon will always be released before drvdata. Which means that we have a uaf if hwmon sysfs is accessed when drvdata has been released but hwmon hasn't. The only way out of this seems to be do get rid of devm_ and release/free everything explicitly during device unbind. v2: Change commit message and other minor code changes v3: Cleanup from i915_hwmon_register on error (Armin Wolf) v4: Eliminate potential static analyzer warning (Rodrigo) Eliminate fetch_and_zero (Jani) v5: Restore previous logic for ddat_gt->hwmon_dev error return (Andi)
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Uncontrolled Resource Consumption
The product does not properly control the allocation and maintenance of a limited resource.
How developers prevent this class of flaw
- Ensure that protocols have specific limits of scale placed on them.
- Ensure that all failures in resource allocation place the system into a safe posture.
More Uncontrolled Resource Consumption vulnerabilities (CWE-400)
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
Recent Uncontrolled Resource Consumption vulnerabilities
- 7.5 High severity
- 7.5 High severity
- 7.5 High severity
- 7.5 High severity
- 9.8 Critical severity
- 7.5 High severity
Spotted an error? Tell us.