From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-89627: HID: roccat: free buffered reports when destroying device
Date: Fri, 11 Sep 2026 21:45:16 +0200 [thread overview]
Message-ID: <2026091138-CVE-2026-89627-b945@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
HID: roccat: free buffered reports when destroying device
roccat_report_event() duplicates each report with kmemdup() and stores
the allocation in a circular-buffer slot. The allocation is released only
when that slot is reused.
The device destruction paths free struct roccat_device without releasing
reports still stored in cbuf[]. This makes those allocations unreachable
and leaks up to ROCCAT_CBUF_SIZE report buffers per device.
Add a small destructor that frees every buffered report before freeing the
device, and use it in both paths that can destroy a registered device.
The Linux kernel CVE team has assigned CVE-2026-89627 to this issue.
Affected and fixed versions
===========================
Issue introduced in 2.6.35 with commit 206f5f2fcb5ff5bb0c60f9e9189937f3ca03e378 and fixed in 6.12.109 with commit 943b8dc2c6044c01e36395f51bb809a4b6bdfd22
Issue introduced in 2.6.35 with commit 206f5f2fcb5ff5bb0c60f9e9189937f3ca03e378 and fixed in 6.18.50 with commit da00eac19feef209c9591e48c860afc2014603be
Issue introduced in 2.6.35 with commit 206f5f2fcb5ff5bb0c60f9e9189937f3ca03e378 and fixed in 7.2.4 with commit fbb5a60f5c31b5625f0d89a79912fbcb2559289b
Issue introduced in 2.6.35 with commit 206f5f2fcb5ff5bb0c60f9e9189937f3ca03e378 and fixed in 7.3-rc1 with commit bbff0ccbff360a5498075525005f6a913239a3d7
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-89627
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-roccat.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/943b8dc2c6044c01e36395f51bb809a4b6bdfd22
https://git.kernel.org/stable/c/da00eac19feef209c9591e48c860afc2014603be
https://git.kernel.org/stable/c/fbb5a60f5c31b5625f0d89a79912fbcb2559289b
https://git.kernel.org/stable/c/bbff0ccbff360a5498075525005f6a913239a3d7
reply other threads:[~2026-09-11 20:00 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=2026091138-CVE-2026-89627-b945@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.