linux-cve-announce - CVE-2026-23063: uacce: ensure safe queue release with state management

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <2026020415-CVE-2026-23063-d727@gregkh>
Date: Wed,  4 Feb 2026 17:14:22 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2026-23063: uacce: ensure safe queue release with state management

From: Greg Kroah-Hartman <gregkh@...nel.org>

Description
===========

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

uacce: ensure safe queue release with state management

Directly calling `put_queue` carries risks since it cannot
guarantee that resources of `uacce_queue` have been fully released
beforehand. So adding a `stop_queue` operation for the
UACCE_CMD_PUT_Q command and leaving the `put_queue` operation to
the final resource release ensures safety.

Queue states are defined as follows:
- UACCE_Q_ZOMBIE: Initial state
- UACCE_Q_INIT: After opening `uacce`
- UACCE_Q_STARTED: After `start` is issued via `ioctl`

When executing `poweroff -f` in virt while accelerator are still
working, `uacce_fops_release` and `uacce_remove` may execute
concurrently. This can cause `uacce_put_queue` within
`uacce_fops_release` to access a NULL `ops` pointer. Therefore, add
state checks to prevent accessing freed pointers.

The Linux kernel CVE team has assigned CVE-2026-23063 to this issue.


Affected and fixed versions
===========================

	Issue introduced in 5.7 with commit 015d239ac0142ad0e26567fd890ef8d171f13709 and fixed in 6.6.122 with commit 43f233eb6e7b9d88536881a9bc43726d0e34800d
	Issue introduced in 5.7 with commit 015d239ac0142ad0e26567fd890ef8d171f13709 and fixed in 6.12.68 with commit 47634d70073890c9c37e39ab4ff93d4b585b028a
	Issue introduced in 5.7 with commit 015d239ac0142ad0e26567fd890ef8d171f13709 and fixed in 6.18.8 with commit 92e4f11e29b98ef424ff72d6371acac03e5d973c
	Issue introduced in 5.7 with commit 015d239ac0142ad0e26567fd890ef8d171f13709 and fixed in 6.19-rc7 with commit 26c08dabe5475d99a13f353d8dd70e518de45663

Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.

Unaffected versions might change over time as fixes are backported to
older supported kernel versions.  The official CVE entry at
	https://cve.org/CVERecord/?id=CVE-2026-23063
will be updated if fixes are backported, please check that for the most
up to date information about this issue.


Affected files
==============

The file(s) affected by this issue are:
	drivers/misc/uacce/uacce.c


Mitigation
==========

The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes.  Individual
changes are never tested alone, but rather are part of a larger kernel
release.  Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all.  If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
	https://git.kernel.org/stable/c/43f233eb6e7b9d88536881a9bc43726d0e34800d
	https://git.kernel.org/stable/c/47634d70073890c9c37e39ab4ff93d4b585b028a
	https://git.kernel.org/stable/c/92e4f11e29b98ef424ff72d6371acac03e5d973c
	https://git.kernel.org/stable/c/26c08dabe5475d99a13f353d8dd70e518de45663