LiveActive security incident?Get immediate response
CVE Record

CVE-2026-64051: accel/qaic: Add overflow check to remap_pfn_range during mmap

In the Linux kernel, the following vulnerability has been resolved: accel/qaic: Add overflow check to remap_pfn_range during mmap The call to remap_pfn_range in qaic_gem_object_mmap is susceptible to (re)mapping beyond the VMA if the BO is too large. This can cause use after free issues when munmap() unmaps only the VMA region and not the additional mappings. To prevent this, check the remaining size of the VMA before remapping and truncate the remapped length if sg->length is too large. [jhugo: fix braces from checkpatch --strict]

HighCVSS 7.8Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2026-64051 is a high-severity Linux kernel flaw in the qaic accelerator driver. A local low-privileged attacker could trigger incorrect memory remapping during mmap, potentially leading to use-after-free conditions with confidentiality, integrity, and availability impact.

Executive priority

Treat as high priority for Linux fleets that use Qualcomm Cloud AI accelerator support. It is not presented as remotely exploitable, but local privilege and memory-corruption impact justify prompt patch validation.

Technical view

The qaic_gem_object_mmap path called remap_pfn_range without sufficiently bounding the remap length to the VMA. If a buffer object was too large, mappings could extend past the VMA, leaving extra mappings after munmap and creating use-after-free risk.

Likely exposure

Exposure is likely limited to Linux systems using affected kernel builds with the accel/qaic driver present and relevant hardware or workloads. The source data lists Linux kernel affected versions and stable commits, but distribution backport status must be verified separately.

Exploitation context

The CVSS vector is local, low complexity, low privileges, and no user interaction. The bundle does not include KEV status or any cited evidence of active exploitation, so active exploitation is not established.

Researcher notes

Key uncertainty is exact downstream exposure: the CVE source gives upstream Linux commits and version data, but not distro-specific package names, hardware prevalence, exploit proofs, or operational mitigations beyond the code fix.

Mitigation direction

  • Apply kernel updates containing the referenced stable fixes.
  • Verify your distribution advisory maps to the kernel stable commits.
  • Prioritize systems exposing or using the accel/qaic driver.
  • If patching is delayed, consult vendor guidance for driver-specific risk reduction.

Validation and detection

  • Inventory Linux hosts and kernel versions against vendor advisories.
  • Check whether the accel/qaic driver is present or in use.
  • Confirm installed kernel includes one of the referenced fixes or equivalent backport.
  • Review local access controls for systems using qaic acceleration.
Prepared
Confidence
medium
Sources
7

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-2026-64051 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
6Source 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-64051Attack 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.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxff13be8303336ead5621712f2c55012d738878b5, ff13be8303336ead5621712f2c55012d738878b5, ff13be8303336ead5621712f2c55012d738878b5, ff13be8303336ead5621712f2c55012d738878b5, ff13be8303336ead5621712f2c55012d738878b5unaffected
LinuxLinux6.4, 0, 6.6.142, 6.12.92, 6.18.34, 7.0.11, 7.1affected
Weakness

CWE details

No CWE listed

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