OESA-2026-1762 (CVE-2023-53548)
Vulnerability from osv_openeuler – Published: 2026-03-27 11:10 – Updated: 2026-08-06 11:10 – Source websiteThe Linux Kernel, the operating system core itself.
Security Fix(es):
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.(CVE-2023-53548)
| URL | Type | |
|---|---|---|
{
"affected": [
{
"ecosystem_specific": {
"aarch64": [
"bpftool-4.19.90-2603.3.0.0366.oe2003sp4.aarch64.rpm",
"bpftool-debuginfo-4.19.90-2603.3.0.0366.oe2003sp4.aarch64.rpm",
"kernel-4.19.90-2603.3.0.0366.oe2003sp4.aarch64.rpm",
"kernel-debuginfo-4.19.90-2603.3.0.0366.oe2003sp4.aarch64.rpm",
"kernel-debugsource-4.19.90-2603.3.0.0366.oe2003sp4.aarch64.rpm",
"kernel-devel-4.19.90-2603.3.0.0366.oe2003sp4.aarch64.rpm",
"kernel-source-4.19.90-2603.3.0.0366.oe2003sp4.aarch64.rpm",
"kernel-tools-4.19.90-2603.3.0.0366.oe2003sp4.aarch64.rpm",
"kernel-tools-debuginfo-4.19.90-2603.3.0.0366.oe2003sp4.aarch64.rpm",
"kernel-tools-devel-4.19.90-2603.3.0.0366.oe2003sp4.aarch64.rpm",
"perf-4.19.90-2603.3.0.0366.oe2003sp4.aarch64.rpm",
"perf-debuginfo-4.19.90-2603.3.0.0366.oe2003sp4.aarch64.rpm",
"python2-perf-4.19.90-2603.3.0.0366.oe2003sp4.aarch64.rpm",
"python2-perf-debuginfo-4.19.90-2603.3.0.0366.oe2003sp4.aarch64.rpm",
"python3-perf-4.19.90-2603.3.0.0366.oe2003sp4.aarch64.rpm",
"python3-perf-debuginfo-4.19.90-2603.3.0.0366.oe2003sp4.aarch64.rpm"
],
"src": [
"kernel-4.19.90-2603.3.0.0366.oe2003sp4.src.rpm"
],
"x86_64": [
"bpftool-4.19.90-2603.3.0.0366.oe2003sp4.x86_64.rpm",
"bpftool-debuginfo-4.19.90-2603.3.0.0366.oe2003sp4.x86_64.rpm",
"kernel-4.19.90-2603.3.0.0366.oe2003sp4.x86_64.rpm",
"kernel-debuginfo-4.19.90-2603.3.0.0366.oe2003sp4.x86_64.rpm",
"kernel-debugsource-4.19.90-2603.3.0.0366.oe2003sp4.x86_64.rpm",
"kernel-devel-4.19.90-2603.3.0.0366.oe2003sp4.x86_64.rpm",
"kernel-source-4.19.90-2603.3.0.0366.oe2003sp4.x86_64.rpm",
"kernel-tools-4.19.90-2603.3.0.0366.oe2003sp4.x86_64.rpm",
"kernel-tools-debuginfo-4.19.90-2603.3.0.0366.oe2003sp4.x86_64.rpm",
"kernel-tools-devel-4.19.90-2603.3.0.0366.oe2003sp4.x86_64.rpm",
"perf-4.19.90-2603.3.0.0366.oe2003sp4.x86_64.rpm",
"perf-debuginfo-4.19.90-2603.3.0.0366.oe2003sp4.x86_64.rpm",
"python2-perf-4.19.90-2603.3.0.0366.oe2003sp4.x86_64.rpm",
"python2-perf-debuginfo-4.19.90-2603.3.0.0366.oe2003sp4.x86_64.rpm",
"python3-perf-4.19.90-2603.3.0.0366.oe2003sp4.x86_64.rpm",
"python3-perf-debuginfo-4.19.90-2603.3.0.0366.oe2003sp4.x86_64.rpm"
]
},
"package": {
"ecosystem": "openEuler:20.03-LTS-SP4",
"name": "kernel",
"purl": "pkg:rpm/openEuler/kernel\u0026distro=openEuler-20.03-LTS-SP4"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "4.19.90-2603.3.0.0366.oe2003sp4"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"database_specific": {
"severity": "Medium"
},
"details": "The Linux Kernel, the operating system core itself.\r\n\r\nSecurity Fix(es):\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: usbnet: Fix WARNING in usbnet_start_xmit/usb_submit_urb\n\nThe syzbot fuzzer identified a problem in the usbnet driver:\n\nusb 1-1: BOGUS urb xfer, pipe 3 != type 1\nWARNING: CPU: 0 PID: 754 at drivers/usb/core/urb.c:504 usb_submit_urb+0xed6/0x1880 drivers/usb/core/urb.c:504\nModules linked in:\nCPU: 0 PID: 754 Comm: kworker/0:2 Not tainted 6.4.0-rc7-syzkaller-00014-g692b7dc87ca6 #0\nHardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/27/2023\nWorkqueue: mld mld_ifc_work\nRIP: 0010:usb_submit_urb+0xed6/0x1880 drivers/usb/core/urb.c:504\nCode: 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 \u0026lt;0f\u0026gt; 0b e9 58 f8 ff ff e8 fe b3 5b fb 48 81 c5 c0 05 00 00 e9 84 f7\nRSP: 0018:ffffc9000463f568 EFLAGS: 00010086\nRAX: 0000000000000000 RBX: 0000000000000001 RCX: 0000000000000000\nRDX: ffff88801eb28000 RSI: ffffffff814c03b7 RDI: 0000000000000001\nRBP: ffff8881443b7190 R08: 0000000000000001 R09: 0000000000000000\nR10: 0000000000000000 R11: 0000000000000001 R12: 0000000000000003\nR13: ffff88802a77cb18 R14: 0000000000000003 R15: ffff888018262500\nFS: 0000000000000000(0000) GS:ffff8880b9800000(0000) knlGS:0000000000000000\nCS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 0000556a99c15a18 CR3: 0000000028c71000 CR4: 0000000000350ef0\nCall Trace:\n \u0026lt;TASK\u0026gt;\n usbnet_start_xmit+0xfe5/0x2190 drivers/net/usb/usbnet.c:1453\n __netdev_start_xmit include/linux/netdevice.h:4918 [inline]\n netdev_start_xmit include/linux/netdevice.h:4932 [inline]\n xmit_one net/core/dev.c:3578 [inline]\n dev_hard_start_xmit+0x187/0x700 net/core/dev.c:3594\n...\n\nThis bug is caused by the fact that usbnet trusts the bulk endpoint\naddresses its probe routine receives in the driver_info structure, and\nit does not check to see that these endpoints actually exist and have\nthe expected type and directions.\n\nThe fix is simply to add such a check.(CVE-2023-53548)",
"id": "OESA-2026-1762",
"modified": "2026-08-06T11:10:47Z",
"published": "2026-03-27T11:10:47Z",
"references": [
{
"type": "ADVISORY",
"url": "https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2026-1762"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2023-53548"
}
],
"schema_version": "1.7.2",
"severity": [
{
"score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H",
"type": "CVSS_V3"
}
],
"summary": "kernel security update",
"upstream": [
"CVE-2023-53548"
]
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.