From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-99331: HID: cp2112: validate response report lengths
Date: Thu, 19 Nov 2026 15:23:49 +0100 [thread overview]
Message-ID: <2026111944-CVE-2026-99331-5ee2@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
HID: cp2112: validate response report lengths
The HID core invokes raw_event callbacks before validating the report
length. cp2112_raw_event() reads every field of a transfer status response
without checking size. For a data response, it reads the length at offset
two and copies that many bytes from offset three, again without ensuring
that the input report contains them.
Require a complete transfer status structure. For data responses, first
require the header and then ensure the clamped payload length fits in the
received report before copying it.
Commit 47669bec44fe ("HID: asus: refactor the two workqueues and init
sequence") added the same kind of raw_event length validation to hid-asus.
The Linux kernel CVE team has assigned CVE-2026-99331 to this issue.
Affected and fixed versions
===========================
Issue introduced in 3.15 with commit e932d817866770d456815c9a84b7ed94f0589d80 and fixed in 6.12.117 with commit e178cdd6ed0f4ac20afc9220eceae3a89e6719af
Issue introduced in 3.15 with commit e932d817866770d456815c9a84b7ed94f0589d80 and fixed in 6.18.61 with commit 94d0e789d8b0d2ea8e25ed5ff2fe2648e11f2297
Issue introduced in 3.15 with commit e932d817866770d456815c9a84b7ed94f0589d80 and fixed in 7.3.2 with commit 773307dd4c3e8c27eb31650af2df2d91cba22de8
Issue introduced in 3.15 with commit e932d817866770d456815c9a84b7ed94f0589d80 and fixed in 7.4-rc1 with commit fc54e71a063c0dcc4bceba6d0f71805a9b84082d
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-99331
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-cp2112.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/e178cdd6ed0f4ac20afc9220eceae3a89e6719af
https://git.kernel.org/stable/c/94d0e789d8b0d2ea8e25ed5ff2fe2648e11f2297
https://git.kernel.org/stable/c/773307dd4c3e8c27eb31650af2df2d91cba22de8
https://git.kernel.org/stable/c/fc54e71a063c0dcc4bceba6d0f71805a9b84082d
reply other threads:[~2026-11-19 14:27 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=2026111944-CVE-2026-99331-5ee2@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.