Skip to content
Noroxi
CVE-2026-68085· NVD / CVE Program· CNA Linux

Bluetooth: hci_uart: clear HCI_UART_SENDING when write_work is canceled

Noroxi assessment

Priority: Monitor (action score 32/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.19% (FIRST EPSS).
  • Someone on the same network segment 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 1b0d946d6f08bd39211385bc703a440911b41e46, 5.11, 5.16; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 Release Notes; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 Release Notes.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 1b0d946d6f08bd39211385bc703a440911b41e46, 5.11, 5.16; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 Release Notes; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 Release Notes 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: hci_uart: clear HCI_UART_SENDING when write_work is canceled HCI_UART_SENDING bit in tx_state means write_work is pending and blocks queueing it again. Currently this bit is not cleared when canceling the work in hci_uart_close(), which blocks future writes when device is reopened later if write_work was pending. Fix by clearing HCI_UART_SENDING when canceling the work. Also make clearing of tx_skb safe by using disable_work_sync + enable_work instead of just cancel_work_sync. hci_uart_flush() purges the proto tx queue so we can cancel the pending write_work there, instead of doing it just in hci_uart_close(). Re-enable and possibly requeue the work after queue flush.

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

Report tools

JSON

Action score

32

Monitor

Low priority for now.

CVSS
32 / 40 · 8.0 / 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
8.0
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-68085

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

Running WordPress? Scan your site free with WP Lens

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

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

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

    • 78aad93e938f013d9272fe0ee168f27883afa95c, e2d19969c8d9198ecc3090bcd5312ecd503a3339, c85cff648a2bc92322912db5f1727ad05afae7b6, 9d20d48be2c4a071fb015eb09bda2cecd25daf34, 7338031946bd06f6dff149e67b60c4cd083bfea8, 7.1affected
    • 81c7a3c22a0f2808cf4ae0b4908f59763b23606d and later · before d52446b3e735cfdbdc2a58342163803bc2e64249affected · git
    • 192cb0f1ca706d9a1bc36ae0ad5f666d1e4fd894 and later · before b9dd39cf1667e378b25a082ca796d495d578c5d3affected · git
    • c1bb9336ae6b54a5f6a353c4bd4ed9a4307e429b and later · before 714d861d35d937f23375a4517569b13917bbbe51affected · git
    • c1bb9336ae6b54a5f6a353c4bd4ed9a4307e429b and later · before 1b0d946d6f08bd39211385bc703a440911b41e46affected · git
    • 6.12.92 and later · before 6.12.96affected · semver
    • 6.18.34 and later · before 6.18.39affected · semver
    • 5.10.258 and later · before 5.11affected · semver
    • 5.15.209 and later · before 5.16affected · semver
    • 6.1.175 and later · before 6.2affected · semver

Package-level exposure

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

EcosystemPackageAffected rangeFix
Debian:12linuxfrom 0—
Debian:13linuxbefore 6.12.96-16.12.96-1
Debian:14linuxbefore 7.1.4-17.1.4-1

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-68428Aug 10, 2026 · KVM: x86/mmu: Fix use-after-free on vendor module reload
    0Monitor
  • ← EarlierCVE-2026-68083Aug 10, 2026 · ksmbd: fix path resolution in ksmbd_vfs_kern_path_create
    36Monitor
  • Later →CVE-2026-68091Aug 10, 2026 · HID: wacom: stop hardware after post-start probe failures
    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 Linux1b0d946d6f08bd39211385bc703a440911b41e46Vendor (CNA)
Linux Linux5.11Vendor (CNA)
Linux Linux5.16Vendor (CNA)
Linux Linux6.12.96Vendor (CNA)
Linux Linux6.18.39Vendor (CNA)
Linux Linux6.2Vendor (CNA)
Linux Linux6.7Vendor (CNA)
Linux Linux7.1Vendor (CNA)
Linux Linux714d861d35d937f23375a4517569b13917bbbe51Vendor (CNA)
Linux Linuxb9dd39cf1667e378b25a082ca796d495d578c5d3Vendor (CNA)
Linux Linuxd52446b3e735cfdbdc2a58342163803bc2e64249Vendor (CNA)
azl3 kernel 6.6.152.1-1 on Azure Linux 3.0Release NotesMicrosoft (MSRC)
azl3 kernel 6.6.157.1-1 on Azure Linux 3.0Release NotesMicrosoft (MSRC)
debian:linux6.12.96-1 · Debian:13Package 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).

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 researchers

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-6453414 days apartnvmet-tcp: check INIT_FAILED before nvmet_req_uninit in digest error path
    39Monitor
  • CVE-2026-721005 days apartdm-integrity: fix a bug if the bio is out of limits
    35Monitor
  • CVE-2026-6386322 days apartdrm/gpusvm: Fix unbalanced unlock in drm_gpusvm_scan_mm()
    35Monitor
  • CVE-2026-720125 days aparttracing/osnoise: Call synchronize_rcu() when unregistering
    31Monitor
  • CVE-2025-68770209 days apartbnxt_en: Fix XDP_TX path
    30Monitor

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 on the same network segment 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
Adjacent
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

CWE-667 · Improper Locking

CVSS vector

CVSS:3.1/AV:A/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.

Change log

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

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

References

Show all references (3 more)

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

All records