Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2026-68391: Bluetooth: mgmt: hold reference for hci_conn in mgmt_pending_cmds

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 84674dd1d3192ecb050827d3148642609c0c9dbb, b56f2ecafc08f372bf0529f9c4f3f429cb1702dc, d5b3b484b62bb0f4542e7622789d28871626cdf0; azl3 kernel 6.6.143.1-1 on Azure Linux 3.0 6.6.150.1-1.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 84674dd1d3192ecb050827d3148642609c0c9dbb, b56f2ecafc08f372bf0529f9c4f3f429cb1702dc, d5b3b484b62bb0f4542e7622789d28871626cdf0; azl3 kernel 6.6.143.1-1 on Azure Linux 3.0 6.6.150.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: hold reference for hci_conn in mgmt_pending_cmds Dereferencing RCU-protected pointers outside critical sections is invalid and may lead to UAF. Use of hci_conn in hci_sync callbacks also needs to hold refcount to avoid UAF. Take appropriate locks for hci_conn lookups, and take refcount for hci_conn pointers stored in mgmt_pending_cmd so that the pointer stays valid. When accessing conn->state, ensure hdev->lock is held to avoid data race.

HighCVSS 7.8 · v3.1—No exploit Fix available
Published
Aug 10, 2026
Updated
Oct 19, 2026
EPSS
0.1% · 2th percentile

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

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

