From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-23096: uacce: fix cdev handling in the cleanup path
Date: Wed, 4 Feb 2026 17:14:55 +0100 [thread overview]
Message-ID: <2026020427-CVE-2026-23096-e5af@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
uacce: fix cdev handling in the cleanup path
When cdev_device_add fails, it internally releases the cdev memory,
and if cdev_device_del is then executed, it will cause a hang error.
To fix it, we check the return value of cdev_device_add() and clear
uacce->cdev to avoid calling cdev_device_del in the uacce_remove.
The Linux kernel CVE team has assigned CVE-2026-23096 to this issue.
Affected and fixed versions
===========================
Issue introduced in 5.7 with commit 015d239ac0142ad0e26567fd890ef8d171f13709 and fixed in 6.6.122 with commit d9031575a2f8aabc53af3025dd79af313a2e046b
Issue introduced in 5.7 with commit 015d239ac0142ad0e26567fd890ef8d171f13709 and fixed in 6.12.68 with commit 98d67a1bd6caddd0a8b8c82a0b925742cf500936
Issue introduced in 5.7 with commit 015d239ac0142ad0e26567fd890ef8d171f13709 and fixed in 6.18.8 with commit bd2393ed7712513e7e2dbcb6e21464a67ff9e702
Issue introduced in 5.7 with commit 015d239ac0142ad0e26567fd890ef8d171f13709 and fixed in 6.19-rc7 with commit a3bece3678f6c88db1f44c602b2a63e84b4040ac
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-23096
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/d9031575a2f8aabc53af3025dd79af313a2e046b
https://git.kernel.org/stable/c/98d67a1bd6caddd0a8b8c82a0b925742cf500936
https://git.kernel.org/stable/c/bd2393ed7712513e7e2dbcb6e21464a67ff9e702
https://git.kernel.org/stable/c/a3bece3678f6c88db1f44c602b2a63e84b4040ac
reply other threads:[~2026-02-04 16:21 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2026020427-CVE-2026-23096-e5af@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cve@kernel.org \
--cc=gregkh@kernel.org \
--cc=linux-cve-announce@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.