LiveActive security incident?Get immediate response
CVE Record

CVE-2026-23280: accel/amdxdna: Prevent ubuf size overflow

In the Linux kernel, the following vulnerability has been resolved: accel/amdxdna: Prevent ubuf size overflow The ubuf size calculation may overflow, resulting in an undersized allocation and possible memory corruption. Use check_add_overflow() helpers to validate the size calculation before allocation.

HighCVSS 7.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A flaw in the Linux AMD XDNA accelerator driver can miscalculate a user-buffer allocation, potentially corrupting kernel memory. A local user with low privileges may be able to compromise confidentiality, integrity, or availability. The supplied CVSS score is 7.8, rated high.

Executive priority

Treat this as a high-priority local privilege boundary risk on systems using AMD XDNA acceleration, especially shared compute hosts. Inventory exposure promptly and deploy supported kernel updates. Internet-facing status alone does not determine risk because exploitation requires local access.

Technical view

An integer overflow in the accel/amdxdna ubuf size calculation can produce an undersized allocation and subsequent memory corruption. The kernel fix uses check_add_overflow() before allocation. The CVSS vector indicates local access, low complexity, low privileges, no user interaction, and high potential impact.

Likely exposure

Exposure is most likely on affected Linux kernels where the accel/amdxdna driver and relevant AMD XDNA hardware or interfaces are available to local users. The supplied affected-version data is ambiguous, so kernel versions alone should not be treated as definitive without distributor or vendor confirmation.

Exploitation context

The CVSS vector describes a local, low-privilege attack surface rather than remote exploitation. CISA KEV status is false in the supplied bundle, and no cited source establishes active exploitation or public weaponization. Practical exploitability is not demonstrated by the available evidence.

Researcher notes

The central condition is arithmetic overflow before ubuf allocation, followed by possible kernel memory corruption. The supplied records identify check_add_overflow() as the correction and provide three stable commits. Exact vulnerable-to-fixed version boundaries and exploitation reliability are not established in the bundle.

Mitigation direction

  • Apply a vendor-supported kernel containing the referenced overflow-check fix.
  • Check Linux distributor guidance for package-specific fixed versions and backports.
  • Prioritize multi-user systems exposing AMD XDNA accelerator interfaces.
  • Restrict untrusted local access until remediation is confirmed.

Validation and detection

  • Record the running kernel and installed kernel package versions.
  • Determine whether accel/amdxdna is present and usable on each system.
  • Map distributor packages against the referenced stable-kernel fixes.
  • After updating, verify the remediated kernel is running.
  • Monitor vendor advisories for clarified affected and fixed version ranges.
Prepared
Confidence
medium
Sources
5

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-23280 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
High
CVSS
7.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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.

1CVSS vectors
3Timeline events
0ADP providers
4Source 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.

ScoreVersionSeverityVectorExploitImpactSource
7.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9Linux

Vulnerability scoring details

Base CVSS 3.1 score

7.8High
CVSS 3.1 vector shape for CVE-2026-23280Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

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.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxbd72d4acda1069579b35123e3cc0b21ec1193a21, bd72d4acda1069579b35123e3cc0b21ec1193a21, bd72d4acda1069579b35123e3cc0b21ec1193a21unaffected
LinuxLinux6.18, 0, 6.18.17, 6.19.7, 7.0affected
Weakness

CWE details

No CWE listed

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