LiveActive security incident?Get immediate response
CVE Record

CVE-2024-42146: drm/xe: Add outer runtime_pm protection to xe_live_ktest@xe_dma_buf

In the Linux kernel, the following vulnerability has been resolved: drm/xe: Add outer runtime_pm protection to xe_live_ktest@xe_dma_buf Any kunit doing any memory access should get their own runtime_pm outer references since they don't use the standard driver API entries. In special this dma_buf from the same driver. Found by pre-merge CI on adding WARN calls for unprotected inner callers: <6> [318.639739] # xe_dma_buf_kunit: running xe_test_dmabuf_import_same_driver <4> [318.639957] ------------[ cut here ]------------ <4> [318.639967] xe 0000:4d:00.0: Missing outer runtime PM protection <4> [318.640049] WARNING: CPU: 117 PID: 3832 at drivers/gpu/drm/xe/xe_pm.c:533 xe_pm_runtime_get_noresume+0x48/0x60 [xe]

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This CVE is a Linux kernel drm/xe driver issue where a KUnit test path accessed memory without the expected runtime power-management protection. The public record does not describe a business-impacting exploit path, data exposure, or service outage scenario. Treat it as a kernel maintenance item unless your vendor rates the same fix higher.

Executive priority

Handle through normal Linux kernel patch management. Escalate only if your fleet depends on affected Xe DRM kernels, your vendor assigns higher severity, or the affected systems are high-value workstations or GPU-enabled servers.

Technical view

The fix adds outer runtime_pm protection around xe_live_ktest@xe_dma_buf. The warning showed xe_pm_runtime_get_noresume reporting missing outer runtime PM protection during xe_dma_buf_kunit testing. Sources identify Linux kernel affected versions and two stable kernel commits, but provide no CVSS, CWE, concrete impact, or exploit details.

Likely exposure

Exposure appears limited to Linux kernels carrying the affected drm/xe code, especially environments using or testing the Xe DRM driver. The source lists Linux 6.8, 6.9.9, and 6.10-related version data, but distro backports may differ. Validate against your vendor kernel package, not upstream version alone.

Exploitation context

No active exploitation is identified: the CVE is not listed as KEV in the provided bundle, and the description says it was found by pre-merge CI. The sources do not provide exploitability, attacker prerequisites, or impact details, so offensive risk cannot be stated confidently.

Researcher notes

The available evidence is sparse and fix-oriented. It identifies a missing runtime PM guard in a drm/xe KUnit dma_buf path, detected by CI warning instrumentation. There is no CVSS, CWE, public impact analysis, or exploit confirmation in the bundle.

Mitigation direction

  • Apply a vendor kernel update that includes the referenced stable drm/xe fix.
  • Check Linux distribution advisories for backported fixes and package-specific status.
  • Prioritize systems running affected upstream kernel lines with drm/xe enabled.
  • Avoid inventing compensating controls; follow vendor guidance if patching is delayed.

Validation and detection

  • Inventory kernel versions and distribution package revisions across Linux hosts.
  • Check whether the drm/xe driver is present, enabled, or loaded.
  • Confirm the kernel includes commit 0888d15ea45b or f9116f658a62, as applicable.
  • Review vendor changelogs for CVE-2024-42146 or the drm/xe runtime_pm fix.
  • Run normal GPU and kernel regression testing after updating.
Prepared
Confidence
medium
Sources
4

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-42146 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
Unknown
CVSS
Not scored
Known Exploited
No
Published
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.

0CVSS vectors
3Timeline events
2ADP providers
3Source links

SSVC decision data

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

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
LinuxLinuxdd08ebf6c3525a7ea2186e636df064ea47281987, dd08ebf6c3525a7ea2186e636df064ea47281987unaffected
LinuxLinux6.8, 0, 6.9.9, 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.