Skip to content
Noroxi
CVE-2025-71082· NVD / CVE Program· CNA Linux

Bluetooth: btusb: revert use of devm_kzalloc in btusb

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.

HighCVSS 7.8 · v3.1—No exploit Fix available
Published
Jan 13, 2026
Updated
Aug 5, 2026
EPSS
0.1% · 3th percentile
CWE
—
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

31

Monitor

Low priority for now.

CVSS
31 / 40 · 7.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
7.8
CNA · Linux
7.8
agree

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Affected systems

VendorProduct
linuxlinux kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernel3.7.1 and later · before 5.15.198
  • linux linux kernel5.16 and later · before 6.1.160
  • linux linux kernel6.2 and later · before 6.6.120
  • linux linux kernel6.7 and later · before 6.12.64
  • linux linux kernel6.13 and later · before 6.18.4
  • linux linux kernel3.7
  • linux linux kernel6.19

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 3.7affected
    • 98921dbd00c4e2e4bdd56423cb5edf98d57b45f7 and later · before fff9206b0907252a41eb12b7c1407b9347df18b1affected · git
    • 98921dbd00c4e2e4bdd56423cb5edf98d57b45f7 and later · before cca0e9206e3bcc63cd3e72193e60149165d493ccaffected · git
    • 98921dbd00c4e2e4bdd56423cb5edf98d57b45f7 and later · before c0ecb3e4451fe94f4315e6d09c4046dfbc42090baffected · git
    • 98921dbd00c4e2e4bdd56423cb5edf98d57b45f7 and later · before 1e54c19eaf84ba652c4e376571093e58e144b339affected · git
    • 98921dbd00c4e2e4bdd56423cb5edf98d57b45f7 and later · before fdf7c640fb8a44a59b0671143d8c2f738bc48003affected · git
    • 98921dbd00c4e2e4bdd56423cb5edf98d57b45f7 and later · before 252714f1e8bdd542025b16321c790458014d6880affected · git
    • before 3.7not affected · semver
    • 5.15.198 and later · up to and including 5.15.*not affected · semver
    • 6.1.160 and later · up to and including 6.1.*not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
AlmaLinux:8bpftoolbefore 4.18.0-553.166.1.el8_104.18.0-553.166.1.el8_10
AlmaLinux:8kernelbefore 4.18.0-553.166.1.el8_104.18.0-553.166.1.el8_10
AlmaLinux:8kernel-abi-stablelistsbefore 4.18.0-553.166.1.el8_104.18.0-553.166.1.el8_10
AlmaLinux:8kernel-corebefore 4.18.0-553.166.1.el8_104.18.0-553.166.1.el8_10
AlmaLinux:8kernel-cross-headersbefore 4.18.0-553.166.1.el8_104.18.0-553.166.1.el8_10
AlmaLinux:8kernel-debugbefore 4.18.0-553.166.1.el8_104.18.0-553.166.1.el8_10
AlmaLinux:8kernel-debug-corebefore 4.18.0-553.166.1.el8_104.18.0-553.166.1.el8_10
AlmaLinux:8kernel-debug-develbefore 4.18.0-553.166.1.el8_104.18.0-553.166.1.el8_10
AlmaLinux:8kernel-debug-modulesbefore 4.18.0-553.166.1.el8_104.18.0-553.166.1.el8_10
AlmaLinux:8kernel-debug-modules-extrabefore 4.18.0-553.166.1.el8_104.18.0-553.166.1.el8_10
AlmaLinux:8kernel-develbefore 4.18.0-553.166.1.el8_104.18.0-553.166.1.el8_10
AlmaLinux:8kernel-docbefore 4.18.0-553.166.1.el8_104.18.0-553.166.1.el8_10
AlmaLinux:8kernel-headersbefore 4.18.0-553.166.1.el8_104.18.0-553.166.1.el8_10
AlmaLinux:8kernel-modulesbefore 4.18.0-553.166.1.el8_104.18.0-553.166.1.el8_10
AlmaLinux:8kernel-modules-extrabefore 4.18.0-553.166.1.el8_104.18.0-553.166.1.el8_10
AlmaLinux:8kernel-rtbefore 4.18.0-553.166.1.rt7.507.el8_104.18.0-553.166.1.rt7.507.el8_10
AlmaLinux:8kernel-rt-corebefore 4.18.0-553.166.1.rt7.507.el8_104.18.0-553.166.1.rt7.507.el8_10
AlmaLinux:8kernel-rt-debugbefore 4.18.0-553.166.1.rt7.507.el8_104.18.0-553.166.1.rt7.507.el8_10
AlmaLinux:8kernel-rt-debug-corebefore 4.18.0-553.166.1.rt7.507.el8_104.18.0-553.166.1.rt7.507.el8_10
AlmaLinux:8kernel-rt-debug-develbefore 4.18.0-553.166.1.rt7.507.el8_104.18.0-553.166.1.rt7.507.el8_10
AlmaLinux:8kernel-rt-debug-modulesbefore 4.18.0-553.166.1.rt7.507.el8_104.18.0-553.166.1.rt7.507.el8_10
AlmaLinux:8kernel-rt-debug-modules-extrabefore 4.18.0-553.166.1.rt7.507.el8_104.18.0-553.166.1.rt7.507.el8_10
AlmaLinux:8kernel-rt-develbefore 4.18.0-553.166.1.rt7.507.el8_104.18.0-553.166.1.rt7.507.el8_10
AlmaLinux:8kernel-rt-modulesbefore 4.18.0-553.166.1.rt7.507.el8_104.18.0-553.166.1.rt7.507.el8_10

