Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2026-74510: Bluetooth: mgmt: fix UAF in pair command cancellation

HighCVSS 7.8 · v3.1—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 31/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.13% (FIRST EPSS).
  • 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.
  • Fixed version: Linux Linux 50af4280a587c9971b5388cbc438f1324e626b7b, 51be7280980fddc90ebe874a69c2fe8ab02bb46a, 7c2a152a897cd1c184b2051484d4f74d803e7f4a; azl3 kernel 6.6.150.1-1 on Azure Linux 3.0 6.6.152.1-1.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 50af4280a587c9971b5388cbc438f1324e626b7b, 51be7280980fddc90ebe874a69c2fe8ab02bb46a, 7c2a152a897cd1c184b2051484d4f74d803e7f4a; azl3 kernel 6.6.150.1-1 on Azure Linux 3.0 6.6.152.1-1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

Published
Aug 15, 2026
Updated
Oct 16, 2026
EPSS
0.1% · 3th percentile
CWE
—

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
—
CNA · Linux
7.8
NVD has not scored this yet; the score shown is the CNA’s.

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

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-74510

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

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

    • 2.6.39affected
    • e9a416b5ce0c0f93819f55d34cf6882196e9c3b2 and later · before 50af4280a587c9971b5388cbc438f1324e626b7baffected · git
    • e9a416b5ce0c0f93819f55d34cf6882196e9c3b2 and later · before 86ed4dd6548ccf277bc691bc912ca06e76b9d80caffected · git
    • e9a416b5ce0c0f93819f55d34cf6882196e9c3b2 and later · before 7c2a152a897cd1c184b2051484d4f74d803e7f4aaffected · git
    • e9a416b5ce0c0f93819f55d34cf6882196e9c3b2 and later · before c569def320aa8b1fde89227e2ea96606790fd86daffected · git
    • e9a416b5ce0c0f93819f55d34cf6882196e9c3b2 and later · before 51be7280980fddc90ebe874a69c2fe8ab02bb46aaffected · git
    • e9a416b5ce0c0f93819f55d34cf6882196e9c3b2 and later · before d0a7b48ad0921bd88effaee10bf970ab1d5d0dddaffected · git
    • before 2.6.39not affected · semver
    • 6.1.184 and later · up to and including 6.1.*not affected · semver
    • 6.6.151 and later · up to and including 6.6.*not affected · semver

Package-level exposure

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

