CVE-2023-53548 json
net: usbnet: Fix WARNING in usbnet_start_xmit/usb_submit_urb
published 2025-10-04 13 mo ago modified 2026-11-05 3 d ago also EUVD-2025-32325
- cvss
- 5.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 5%
- public exploits
- 0
- none known
Summary
In the Linux kernel, the following vulnerability has been resolved:
net: usbnet: Fix WARNING in usbnet_start_xmit/usb_submit_urb
The syzbot fuzzer identified a problem in the usbnet driver:
usb 1-1: BOGUS urb xfer, pipe 3 != type 1 WARNING: CPU: 0 PID: 754 at drivers/usb/core/urb.c:504 usb_submit_urb+0xed6/0x1880 drivers/usb/core/urb.c:504 Modules linked in: CPU: 0 PID: 754 Comm: kworker/0:2 Not tainted 6.4.0-rc7-syzkaller-00014-g692b7dc87ca6 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/27/2023 Workqueue: mld mld_ifc_work RIP: 0010:usb_submit_urb+0xed6/0x1880 drivers/usb/core/urb.c:504 Code: 7c 24 18 e8 2c b4 5b fb 48 8b 7c 24 18 e8 42 07 f0 fe 41 89 d8 44 89 e1 4c 89 ea 48 89 c6 48 c7 c7 a0 c9 fc 8a e8 5a 6f 23 fb <0f> 0b e9 58 f8 ff ff e8 fe b3 5b fb 48 81 c5 c0 05 00 00 e9 84 f7 RSP: 0018:ffffc9000463f568 EFLAGS: 00010086 RAX: 0000000000000000 RBX: 0000000000000001 RCX: 0000000000000000 RDX: ffff88801eb28000 RSI: ffffffff814c03b7 RDI: 0000000000000001 RBP: ffff8881443b7190 R08: 0000000000000001 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000001 R12: 0000000000000003 R13: ffff88802a77cb18 R14: 0000000000000003 R15: ffff888018262500 FS: 0000000000000000(0000) GS:ffff8880b9800000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000556a99c15a18 CR3: 0000000028c71000 CR4: 0000000000350ef0 Call Trace: <TASK> usbnet_start_xmit+0xfe5/0x2190 drivers/net/usb/usbnet.c:1453 __netdev_start_xmit include/linux/netdevice.h:4918 [inline] netdev_start_xmit include/linux/netdevice.h:4932 [inline] xmit_one net/core/dev.c:3578 [inline] dev_hard_start_xmit+0x187/0x700 net/core/dev.c:3594 ...
This bug is caused by the fact that usbnet trusts the bulk endpoint addresses its probe routine receives in the driver_info structure, and it does not check to see that these endpoints actually exist and have the expected type and directions.
The fix is simply to add such a check.
Patch / fix
- Linux Linux 4.14.322, 4.19.291, 5.4.253, 5.10.190, 5.15.126, 6.1.45, 6.4.10, 6.5
- linux Debian 12 6.1.52-1
- linux Debian 14, Debian 13 6.4.11-1
debian advisories DEBIAN-CVE-2023-53548
- linux Ubuntu 20.04 LTS 5.4.0-169.187
- linux Ubuntu 22.04 LTS 5.15.0-88.98
- linux-aws Ubuntu 20.04 LTS 5.4.0-1116.126
- linux-aws Ubuntu 22.04 LTS 5.15.0-1049.54
- linux-gcp Ubuntu 20.04 LTS 5.4.0-1120.129
- linux-gcp Ubuntu 22.04 LTS 5.15.0-1046.54
- linux-gke Ubuntu 22.04 LTS 5.15.0-1046.51
- linux-ibm Ubuntu 20.04 LTS 5.4.0-1063.68
ubuntu advisories UBUNTU-CVE-2023-53548
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- kernel-64kb SLES 15 SP5-LTSS, SLE High Performance Computing 15 SP5-LTSS, SLE High Performance Computing 15 SP5-ESPOS 5.14.21-150500.55.127.1
- kernel-syms SLES for SAP 15 SP5, SLES 15 SP5-LTSS, SLE High Performance Computing 15 SP5-LTSS +1 more 5.14.21-150500.55.127.1
- kernel-source SLES for SAP 15 SP5, SLES 15 SP5-LTSS, SLE Micro 5.5 +2 more 5.14.21-150500.55.127.1
- kernel-default SLES for SAP 15 SP5, SLES 15 SP5-LTSS, SLE Micro 5.5 +3 more 5.14.21-150500.55.127.1
- kernel-obs-build SLES for SAP 15 SP5, SLES 15 SP5-LTSS, SLE High Performance Computing 15 SP5-LTSS +1 more 5.14.21-150500.55.127.1
- kernel-default-base SLES for SAP 15 SP5, SLES 15 SP5-LTSS, SLE Micro 5.5 +2 more 5.14.21-150500.55.127.1.150500.6.61.1
- kernel-rt Real Time Module 15 SP6, openSUSE Leap 15.6 6.4.0-150600.10.58.1
- kernel-syms-rt Real Time Module 15 SP6, openSUSE Leap 15.6 6.4.0-150600.10.58.1
suse advisories SUSE-SU-2025:4320-1SUSE-SU-2025:4301-1SUSE-SU-2025:21052-1SUSE-SU-2025:21064-1SUSE-SU-2025:4189-1SUSE-SU-2025:4149-1
- git.kernel.org/stable/c/a0715d04cf687a7e21f0d6ac8c1d479294a3f6f8 commit
- git.kernel.org/stable/c/53c250ea57cf03af41339234b9855ae284f9db91 commit
- git.kernel.org/stable/c/a05ac5d00eb7fcb2fda806caa4f56e88df6bc6bb commit
- git.kernel.org/stable/c/ec0d0be41721aca683c5606354a58ee2c687e3f8 commit
- git.kernel.org/stable/c/27d0f755d649d388fcd12f01436c9a33289e14e3 commit
- git.kernel.org/stable/c/1bebbd9b8037a9cc75984317cb495dec4824c399 commit
- git.kernel.org/stable/c/0dd3e0c31bf3e933fb85faf1443833aef90b8e46 commit
- git.kernel.org/stable/c/5e1627cb43ddf1b24b92eb26f8d958a3f5676ccb commit
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2023-53548 updated cvss 4.3
kernel: net: usbnet: Fix WARNING in usbnet_start_xmit/usb_submit_urb
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 moreaffected: no fix planned “Out of support scope”
-
Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 moreaffected: no fix available “Fix deferred”
-
Red Hat Enterprise Linux 10 kernelnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 3 d ago
Exploit prediction
0.16% chance of exploitation in the next 30 days, higher than 5% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
Affected products
- Linux Linux
Classification
- Technology feeds
References
-
git.kernel.org
/stable/c/a0715d04cf687a7e21f0d6ac8c1d479294a3f6f8
patch
-
git.kernel.org
/stable/c/53c250ea57cf03af41339234b9855ae284f9db91
patch
-
git.kernel.org
/stable/c/a05ac5d00eb7fcb2fda806caa4f56e88df6bc6bb
patch
-
git.kernel.org
/stable/c/ec0d0be41721aca683c5606354a58ee2c687e3f8
patch
-
git.kernel.org
/stable/c/27d0f755d649d388fcd12f01436c9a33289e14e3
patch
-
git.kernel.org
/stable/c/1bebbd9b8037a9cc75984317cb495dec4824c399
patch
-
git.kernel.org
/stable/c/0dd3e0c31bf3e933fb85faf1443833aef90b8e46
patch
-
git.kernel.org
/stable/c/5e1627cb43ddf1b24b92eb26f8d958a3f5676ccb
patch
Sources
- CVE List CVE-2023-53548
- NVD CVE-2023-53548
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.