CVE-2026-23288: accel/amdxdna: Fix out-of-bounds memset in command slot handling
In the Linux kernel, the following vulnerability has been resolved:
accel/amdxdna: Fix out-of-bounds memset in command slot handling
The remaining space in a command slot may be smaller than the size of
the command header. Clearing the command header with memset() before
verifying the available slot space can result in an out-of-bounds write
and memory corruption.
Fix this by moving the memset() call after the size validation.
Security readout for executives and security teams
Plain-English summary
A flaw in the Linux AMD XDNA accelerator driver can let a low-privileged local user corrupt kernel memory. Successful exploitation could affect confidentiality, integrity, and availability, including crashes or broader system compromise. The issue was fixed by validating command-slot space before clearing a command header.
Executive priority
Prioritize affected shared, developer, and multi-user Linux systems because exploitation requires only low local privileges and could compromise the host. Remediate through supported kernel updates promptly. Internet-facing status alone does not determine exposure because this is a local attack path.
Technical view
The amdxdna command-slot path performed memset() on a command header before confirming sufficient space remained. If the remaining slot was smaller than the header, the write crossed the slot boundary and corrupted memory. The cited stable-kernel changes move memset() after size validation.
Likely exposure
Exposure is limited to Linux systems using affected amdxdna driver code where a low-privileged local user can reach the vulnerable command-handling path. The bundle does not provide complete vulnerable release ranges; it lists fixing commits and Linux 6.19.4, so distribution kernel status must be verified.
Exploitation context
The CVSS vector indicates local access, low complexity, low privileges, and no user interaction, with potentially high confidentiality, integrity, and availability impact. The CVE is not listed as KEV, and the supplied sources provide no evidence of active exploitation or a public exploit.
Researcher notes
The root cause is an out-of-bounds kernel write caused by incorrect validation ordering. Available evidence establishes the correction but not complete introduction-to-fix version ranges, affected distribution packages, exploitability reliability, or observed attacks. Validate provenance against distribution-maintained kernel branches rather than relying only on upstream version labels.
Mitigation direction
Upgrade to a vendor-supported kernel containing one of the cited stable fixes.
Check Linux distribution advisories for the exact affected and corrected kernel package versions.
Where upgrading is delayed, assess whether the amdxdna driver can be disabled without operational impact.
Restrict local account access and monitor privileged workloads until remediation is confirmed.
Validation and detection
Inventory systems running Linux kernels that include or enable the amdxdna driver.
Compare each kernel package against vendor advisories and the cited fixing commits.
Confirm the installed replacement kernel is active after maintenance or reboot.
Review local-access controls and logs for unusual activity involving accelerator workloads.
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-2026-23288 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
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
0ADP providers
3Source links
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.