LiveActive security incident?Get immediate response
CVE Record

CVE-2024-46866: drm/xe/client: add missing bo locking in show_meminfo()

In the Linux kernel, the following vulnerability has been resolved: drm/xe/client: add missing bo locking in show_meminfo() bo_meminfo() wants to inspect bo state like tt and the ttm resource, however this state can change at any point leading to stuff like NPD and UAF, if the bo lock is not held. Grab the bo lock when calling bo_meminfo(), ensuring we drop any spinlocks first. In the case of object_idr we now also need to hold a ref. v2 (MattB) - Also add xe_bo_assert_held() (cherry picked from commit 4f63d712fa104c3ebefcb289d1e733e86d8698c7)

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

Security readout for executives and security teams

Plain-English summary

CVE-2024-46866 is a Linux kernel issue in the drm/xe graphics driver. The vulnerable code reads graphics buffer-object memory state without taking the required lock, so concurrent changes can cause null pointer dereference or use-after-free conditions. Public sources do not provide CVSS, confirmed exploitation, or broad operational impact details.

Executive priority

Treat as a kernel maintenance and exposure-verification item, not a confirmed emergency. Prioritize systems using affected Linux kernel branches with drm/xe support, especially endpoints where graphics drivers are enabled, and rely on distribution security updates.

Technical view

The flaw is in drm/xe/client show_meminfo(). bo_meminfo() inspects buffer-object fields such as tt and the TTM resource without holding the BO lock. The upstream fix takes the BO lock, drops spinlocks before calling bo_meminfo(), holds a reference for object_idr handling, and adds xe_bo_assert_held().

Likely exposure

Likely exposure is limited to Linux kernels containing the affected drm/xe client code and using affected versions identified by the CVE data, including 6.8, 6.10.11, and 6.11 entries. Downstream distribution exposure depends on backports and kernel configuration.

Exploitation context

The source bundle does not cite active exploitation, CISA KEV listing, proof-of-concept availability, or remote attack details. The described failure mode is kernel memory-safety related, but the public text does not establish attacker prerequisites or exploitability.

Researcher notes

Evidence is limited to the CVE description and two Linux stable references. The root issue is missing BO locking around state inspection in show_meminfo(), creating NPD and UAF risk. No CVSS, CWE mapping, exploit prerequisites, or confirmed exploitation are provided.

Mitigation direction

  • Check Linux distribution advisories for CVE-2024-46866 coverage and fixed kernel packages.
  • Prioritize kernel updates where drm/xe is enabled or Intel Xe graphics is in use.
  • Track the referenced stable kernel commits in vendor-maintained kernel branches.
  • If no vendor package is available, follow vendor guidance for supported kernel upgrade paths.

Validation and detection

  • Inventory Linux kernel versions across affected workstation, server, and fleet images.
  • Confirm whether the drm/xe driver code is present or enabled in relevant kernels.
  • Verify whether vendor kernels include the referenced stable fixes or equivalent backports.
  • Review crash telemetry for related null pointer dereference or use-after-free symptoms.
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-46866 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.