From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: CVE-2025-21797: HID: corsair-void: Add missing delayed work cancel for headset status
Date: Wed, 26 Feb 2025 18:17:53 -0800 [thread overview]
Message-ID: <2025022610-CVE-2025-21797-04ee@gregkh> (raw)
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
HID: corsair-void: Add missing delayed work cancel for headset status
The cancel_delayed_work_sync() call was missed, causing a use-after-free
in corsair_void_remove().
The Linux kernel CVE team has assigned CVE-2025-21797 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.13 with commit 6ea2a6fd3872e60a4d500b548ad65ed94e459ddd and fixed in 6.13.4 with commit 2dcb56a0a4da6946f6c18288da595c13e0d2af86
Issue introduced in 6.13 with commit 6ea2a6fd3872e60a4d500b548ad65ed94e459ddd and fixed in 6.14-rc3 with commit 48e487b002891eb0aeaec704c9bed51f028deff1
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-2025-21797
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/hid/hid-corsair-void.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/2dcb56a0a4da6946f6c18288da595c13e0d2af86
https://git.kernel.org/stable/c/48e487b002891eb0aeaec704c9bed51f028deff1
reply other threads:[~2025-02-27 2:19 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=2025022610-CVE-2025-21797-04ee@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cve@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.