linux-cve-announce - CVE-2026-23094: uacce: fix isolate sysfs check condition

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: <2026020426-CVE-2026-23094-9cb7@gregkh>
Date: Wed,  4 Feb 2026 17:14:53 +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-23094: uacce: fix isolate sysfs check condition

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

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

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

uacce: fix isolate sysfs check condition

uacce supports the device isolation feature. If the driver
implements the isolate_err_threshold_read and
isolate_err_threshold_write callback functions, uacce will create
sysfs files now. Users can read and configure the isolation policy
through sysfs. Currently, sysfs files are created as long as either
isolate_err_threshold_read or isolate_err_threshold_write callback
functions are present.

However, accessing a non-existent callback function may cause the
system to crash. Therefore, intercept the creation of sysfs if
neither read nor write exists; create sysfs if either is supported,
but intercept unsupported operations at the call site.

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


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

	Issue introduced in 6.3 with commit e3e289fbc0b520cf469469e8cdba84a50424eb65 and fixed in 6.6.122 with commit 9ab05cdcac354b1b1139918f49c6418b9005d042
	Issue introduced in 6.3 with commit e3e289fbc0b520cf469469e8cdba84a50424eb65 and fixed in 6.12.68 with commit fdbbb47d15ae17bf39fafec7e2028c1f8efba15e
	Issue introduced in 6.3 with commit e3e289fbc0b520cf469469e8cdba84a50424eb65 and fixed in 6.18.8 with commit 82821a681d5dcce31475a65190fc39ea8f372cc0
	Issue introduced in 6.3 with commit e3e289fbc0b520cf469469e8cdba84a50424eb65 and fixed in 6.19-rc7 with commit 98eec349259b1fd876f350b1c600403bcef8f85d

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-23094
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/9ab05cdcac354b1b1139918f49c6418b9005d042
	https://git.kernel.org/stable/c/fdbbb47d15ae17bf39fafec7e2028c1f8efba15e
	https://git.kernel.org/stable/c/82821a681d5dcce31475a65190fc39ea8f372cc0
	https://git.kernel.org/stable/c/98eec349259b1fd876f350b1c600403bcef8f85d