LiveActive security incident?Get immediate response
CVE Record

CVE-2024-35939: dma-direct: Leak pages on dma_set_decrypted() failure

In the Linux kernel, the following vulnerability has been resolved: dma-direct: Leak pages on dma_set_decrypted() failure On TDX it is possible for the untrusted host to cause set_memory_encrypted() or set_memory_decrypted() to fail such that an error is returned and the resulting memory is shared. Callers need to take care to handle these errors to avoid returning decrypted (shared) memory to the page allocator, which could lead to functional or security issues. DMA could free decrypted/shared pages if dma_set_decrypted() fails. This should be a rare case. Just leak the pages in this case instead of freeing them.

CriticalCVSS 9.3Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

A Linux kernel error path can return decrypted, host-shared memory to the normal page allocator in Intel TDX guests. That memory could later be reused, creating confidentiality, integrity, availability, or functional risks. The correction deliberately retains those pages when decryption fails instead of making them available for reuse.

Executive priority

Treat this as urgent where sensitive Linux workloads run in Intel TDX guests, especially under an untrusted host. Establish exposure promptly and deploy vendor-backed kernel updates through expedited change control. Non-TDX systems should be assessed, but the supplied description does not establish equivalent exposure outside TDX.

Technical view

An untrusted TDX host can cause memory encryption or decryption transitions to fail while leaving memory shared. In the vulnerable dma-direct failure path, DMA could free that shared page to the allocator. The referenced stable changes prevent this by leaking the page after dma_set_decrypted() fails. The source describes the condition as rare.

Likely exposure

Exposure appears concentrated in Linux kernels operating as Intel TDX guests. The record lists affected entries including 5.8, 6.1.86, 6.6.27, 6.8.6, and 6.9, plus an ambiguous "0" entry. These data do not establish complete affected ranges, so confirm vendor backport status rather than relying solely on version numbers.

Exploitation context

The supplied CVSS is 9.3 and models local access with no privileges or user interaction. The described threat involves an untrusted host inducing a transition failure in a TDX guest. The record is not in KEV, and the supplied sources provide no evidence of active exploitation or a public exploit.

Researcher notes

The safety invariant is that a page remaining decrypted or shared after dma_set_decrypted() failure must not reenter the allocator. The correction favors a bounded page leak over unsafe reuse. The bundle provides multiple stable commits but unclear version-range semantics and no CWE, reproduction evidence, or exploitation telemetry.

Mitigation direction

  • Upgrade affected guest kernels to vendor-supported releases containing the referenced dma-direct correction.
  • Prioritize remediation for Linux workloads operating as Intel TDX guests on untrusted infrastructure.
  • Reboot guests into the remediated kernel after applying the updated package.
  • If immediate patching is impossible, obtain supported temporary guidance from the Linux distribution or platform vendor.

Validation and detection

  • Inventory running kernel versions for every Intel TDX guest, not merely installed package versions.
  • Confirm the active kernel contains a referenced stable fix or documented vendor backport.
  • Verify remediated guests were rebooted and are executing the intended kernel.
  • Test that decryption failure handling does not return shared pages to the allocator.
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-35939 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
Critical
CVSS
9.3 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/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
5Source 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
9.3CVSS 3.1CriticalCVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H2.56Linux

Vulnerability scoring details

Base CVSS 3.1 score

9.3Critical
CVSS 3.1 vector shape for CVE-2024-35939Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/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

CISA-ADPCISA ADP Vulnrichment
other:ssvc
CVECVE Program Container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux56fccf21d1961a06e2a0c96ce446ebf036651062, 56fccf21d1961a06e2a0c96ce446ebf036651062, 56fccf21d1961a06e2a0c96ce446ebf036651062, 56fccf21d1961a06e2a0c96ce446ebf036651062, 91c7b0407ca6a62c095d265f76926b67bf66c026, 5.7.7unaffected
LinuxLinux5.8, 0, 6.1.86, 6.6.27, 6.8.6, 6.9affected
Weakness

CWE details

No CWE listed

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