Your free account also gets you

  • Stack 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 (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.

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

    • 6.0affected
    • 7b445e220db9a2c58be5d09bbbd322abf1b1452a and later · before 84674dd1d3192ecb050827d3148642609c0c9dbbaffected · git
    • 7b445e220db9a2c58be5d09bbbd322abf1b1452a and later · before b56f2ecafc08f372bf0529f9c4f3f429cb1702dcaffected · git
    • 7b445e220db9a2c58be5d09bbbd322abf1b1452a and later · before f915e74b6f18293d1d69a2a3305ef321ff7c0172affected · git
    • 7b445e220db9a2c58be5d09bbbd322abf1b1452a and later · before d5b3b484b62bb0f4542e7622789d28871626cdf0affected · git
    • 7b445e220db9a2c58be5d09bbbd322abf1b1452a and later · before ecdcb55ea1c01dda074406f38058785a69526734affected · git
    • 7b445e220db9a2c58be5d09bbbd322abf1b1452a and later · before da55f570191d5d72f10c607a7043b947eb05ea46affected · git
    • before 6.0not affected · semver
    • 6.1.189 and later · up to and including 6.1.*not affected · semver
    • 6.6.148 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:10kernel-64k-debug-develbefore 6.12.0-211.58.1.el10_26.12.0-211.58.1.el10_2
AlmaLinux:10kernel-64k-debug-devel-matchedbefore 6.12.0-211.58.1.el10_26.12.0-211.58.1.el10_2
AlmaLinux:10kernel-64k-develbefore 6.12.0-211.58.1.el10_26.12.0-211.58.1.el10_2
AlmaLinux:10kernel-64k-devel-matchedbefore 6.12.0-211.58.1.el10_26.12.0-211.58.1.el10_2
AlmaLinux:10kernel-cross-headersbefore 6.12.0-211.58.1.el10_26.12.0-211.58.1.el10_2
AlmaLinux:10kernel-debugbefore 6.12.0-211.58.1.el10_26.12.0-211.58.1.el10_2
AlmaLinux:10kernel-debug-corebefore 6.12.0-211.58.1.el10_26.12.0-211.58.1.el10_2
AlmaLinux:10kernel-debug-develbefore 6.12.0-211.58.1.el10_26.12.0-211.58.1.el10_2
AlmaLinux:10kernel-debug-devel-matchedbefore 6.12.0-211.58.1.el10_26.12.0-211.58.1.el10_2
AlmaLinux:10kernel-debug-modulesbefore 6.12.0-211.58.1.el10_26.12.0-211.58.1.el10_2
AlmaLinux:10kernel-debug-modules-corebefore 6.12.0-211.58.1.el10_26.12.0-211.58.1.el10_2
AlmaLinux:10kernel-debug-modules-extrabefore 6.12.0-211.58.1.el10_26.12.0-211.58.1.el10_2
AlmaLinux:10kernel-debug-uki-virtbefore 6.12.0-211.58.1.el10_26.12.0-211.58.1.el10_2
AlmaLinux:10kernel-develbefore 6.12.0-211.58.1.el10_26.12.0-211.58.1.el10_2
AlmaLinux:10kernel-devel-matchedbefore 6.12.0-211.58.1.el10_26.12.0-211.58.1.el10_2
AlmaLinux:10kernel-docbefore 6.12.0-211.58.1.el10_26.12.0-211.58.1.el10_2
AlmaLinux:10kernel-headersbefore 6.12.0-211.58.1.el10_26.12.0-211.58.1.el10_2
AlmaLinux:10kernel-modulesbefore 6.12.0-211.58.1.el10_26.12.0-211.58.1.el10_2
AlmaLinux:10kernel-modules-corebefore 6.12.0-211.58.1.el10_26.12.0-211.58.1.el10_2
AlmaLinux:10kernel-modules-extrabefore 6.12.0-211.58.1.el10_26.12.0-211.58.1.el10_2
AlmaLinux:10kernel-modules-extra-matchedbefore 6.12.0-211.58.1.el10_26.12.0-211.58.1.el10_2
AlmaLinux:10kernel-rtbefore 6.12.0-211.58.1.el10_26.12.0-211.58.1.el10_2
AlmaLinux:10kernel-rt-64kbefore 6.12.0-211.58.1.el10_26.12.0-211.58.1.el10_2
AlmaLinux:10kernel-rt-64k-corebefore 6.12.0-211.58.1.el10_26.12.0-211.58.1.el10_2

+96

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-68386Aug 10, 2026 · bpf, sockmap: Reject unhashed UDP sockets on sockmap update
    0Monitor
  • ← EarlierCVE-2026-68388Aug 10, 2026 · smb/client: handle overlapping allocated ranges in fallocate
    39Monitor
  • Later →CVE-2026-68393Aug 10, 2026 · Bluetooth: hci_sync: extend conn_hash lookup critical sections
    35Monitor

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 Linux84674dd1d3192ecb050827d3148642609c0c9dbbVendor (CNA)
Linux Linuxb56f2ecafc08f372bf0529f9c4f3f429cb1702dcVendor (CNA)
Linux Linuxd5b3b484b62bb0f4542e7622789d28871626cdf0Vendor (CNA)
Linux Linuxda55f570191d5d72f10c607a7043b947eb05ea46Vendor (CNA)
Linux Linuxecdcb55ea1c01dda074406f38058785a69526734Vendor (CNA)
Linux Linuxf915e74b6f18293d1d69a2a3305ef321ff7c0172Vendor (CNA)
azl3 kernel 6.6.143.1-1 on Azure Linux 3.06.6.150.1-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
almalinux:kernel5.14.0-687.50.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k5.14.0-687.50.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-core5.14.0-687.50.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug5.14.0-687.50.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-core5.14.0-687.50.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel5.14.0-687.50.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel-matched5.14.0-687.50.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules5.14.0-687.50.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-core5.14.0-687.50.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-extra5.14.0-687.50.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-devel5.14.0-687.50.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-devel-matched5.14.0-687.50.1.el9_8 · AlmaLinux:9Package registry (OSV)
debian:linux6.1.190-1 · Debian:12Package registry (OSV)
debian:linux6.12.101-1 · Debian:13Package registry (OSV)
debian:linux-6.126.12.101-1~deb12u1 · Debian:12Package registry (OSV)
red hat:kernel-64k-debug-debuginfo0:5.14.0-687.50.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel0:5.14.0-687.50.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel-matched0:5.14.0-687.50.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debuginfo0:5.14.0-687.50.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-devel0:5.14.0-687.50.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-devel-matched0:5.14.0-687.50.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debug-debuginfo0:5.14.0-687.50.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debug-devel0:5.14.0-687.50.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)

+5

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.

  • CVE-2026-681170 days aparttipc: clear sock->sk on the failed-insert path in tipc_sk_create()
    39Monitor
  • CVE-2026-681270 days apartila: reload IPv6 header after pskb_may_pull in checksum adjust
    39Monitor
  • CVE-2026-681440 days apartphonet: pep: fix use-after-free in pep_get_sb()
    39Monitor
  • CVE-2026-681560 days apartlibceph: refresh auth->authorizer_buf{,_len} after authorizer update
    39Monitor
  • CVE-2026-683810 days apartksmbd: pin conn during async oplock break notification
    39Monitor
  • CVE-2026-684260 days apartxfrm: fix stale skb->prev after async crypto steals a GSO segment
    39Monitor

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

National notice (Türkiye Cybersecurity Directorate / USOM)

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

All national notices →

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 Free

CVSS vector

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

nvd-secondary

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.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

c
free(dev->buf);/* ... another thread is still running ... */process(dev->buf);

Fixed

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

Change log

  1. SSVC exploitation— → none
  2. Fix✗ → ✓

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

References

All records