All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-74455: can: peak_usb: validate uCAN receive record lengths
Date: Sat, 15 Aug 2026 21:25:36 +0900	[thread overview]
Message-ID: <2026081531-CVE-2026-74455-b371@gregkh> (raw)

From: Greg Kroah-Hartman <gregkh@kernel.org>

Description
===========

In the Linux kernel, the following vulnerability has been resolved:

can: peak_usb: validate uCAN receive record lengths

pcan_usb_fd_decode_buf() walks uCAN records packed in one USB
receive buffer.

Require each record to contain the fixed header for its type, and verify
CAN payload bytes before copying them into the skb.

The Linux kernel CVE team has assigned CVE-2026-74455 to this issue.


Affected and fixed versions
===========================

	Issue introduced in 4.0 with commit 0a25e1f4f18566b750ebd3ae995af64e23111e63 and fixed in 6.6.151 with commit 6067c878e38d02a3d5c43497347e143f85c9064a
	Issue introduced in 4.0 with commit 0a25e1f4f18566b750ebd3ae995af64e23111e63 and fixed in 6.12.103 with commit 2c8f08f3641a074da40acf05baa5a18ae2739260
	Issue introduced in 4.0 with commit 0a25e1f4f18566b750ebd3ae995af64e23111e63 and fixed in 6.18.44 with commit 2427ef427bdd78d862c7c76597bfd9eda88b81f1
	Issue introduced in 4.0 with commit 0a25e1f4f18566b750ebd3ae995af64e23111e63 and fixed in 7.1.8 with commit d9c115948c3dd5fcc2d0245cec5eb76c098503c8
	Issue introduced in 4.0 with commit 0a25e1f4f18566b750ebd3ae995af64e23111e63 and fixed in 7.2-rc6 with commit 93fcab2c6968446316bbb49548848df604d6346f

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-74455
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_fd.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/6067c878e38d02a3d5c43497347e143f85c9064a
	https://git.kernel.org/stable/c/2c8f08f3641a074da40acf05baa5a18ae2739260
	https://git.kernel.org/stable/c/2427ef427bdd78d862c7c76597bfd9eda88b81f1
	https://git.kernel.org/stable/c/d9c115948c3dd5fcc2d0245cec5eb76c098503c8
	https://git.kernel.org/stable/c/93fcab2c6968446316bbb49548848df604d6346f

                 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=2026081531-CVE-2026-74455-b371@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.