7.8
CVE-2025-38555
- EPSS 0.16%
- Veröffentlicht 19.08.2025 17:15:31
- Zuletzt bearbeitet 08.01.2026 20:49:46
- Quelle 416baaa9-dc9f-4396-8d5f-8c081f
- CVE-Watchlists
- Unerledigt
usb: gadget : fix use-after-free in composite_dev_cleanup()
In the Linux kernel, the following vulnerability has been resolved: usb: gadget : fix use-after-free in composite_dev_cleanup() 1. In func configfs_composite_bind() -> composite_os_desc_req_prepare(): if kmalloc fails, the pointer cdev->os_desc_req will be freed but not set to NULL. Then it will return a failure to the upper-level function. 2. in func configfs_composite_bind() -> composite_dev_cleanup(): it will checks whether cdev->os_desc_req is NULL. If it is not NULL, it will attempt to use it.This will lead to a use-after-free issue. BUG: KASAN: use-after-free in composite_dev_cleanup+0xf4/0x2c0 Read of size 8 at addr 0000004827837a00 by task init/1 CPU: 10 PID: 1 Comm: init Tainted: G O 5.10.97-oh #1 kasan_report+0x188/0x1cc __asan_load8+0xb4/0xbc composite_dev_cleanup+0xf4/0x2c0 configfs_composite_bind+0x210/0x7ac udc_bind_to_driver+0xb4/0x1ec usb_gadget_probe_driver+0xec/0x21c gadget_dev_desc_UDC_store+0x264/0x27c
Daten sind bereitgestellt durch National Vulnerability Database (NVD)
Linux ≫ Linux Kernel Version >= 3.16 < 5.4.297
Linux ≫ Linux Kernel Version >= 5.5 < 5.10.241
Linux ≫ Linux Kernel Version >= 5.11 < 5.15.190
Linux ≫ Linux Kernel Version >= 5.16 < 6.1.148
Linux ≫ Linux Kernel Version >= 6.2 < 6.6.102
Linux ≫ Linux Kernel Version >= 6.7 < 6.12.42
Linux ≫ Linux Kernel Version >= 6.13 < 6.15.10
Linux ≫ Linux Kernel Version >= 6.16 < 6.16.1
Debian ≫ Debian Linux Version11.0
VulnDex Vulnerability Enrichment
| Typ | Quelle | Score | Percentile |
|---|---|---|---|
| EPSS | FIRST.org | 0.16% | 0.057 |
| Quelle | Base Score | Exploit Score | Impact Score | Vector String |
|---|---|---|---|---|
| nvd@nist.gov | 7.8 | 1.8 | 5.9 |
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
|
CWE-416 Use After Free
The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer.
https://git.kernel.org/stable/c/151c0aa896c47a4459e07fee7d4843f44c1bb18e
https://git.kernel.org/stable/c/5f06ee9f9a3665d43133f125c17e5258a13f3963
https://git.kernel.org/stable/c/aada327a9f8028c573636fa60c0abc80fb8135c9
https://git.kernel.org/stable/c/bd3c4ef60baf7f65c963f3e12d9d7b2b091e20ba
https://git.kernel.org/stable/c/e1be1f380c82a69f80c68c96a7cfe8759fb30355
https://git.kernel.org/stable/c/e624bf26127645a2f7821e73fdf6dc64bad07835
https://git.kernel.org/stable/c/2db29235e900a084a656dea7e0939b0abb7bb897
https://git.kernel.org/stable/c/8afb22aa063f706f3343707cdfb8cda4d021dd33
https://git.kernel.org/stable/c/dba96dfa5a0f685b959dd28a52ac8dab0b805204
https://lists.debian.org/debian-lts-announce/2025/10/msg00007.html
https://lists.debian.org/debian-lts-announce/2025/10/msg00008.html