Linux Kernel: Use-After-Free (CVE-2026-74510)
Published Last modified Sources: SUSE, HKCERT, Ubuntu, Debian LTS, Debian, BSI, CVE.org, Msrc Update Guide
What is affected, what to do
In the Linux kernel, the following vulnerability has been resolved: Bluetooth: mgmt: fix UAF in pair command cancellation The pairing completion and authentication failure callbacks look up the pending MGMT_OP_PAIR_DEVICE command by walking hdev->mgmt_pending. The lookup returned a command that was still linked on the shared pending list, without keeping mgmt_pending_lock held for the later dereference and removal.
Update Linux Kernel to version 6.1.184, Linux Kernel to version 6.6.151, Linux Kernel to version 6.12.103.
- Affected
- Linux Kernel
lt 2.6.39..6.1.184 - Linux Kernel
lt 6.2..6.6.151 - Linux Kernel
lt 6.7..6.12.103 - Linux Kernel
lt 6.13..6.18.44 - Linux Kernel
lt 6.19..7.1.8
- Linux Kernel
- Fixed in
- Linux Kernel
6.1.184 - Linux Kernel
6.6.151 - Linux Kernel
6.12.103 - Linux Kernel
6.18.44 - Linux Kernel
7.1.8 - Linux Kernel
7.2
- Linux Kernel
Not sure whether and how you are affected? Ask a question about this vulnerability
Metrics
6.4
Priority
XIEM Effective CVSS: highest available CVSS rating from NVD and vendor data.
Source: Vendor (CNA), CVSS v3
6.4
CVSS v3
Severity Medium on the scale from 0 to 10.
Source: SUSE, HKCERT, Ubuntu, Debian LTS, Debian, BSI, CVE.org, Msrc Update Guide
0.1 %
EPSS score
Low — model estimates < 1% exploitation likelihood.
Source: FIRST EPSS, percentile 3.3
Show all metrics
- Severity
- Medium
Priority (0–325)
The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?
Read in glossary- 54.97 Methodology
Exploit maturity
An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.
Read in glossary- no public PoC known
XIEM Effective CVSS
XIEM® is the tiered managed-security operating model from NEOSEC and a registered trademark of NEOSEC GmbH. It extends classic SIEM — the central collection, normalisation and correlation of security-relevant events — with endpoint forensics, network visibility and deception technology, and consolidates them into three building tiers: Sentry, Orchestrate and Command.
Read in glossary- 6.4 Methodology
CVSS v3
CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.
Read in glossary- 6.4
EPSS score
The EPSS score is the absolute model output for an individual vulnerability: the estimated probability of real-world exploitation within the next 30 days, expressed as a value between 0 and 1 (i.e. 0 % to 100 %). A score of 0.42 means „the model estimates a 42 % chance of real-world exploitation within 30 days“.
Read in glossary- 0.1 %
- Low — model estimates < 1% exploitation likelihood.
EPSS percentile
The EPSS percentile is the relative position of a vulnerability within all EPSS-scored CVEs, expressed as a value between 0 and 1. A percentile of 0.90 means „this CVE has a higher EPSS score than 90 % of all other scored CVEs“. Unlike the EPSS score, it is not a probability — but a positioning within a ranking.
Read in glossary- 3.3
- Low — this CVE sits in the lower 10% of all CVEs scored today.
KEV status
The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.
Read in glossary- —
- Published
- CISA assessment (SSVC)
- Exploitation: none known · not automatable · Technical impact: total
- Source: CISA Vulnrichment, as of 16 October 2026
Detection rules
No NEOSEC detection rule is available for this vulnerability yet.
Classification under NIS2 and CRA
Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.
NIS2
NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.
Read in glossary- Handle the vulnerability in regular vulnerability handling under Art. 21(2)(e) NIS2.
CRA
The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.
Read in glossary- From 11.12.2027, Annex I Part II CRA requires manufacturers of affected products with digital elements to handle vulnerabilities without delay and provide security updates.
ISO/IEC 27001
ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.
Read in glossary- Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.
Description
In the Linux kernel, the following vulnerability has been resolved: Bluetooth: mgmt: fix UAF in pair command cancellation The pairing completion and authentication failure callbacks look up the pending MGMT_OP_PAIR_DEVICE command by walking hdev->mgmt_pending. The lookup returned a command that was still linked on the shared pending list, without keeping mgmt_pending_lock held for the later dereference and removal. A concurrent MGMT_OP_CANCEL_PAIR_DEVICE request can remove and free the same pending command before the callback uses it. The reverse race is also possible when cancel_pair_device() gets a command from pending_find() and a callback removes it before the cancel path dereferences it. This can lead to a use-after-free and a second list_del(). Make the pairing lookup helpers transfer ownership of the pending command by removing it from hdev->mgmt_pending while holding mgmt_pending_lock. The callbacks and cancel path then complete the command and free it directly, so racing paths cannot find or free the same command again. Take a temporary hci_conn reference in cancel_pair_device() because the command completion drops the reference stored in the pending command.
Source: suse_csaf, HKCERT (CC BY 3.0 HK) · HKCERT rating: medium, Ubuntu Security Notices, Debian LTS Advisories, Debian Security Advisories, BSI WID Portal, BSI CSAF, cvelistv5, NVD (NIST), Microsoft Security Update Guide
Affected products
The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.
| Affected versions | Fixed in | ||
|---|---|---|---|
| Linux | Linux |
|
|
Vendors and products
Affected operating systems
| Linux | debian | linux | bookworm |
| Linux | debian | linux | trixie |
| Linux | ubuntu | linux | resolute |
| Linux | debian | linux-6.12 | bookworm |
| Linux | ubuntu | linux-aws | resolute |
| Linux | ubuntu | linux-gcp | resolute |
| Linux | ubuntu | linux-hwe-7.0 | noble |
| Linux | ubuntu | linux-ibm | resolute |
| Linux | ubuntu | linux-oem-7.0 | resolute |
| Linux | ubuntu | linux-oracle | resolute |
References & sources
- git.kernel.orgstable/c/86ed4dd6548ccf277bc691bc912ca06e76b9d80c
- git.kernel.orgstable/c/7c2a152a897cd1c184b2051484d4f74d803e7f4a
- git.kernel.orgstable/c/c569def320aa8b1fde89227e2ea96606790fd86d
- git.kernel.orgstable/c/51be7280980fddc90ebe874a69c2fe8ab02bb46a
- git.kernel.orgstable/c/d0a7b48ad0921bd88effaee10bf970ab1d5d0ddd
- git.kernel.orgstable/c/50af4280a587c9971b5388cbc438f1324e626b7b
Changes to this CVE
Who changed this CVE and when: NVD (analysis, affected products, CVSS), the CVE publisher (CNA) and additional providers such as CISA (ADP).
Record modifiedLinux
New references:- https://git.kernel.org/stable/c/50af4280a587c9971b5388cbc438f1324e626b7b
- https://git.kernel.org/stable/c/51be7280980fddc90ebe874a69c2fe8ab02bb46a
- https://git.kernel.org/stable/c/7c2a152a897cd1c184b2051484d4f74d803e7f4a
- https://git.kernel.org/stable/c/86ed4dd6548ccf277bc691bc912ca06e76b9d80c
and 2 more references
Show 12 original changes
Individual changes of this event as published by NVD Type Action Before After Reference added —https://git.kernel.org/stable/c/50af4280a587c9971b5388cbc438f1324e626b7bReference added —https://git.kernel.org/stable/c/51be7280980fddc90ebe874a69c2fe8ab02bb46aReference added —https://git.kernel.org/stable/c/7c2a152a897cd1c184b2051484d4f74d803e7f4aReference added —https://git.kernel.org/stable/c/86ed4dd6548ccf277bc691bc912ca06e76b9d80cReference added —https://git.kernel.org/stable/c/c569def320aa8b1fde89227e2ea96606790fd86dReference added —https://git.kernel.org/stable/c/d0a7b48ad0921bd88effaee10bf970ab1d5d0dddReference removed https://git.kernel.org/stable/c/50af4280a587c9971b5388cbc438f1324e626b7b—Reference removed https://git.kernel.org/stable/c/51be7280980fddc90ebe874a69c2fe8ab02bb46a—Reference removed https://git.kernel.org/stable/c/7c2a152a897cd1c184b2051484d4f74d803e7f4a—Reference removed https://git.kernel.org/stable/c/86ed4dd6548ccf277bc691bc912ca06e76b9d80c—Reference removed https://git.kernel.org/stable/c/c569def320aa8b1fde89227e2ea96606790fd86d—Reference removed https://git.kernel.org/stable/c/d0a7b48ad0921bd88effaee10bf970ab1d5d0ddd—Source identifier: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Record modifiedCISA ADP
CISA assessment (SSVC): exploitation: none known, automatable: no
Show the original change
Individual changes of this event as published by NVD Type Action Before After SSVC assessment added —{"id":"CVE-2026-74510","role":"CISA Coordinator","options":[{"exploitation":"none"},{"automatable":"no"},{"technicalImpact":"total"}],"version":"2.0.3","timestamp":"2026-10-16T18:58:39.693080Z"}Source identifier: 134c704f-9b21-4f2e-91b3-4a467353bcc0
Record modifiedLinux
Show 2 original changes
Individual changes of this event as published by NVD Type Action Before After Reference added —https://git.kernel.org/stable/c/50af4280a587c9971b5388cbc438f1324e626b7bAffected versions (publisher) changed Linux, LinuxLinux, LinuxSource identifier: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Record modifiedLinux
CVSS V3.1: AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Show 2 original changes
Individual changes of this event as published by NVD Type Action Before After CVSS added —AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HAffected versions (publisher) changed Linux, LinuxLinux, LinuxSource identifier: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
ReceivedLinux
Description added or changed
New references:- https://git.kernel.org/stable/c/51be7280980fddc90ebe874a69c2fe8ab02bb46a
- https://git.kernel.org/stable/c/7c2a152a897cd1c184b2051484d4f74d803e7f4a
- https://git.kernel.org/stable/c/86ed4dd6548ccf277bc691bc912ca06e76b9d80c
- https://git.kernel.org/stable/c/c569def320aa8b1fde89227e2ea96606790fd86d
and 1 more reference
Show 7 original changes
Individual changes of this event as published by NVD Type Action Before After Affected versions (publisher) added —Linux, LinuxDescription added —In the Linux kernel, the following vulnerability has been resolved: Bluetooth: mgmt: fix UAF in pair command cancellation The pairing completion and authentication failure callbacks look up the pending MGMT_OP_PAIR_DEVICE command by walking hdev->mgmt_pending. The lookup returned a command that was still linked on the shared pending list, without keeping mgmt_pending_lock held for the later dereference and removal. A concurrent MGMT_OP_CANCEL_PAIR_DEVICE request can remove and free the same pending command before the callback uses it. The reverse race is also possible when cancel_pair_device() gets a command from pending_find() and a callback removes it before the cancel path dereferences it. This can lead to a use-after-free and a second list_del(). Make the pairing lookup helpers transfer ownership of the pending command by removing it from hdev->mgmt_pending while holding mgmt_pending_lock. The callbacks and cancel path then complete the command and free it directly, so racing paths cannot find or free the same command again. Take a temporary hci_conn reference in cancel_pair_device() because the command completion drops the reference stored in the pending command.Reference added —https://git.kernel.org/stable/c/51be7280980fddc90ebe874a69c2fe8ab02bb46aReference added —https://git.kernel.org/stable/c/7c2a152a897cd1c184b2051484d4f74d803e7f4aReference added —https://git.kernel.org/stable/c/86ed4dd6548ccf277bc691bc912ca06e76b9d80cReference added —https://git.kernel.org/stable/c/c569def320aa8b1fde89227e2ea96606790fd86dReference added —https://git.kernel.org/stable/c/d0a7b48ad0921bd88effaee10bf970ab1d5d0dddSource identifier: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Embed badge
Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.
<a href="https://intel.neosec.eu/en/cve/CVE-2026-74510"><img src="https://intel.neosec.eu/badge/cve/CVE-2026-74510.svg?lang=en" alt="CVE-2026-74510 – NEOSEC Intel" height="20"></a>