Answer in brief
CVE-2024-39494 records a Unknown severity vulnerability in ima: Fix use-after-free on a dentry's dname.name. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
Answer in brief
CVE-2024-39494 records a Unknown severity vulnerability in ima: Fix use-after-free on a dentry's dname.name. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (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). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=2fe5d6def1672ae6635dd71867bf36dcfaa7434b <480afcbeb7aaaa22677d3dd48ec590b441eaac1a || >=2fe5d6def1672ae6635dd71867bf36dcfaa7434b <edf287bc610b18d7a9c0c0c1cb2e97b9348c71bb || >=2fe5d6def1672ae6635dd71867bf36dcfaa7434b <0b31e28fbd773aefb6164687e0767319b8199829 || >=2fe5d6def1672ae6635dd71867bf36dcfaa7434b <7fb374981e31c193b1152ed8d3b0a95b671330d4 || >=2fe5d6def1672ae6635dd71867bf36dcfaa7434b <dd431c3ac1fc34a9268580dd59ad3e3c76b32a8c || >=2fe5d6def1672ae6635dd71867bf36dcfaa7434b <a78a6f0da57d058e2009e9958fdcef66f165208c || >=2fe5d6def1672ae6635dd71867bf36dcfaa7434b <be84f32bb2c981ca670922e047cdde1488b233de | 480afcbeb7aaaa22677d3dd48ec590b441eaac1a, edf287bc610b18d7a9c0c0c1cb2e97b9348c71bb, 0b31e28fbd773aefb6164687e0767319b8199829, 7fb374981e31c193b1152ed8d3b0a95b671330d4, dd431c3ac1fc34a9268580dd59ad3e3c76b32a8c, a78a6f0da57d058e2009e9958fdcef66f165208c, be84f32bb2c981ca670922e047cdde1488b233de |
| Linux/Linuxgeneric | 3.7 | Not reported |
Published upstream
Jul 12, 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: ima: Fix use-after-free on a dentry's dname.name ->d_name.name can change on rename and the earlier value can be freed; there are conditions sufficient to stabilize it (->d_lock on dentry, ->d_lock on its parent, ->i_rwsem exclusive on the parent's inode, rename_lock), but none of those are met at any of the sites. Take a stable snapshot of the name instead.
Quoted source text, attributed separately from HOL analysis.
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). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=2fe5d6def1672ae6635dd71867bf36dcfaa7434b <480afcbeb7aaaa22677d3dd48ec590b441eaac1a || >=2fe5d6def1672ae6635dd71867bf36dcfaa7434b <edf287bc610b18d7a9c0c0c1cb2e97b9348c71bb || >=2fe5d6def1672ae6635dd71867bf36dcfaa7434b <0b31e28fbd773aefb6164687e0767319b8199829 || >=2fe5d6def1672ae6635dd71867bf36dcfaa7434b <7fb374981e31c193b1152ed8d3b0a95b671330d4 || >=2fe5d6def1672ae6635dd71867bf36dcfaa7434b <dd431c3ac1fc34a9268580dd59ad3e3c76b32a8c || >=2fe5d6def1672ae6635dd71867bf36dcfaa7434b <a78a6f0da57d058e2009e9958fdcef66f165208c || >=2fe5d6def1672ae6635dd71867bf36dcfaa7434b <be84f32bb2c981ca670922e047cdde1488b233de | 480afcbeb7aaaa22677d3dd48ec590b441eaac1a, edf287bc610b18d7a9c0c0c1cb2e97b9348c71bb, 0b31e28fbd773aefb6164687e0767319b8199829, 7fb374981e31c193b1152ed8d3b0a95b671330d4, dd431c3ac1fc34a9268580dd59ad3e3c76b32a8c, a78a6f0da57d058e2009e9958fdcef66f165208c, be84f32bb2c981ca670922e047cdde1488b233de |
| Linux/Linuxgeneric | 3.7 | Not reported |
Published upstream
Jul 12, 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: ima: Fix use-after-free on a dentry's dname.name ->d_name.name can change on rename and the earlier value can be freed; there are conditions sufficient to stabilize it (->d_lock on dentry, ->d_lock on its parent, ->i_rwsem exclusive on the parent's inode, rename_lock), but none of those are met at any of the sites. Take a stable snapshot of the name instead.
Quoted source text, attributed separately from HOL analysis.