Security readout for executives and security teams
Plain-English summary
A flaw in the Linux AMD XDNA accelerator driver could let a low-privileged local user submit a command whose declared payload exceeds the remaining buffer. The supplied CVSS assessment indicates possible disclosure of sensitive data and serious service disruption. It does not indicate remote exploitation or integrity loss.
Executive priority
Treat this as a high-priority local privilege-boundary issue, especially on shared AI, development, or compute hosts. It is less urgent than a remotely exploitable flaw, but potential high data exposure and downtime justify prompt patch verification. Escalate systems allowing untrusted local users or workloads.
Technical view
The amdxdna command parser trusted the command-header count when determining payload size without confirming that the declared payload fit inside the remaining command buffer. The referenced Linux stable changes add that validation. CVSS 3.1 is 7.1: local access, low complexity, low privileges, no user interaction, with high confidentiality and availability impact.
Likely exposure
Exposure requires an affected Linux kernel with AMD XDNA functionality present and reachable by a local low-privileged user. The supplied affected-version data names 6.14, 6.18.17, 6.19.7, and 7.0 but does not clearly express range boundaries. Confirm distribution-specific status rather than relying only on version-string comparison.
Exploitation context
The source bundle provides no evidence of active exploitation, and the CVE is not listed as KEV. The CVSS vector describes a local, low-complexity path requiring low privileges and no user interaction. Public exploit availability and practical reliability are not established by the supplied evidence.
Researcher notes
The validated field is the command-header payload count relative to remaining buffer space. The supplied sources establish inadequate bounds validation and the fixing commits, but do not document a demonstrated crash, data disclosure primitive, exploit chain, affected hardware matrix, or exact release-range semantics. Avoid inferring those details without vendor or distribution evidence.
Mitigation direction
- Install a vendor-supported kernel containing the applicable referenced stable fix.
- Check the Linux distribution's advisory for corrected package versions and backports.
- Prioritize multi-user or shared-compute systems exposing AMD XDNA functionality.
- Until updated, restrict untrusted local access to affected accelerator-enabled systems.
Validation and detection
- Inventory kernel versions and whether AMD XDNA functionality is present or enabled.
- Compare installed packages against distribution advisories and referenced stable fixes.
- Confirm the running kernel changed after updating and rebooting.
- Review local account and workload access on affected accelerator-enabled hosts.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-2026-23424 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.1 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
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.
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H1.85.2LinuxVulnerability scoring details
Base CVSS 3.1 score
7.1HighVector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
Source materials
- CVE List V5 sourceCVE List V5
- https://git.kernel.org/stable/c/3464e751755172ddbb849c1bd92f5f59e95c59a1CVE reference, Linux
- https://git.kernel.org/stable/c/3ed2ae6b3fe869f99b75afd02045ba5c0c0773e2CVE reference, Linux
- https://git.kernel.org/stable/c/901ec3470994006bc8dd02399e16b675566c3416CVE reference, Linux
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.