LiveActive security incident?Get immediate response
CVE Record

CVE-2024-39494: ima: Fix use-after-free on a dentry's dname.name

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.

HighCVSS 7.8Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A Linux Integrity Measurement Architecture flaw can access a filename after that memory has been freed during a rename. A local, low-privileged user may be able to trigger serious confidentiality, integrity, or availability impact. The supplied CVSS score is 7.8, but the sources provide no evidence of active exploitation.

Executive priority

Treat as a high-priority kernel maintenance issue, especially on shared hosts, build systems, and servers running untrusted workloads. It is less urgent than a remotely exploitable or KEV-listed flaw, but the stated potential impact is broad. Patch through normal emergency kernel procedures after verifying distribution applicability and reboot requirements.

Technical view

IMA code reads dentry d_name.name without holding any lock that stabilizes it. A concurrent rename can replace and free the earlier name, producing a use-after-free. The kernel fix takes a stable snapshot instead. The supplied vector is local, low complexity, low privileges, no user interaction, with high confidentiality, integrity, and availability impacts.

Likely exposure

Exposure is limited to Linux systems running affected kernel builds, with greatest concern where IMA and relevant rename-processing paths are used. The bundle identifies affected release lines and several stable fixes, but does not provide reliable distribution-package mappings. Containers normally share the host kernel, so assess the host rather than container userland packages.

Exploitation context

The supplied CVSS vector requires local access and low privileges; this is not described as a directly remote flaw. Triggering involves a rename race affecting IMA filename handling. CVE-2024-39494 is not listed as KEV in the bundle, and no supplied source confirms public or active exploitation.

Researcher notes

The key race is lifetime instability of d_name.name during rename; none of the required stabilizing locks were held at affected sites. Stable branches use separate backport commits. The supplied affected-version data includes ambiguous identifiers and duplicates, so commit ancestry or distribution advisories should determine exposure. The bundle does not document exploit reliability, observed attacks, or a non-patch workaround.

Mitigation direction

  • Install a distribution-supported kernel containing the applicable upstream stable fix.
  • Reboot into the updated kernel; installing packages alone does not replace the running kernel.
  • Prioritize multi-user systems where untrusted users or workloads can perform filesystem operations.
  • Consult the Linux or distribution advisory when release-to-package mapping is unclear.

Validation and detection

  • Record the running kernel version, build, architecture, and distribution package revision.
  • Map that build to the vendor advisory or applicable stable-kernel fix commit.
  • Confirm the patched kernel is running after reboot, not merely installed.
  • Assess whether IMA is configured and used on each potentially affected host.
  • Review kernel telemetry for related memory faults, while recognizing absence does not prove safety.
Prepared
Confidence
medium
Sources
6

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2024-39494 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.8 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
3Timeline events
2ADP providers
10Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9Linux

Vulnerability scoring details

Base CVSS 3.1 score

7.8High
CVSS 3.1 vector shape for CVE-2024-39494Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CVECVE Program Container
CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux2fe5d6def1672ae6635dd71867bf36dcfaa7434b, 2fe5d6def1672ae6635dd71867bf36dcfaa7434b, 2fe5d6def1672ae6635dd71867bf36dcfaa7434b, 2fe5d6def1672ae6635dd71867bf36dcfaa7434b, 2fe5d6def1672ae6635dd71867bf36dcfaa7434b, 2fe5d6def1672ae6635dd71867bf36dcfaa7434b, 2fe5d6def1672ae6635dd71867bf36dcfaa7434bunaffected
LinuxLinux3.7, 0, 5.4.291, 5.10.235, 5.15.174, 6.1.97, 6.6.35, 6.9.6, 6.10affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.