Skip to content
Noroxi
NVD / CVE Program· CNA Linux

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

Noroxi assessment

Priority: Monitor (action score 0/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.21% (FIRST EPSS).
  • Fixed version: Linux Linux 02695347be532b628f22488300d40c4eba48b9b7, 4c042bc71474dbe417c268f4bfb8ec196f802f07, 75b29bdc935ff93b8e8bf6f6b4d8a4810b26e06f.

Low priority for now. Upgrade to Linux Linux 02695347be532b628f22488300d40c4eba48b9b7, 4c042bc71474dbe417c268f4bfb8ec196f802f07, 75b29bdc935ff93b8e8bf6f6b4d8a4810b26e06f or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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).

—No exploit Fix available
Published
Feb 4, 2026
Updated
Jun 17, 2026
EPSS
0.2% · 11th percentile
CWE
—

Report tools

JSON

Action score

0

Monitor

Low priority for now.

CVSS
0 / 40 · —
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-23056

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 5.7affected
    • 015d239ac0142ad0e26567fd890ef8d171f13709 and later · before 78d99f062d42e3af2ca46bde1a8e46e0dfd372e3affected · git
    • 015d239ac0142ad0e26567fd890ef8d171f13709 and later · before ebfa85658a39b49ec3901ceea7535b73aa0429e6affected · git
    • 015d239ac0142ad0e26567fd890ef8d171f13709 and later · before 75b29bdc935ff93b8e8bf6f6b4d8a4810b26e06faffected · git
    • 015d239ac0142ad0e26567fd890ef8d171f13709 and later · before 4c042bc71474dbe417c268f4bfb8ec196f802f07affected · git
    • 015d239ac0142ad0e26567fd890ef8d171f13709 and later · before a407ddd61b3e6afc5ccfcd1478797171cf5686eeaffected · git
    • 015d239ac0142ad0e26567fd890ef8d171f13709 and later · before ba29b59d124e725e0377f09b2044909c91d657a1affected · git
    • 015d239ac0142ad0e26567fd890ef8d171f13709 and later · before 02695347be532b628f22488300d40c4eba48b9b7affected · git
    • before 5.7not affected · semver
    • 5.10.249 and later · up to and including 5.10.*not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.162-16.1.162-1
Debian:13linuxbefore 6.12.69-16.12.69-1
Debian:14linuxbefore 6.18.8-16.18.8-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2026-23053Feb 4, 2026 · NFS: Fix a deadlock involving nfs_release_folio()
    0Monitor
  • ← EarlierCVE-2026-23055Feb 4, 2026 · i2c: riic: Move suspend handling to NOIRQ phase
    0Monitor
  • Later →CVE-2026-23057Feb 4, 2026 · vsock/virtio: Coalesce only linear skb
    0Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux02695347be532b628f22488300d40c4eba48b9b7Vendor (CNA)
Linux Linux4c042bc71474dbe417c268f4bfb8ec196f802f07Vendor (CNA)
Linux Linux75b29bdc935ff93b8e8bf6f6b4d8a4810b26e06fVendor (CNA)
Linux Linux78d99f062d42e3af2ca46bde1a8e46e0dfd372e3Vendor (CNA)
Linux Linuxa407ddd61b3e6afc5ccfcd1478797171cf5686eeVendor (CNA)
Linux Linuxba29b59d124e725e0377f09b2044909c91d657a1Vendor (CNA)
Linux Linuxebfa85658a39b49ec3901ceea7535b73aa0429e6Vendor (CNA)
debian:linux6.1.162-1 · Debian:12Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

No CVSS vector for this record, so attack conditions can't be derived.

Weakness class (CWE)

—

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (6 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records