From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-64547: net: usb: net1080: validate packet_len before pad-byte access in rx_fixup
Date: Mon, 27 Jul 2026 22:10:45 +0200 [thread overview]
Message-ID: <2026072736-CVE-2026-64547-4deb@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
net: usb: net1080: validate packet_len before pad-byte access in rx_fixup
For an even packet_len, net1080_rx_fixup() reads the pad byte at
skb->data[packet_len] before the skb->len != packet_len check further
down, and packet_len is only bounded against NC_MAX_PACKET. A malicious
NetChip 1080 device can send a short frame advertising a large even
packet_len (e.g. 0x4000), so the pad-byte read lands past the end of the
skb:
BUG: KASAN: slab-out-of-bounds in net1080_rx_fixup
Read of size 1 at addr ffff8880106c83c6 by task ksoftirqd/0/14
...
net1080_rx_fixup (drivers/net/usb/net1080.c:384)
usbnet_bh (drivers/net/usb/usbnet.c:1589)
process_one_work (kernel/workqueue.c:3322)
bh_worker (kernel/workqueue.c:3708)
tasklet_action (kernel/softirq.c:965)
handle_softirqs (kernel/softirq.c:622)
...
Reject the frame when packet_len >= skb->len before reading.
The Linux kernel CVE team has assigned CVE-2026-64547 to this issue.
Affected and fixed versions
===========================
Issue introduced in 2.6.14 with commit 904813cd8a0b334189da285bb05af0b18b062502 and fixed in 5.10.261 with commit f42217fa7d535e9ec4151f7971f06f6ea65e850a
Issue introduced in 2.6.14 with commit 904813cd8a0b334189da285bb05af0b18b062502 and fixed in 5.15.212 with commit c087749815379e9af2fdbeb08bfc33870b103958
Issue introduced in 2.6.14 with commit 904813cd8a0b334189da285bb05af0b18b062502 and fixed in 6.1.178 with commit e4a87126c085b097d29e17e3b7647295bba8be7c
Issue introduced in 2.6.14 with commit 904813cd8a0b334189da285bb05af0b18b062502 and fixed in 6.6.145 with commit 685e92934f11d5e215dad58813e2f9955ac2f436
Issue introduced in 2.6.14 with commit 904813cd8a0b334189da285bb05af0b18b062502 and fixed in 6.12.97 with commit 4dc8484be3302d187274364820d3bef6c62bde32
Issue introduced in 2.6.14 with commit 904813cd8a0b334189da285bb05af0b18b062502 and fixed in 6.18.40 with commit b153cfe84b1340c69a13d0957665a2bfcf21239c
Issue introduced in 2.6.14 with commit 904813cd8a0b334189da285bb05af0b18b062502 and fixed in 7.1.5 with commit ea866cab12db1a2100b400a8b03569e5bc0ee29a
Issue introduced in 2.6.14 with commit 904813cd8a0b334189da285bb05af0b18b062502 and fixed in 7.2-rc3 with commit 03f384bc0cb8d4a1301d4f5b0baef2d980258383
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-64547
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/usb/net1080.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/f42217fa7d535e9ec4151f7971f06f6ea65e850a
https://git.kernel.org/stable/c/c087749815379e9af2fdbeb08bfc33870b103958
https://git.kernel.org/stable/c/e4a87126c085b097d29e17e3b7647295bba8be7c
https://git.kernel.org/stable/c/685e92934f11d5e215dad58813e2f9955ac2f436
https://git.kernel.org/stable/c/4dc8484be3302d187274364820d3bef6c62bde32
https://git.kernel.org/stable/c/b153cfe84b1340c69a13d0957665a2bfcf21239c
https://git.kernel.org/stable/c/ea866cab12db1a2100b400a8b03569e5bc0ee29a
https://git.kernel.org/stable/c/03f384bc0cb8d4a1301d4f5b0baef2d980258383
reply other threads:[~2026-07-27 20:10 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=2026072736-CVE-2026-64547-4deb@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.