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

Published Feb 4, 2026
·
Updated

In the Linux kernel, the following vulnerability has been resolved:

uacce: implement mremap in uaccevmops to return -EPERM

The current uaccevmops does not support the mremap operation of vmoperationsstruct. 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 vmprivatedata (i.e., q) to the new vma, both munmap operations would trigger vmaclose, causing q->qfr to be freed twice(qfr will be set to null here, so repeated release is ok).

Affected Software

2 affected componentsFixes available
Linux Linux kernel
debian/linux
6.1.176-16.1.190-16.12.107-16.12.115-27.2.12-17.2.15-1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade debian/linux to a version that resolves this vulnerability.

    Fixed in 6.1.176-1Fixed in 6.1.190-1Fixed in 6.12.107-1Fixed in 6.12.113-1Fixed in 7.2.12-1Fixed in 7.2.13-1
  2. Compensating control

    Implement the .mremap operation in uacce_vm_ops to return -EPERM, explicitly disabling mremap for uacce mappings.

Event History

Feb 4, 2026
CVE Published
via MITRE·04:07 PM
Data Sourced
via MITRE·04:07 PM
Description
Data Sourced
via NVD·05:16 PM
Description

Parent advisories

This vulnerability appears in the following advisories.

Peer vulnerabilities

Found alongside the following vulnerabilities.

Frequently Asked Questions

1

What conditions are required to trigger the issue?

An application must use a uacce mapping and perform a sequence involving mmap, mremap, and unmapping both the original and remapped addresses. The issue arises when uacce_vm_ops does not implement mremap and the kernel uses the default mremap behavior.

2

What is the practical effect of the vulnerable mapping sequence?

Default mremap copies the VMA's vm_private_data to the new mapping, so unmapping each address can invoke vma_close twice for the same queue-related state. The described release path tolerates the repeated release because qfr is set to null.

3

What mitigation is provided by the fix?

The fix implements the uacce_vm_ops mremap operation to return -EPERM. This explicitly prevents mremap on affected uacce mappings.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203