From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-74457: can: peak_usb: add bounds check for USB channel index
Date: Sat, 15 Aug 2026 21:25:38 +0900 [thread overview]
Message-ID: <2026081532-CVE-2026-74457-9237@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
can: peak_usb: add bounds check for USB channel index
The channel control index ctrl_idx is derived from rx->len which comes
directly from a device USB payload. The mask 0x0f allows values 0-15, but
the array size of usb_if->dev[] is only 2. Values 2-15 cause heap
out-of-bounds read, eventually causing kernel panic in the IRQ context.
Add bounds checking for ctrl_idx before the array access in both
pcan_usb_pro_handle_canmsg() and pcan_usb_pro_handle_error().
The Linux kernel CVE team has assigned CVE-2026-74457 to this issue.
Affected and fixed versions
===========================
Issue introduced in 3.4 with commit d8a199355f8f8a0797c00d98788d7282c9ea38bd and fixed in 6.6.151 with commit 825c903ca3c98cd0cf0e3de8ab8f2604a5339b3f
Issue introduced in 3.4 with commit d8a199355f8f8a0797c00d98788d7282c9ea38bd and fixed in 6.12.103 with commit f97b7e5e1cdaae15cd95b3a360028c7929664969
Issue introduced in 3.4 with commit d8a199355f8f8a0797c00d98788d7282c9ea38bd and fixed in 6.18.44 with commit 1acab790b7cecd4e144d1d18bdfe549e282f6b0b
Issue introduced in 3.4 with commit d8a199355f8f8a0797c00d98788d7282c9ea38bd and fixed in 7.1.8 with commit 0149fdb50a30944827acf9600a2cc44de0325a7f
Issue introduced in 3.4 with commit d8a199355f8f8a0797c00d98788d7282c9ea38bd and fixed in 7.2-rc6 with commit 39132f166ca8ce00ae60d8a9068e06a60943cc4b
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-74457
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/net/can/usb/peak_usb/pcan_usb_pro.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/825c903ca3c98cd0cf0e3de8ab8f2604a5339b3f
https://git.kernel.org/stable/c/f97b7e5e1cdaae15cd95b3a360028c7929664969
https://git.kernel.org/stable/c/1acab790b7cecd4e144d1d18bdfe549e282f6b0b
https://git.kernel.org/stable/c/0149fdb50a30944827acf9600a2cc44de0325a7f
https://git.kernel.org/stable/c/39132f166ca8ce00ae60d8a9068e06a60943cc4b
reply other threads:[~2026-08-15 12:28 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=2026081532-CVE-2026-74457-9237@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.