EcosystemPackageAffected rangeFix
AlmaLinux:9kernelbefore 5.14.0-687.64.1.el9_85.14.0-687.64.1.el9_8
AlmaLinux:9kernel-64kbefore 5.14.0-687.64.1.el9_85.14.0-687.64.1.el9_8
AlmaLinux:9kernel-64k-corebefore 5.14.0-687.64.1.el9_85.14.0-687.64.1.el9_8
AlmaLinux:9kernel-64k-debugbefore 5.14.0-687.64.1.el9_85.14.0-687.64.1.el9_8
AlmaLinux:9kernel-64k-debug-corebefore 5.14.0-687.64.1.el9_85.14.0-687.64.1.el9_8
AlmaLinux:9kernel-64k-debug-develbefore 5.14.0-687.64.1.el9_85.14.0-687.64.1.el9_8
AlmaLinux:9kernel-64k-debug-devel-matchedbefore 5.14.0-687.64.1.el9_85.14.0-687.64.1.el9_8
AlmaLinux:9kernel-64k-debug-modulesbefore 5.14.0-687.64.1.el9_85.14.0-687.64.1.el9_8
AlmaLinux:9kernel-64k-debug-modules-corebefore 5.14.0-687.64.1.el9_85.14.0-687.64.1.el9_8
AlmaLinux:9kernel-64k-debug-modules-extrabefore 5.14.0-687.64.1.el9_85.14.0-687.64.1.el9_8
AlmaLinux:9kernel-64k-develbefore 5.14.0-687.64.1.el9_85.14.0-687.64.1.el9_8
AlmaLinux:9kernel-64k-devel-matchedbefore 5.14.0-687.64.1.el9_85.14.0-687.64.1.el9_8
AlmaLinux:9kernel-64k-modulesbefore 5.14.0-687.64.1.el9_85.14.0-687.64.1.el9_8
AlmaLinux:9kernel-64k-modules-corebefore 5.14.0-687.64.1.el9_85.14.0-687.64.1.el9_8
AlmaLinux:9kernel-64k-modules-extrabefore 5.14.0-687.64.1.el9_85.14.0-687.64.1.el9_8
AlmaLinux:9kernel-abi-stablelistsbefore 5.14.0-687.64.1.el9_85.14.0-687.64.1.el9_8
AlmaLinux:9kernel-corebefore 5.14.0-687.64.1.el9_85.14.0-687.64.1.el9_8
AlmaLinux:9kernel-cross-headersbefore 5.14.0-687.64.1.el9_85.14.0-687.64.1.el9_8
AlmaLinux:9kernel-debugbefore 5.14.0-687.64.1.el9_85.14.0-687.64.1.el9_8
AlmaLinux:9kernel-debug-corebefore 5.14.0-687.64.1.el9_85.14.0-687.64.1.el9_8
AlmaLinux:9kernel-debug-develbefore 5.14.0-687.64.1.el9_85.14.0-687.64.1.el9_8
AlmaLinux:9kernel-debug-devel-matchedbefore 5.14.0-687.64.1.el9_85.14.0-687.64.1.el9_8
AlmaLinux:9kernel-debug-modulesbefore 5.14.0-687.64.1.el9_85.14.0-687.64.1.el9_8
AlmaLinux:9kernel-debug-modules-corebefore 5.14.0-687.64.1.el9_85.14.0-687.64.1.el9_8

+55

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2026-74508Aug 15, 2026 · Bluetooth: HIDP: reject frames without a transaction header
    35Monitor
  • ← EarlierCVE-2026-74509Aug 15, 2026 · Bluetooth: hci_sync: Fix advertising data UAFs
    35Monitor
  • Later →CVE-2026-74512Aug 15, 2026 · audit: fix potential use-after-free in audit_del_rule()
    31Monitor

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 Linux50af4280a587c9971b5388cbc438f1324e626b7bVendor (CNA)
Linux Linux51be7280980fddc90ebe874a69c2fe8ab02bb46aVendor (CNA)
Linux Linux7c2a152a897cd1c184b2051484d4f74d803e7f4aVendor (CNA)
Linux Linux86ed4dd6548ccf277bc691bc912ca06e76b9d80cVendor (CNA)
Linux Linuxc569def320aa8b1fde89227e2ea96606790fd86dVendor (CNA)
Linux Linuxd0a7b48ad0921bd88effaee10bf970ab1d5d0dddVendor (CNA)
azl3 kernel 6.6.150.1-1 on Azure Linux 3.06.6.152.1-1 · Release NotesMicrosoft (MSRC)
almalinux:kernel5.14.0-687.64.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k5.14.0-687.64.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-core5.14.0-687.64.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug5.14.0-687.64.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-core5.14.0-687.64.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel5.14.0-687.64.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel-matched5.14.0-687.64.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules5.14.0-687.64.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-core5.14.0-687.64.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-extra5.14.0-687.64.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-devel5.14.0-687.64.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-devel-matched5.14.0-687.64.1.el9_8 · AlmaLinux:9Package registry (OSV)
debian:linux6.1.187-1 · Debian:12Package registry (OSV)
debian:linux-6.126.12.107-1~deb12u1 · Debian:12Package registry (OSV)
rocky linux:kernel0:5.14.0-687.64.1.el9_8 · Rocky Linux:9Package registry (OSV)

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).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

Not on record for this CVE: patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.

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-secondary

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.

References

Show all references (5 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records