CVE-2025-71082High· 7.8▾ TwilightIn 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…
▾ Twilight zone — High severity, or a signal on a lesser flaw
impact 42.9 · likelihood 0 · exploitation 0
Need a working PoC? Pro members can cast a request and our team develops one — it lands right here.
Stakeholder-Specific Vulnerability Categorization from CISA's ADP record at CVE.org: whether exploitation is observed, whether an attack can be automated, and how much of the system is at stake. The CVSS score shown above comes from the assigning CNA record, not NVD.
Exploit-prediction probability, daily snapshots since Oct 19.
Disclosure to exploitation, from the record and what we observed since indexing it.
Disclosed via CVEORG
Last analysed / modified upstream
0.1%
0.1% → 0.1%
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.
Linux >= 98921dbd00c4e2e4bdd56423cb5edf98d57b45f7 < fff9206b0907252a41eb12b7c1407b9347df18b1Linux >= 98921dbd00c4e2e4bdd56423cb5edf98d57b45f7 < cca0e9206e3bcc63cd3e72193e60149165d493ccLinux >= 98921dbd00c4e2e4bdd56423cb5edf98d57b45f7 < c0ecb3e4451fe94f4315e6d09c4046dfbc42090bLinux >= 98921dbd00c4e2e4bdd56423cb5edf98d57b45f7 < 1e54c19eaf84ba652c4e376571093e58e144b339Linux >= 98921dbd00c4e2e4bdd56423cb5edf98d57b45f7 < fdf7c640fb8a44a59b0671143d8c2f738bc48003Linux >= 98921dbd00c4e2e4bdd56423cb5edf98d57b45f7 < 252714f1e8bdd542025b16321c790458014d6880Linux 3.7Refer to the linked advisories for vendor-supplied fixes and affected version ranges.
Connected by shared product, vendor, weakness, or advisory.
CVE-2026-99118Nonedrm/i915/dmc: Harden DMC firmware payload parsing
CVE-2026-99117Nonenet: bridge: mcast: don't truncate the port group walk on teardown
CVE-2026-99121Noneipv4: avoid divide by zero in fib_rebalance
CVE-2026-99120NoneKVM: x86/mmu: Cope with the SS bit being set in #NPF exit codes
CVE-2026-99119Nonedrm/amdgpu/userq: actually validate userq BOs
CVE-2026-99123Nonevsock/virtio: validate packet source for connected sockets