Answer in brief
CVE-2024-39479 records a Unknown severity vulnerability in drm/i915/hwmon: Get rid of devm. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic), linux/linux_kernel (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic), linux/linux_kernel (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=b3b088e28183b84080b7f0a0b8da84ec42b4b0e8 <cfa73607eb21a4ce1d6294a2c5733628897b48a2 || >=b3b088e28183b84080b7f0a0b8da84ec42b4b0e8 <ce5a22d22db691d14516c3b8fdbf69139eb2ea8f || >=b3b088e28183b84080b7f0a0b8da84ec42b4b0e8 <5bc9de065b8bb9b8dd8799ecb4592d0403b54281 | cfa73607eb21a4ce1d6294a2c5733628897b48a2, ce5a22d22db691d14516c3b8fdbf69139eb2ea8f, 5bc9de065b8bb9b8dd8799ecb4592d0403b54281 |
| Linux/Linuxgeneric | 6.2 | Not reported |
| linux/linux_kernelgeneric | >=1da177e4c3f4 <cfa73607eb21 || >=1da177e4c3f4 <ce5a22d22db6 || >=1da177e4c3f4 <5bc9de065b8b | cfa73607eb21, ce5a22d22db6, 5bc9de065b8b |
Published upstream
Jul 5, 2024
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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)
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2024-39479 records a Unknown severity vulnerability in drm/i915/hwmon: Get rid of devm. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic), linux/linux_kernel (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic), linux/linux_kernel (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=b3b088e28183b84080b7f0a0b8da84ec42b4b0e8 <cfa73607eb21a4ce1d6294a2c5733628897b48a2 || >=b3b088e28183b84080b7f0a0b8da84ec42b4b0e8 <ce5a22d22db691d14516c3b8fdbf69139eb2ea8f || >=b3b088e28183b84080b7f0a0b8da84ec42b4b0e8 <5bc9de065b8bb9b8dd8799ecb4592d0403b54281 | cfa73607eb21a4ce1d6294a2c5733628897b48a2, ce5a22d22db691d14516c3b8fdbf69139eb2ea8f, 5bc9de065b8bb9b8dd8799ecb4592d0403b54281 |
| Linux/Linuxgeneric | 6.2 | Not reported |
| linux/linux_kernelgeneric | >=1da177e4c3f4 <cfa73607eb21 || >=1da177e4c3f4 <ce5a22d22db6 || >=1da177e4c3f4 <5bc9de065b8b | cfa73607eb21, ce5a22d22db6, 5bc9de065b8b |
Published upstream
Jul 5, 2024
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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)
Quoted source text, attributed separately from HOL analysis.