LiveActive security incident?Get immediate response
CVE Record

CVE-2026-23056: uacce: implement mremap in uacce_vm_ops to return -EPERM

In the Linux kernel, the following vulnerability has been resolved: uacce: implement mremap in uacce_vm_ops to return -EPERM The current uacce_vm_ops does not support the mremap operation of vm_operations_struct. Implement .mremap to return -EPERM to remind users. The reason we need to explicitly disable mremap is that when the driver does not implement .mremap, it uses the default mremap method. This could lead to a risk scenario: An application might first mmap address p1, then mremap to p2, followed by munmap(p1), and finally munmap(p2). Since the default mremap copies the original vma's vm_private_data (i.e., q) to the new vma, both munmap operations would trigger vma_close, causing q->qfr to be freed twice(qfr will be set to null here, so repeated release is ok).

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

Security readout for executives and security teams

Plain-English summary

CVE-2026-23056 is a Linux kernel uacce driver issue where an unsupported memory remap operation could lead to duplicated cleanup of internal driver state. Public sources do not provide CVSS, confirmed impact, or exploitation evidence. Treat it as a kernel maintenance item requiring vendor version mapping.

Executive priority

Monitor and remediate through normal kernel patch cycles unless your environment exposes uacce to untrusted local users. Escalate priority for shared compute, accelerator, or multi-tenant systems using this subsystem.

Technical view

The uacce vm_operations did not implement .mremap, so Linux used the default behavior. That could copy vm_private_data into a new VMA and later cause vma_close to free related qfr state twice. The fix explicitly implements mremap and returns -EPERM.

Likely exposure

Exposure is likely limited to Linux systems running affected kernel versions with the uacce accelerator framework present and usable by local applications. The CVE record lists Linux as affected but version data requires distribution-specific interpretation.

Exploitation context

No public source in the bundle reports active exploitation, and the CVE is not listed as KEV. The issue appears local and tied to user-space interaction with uacce memory mappings, not a remote network attack.

Researcher notes

The public record describes a resolved kernel memory-management bug but lacks CVSS, exploitability analysis, and concrete impact classification. Avoid assuming privilege escalation or denial of service without further vendor or upstream analysis.

Mitigation direction

  • Apply Linux stable updates containing the referenced uacce mremap fix.
  • Use distribution advisories to map this CVE to packaged kernel versions.
  • Prioritize systems exposing uacce devices to untrusted local users.
  • If no vendor package is available, follow vendor kernel guidance.

Validation and detection

  • Inventory Linux kernel versions across affected server and workstation fleets.
  • Check whether uacce support is enabled and used on relevant systems.
  • Confirm the kernel includes one of the referenced stable commits or vendor backports.
  • Track vendor advisories for corrected package versions and reboot requirements.
Prepared
Confidence
medium
Sources
9

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-23056 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
0ADP providers
8Source links

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
LinuxLinux015d239ac0142ad0e26567fd890ef8d171f13709, 015d239ac0142ad0e26567fd890ef8d171f13709, 015d239ac0142ad0e26567fd890ef8d171f13709, 015d239ac0142ad0e26567fd890ef8d171f13709, 015d239ac0142ad0e26567fd890ef8d171f13709, 015d239ac0142ad0e26567fd890ef8d171f13709, 015d239ac0142ad0e26567fd890ef8d171f13709unaffected
LinuxLinux5.7, 0, 5.10.249, 5.15.199, 6.1.162, 6.6.122, 6.12.68, 6.18.8, 6.19affected
Weakness

CWE details

No CWE listed

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