Bluetooth: Fix potential use-after-free when clear keys
In the Linux kernel, the following vulnerability has been resolved: Bluetooth: Fix potential use-after-free when clear keys Similar to commit c5d2b6fa26b5 ("Bluetooth: Fix use-after-free in hci_remove_ltk/hci_remove_irk"). We can not access k after kfree_rcu() call.
- Published
- Sep 18, 2025
- Updated
- Aug 5, 2026
- EPSS
- 0.1% · 3th percentile
- CWE
- CWE-416
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
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
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel5.7 and later · before 5.10.195
- linux linux kernel5.11 and later · before 5.15.132
- linux linux kernel5.16 and later · before 6.1.53
- linux linux kernel6.2 and later · before 6.4.16
- linux linux kernel6.5 and later · before 6.5.3
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
- 5.7affected
- d7d41682efc25d58b5bd8b80e85e3c9ce586635c and later · before e87da6a0ac6e631454e7da53a76aa9fe44aaa5ddaffected · git
- d7d41682efc25d58b5bd8b80e85e3c9ce586635c and later · before 942d8cefb022f384d5424f8b90c7878f3f93726faffected · git
- d7d41682efc25d58b5bd8b80e85e3c9ce586635c and later · before 94617b736c25091b60e514e2e7aeafcbbee6b700affected · git
- d7d41682efc25d58b5bd8b80e85e3c9ce586635c and later · before da19f35868dfbecfff4f81166c054d2656cb1be4affected · git
- d7d41682efc25d58b5bd8b80e85e3c9ce586635c and later · before 35cc42f04bc49f0656f6840cb7451b3df6049649affected · git
- d7d41682efc25d58b5bd8b80e85e3c9ce586635c and later · before 3673952cf0c6cf81b06c66a0b788abeeb02ff3aeaffected · git
- before 5.7not affected · semver
- 5.10.195 and later · up to and including 5.10.*not affected · semver
- 5.15.132 and later · up to and including 5.15.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:8 | bpftool | before 4.18.0-553.81.1.el8_10 | 4.18.0-553.81.1.el8_10 |
| AlmaLinux:8 | kernel | before 4.18.0-553.81.1.el8_10 | 4.18.0-553.81.1.el8_10 |
| AlmaLinux:8 | kernel-abi-stablelists | before 4.18.0-553.81.1.el8_10 | 4.18.0-553.81.1.el8_10 |
| AlmaLinux:8 | kernel-core | before 4.18.0-553.81.1.el8_10 | 4.18.0-553.81.1.el8_10 |
| AlmaLinux:8 | kernel-cross-headers | before 4.18.0-553.81.1.el8_10 | 4.18.0-553.81.1.el8_10 |
| AlmaLinux:8 | kernel-debug | before 4.18.0-553.81.1.el8_10 | 4.18.0-553.81.1.el8_10 |
| AlmaLinux:8 | kernel-debug-core | before 4.18.0-553.81.1.el8_10 | 4.18.0-553.81.1.el8_10 |
| AlmaLinux:8 | kernel-debug-devel | before 4.18.0-553.81.1.el8_10 | 4.18.0-553.81.1.el8_10 |
| AlmaLinux:8 | kernel-debug-modules | before 4.18.0-553.81.1.el8_10 | 4.18.0-553.81.1.el8_10 |
| AlmaLinux:8 | kernel-debug-modules-extra | before 4.18.0-553.81.1.el8_10 | 4.18.0-553.81.1.el8_10 |
| AlmaLinux:8 | kernel-devel | before 4.18.0-553.81.1.el8_10 | 4.18.0-553.81.1.el8_10 |
| AlmaLinux:8 | kernel-doc | before 4.18.0-553.81.1.el8_10 | 4.18.0-553.81.1.el8_10 |
| AlmaLinux:8 | kernel-headers | before 4.18.0-553.81.1.el8_10 | 4.18.0-553.81.1.el8_10 |
| AlmaLinux:8 | kernel-modules | before 4.18.0-553.81.1.el8_10 | 4.18.0-553.81.1.el8_10 |
| AlmaLinux:8 | kernel-modules-extra | before 4.18.0-553.81.1.el8_10 | 4.18.0-553.81.1.el8_10 |
| AlmaLinux:8 | kernel-rt | before 4.18.0-553.81.1.rt7.422.el8_10 | 4.18.0-553.81.1.rt7.422.el8_10 |
| AlmaLinux:8 | kernel-rt-core | before 4.18.0-553.81.1.rt7.422.el8_10 | 4.18.0-553.81.1.rt7.422.el8_10 |
| AlmaLinux:8 | kernel-rt-debug | before 4.18.0-553.81.1.rt7.422.el8_10 | 4.18.0-553.81.1.rt7.422.el8_10 |
| AlmaLinux:8 | kernel-rt-debug-core | before 4.18.0-553.81.1.rt7.422.el8_10 | 4.18.0-553.81.1.rt7.422.el8_10 |
| AlmaLinux:8 | kernel-rt-debug-devel | before 4.18.0-553.81.1.rt7.422.el8_10 | 4.18.0-553.81.1.rt7.422.el8_10 |
| AlmaLinux:8 | kernel-rt-debug-modules | before 4.18.0-553.81.1.rt7.422.el8_10 | 4.18.0-553.81.1.rt7.422.el8_10 |
| AlmaLinux:8 | kernel-rt-debug-modules-extra | before 4.18.0-553.81.1.rt7.422.el8_10 | 4.18.0-553.81.1.rt7.422.el8_10 |
| AlmaLinux:8 | kernel-rt-devel | before 4.18.0-553.81.1.rt7.422.el8_10 | 4.18.0-553.81.1.rt7.422.el8_10 |
| AlmaLinux:8 | kernel-rt-modules | before 4.18.0-553.81.1.rt7.422.el8_10 | 4.18.0-553.81.1.rt7.422.el8_10 |
+96
Same product
linux: all recordsOther 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 KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
- 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 haKEV83Now
- 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 creKEV77This 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 addKEV77This 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 loKEV77This 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 / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 35cc42f04bc49f0656f6840cb7451b3df6049649 | Vendor (CNA) |
| Linux Linux | 3673952cf0c6cf81b06c66a0b788abeeb02ff3ae | Vendor (CNA) |
| Linux Linux | 942d8cefb022f384d5424f8b90c7878f3f93726f | Vendor (CNA) |
| Linux Linux | 94617b736c25091b60e514e2e7aeafcbbee6b700 | Vendor (CNA) |
| Linux Linux | da19f35868dfbecfff4f81166c054d2656cb1be4 | Vendor (CNA) |
| Linux Linux | e87da6a0ac6e631454e7da53a76aa9fe44aaa5dd | Vendor (CNA) |
| almalinux:bpftool | 4.18.0-553.81.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel | 4.18.0-553.81.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-abi-stablelists | 4.18.0-553.81.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-core | 4.18.0-553.81.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-cross-headers | 4.18.0-553.81.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-debug | 4.18.0-553.81.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-debug-core | 4.18.0-553.81.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-debug-devel | 4.18.0-553.81.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-debug-modules | 4.18.0-553.81.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-debug-modules-extra | 4.18.0-553.81.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-devel | 4.18.0-553.81.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-doc | 4.18.0-553.81.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| debian:linux | 6.1.55-1 · Debian:12 | Package registry (OSV) |
| red hat:bpftool | 0:4.18.0-553.81.1.el8_10 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:bpftool-debuginfo | 0:4.18.0-553.81.1.el8_10 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:kernel | 0:4.18.0-553.81.1.el8_10 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:kernel-abi-stablelists | 0:4.18.0-553.81.1.el8_10 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:kernel-core | 0:4.18.0-553.81.1.el8_10 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:kernel-debug | 0:4.18.0-553.81.1.el8_10 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:kernel-debug-core | 0:4.18.0-553.81.1.el8_10 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:kernel-debug-debuginfo | 0:4.18.0-553.81.1.el8_10 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:kernel-debug-devel | 0:4.18.0-553.81.1.el8_10 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:kernel-debug-modules | 0:4.18.0-553.81.1.el8_10 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:kernel-debug-modules-extra | 0:4.18.0-553.81.1.el8_10 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
+3
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.
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.
Credits
All researchersFinders, 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)
CWE-416 · Use After FreeCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Root cause
After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.
The bug in code
The whole CWE-416 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
free(dev->buf);/* ... another thread is still running ... */process(dev->buf);Fixed
lock(&dev->lock);free(dev->buf);dev->buf = NULL;unlock(&dev->lock);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 helpChange log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
- git.kernel.org/stable/c/35cc42f04bc49f0656f6840cb7451b3df6049649
- git.kernel.org/stable/c/3673952cf0c6cf81b06c66a0b788abeeb02ff3ae
- git.kernel.org/stable/c/942d8cefb022f384d5424f8b90c7878f3f93726f
- git.kernel.org/stable/c/94617b736c25091b60e514e2e7aeafcbbee6b700
- git.kernel.org/stable/c/da19f35868dfbecfff4f81166c054d2656cb1be4
- git.kernel.org/stable/c/e87da6a0ac6e631454e7da53a76aa9fe44aaa5dd
Vendor advisories and official records. Exploit/PoC links are deliberately left out.