Go to homepageCyberStrike

Menu

Star on GitHub · 3.2k
Sign inDownload

CVE-2024-39479

7.8 · HIGH

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 ex…

Published Jul 5, 2024CWE-400EPSS 0.22%

Overview

CVE-2024-39479 is a high-severity vulnerability. It was published on July 5, 2024 and has a CVSS 3.1 base score of 7.8 (HIGH).

This vulnerability has a CVSS 3.1 base score of 7.8, rated HIGH. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

Technical 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_interna

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

References

Refgit.kernel.org/stable/c/5bc9de065b8bb9b8dd8799ecb4592d0403b54281Refgit.kernel.org/stable/c/ce5a22d22db691d14516c3b8fdbf69139eb2ea8fRefgit.kernel.org/stable/c/cfa73607eb21a4ce1d6294a2c5733628897b48a2Refgit.kernel.org/stable/c/5bc9de065b8bb9b8dd8799ecb4592d0403b54281Refgit.kernel.org/stable/c/ce5a22d22db691d14516c3b8fdbf69139eb2ea8fRefgit.kernel.org/stable/c/cfa73607eb21a4ce1d6294a2c5733628897b48a2

How CyberStrike helps

Frequently asked questions

What is CVE-2024-39479?

CVE-2024-39479 is a high-severity vulnerability. It was published on July 5, 2024 and has a CVSS 3.1 base score of 7.8 (HIGH).

How severe is CVE-2024-39479?

This vulnerability has a CVSS 3.1 base score of 7.8, rated HIGH. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

How do I fix or remediate CVE-2024-39479?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2024-39479?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2024-39479 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related HIGH CVEs from 2024

View all
Browse by year2026202520242023202220212020201920182017201620152014201320122011201020092008200720062005200420032002200120001999