+65

Other highest-scoring records for the same primary product.

  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now
  • CVE-2016-5195Race condition in mm/gup.c in the Linux kernel 2.x through 4.x before 4.8.3 allows local users to gain privileges by leveraging incorrect haKEV
    83Now
  • CVE-2019-13272In the Linux kernel before 5.1.17, ptrace_link in kernel/ptrace.c mishandles the recording of the credentials of a process that wants to creKEV
    77This week
  • CVE-2013-6282The (1) get_user and (2) put_user API functions in the Linux kernel before 3.5.5 on the v6k and v7 ARM platforms do not validate certain addKEV
    77This week
  • CVE-2013-2094The perf_swevent_init function in kernel/events/core.c in the Linux kernel before 3.8.9 uses an incorrect integer data type, which allows loKEV
    77This week

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux1e54c19eaf84ba652c4e376571093e58e144b339Vendor (CNA)
Linux Linux252714f1e8bdd542025b16321c790458014d6880Vendor (CNA)
Linux Linuxc0ecb3e4451fe94f4315e6d09c4046dfbc42090bVendor (CNA)
Linux Linuxcca0e9206e3bcc63cd3e72193e60149165d493ccVendor (CNA)
Linux Linuxfdf7c640fb8a44a59b0671143d8c2f738bc48003Vendor (CNA)
Linux Linuxfff9206b0907252a41eb12b7c1407b9347df18b1Vendor (CNA)
azl3 kernel 6.6.119.3-3 on Azure Linux 3.06.6.121.1-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
almalinux:bpftool4.18.0-553.166.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel4.18.0-553.166.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-abi-stablelists4.18.0-553.166.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-core4.18.0-553.166.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-cross-headers4.18.0-553.166.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-debug4.18.0-553.166.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-debug-core4.18.0-553.166.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-debug-devel4.18.0-553.166.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-debug-modules4.18.0-553.166.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-debug-modules-extra4.18.0-553.166.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-devel4.18.0-553.166.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-doc4.18.0-553.166.1.el8_10 · AlmaLinux:8Package registry (OSV)
debian:linux6.1.162-1 · Debian:12Package registry (OSV)
red hat:bpftool0:4.18.0-553.166.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:bpftool-debuginfo0:4.18.0-553.166.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:kernel0:4.18.0-553.166.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:kernel-abi-stablelists0:4.18.0-553.166.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:kernel-core0:4.18.0-553.166.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:kernel-debug0:4.18.0-553.166.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:kernel-debug-core0:4.18.0-553.166.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:kernel-debug-debuginfo0:4.18.0-553.166.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:kernel-debug-devel0:4.18.0-553.166.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:kernel-debug-modules0:4.18.0-553.166.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)

+4

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

—

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records