can: gs_usb: gs_usb_open/close(): fix memory leak
In the Linux kernel, the following vulnerability has been resolved: can: gs_usb: gs_usb_open/close(): fix memory leak The gs_usb driver appears to suffer from a malady common to many USB CAN adapter drivers in that it performs usb_alloc_coherent() to allocate a number of USB request blocks (URBs) for RX, and then later relies on usb_kill_anchored_urbs() to free them, but this doesn't actually free them. As a result, this may be leaking DMA memory that's been used by the driver. This commit is an adaptation of the techniques found in the esd_usb2 driver where a similar design pattern led to a memory leak. It explicitly frees the RX URBs and their DMA memory via a call to usb_free_coherent(). Since the RX URBs were allocated in the gs_can_open(), we remove them in gs_can_close() rather than in the disconnect function as was done in esd_usb2. For more information, see the 928150fad41b ("can: esd_usb2: fix memory leak").
- Products
- Kernel
- Affected versions
- Not specified
- Fixed versions
- 4.14.288, 4.19.252, 4.9.323, 5.10.130, 5.15.54, 5.18.11, 5.4.205
- CVEs
- CVE-2022-49661
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 4 Nov 2026, 16:59 UTC · Revision 1
Source evidence
can: gs_usb: gs_usb_open/close(): fix memory leak
core-osv · Original sourcePublished 26 Feb 2025, 02:23 UTC
In the Linux kernel, the following vulnerability has been resolved: can: gs_usb: gs_usb_open/close(): fix memory leak The gs_usb driver appears to suffer from a malady common to many USB CAN adapter drivers in that it performs usb_alloc_coherent() to allocate a number of USB request blocks (URBs) for RX, and then later relies on usb_kill_anchored_urbs() to free them, but this doesn't actually free them. As a result, this may be leaking DMA memory that's been used by the driver. This commit is an adaptation of the techniques found in the esd_usb2 driver where a similar design pattern led to a memory leak. It explicitly frees the RX URBs and their DMA memory via a call to usb_free_coherent(). Since the RX URBs were allocated in the gs_can_open(), we remove them in gs_can_close() rather than in the disconnect function as was done in esd_usb2. For more information, see the 928150fad41b ("can: esd_usb2: fix memory leak").
osv:CVE-2022-49661
Kernel
Fixed versions: 4.9.323, 4.14.288, 4.19.252, 5.4.205, 5.10.130, 5.15.54, 5.18.11
Complete source record
{
"id": "cb6aad1b99462fa1e24d00ec7183a77263b3212ff9783e3eb69282234a1c42bf",
"url": "https://osv.dev/vulnerability/CVE-2022-49661",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "can: gs_usb: gs_usb_open/close(): fix memory leak",
"summary": "In the Linux kernel, the following vulnerability has been resolved: can: gs_usb: gs_usb_open/close(): fix memory leak The gs_usb driver appears to suffer from a malady common to many USB CAN adapter drivers in that it performs usb_alloc_coherent() to allocate a number of USB request blocks (URBs) for RX, and then later relies on usb_kill_anchored_urbs() to free them, but this doesn't actually free them. As a result, this may be leaking DMA memory that's been used by the driver. This commit is an adaptation of the techniques found in the esd_usb2 driver where a similar design pattern led to a memory leak. It explicitly frees the RX URBs and their DMA memory via a call to usb_free_coherent(). Since the RX URBs were allocated in the gs_can_open(), we remove them in gs_can_close() rather than in the disconnect function as was done in esd_usb2. For more information, see the 928150fad41b (\"can: esd_usb2: fix memory leak\").",
"evidence": "osv:CVE-2022-49661",
"products": [
{
"name": {
"value": "Kernel",
"evidence": "/affected/1/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "4.9.323",
"evidence": "/affected/1/ranges"
},
{
"value": "4.14.288",
"evidence": "/affected/1/ranges"
},
{
"value": "4.19.252",
"evidence": "/affected/1/ranges"
},
{
"value": "5.4.205",
"evidence": "/affected/1/ranges"
},
{
"value": "5.10.130",
"evidence": "/affected/1/ranges"
},
{
"value": "5.15.54",
"evidence": "/affected/1/ranges"
},
{
"value": "5.18.11",
"evidence": "/affected/1/ranges"
}
],
"affected_versions": []
}
],
"severity": "unknown",
"structured": {
"id": "CVE-2022-49661",
"aliases": [
"CVE-2022-49661"
],
"affected": [
{
"ranges": [
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "d08e973a77d128b25e01a08c34d89593fdf222da"
},
{
"fixed": "339fa9f80d3b94177a7a459c6d115d3b56007d5a"
},
{
"fixed": "c1d806bc29ff7ffe0e2a023583c8720ed96cb0b0"
},
{
"fixed": "d91492638b054f4a359621ef216242be5973ed6b"
},
{
"fixed": "6f655b5e13fa4b27e915b6c209ac0da74fd75963"
},
{
"fixed": "d0b8e223998866b3e7b2895927d4e9689b0a80d8"
},
{
"fixed": "0e60230bc64355c80abe993d1719fdb318094e20"
},
{
"fixed": "ffb6cc6601ec7c8fa963dcf76025df4a02f2cf5c"
},
{
"fixed": "2bda24ef95c0311ab93bda00db40486acf30bd0a"
}
]
}
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2022-49661.json"
}
},
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "3.16.0"
},
{
"fixed": "4.9.323"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "4.10.0"
},
{
"fixed": "4.14.288"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "4.15.0"
},
{
"fixed": "4.19.252"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "4.20.0"
},
{
"fixed": "5.4.205"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.5.0"
},
{
"fixed": "5.10.130"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.11.0"
},
{
"fixed": "5.15.54"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.16.0"
},
{
"fixed": "5.18.11"
}
]
}
],
"package": {
"name": "Kernel",
"ecosystem": "Linux"
},
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2022-49661.json"
}
}
],
"modified": "2026-10-28T02:30:37.968509820Z",
"provider": "osv",
"references": [
"https://git.kernel.org/stable/c/0e60230bc64355c80abe993d1719fdb318094e20",
"https://git.kernel.org/stable/c/2bda24ef95c0311ab93bda00db40486acf30bd0a",
"https://git.kernel.org/stable/c/339fa9f80d3b94177a7a459c6d115d3b56007d5a",
"https://git.kernel.org/stable/c/6f655b5e13fa4b27e915b6c209ac0da74fd75963",
"https://git.kernel.org/stable/c/c1d806bc29ff7ffe0e2a023583c8720ed96cb0b0",
"https://git.kernel.org/stable/c/d0b8e223998866b3e7b2895927d4e9689b0a80d8",
"https://git.kernel.org/stable/c/d91492638b054f4a359621ef216242be5973ed6b",
"https://git.kernel.org/stable/c/ffb6cc6601ec7c8fa963dcf76025df4a02f2cf5c",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2022/49xxx/CVE-2022-49661.json",
"https://nvd.nist.gov/vuln/detail/CVE-2022-49661",
"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/49xxx/CVE-2022-49661.json"
}
},
"related_cves": [
{
"value": "CVE-2022-49661",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": null
},
"source_id": "core-osv",
"document_id": 505056,
"published_at": "2025-02-26T02:23:58.352+00:00"
}