NVD / CVE Program· CNA Linux

CVE-2024-39479: drm/i915/hwmon: Get rid of devm

HighCVSS 7.8 · v3.1—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 31/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 0.22% (FIRST EPSS).
Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
Fixed version: Linux Linux 5bc9de065b8bb9b8dd8799ecb4592d0403b54281, ce5a22d22db691d14516c3b8fdbf69139eb2ea8f, cfa73607eb21a4ce1d6294a2c5733628897b48a2; azl3 kernel 6.6.22.1-2 on Azure Linux 3.0 6.6.35.1-5; azl3 kernel 6.6.35.1-5 on Azure Linux 3.0 -.
Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 5bc9de065b8bb9b8dd8799ecb4592d0403b54281, ce5a22d22db691d14516c3b8fdbf69139eb2ea8f, cfa73607eb21a4ce1d6294a2c5733628897b48a2; azl3 kernel 6.6.22.1-2 on Azure Linux 3.0 6.6.35.1-5; azl3 kernel 6.6.35.1-5 on Azure Linux 3.0 - or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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)

Denial of service

BDU:2024-06085

Published: Jul 5, 2024
Updated: Aug 5, 2026
EPSS: 0.2% · 12th percentile
CWE: CWE-400

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 31 / 40 · 7.8 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.2%

CISA SSVC decision

Exploitation: none
Automatable: no
Technical impact: total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD: 7.8
CNA · Linux: 7.8; agree

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
linux	linux kernel	cpe:2.3:o:linux:linux_kernel

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

Linux Linux
- 6.2affected
- b3b088e28183b84080b7f0a0b8da84ec42b4b0e8 and later · before cfa73607eb21a4ce1d6294a2c5733628897b48a2affected · git
- b3b088e28183b84080b7f0a0b8da84ec42b4b0e8 and later · before ce5a22d22db691d14516c3b8fdbf69139eb2ea8faffected · git
- b3b088e28183b84080b7f0a0b8da84ec42b4b0e8 and later · before 5bc9de065b8bb9b8dd8799ecb4592d0403b54281affected · git
- before 6.2not affected · semver
- 6.6.34 and later · up to and including 6.6.*not affected · semver
- 6.9.5 and later · up to and including 6.9.*not affected · semver
- 6.10 and laternot affected · original_commit_for_fix

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

linux linux kernel6.2 and later · before 6.6.34
linux linux kernel6.7 and later · before 6.9.5

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Ecosystem	Package	Affected range	Fix
Debian:13	linux	before 6.9.7-1	6.9.7-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
90Now
CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV
89Now
CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
85Now

Published before and after this one in the same product

← EarlierCVE-2024-39477Jul 5, 2024 · mm/hugetlb: do not call vma_add_reservation upon ENOMEM
22Monitor
← EarlierCVE-2024-39478Jul 5, 2024 · crypto: starfive - Do not free stack buffer
22Monitor
Later →CVE-2024-39480Jul 5, 2024 · kdb: Fix buffer overflow during tab-complete
31Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
Linux Linux	5bc9de065b8bb9b8dd8799ecb4592d0403b54281	Vendor (CNA)
Linux Linux	ce5a22d22db691d14516c3b8fdbf69139eb2ea8f	Vendor (CNA)
Linux Linux	cfa73607eb21a4ce1d6294a2c5733628897b48a2	Vendor (CNA)
azl3 kernel 6.6.22.1-2 on Azure Linux 3.0	6.6.35.1-5 · CBL-Mariner Releases	Microsoft (MSRC)
azl3 kernel 6.6.35.1-5 on Azure Linux 3.0	- · CBL-Mariner Releases	Microsoft (MSRC)
debian:linux	6.9.7-1 · Debian:13	Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

CVE-2024-3946210 days apartclk: bcm: dvp: Assign ->num before accessing ->hws
39Monitor
CVE-2021-444010 days apartx86/xen: Drop USERGS_SYSRET64 paravirt call
35Monitor
CVE-2021-4731345 days apartcpufreq: CPPC: Fix potential memleak in cppc_cpufreq_cpu_init
33Monitor
CVE-2024-3861616 days apartwifi: carl9170: re-fix fortified-memset warning
32Monitor
CVE-2021-47023128 days apartnet: marvell: prestera: fix port event handling on init
32Monitor
CVE-2024-3838411 days apartblk-cgroup: fix list corruption from reorder of WRITE ->lqueued
31Monitor

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

TR-24-0883 · Jul 8, 2024(Linux Kernel Güncellemesi)

All national notices →

Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · public bounty program.

Technical details

Attack conditions

Someone with local access to the system can trigger it.
A low-privileged account is enough.
No user action is required.
No special conditions are required; it is repeatable.

If successful

Confidentiality: high · data can be read
Integrity: high · data or configuration can be modified
Availability: high · the service can be disrupted

Attack vector: Local
Attack complexity: Low
Privileges required: Low
User interaction: None
Scope: Unchanged
Confidentiality impact: High
Integrity impact: High
Availability impact: High

Weakness class (CWE)

CWE-400 · Uncontrolled Resource Consumption

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

nvd-primary

Root cause

Code that parses nested structures sets no depth or size limit. A small input can turn into a disproportionate processing load.

The bug in code

The whole CWE-400 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1function expand(node) {
2  return node.children.map(expand);
3}

Fixed

1const MAX_DEPTH = 32;
2function expand(node, depth = 0) {
3  if (depth > MAX_DEPTH) throw new Error("too deep");
4  return node.children.map((c) => expand(c, depth + 1));
5}

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Attack patterns (CAPEC)

ATT&CK techniques

Endpoint Denial of ServiceT1499

Change log (1)

Fix✗ → ✓Sep 28, 2026, 10:10 PM UTC

For records you follow, these changes also arrive as notifications. →

References

git.kernel.org/stable/c/5bc9de065b8bb9b8dd8799ecb4592d0403b54281

Show all references (2 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records