usb: usbtmc: Fix bug in pipe direction for control transfers
In the Linux kernel, the following vulnerability has been resolved: usb: usbtmc: Fix bug in pipe direction for control transfers The syzbot fuzzer reported a minor bug in the usbtmc driver: usb 5-1: BOGUS control dir, pipe 80001e80 doesn't match bRequestType 0 WARNING: CPU: 0 PID: 3813 at drivers/usb/core/urb.c:412 usb_submit_urb+0x13a5/0x1970 drivers/usb/core/urb.c:410 Modules linked in: CPU: 0 PID: 3813 Comm: syz-executor122 Not tainted 5.17.0-rc5-syzkaller-00306-g2293be58d6a1 #0 ... Call Trace: usb_start_wait_urb+0x113/0x530 drivers/usb/core/message.c:58 usb_internal_control_msg drivers/usb/core/message.c:102 [inline] usb_control_msg+0x2a5/0x4b0 drivers/usb/core/message.c:153 usbtmc_ioctl_request drivers/usb/class/usbtmc.c:1947 [inline] The problem is that usbtmc_ioctl_request() uses usb_rcvctrlpipe() for all of its transfers, whether they are in or out. It's easy to fix.
- Products
- Kernel
- Affected versions
- Not specified
- Fixed versions
- 5.10.108, 5.15.31, 5.16.17, 5.4.187
- CVEs
- CVE-2022-48834
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 8 Nov 2026, 02:54 UTC · Revision 1
Source evidence
usb: usbtmc: Fix bug in pipe direction for control transfers
core-osv · Original sourcePublished 16 Jul 2024, 12:25 UTC
In the Linux kernel, the following vulnerability has been resolved: usb: usbtmc: Fix bug in pipe direction for control transfers The syzbot fuzzer reported a minor bug in the usbtmc driver: usb 5-1: BOGUS control dir, pipe 80001e80 doesn't match bRequestType 0 WARNING: CPU: 0 PID: 3813 at drivers/usb/core/urb.c:412 usb_submit_urb+0x13a5/0x1970 drivers/usb/core/urb.c:410 Modules linked in: CPU: 0 PID: 3813 Comm: syz-executor122 Not tainted 5.17.0-rc5-syzkaller-00306-g2293be58d6a1 #0 ... Call Trace: usb_start_wait_urb+0x113/0x530 drivers/usb/core/message.c:58 usb_internal_control_msg drivers/usb/core/message.c:102 [inline] usb_control_msg+0x2a5/0x4b0 drivers/usb/core/message.c:153 usbtmc_ioctl_request drivers/usb/class/usbtmc.c:1947 [inline] The problem is that usbtmc_ioctl_request() uses usb_rcvctrlpipe() for all of its transfers, whether they are in or out. It's easy to fix.
osv:CVE-2022-48834
Kernel
Fixed versions: 5.4.187, 5.10.108, 5.15.31, 5.16.17
Complete source record
{
"id": "3968975d2c818f5d6f5116f759c229734abf167d06e58e354c7b511274085691",
"url": "https://osv.dev/vulnerability/CVE-2022-48834",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "usb: usbtmc: Fix bug in pipe direction for control transfers",
"summary": "In the Linux kernel, the following vulnerability has been resolved: usb: usbtmc: Fix bug in pipe direction for control transfers The syzbot fuzzer reported a minor bug in the usbtmc driver: usb 5-1: BOGUS control dir, pipe 80001e80 doesn't match bRequestType 0 WARNING: CPU: 0 PID: 3813 at drivers/usb/core/urb.c:412 usb_submit_urb+0x13a5/0x1970 drivers/usb/core/urb.c:410 Modules linked in: CPU: 0 PID: 3813 Comm: syz-executor122 Not tainted 5.17.0-rc5-syzkaller-00306-g2293be58d6a1 #0 ... Call Trace: usb_start_wait_urb+0x113/0x530 drivers/usb/core/message.c:58 usb_internal_control_msg drivers/usb/core/message.c:102 [inline] usb_control_msg+0x2a5/0x4b0 drivers/usb/core/message.c:153 usbtmc_ioctl_request drivers/usb/class/usbtmc.c:1947 [inline] The problem is that usbtmc_ioctl_request() uses usb_rcvctrlpipe() for all of its transfers, whether they are in or out. It's easy to fix.",
"evidence": "osv:CVE-2022-48834",
"products": [
{
"name": {
"value": "Kernel",
"evidence": "/affected/1/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "5.4.187",
"evidence": "/affected/1/ranges"
},
{
"value": "5.10.108",
"evidence": "/affected/1/ranges"
},
{
"value": "5.15.31",
"evidence": "/affected/1/ranges"
},
{
"value": "5.16.17",
"evidence": "/affected/1/ranges"
}
],
"affected_versions": []
}
],
"severity": "unknown",
"structured": {
"id": "CVE-2022-48834",
"aliases": [
"CVE-2022-48834"
],
"affected": [
{
"ranges": [
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "658f24f4523e41cda6a389c38b763f4c0cad6fbc"
},
{
"fixed": "700a0715854c1e79a73341724ce4f5bb01abc016"
},
{
"fixed": "10a805334a11acd547602d6c4cf540a0f6ab5c6e"
},
{
"fixed": "c69aef9db878ab277068a8cc1b4bf0cf309dc2b7"
},
{
"fixed": "5f6a2d63c68c12cf61259df7c3527a0e05dce952"
},
{
"fixed": "e9b667a82cdcfe21d590344447d65daed52b353b"
}
]
}
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2022-48834.json"
}
},
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "4.20.0"
},
{
"fixed": "5.4.187"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.5.0"
},
{
"fixed": "5.10.108"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.11.0"
},
{
"fixed": "5.15.31"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.16.0"
},
{
"fixed": "5.16.17"
}
]
}
],
"package": {
"name": "Kernel",
"ecosystem": "Linux"
},
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2022-48834.json"
}
}
],
"modified": "2026-10-28T02:30:53.203866204Z",
"provider": "osv",
"references": [
"https://git.kernel.org/stable/c/10a805334a11acd547602d6c4cf540a0f6ab5c6e",
"https://git.kernel.org/stable/c/5f6a2d63c68c12cf61259df7c3527a0e05dce952",
"https://git.kernel.org/stable/c/700a0715854c1e79a73341724ce4f5bb01abc016",
"https://git.kernel.org/stable/c/c69aef9db878ab277068a8cc1b4bf0cf309dc2b7",
"https://git.kernel.org/stable/c/e9b667a82cdcfe21d590344447d65daed52b353b",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2022/48xxx/CVE-2022-48834.json",
"https://nvd.nist.gov/vuln/detail/CVE-2022-48834",
"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
],
"provider_metadata": {
"cna_assigner": "Linux",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2022/48xxx/CVE-2022-48834.json"
}
},
"related_cves": [
{
"value": "CVE-2022-48834",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": null
},
"source_id": "core-osv",
"document_id": 521983,
"published_at": "2024-07-16T12:25:07.249+00:00"
}