LiveActive security incident?Get immediate response
CVE Record

CVE-2024-46867: drm/xe/client: fix deadlock in show_meminfo()

In the Linux kernel, the following vulnerability has been resolved: drm/xe/client: fix deadlock in show_meminfo() There is a real deadlock as well as sleeping in atomic() bug in here, if the bo put happens to be the last ref, since bo destruction wants to grab the same spinlock and sleeping locks. Fix that by dropping the ref using xe_bo_put_deferred(), and moving the final commit outside of the lock. Dropping the lock around the put is tricky since the bo can go out of scope and delete itself from the list, making it difficult to navigate to the next list entry. (cherry picked from commit 0083b8e6f11d7662283a267d4ce7c966812ffd8a)

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

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel reliability vulnerability in the DRM xe client memory reporting path. Under specific reference-count timing, the kernel can deadlock while handling memory information. The sources do not provide CVSS, confirmed exploitation, or a named business-impact scenario, so urgency depends on whether affected kernels and the xe driver are in use.

Executive priority

Treat as a kernel stability issue requiring normal patch governance unless affected GPU-heavy systems are business-critical. Escalate priority where crashes, hangs, or service reliability have direct operational impact.

Technical view

CVE-2024-46867 fixes a real deadlock and sleeping-in-atomic bug in drm/xe/client show_meminfo(). If xe_bo_put() drops the last reference, object destruction can try to acquire the same spinlock and sleeping locks. The fix defers the bo put and moves the final commit outside the lock.

Likely exposure

Likely exposure is Linux systems running affected kernel versions with the drm/xe code present and reachable. The bundle lists Linux 6.8, 6.10.11, and 6.11 as affected, but does not define exact distro package ranges, attack vector, or required privileges.

Exploitation context

No active exploitation is stated. KEV is false, and the provided sources describe the issue as a kernel deadlock/sleeping-in-atomic bug, not a public exploit. The bundle does not identify remote exploitability or privilege escalation.

Researcher notes

The evidence is narrow: upstream says the vulnerability is resolved and describes the lock/refcount failure mode. Missing data includes CVSS, CWE, privilege requirements, reachable interface details, and distribution-specific fixed package versions.

Mitigation direction

  • Check Linux vendor advisories for fixed kernel packages for CVE-2024-46867.
  • Upgrade affected kernels to versions containing the referenced stable fixes.
  • Prioritize systems using drm/xe graphics support or exposed GPU workloads.
  • If no vendor package exists, follow vendor guidance for temporary operational risk reduction.

Validation and detection

  • Inventory Linux kernel versions and compare them with vendor CVE guidance.
  • Confirm whether deployed kernels contain commits 9d3de463e23b or 9bd7ff293fc8.
  • Identify systems using the drm/xe driver or related GPU functionality.
  • Review kernel logs for deadlock, hung task, or sleeping-in-atomic warnings.
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-46867 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
1ADP 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

CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux0845233388f8a26d00acf9bf230cfd4f36aa4c30, 0845233388f8a26d00acf9bf230cfd4f36aa4c30unaffected
LinuxLinux6.8, 0, 6.10.11, 6.11affected
Weakness

CWE details

No CWE listed

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