CVE-2023-53529 (GCVE-0-2023-53529)
Vulnerability from cvelistv5
Published
2025-10-01 11:46
Modified
2025-10-02 07:04
Severity ?
VLAI Severity ?
EPSS score ?
Summary
In the Linux kernel, the following vulnerability has been resolved:
wifi: rtw88: Fix memory leak in rtw88_usb
Kmemleak shows the following leak arising from routine in the usb
probe routine:
unreferenced object 0xffff895cb29bba00 (size 512):
comm "(udev-worker)", pid 534, jiffies 4294903932 (age 102751.088s)
hex dump (first 32 bytes):
77 30 30 30 00 00 00 00 02 2f 2d 2b 30 00 00 00 w000...../-+0...
02 00 2a 28 00 00 00 00 ff 55 ff ff ff 00 00 00 ..*(.....U......
backtrace:
[<ffffffff9265fa36>] kmalloc_trace+0x26/0x90
[<ffffffffc17eec41>] rtw_usb_probe+0x2f1/0x680 [rtw_usb]
[<ffffffffc03e19fd>] usb_probe_interface+0xdd/0x2e0 [usbcore]
[<ffffffff92b4f2fe>] really_probe+0x18e/0x3d0
[<ffffffff92b4f5b8>] __driver_probe_device+0x78/0x160
[<ffffffff92b4f6bf>] driver_probe_device+0x1f/0x90
[<ffffffff92b4f8df>] __driver_attach+0xbf/0x1b0
[<ffffffff92b4d350>] bus_for_each_dev+0x70/0xc0
[<ffffffff92b4e51e>] bus_add_driver+0x10e/0x210
[<ffffffff92b50935>] driver_register+0x55/0xf0
[<ffffffffc03e0708>] usb_register_driver+0x88/0x140 [usbcore]
[<ffffffff92401153>] do_one_initcall+0x43/0x210
[<ffffffff9254f42a>] do_init_module+0x4a/0x200
[<ffffffff92551d1c>] __do_sys_finit_module+0xac/0x120
[<ffffffff92ee6626>] do_syscall_64+0x56/0x80
[<ffffffff9300006a>] entry_SYSCALL_64_after_hwframe+0x46/0xb0
The leak was verified to be real by unloading the driver, which resulted
in a dangling pointer to the allocation.
The allocated memory is freed in rtw_usb_intf_deinit().
References
Impacted products
{
"containers": {
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"drivers/net/wireless/realtek/rtw88/usb.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "5bba1ad561a8b5bb14704d8f511cf10466336e3d",
"status": "affected",
"version": "e3037485c68ec1a299ff41160d8fedbd4abc29b9",
"versionType": "git"
},
{
"lessThan": "59a3a312009723e3e5082899655fdcc420e2b47a",
"status": "affected",
"version": "e3037485c68ec1a299ff41160d8fedbd4abc29b9",
"versionType": "git"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"drivers/net/wireless/realtek/rtw88/usb.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"status": "affected",
"version": "5.2"
},
{
"lessThan": "5.2",
"status": "unaffected",
"version": "0",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.3.*",
"status": "unaffected",
"version": "6.3.4",
"versionType": "semver"
},
{
"lessThanOrEqual": "*",
"status": "unaffected",
"version": "6.4",
"versionType": "original_commit_for_fix"
}
]
}
],
"cpeApplicability": [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.3.4",
"versionStartIncluding": "5.2",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.4",
"versionStartIncluding": "5.2",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
]
}
],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nwifi: rtw88: Fix memory leak in rtw88_usb\n\nKmemleak shows the following leak arising from routine in the usb\nprobe routine:\n\nunreferenced object 0xffff895cb29bba00 (size 512):\n comm \"(udev-worker)\", pid 534, jiffies 4294903932 (age 102751.088s)\n hex dump (first 32 bytes):\n 77 30 30 30 00 00 00 00 02 2f 2d 2b 30 00 00 00 w000...../-+0...\n 02 00 2a 28 00 00 00 00 ff 55 ff ff ff 00 00 00 ..*(.....U......\n backtrace:\n [\u003cffffffff9265fa36\u003e] kmalloc_trace+0x26/0x90\n [\u003cffffffffc17eec41\u003e] rtw_usb_probe+0x2f1/0x680 [rtw_usb]\n [\u003cffffffffc03e19fd\u003e] usb_probe_interface+0xdd/0x2e0 [usbcore]\n [\u003cffffffff92b4f2fe\u003e] really_probe+0x18e/0x3d0\n [\u003cffffffff92b4f5b8\u003e] __driver_probe_device+0x78/0x160\n [\u003cffffffff92b4f6bf\u003e] driver_probe_device+0x1f/0x90\n [\u003cffffffff92b4f8df\u003e] __driver_attach+0xbf/0x1b0\n [\u003cffffffff92b4d350\u003e] bus_for_each_dev+0x70/0xc0\n [\u003cffffffff92b4e51e\u003e] bus_add_driver+0x10e/0x210\n [\u003cffffffff92b50935\u003e] driver_register+0x55/0xf0\n [\u003cffffffffc03e0708\u003e] usb_register_driver+0x88/0x140 [usbcore]\n [\u003cffffffff92401153\u003e] do_one_initcall+0x43/0x210\n [\u003cffffffff9254f42a\u003e] do_init_module+0x4a/0x200\n [\u003cffffffff92551d1c\u003e] __do_sys_finit_module+0xac/0x120\n [\u003cffffffff92ee6626\u003e] do_syscall_64+0x56/0x80\n [\u003cffffffff9300006a\u003e] entry_SYSCALL_64_after_hwframe+0x46/0xb0\n\nThe leak was verified to be real by unloading the driver, which resulted\nin a dangling pointer to the allocation.\n\nThe allocated memory is freed in rtw_usb_intf_deinit()."
}
],
"providerMetadata": {
"dateUpdated": "2025-10-02T07:04:30.330Z",
"orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"shortName": "Linux"
},
"references": [
{
"url": "https://git.kernel.org/stable/c/5bba1ad561a8b5bb14704d8f511cf10466336e3d"
},
{
"url": "https://git.kernel.org/stable/c/59a3a312009723e3e5082899655fdcc420e2b47a"
}
],
"title": "wifi: rtw88: Fix memory leak in rtw88_usb",
"x_generator": {
"engine": "bippy-1.2.0"
}
}
},
"cveMetadata": {
"assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"assignerShortName": "Linux",
"cveId": "CVE-2023-53529",
"datePublished": "2025-10-01T11:46:14.358Z",
"dateReserved": "2025-10-01T11:39:39.408Z",
"dateUpdated": "2025-10-02T07:04:30.330Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.1",
"vulnerability-lookup:meta": {
"nvd": "{\"cve\":{\"id\":\"CVE-2023-53529\",\"sourceIdentifier\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"published\":\"2025-10-01T12:15:57.590\",\"lastModified\":\"2025-10-02T19:11:46.753\",\"vulnStatus\":\"Awaiting Analysis\",\"cveTags\":[],\"descriptions\":[{\"lang\":\"en\",\"value\":\"In the Linux kernel, the following vulnerability has been resolved:\\n\\nwifi: rtw88: Fix memory leak in rtw88_usb\\n\\nKmemleak shows the following leak arising from routine in the usb\\nprobe routine:\\n\\nunreferenced object 0xffff895cb29bba00 (size 512):\\n comm \\\"(udev-worker)\\\", pid 534, jiffies 4294903932 (age 102751.088s)\\n hex dump (first 32 bytes):\\n 77 30 30 30 00 00 00 00 02 2f 2d 2b 30 00 00 00 w000...../-+0...\\n 02 00 2a 28 00 00 00 00 ff 55 ff ff ff 00 00 00 ..*(.....U......\\n backtrace:\\n [\u003cffffffff9265fa36\u003e] kmalloc_trace+0x26/0x90\\n [\u003cffffffffc17eec41\u003e] rtw_usb_probe+0x2f1/0x680 [rtw_usb]\\n [\u003cffffffffc03e19fd\u003e] usb_probe_interface+0xdd/0x2e0 [usbcore]\\n [\u003cffffffff92b4f2fe\u003e] really_probe+0x18e/0x3d0\\n [\u003cffffffff92b4f5b8\u003e] __driver_probe_device+0x78/0x160\\n [\u003cffffffff92b4f6bf\u003e] driver_probe_device+0x1f/0x90\\n [\u003cffffffff92b4f8df\u003e] __driver_attach+0xbf/0x1b0\\n [\u003cffffffff92b4d350\u003e] bus_for_each_dev+0x70/0xc0\\n [\u003cffffffff92b4e51e\u003e] bus_add_driver+0x10e/0x210\\n [\u003cffffffff92b50935\u003e] driver_register+0x55/0xf0\\n [\u003cffffffffc03e0708\u003e] usb_register_driver+0x88/0x140 [usbcore]\\n [\u003cffffffff92401153\u003e] do_one_initcall+0x43/0x210\\n [\u003cffffffff9254f42a\u003e] do_init_module+0x4a/0x200\\n [\u003cffffffff92551d1c\u003e] __do_sys_finit_module+0xac/0x120\\n [\u003cffffffff92ee6626\u003e] do_syscall_64+0x56/0x80\\n [\u003cffffffff9300006a\u003e] entry_SYSCALL_64_after_hwframe+0x46/0xb0\\n\\nThe leak was verified to be real by unloading the driver, which resulted\\nin a dangling pointer to the allocation.\\n\\nThe allocated memory is freed in rtw_usb_intf_deinit().\"}],\"metrics\":{},\"references\":[{\"url\":\"https://git.kernel.org/stable/c/59a3a312009723e3e5082899655fdcc420e2b47a\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/5bba1ad561a8b5bb14704d8f511cf10466336e3d\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"}]}}"
}
}
Loading…
Loading…
Sightings
| Author | Source | Type | Date |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
- Confirmed: The vulnerability is confirmed from an analyst perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
- Patched: This vulnerability was successfully patched by the user reporting the sighting.
- Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
- Not confirmed: The user expresses doubt about the veracity of the vulnerability.
- Not patched: This vulnerability was not successfully patched by the user reporting the sighting.
Loading…
Loading…