Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

Description

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

Timeline

  1. ID reserved

    By Linux

  2. · 22 days later

    Published

  3. · 3 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Deferred.

EPSS (exploitation in 30 days)
0.21% · top 88% of all CVEs (17 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected 015d239ac0142ad0e26567fd890ef8d171f13709 – < 78d99f062d42e3af2ca46bde1a8e46e0dfd372e3
    • affected 015d239ac0142ad0e26567fd890ef8d171f13709 – < ebfa85658a39b49ec3901ceea7535b73aa0429e6
    • affected 015d239ac0142ad0e26567fd890ef8d171f13709 – < 75b29bdc935ff93b8e8bf6f6b4d8a4810b26e06f
    • affected 015d239ac0142ad0e26567fd890ef8d171f13709 – < 4c042bc71474dbe417c268f4bfb8ec196f802f07
    • affected 015d239ac0142ad0e26567fd890ef8d171f13709 – < a407ddd61b3e6afc5ccfcd1478797171cf5686ee
    • affected 015d239ac0142ad0e26567fd890ef8d171f13709 – < ba29b59d124e725e0377f09b2044909c91d657a1
    • affected 015d239ac0142ad0e26567fd890ef8d171f13709 – < 02695347be532b628f22488300d40c4eba48b9b7
  • Linux · Linux

    • affected 5.7
    • unaffected < 5.7
    • unaffected 5.10.249 – ≤ 5.10.*
    • unaffected 5.15.199 – ≤ 5.15.*
    • unaffected 6.1.162 – ≤ 6.1.*
    • unaffected 6.6.122 – ≤ 6.6.*
    • unaffected 6.12.68 – ≤ 6.12.*
    • unaffected 6.18.8 – ≤ 6.18.*
    • unaffected 6.19 – ≤ *

References

References7

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-23056 badge
[![CVE-2026-23056](https://cveledger.app/badge/CVE-2026-23056.svg)](https://cveledger.app/cve/CVE-2026-23056)

Record last updated .