CVE-2026-23063: uacce: ensure safe queue release with state management
In the Linux kernel, the following vulnerability has been resolved:
uacce: ensure safe queue release with state management
Directly calling putqueue carries risks since it cannot guarantee that resources of uaccequeue have been fully released beforehand. So adding a stopqueue operation for the UACCECMDPUTQ command and leaving the putqueue operation to the final resource release ensures safety.
Queue states are defined as follows: - UACCEQZOMBIE: Initial state - UACCEQINIT: After opening uacce - UACCEQSTARTED: After start is issued via ioctl
When executing poweroff -f in virt while accelerator are still working, uaccefopsrelease and uacceremove may execute concurrently. This can cause uacceputqueue within uaccefopsrelease to access a NULL ops pointer. Therefore, add state checks to prevent accessing freed pointers.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
debian/linuxto 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
Event History
Frequently Asked Questions
What is the severity of CVE-2026-23063?
The severity of CVE-2026-23063 is classified as medium due to the potential impact on system stability.
How do I fix CVE-2026-23063?
To fix CVE-2026-23063, you should update your Linux kernel to the latest version where the vulnerability has been patched.
What systems are affected by CVE-2026-23063?
CVE-2026-23063 affects specific versions of the Linux kernel related to the uacce queue management.
What is the main issue addressed by CVE-2026-23063?
CVE-2026-23063 addresses the risk associated with directly calling `put_queue`, which may not ensure complete resource release of the `uacce_queue`.
Is CVE-2026-23063 known to be exploited in the wild?
As of now, there have been no public reports of CVE-2026-23063 being actively exploited in the wild.