Answer in brief
CVE-2025-71082 records a High severity (CVSS 7.8) vulnerability in Bluetooth: btusb: revert use of devm_kzalloc in btusb. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=98921dbd00c4e2e4bdd56423cb5edf98d57b45f7 <fff9206b0907252a41eb12b7c1407b9347df18b1 || >=98921dbd00c4e2e4bdd56423cb5edf98d57b45f7 <cca0e9206e3bcc63cd3e72193e60149165d493cc || >=98921dbd00c4e2e4bdd56423cb5edf98d57b45f7 <c0ecb3e4451fe94f4315e6d09c4046dfbc42090b || >=98921dbd00c4e2e4bdd56423cb5edf98d57b45f7 <1e54c19eaf84ba652c4e376571093e58e144b339 || >=98921dbd00c4e2e4bdd56423cb5edf98d57b45f7 <fdf7c640fb8a44a59b0671143d8c2f738bc48003 || >=98921dbd00c4e2e4bdd56423cb5edf98d57b45f7 <252714f1e8bdd542025b16321c790458014d6880 | fff9206b0907252a41eb12b7c1407b9347df18b1, cca0e9206e3bcc63cd3e72193e60149165d493cc, c0ecb3e4451fe94f4315e6d09c4046dfbc42090b, 1e54c19eaf84ba652c4e376571093e58e144b339, fdf7c640fb8a44a59b0671143d8c2f738bc48003, 252714f1e8bdd542025b16321c790458014d6880 |
| Linux/Linuxgeneric | 3.7 | Not reported |
Published upstream
Jan 13, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 19, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Oct 19, 2026
In the Linux kernel, the following vulnerability has been resolved: Bluetooth: btusb: revert use of devm_kzalloc in btusb This reverts commit 98921dbd00c4e ("Bluetooth: Use devm_kzalloc in btusb.c file"). In btusb_probe(), we use devm_kzalloc() to allocate the btusb data. This ties the lifetime of all the btusb data to the binding of a driver to one interface, INTF. In a driver that binds to other interfaces, ISOC and DIAG, this is an accident waiting to happen. The issue is revealed in btusb_disconnect(), where calling usb_driver_release_interface(&btusb_driver, data->intf) will have devm free the data that is also being used by the other interfaces of the driver that may not be released yet. To fix this, revert the use of devm and go back to freeing memory explicitly.
Quoted source text, attributed separately from HOL analysis.