CVE-2026-23056
Awaiting Analysis Awaiting Analysis - Queue
BaseFortify

Publication date: 2026-02-04

Last updated on: 2026-02-06

Assigner: kernel.org

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).
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-02-04
Last Modified
2026-02-06
Generated
2026-05-07
AI Q&A
2026-02-04
EPSS Evaluated
2026-05-05
NVD
CVE-2026-23056
Affected Vendors & Products
Currently, no data is known.
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-UNKNOWN
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

This vulnerability exists in the Linux kernel's uacce driver where the mremap operation was not explicitly implemented in the uacce_vm_ops structure.

Because the mremap operation was missing, the default mremap method was used, which copies the original virtual memory area's private data to the new virtual memory area.

This behavior can lead to a risk where an application that performs a sequence of mmap, mremap, and munmap calls could cause the same resource to be freed twice, potentially leading to memory corruption or instability.

The fix was to implement the mremap operation to explicitly return -EPERM, preventing this unsafe behavior.


How can this vulnerability impact me? :

This vulnerability can lead to a double free of kernel resources when certain memory operations are performed by an application.

Double freeing memory can cause memory corruption, which may result in system instability, crashes, or potentially allow an attacker to exploit the kernel for privilege escalation or denial of service.


How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:

I don't know


How can this vulnerability be detected on my network or system? Can you suggest some commands?

I don't know


What immediate steps should I take to mitigate this vulnerability?

I don't know


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart