From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-89629: HID: corsair-void: Check size of status and firmware events before reading them
Date: Fri, 11 Sep 2026 21:45:18 +0200 [thread overview]
Message-ID: <2026091139-CVE-2026-89629-0f78@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
HID: corsair-void: Check size of status and firmware events before reading them
Malformed status and firmware events could cause an out-of-bounds read since
the size wasn't being checked. Check the size and warn on unexpected values to
avoid this.
The Linux kernel CVE team has assigned CVE-2026-89629 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.13 with commit 6ea2a6fd3872e60a4d500b548ad65ed94e459ddd and fixed in 6.18.50 with commit 79465a30050dad62b3c9e7796368db75dac6fa0d
Issue introduced in 6.13 with commit 6ea2a6fd3872e60a4d500b548ad65ed94e459ddd and fixed in 7.2.4 with commit 0329354abba357340ee88452425857f3718b5807
Issue introduced in 6.13 with commit 6ea2a6fd3872e60a4d500b548ad65ed94e459ddd and fixed in 7.3-rc1 with commit 08d8814521885e67b1bdf6a3036ee264e3e58377
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-89629
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/79465a30050dad62b3c9e7796368db75dac6fa0d
https://git.kernel.org/stable/c/0329354abba357340ee88452425857f3718b5807
https://git.kernel.org/stable/c/08d8814521885e67b1bdf6a3036ee264e3e58377
reply other threads:[~2026-09-11 20:01 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=2026091139-CVE-2026-89629-0f78@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.