BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2026
CVE-2026-68189High confidence

Bluetooth: hci_sync: Protect UUID list traversal

Linux · Linux

7.8HighCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 121 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityHighOperational priority:Medium, lowered one band.downgradedsince 19 Aug 2026

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • Exploitation requires an existing local or physical foothold with privileges.
  • EPSS is 0.17% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict local access and enforce least privilege on affected hosts.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs Linux Linux and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: As exposure requiresRemediation target: Within 365 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 121 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

25 package states
Package result overrides the generic status

BlackTree has verified remediation for at least one product or source, but the relevant distribution still reports no fixed package for 20 affected package states shown here. Treat those rows as affected with no fix until that distribution publishes a fixed version.

Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.12.101-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.187-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcelinux-6.12Vendor fix publishedDebian records a fixed source-package version for this release.6.12.101-1~deb12u1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.1.6-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.1.6-1Debian Security Tracker ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinuxAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-awsAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azureAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azure-fdeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azure-nvidiaAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gcpAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gkeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gkeopAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-ibmAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-lowlatencyAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidiaAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidia-lowlatencyAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidia-tegraAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oem-6.11Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oracleAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-raspiAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-raspi-realtimeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-realtimeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-riscvAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-xilinxAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

2 current
CVE-2026-68189 · CSAF 2.0 · revision 10 · interimSUSE Product Security TeamCVE-2026-68189
105 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • cluster-md-kmp-default as component of SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS
  • dlm-kmp-default as component of SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS
  • gfs2-kmp-default as component of SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS
  • kernel-default as component of SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS
  • kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS
  • kernel-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS
  • kernel-macros as component of SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS
  • kernel-source as component of SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS
  • ocfs2-kmp-default as component of SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS
  • cluster-md-kmp-default as component of SUSE Linux Enterprise High Performance Computing 15 SP5
  • dlm-kmp-default as component of SUSE Linux Enterprise High Performance Computing 15 SP5
  • gfs2-kmp-default as component of SUSE Linux Enterprise High Performance Computing 15 SP5
Summary
In the Linux kernel, the following vulnerability has been resolved: Bluetooth: hci_sync: Protect UUID list traversal The hci_sync conversion moved class-of-device and EIR generation from an HCI request built under hdev->lock to asynchronous command sync work. The worker holds hdev->req_lock, but that lock does not serialize access to hdev->uuids against add_uuid() and remove_uuid(), which update the list under hdev->lock. The following interleaving can therefore occur: CPU0 (command sync work) CPU1 (management socket) fetch uuid from the list list_del(&uuid->list) kfree(uuid) read uuid->size KASAN reports the resulting use-after-free: BUG: KASAN: slab-use-after-free in eir_create+0xb8f/0xee0 Read of size 1 at addr ffff88810dbd8620 by task kworker/u17:0/87 Workqueue: hci0 hci_cmd_sync_work Call Trace: eir_create+0xb8f/0xee0 hci_update_eir_sync+0x1c0/0x330 hci_cmd_sync_work+0x13c/0x290 process_one_work+0x63a/0x1070 worker_thread+0x45b/0xd10 Allocated by task 86: __kasan_kmalloc+0x8f/0xa0 add_uuid+0x18a/0x4b0 hci_sock_sendmsg+0x1033/0x1ea0 Freed by task 92: __kasan_slab_free+0x43/0x70 kfree+0x131/0x3c0 remove_uuid+0x25e/0x560 hci_sock_sendmsg+0x1033/0x1ea0 Hold hdev->lock while generating and committing the class-of-device and EIR snapshots. Release it before sending an HCI command, so controller waits do not happen under the device lock. This protects all UUID list walks in these paths and restores the serialization lost in the command sync conversion.
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
CVE-2026-68189 · CSAF 2.0 · revision 3 · status not statedRed Hat Product Securitykernel: Bluetooth: hci_sync: Protect UUID list traversal
101 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • kernel as a component of Red Hat Enterprise Linux 10
  • kernel-64k as a component of Red Hat Enterprise Linux 10
  • kernel-64k-core as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-core as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-devel as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-devel-matched as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-modules as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-modules-core as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-modules-extra as a component of Red Hat Enterprise Linux 10
  • kernel-64k-devel as a component of Red Hat Enterprise Linux 10
  • kernel-64k-devel-matched as a component of Red Hat Enterprise Linux 10
Summary
A flaw was found in the Bluetooth hci_sync component of the Linux kernel. A race condition during the UUID list traversal, caused by improper synchronization between asynchronous command sync work and UUID list updates, can lead to a use-after-free vulnerability. This could allow a local attacker to potentially cause a denial of service or achieve arbitrary code execution.
Remediation
Fix deferred
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2026-55290

No EUVD known-exploited evidence

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: hci_sync: Protect UUID list traversal The hci_sync conversion moved class-of-device and EIR generation from an HCI request built under hdev->lock to asynchronous command sync work. The worker holds hdev->req_lock, but that lock does not serialize access to hdev->uuids against add_uuid() and remove_uuid(), which update the list under hdev->lock. The following interleaving can therefore occur: CPU0 (command sync work) CPU1 (management socket) fetch uuid from the list list_del(&uuid->list) kfree(uuid) read uuid->size KASAN reports the resulting use-after-free: BUG: KASAN: slab-use-after-free in eir_create+0xb8f/0xee0 Read of size 1 at addr ffff88810dbd8620 by task kworker/u17:0/87 Workqueue: hci0 hci_cmd_sync_work Call Trace: eir_create+0xb8f/0xee0 hci_update_eir_sync+0x1c0/0x330 hci_cmd_sync_work+0x13c/0x290 process_one_work+0x63a/0x1070 worker_thread+0x45b/0xd10 Allocated by task 86: __kasan_kmalloc+0x8f/0xa0 add_uuid+0x18a/0x4b0 hci_sock_sendmsg+0x1033/0x1ea0 Freed by task 92: __kasan_slab_free+0x43/0x70 kfree+0x131/0x3c0 remove_uuid+0x25e/0x560 hci_sock_sendmsg+0x1033/0x1ea0 Hold hdev->lock while generating and committing the class-of-device and EIR snapshots. Release it before sending an HCI command, so controller waits do not happen under the device lock. This protects all UUID list walks in these paths and restores the serialization lost in the command sync conversion.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
7.8 · CVSS 3.1
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 121 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: hci_sync: Protect UUID list traversal The hci_sync conversion moved class-of-device and EIR generation from an HCI request built under hdev->lock to asynchronous command sync work. The worker holds hdev->req_lock, but that lock does not serialize access to hdev->uuids against add_uuid() and remove_uuid(), which update the list under hdev->lock. The following interleaving can therefore occur: CPU0 (command sync work) CPU1 (management socket) fetch uuid from the list list_del(&uuid->list) kfree(uuid) read uuid->size KASAN reports the resulting use-after-free: BUG: KASAN: slab-use-after-free in eir_create+0xb8f/0xee0 Read of size 1 at addr ffff88810dbd8620 by task kworker/u17:0/87 Workqueue: hci0 hci_cmd_sync_work Call Trace: eir_create+0xb8f/0xee0 hci_update_eir_sync+0x1c0/0x330 hci_cmd_sync_work+0x13c/0x290 process_one_work+0x63a/0x1070 worker_thread+0x45b/0xd10 Allocated by task 86: __kasan_kmalloc+0x8f/0xa0 add_uuid+0x18a/0x4b0 hci_sock_sendmsg+0x1033/0x1ea0 Freed by task 92: __kasan_slab_free+0x43/0x70 kfree+0x131/0x3c0 remove_uuid+0x25e/0x560 hci_sock_sendmsg+0x1033/0x1ea0 Hold hdev->lock while generating and committing the class-of-device and EIR snapshots. Release it before sending an HCI command, so controller waits do not happen under the device lock. This protects all UUID list walks in these paths and restores the serialization lost in the command sync conversion.

What

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: hci_sync: Protect UUID list traversal The hci_sync conversion moved class-of-device and EIR generation from an HCI request built under hdev->lock to asynchronous command sync work. The worker holds hdev->req_lock, but that lock does not serialize access to hdev->uuids against add_uuid() and remove_uuid(), which update the list under hdev->lock. The following interleaving can therefore occur: CPU0 (command sync work) CPU1 (management socket) fetch uuid from the list list_del(&uuid->list) kfree(uuid) read uuid->size KASAN reports the resulting use-after-free: BUG: KASAN: slab-use-after-free in eir_create+0xb8f/0xee0 Read of size 1 at addr ffff88810dbd8620 by task kworker/u17:0/87 Workqueue: hci0 hci_cmd_sync_work Call Trace: eir_create+0xb8f/0xee0 hci_update_eir_sync+0x1c0/0x330 hci_cmd_sync_work+0x13c/0x290 process_one_work+0x63a/0x1070 worker_thread+0x45b/0xd10 Allocated by task 86: __kasan_kmalloc+0x8f/0xa0 add_uuid+0x18a/0x4b0 hci_sock_sendmsg+0x1033/0x1ea0 Freed by task 92: __kasan_slab_free+0x43/0x70 kfree+0x131/0x3c0 remove_uuid+0x25e/0x560 hci_sock_sendmsg+0x1033/0x1ea0 Hold hdev->lock while generating and committing the class-of-device and EIR snapshots. Release it before sending an HCI command, so controller waits do not happen under the device lock. This protects all UUID list walks in these paths and restores the serialization lost in the command sync conversion.

Why

The current structured CVE record identifies a security weakness, but the root cause requires confirmation in the linked vendor material.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: hci_sync: Protect UUID list traversal The hci_sync conversion moved class-of-device and EIR generation from an HCI request built under hdev->lock to asynchronous command sync work. The worker holds hdev->req_lock, but that lock does not serialize access to hdev->uuids against add_uuid() and remove_uuid(), which update the list under hdev->lock. The following interleaving can therefore occur: CPU0 (command sync work) CPU1 (management socket) fetch uuid from the list list_del(&uuid->list) kfree(uuid) read uuid->size KASAN reports the resulting use-after-free: BUG: KASAN: slab-use-after-free in eir_create+0xb8f/0xee0 Read of size 1 at addr ffff88810dbd8620 by task kworker/u17:0/87 Workqueue: hci0 hci_cmd_sync_work Call Trace: eir_create+0xb8f/0xee0 hci_update_eir_sync+0x1c0/0x330 hci_cmd_sync_work+0x13c/0x290 process_one_work+0x63a/0x1070 worker_thread+0x45b/0xd10 Allocated by task 86: __kasan_kmalloc+0x8f/0xa0 add_uuid+0x18a/0x4b0 hci_sock_sendmsg+0x1033/0x1ea0 Freed by task 92: __kasan_slab_free+0x43/0x70 kfree+0x131/0x3c0 remove_uuid+0x25e/0x560 hci_sock_sendmsg+0x1033/0x1ea0 Hold hdev->lock while generating and committing the class-of-device and EIR snapshots. Release it before sending an HCI command, so controller waits do not happen under the device lock. This protects all UUID list walks in these paths and restores the serialization lost in the command sync conversion.

Why

The current structured CVE record identifies a security weakness, but the root cause requires confirmation in the linked vendor material.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
local access → vulnerable operation → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Local
Privileges required
Low: a basic authenticated account is required
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration.
CWE not yet assigned
CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRLowPrivileges required: The attacker needs basic user-level privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CHighConfidentiality impact: A successful attack can cause a major loss.IHighIntegrity impact: A successful attack can cause a major loss.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

ENISA EUVD · EUVD-2026-55290Official EUVD mapping

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: hci_sync: Protect UUID list traversal The hci_sync conversion moved class-of-device and EIR generation from an HCI request built under hdev->lock to asynchronous command sync work. The worker holds hdev->req_lock, but that lock does not serialize access to hdev->uuids against add_uuid() and remove_uuid(), which update the list under hdev->lock. The following interleaving can therefore occur: CPU0 (command sync work) CPU1 (management socket) fetch uuid from the list list_del(&uuid->list) kfree(uuid) read uuid->size KASAN reports the resulting use-after-free: BUG: KASAN: slab-use-after-free in eir_create+0xb8f/0xee0 Read of size 1 at addr ffff88810dbd8620 by task kworker/u17:0/87 Workqueue: hci0 hci_cmd_sync_work Call Trace: eir_create+0xb8f/0xee0 hci_update_eir_sync+0x1c0/0x330 hci_cmd_sync_work+0x13c/0x290 process_one_work+0x63a/0x1070 worker_thread+0x45b/0xd10 Allocated by task 86: __kasan_kmalloc+0x8f/0xa0 add_uuid+0x18a/0x4b0 hci_sock_sendmsg+0x1033/0x1ea0 Freed by task 92: __kasan_slab_free+0x43/0x70 kfree+0x131/0x3c0 remove_uuid+0x25e/0x560 hci_sock_sendmsg+0x1033/0x1ea0 Hold hdev->lock while generating and committing the class-of-device and EIR snapshots. Release it before sending an HCI command, so controller waits do not happen under the device lock. This protects all UUID list walks in these paths and restores the serialization lost in the command sync conversion.

Official EUVD record ↗
BSI · German · WID-SEC-2026-2730Linux Kernel: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, darunter möglicherweise die Ausführung von beliebigem Code, die Ausweitung von Berechtigungen, die Offenlegung von Informationen, die Manipulation von Daten oder Denial-of-Service-Zustände.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20260812Security Bulletin 12 Aug 2026

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 12 Aug 2026, published on 12 August 2026. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1255Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2026-68169 Référence CVE CVE-2026-68178 https://www.cve.org/CVERecord?id=CVE-2026-68178 Référence CVE CVE-2026-68179 https://www.cve.org/CVERecord?id=CVE-2026-68179 Référence CVE CVE-2026-68180 https://www.cve.org/CVERecord?id=CVE-2026-68180 Référence CVE CVE-2026-68181 https://www.cve.org/CVERecord?id=CVE-2026-68181 Référence CVE CVE-2026-68182 https://www.cve.org/CVERecord?id=CVE-2026-68182 Référence CVE CVE-2026-68183 https://www.cve.org/CVERecord?id=CVE-2026-68183 Référence CVE CVE-2026-68184 https://www.cve.org/CVERecord?id=CVE-2026-68184 Référence CVE CVE-2026-68188 https://www.cve.org/CVERecord?id=CVE-2026-68188 Référence CVE CVE-2026-68189 https://www.cve.org/CVERecord?id=CVE-2026-68189 Référence CVE CVE-2026-68192 https://www.cve.org/CVERecord?id=CVE-2026-68192 Référence CVE CVE-2026-68193 https://www.cve.org/CVERecord?id=CVE-2026-68193 Référence CVE CVE-2026-68194 https://www.cve.org/CVERecord?id=CVE-2026-68194 Référence CVE CVE-2026-68195 https://www.cve.org/CVERecord?id=CVE-2026-68195 Référence CVE CVE-2026-68196 https://www.cve.org/CVERecord?id=CVE-2026-68196 Référence CVE CVE-2026-68197 https://www.cve.org/CVERecord?id=CVE-2026-68197 Référence CVE CVE-2026-68198 https://www.cve.org/CVERecord?id=CVE-2026-68198 Référence CVE CVE-2026-68199 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1202Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2026-68160 Référence CVE CVE-2026-68161 https://www.cve.org/CVERecord?id=CVE-2026-68161 Référence CVE CVE-2026-68162 https://www.cve.org/CVERecord?id=CVE-2026-68162 Référence CVE CVE-2026-68166 https://www.cve.org/CVERecord?id=CVE-2026-68166 Référence CVE CVE-2026-68180 https://www.cve.org/CVERecord?id=CVE-2026-68180 Référence CVE CVE-2026-68181 https://www.cve.org/CVERecord?id=CVE-2026-68181 Référence CVE CVE-2026-68182 https://www.cve.org/CVERecord?id=CVE-2026-68182 Référence CVE CVE-2026-68184 https://www.cve.org/CVERecord?id=CVE-2026-68184 Référence CVE CVE-2026-68188 https://www.cve.org/CVERecord?id=CVE-2026-68188 Référence CVE CVE-2026-68189 https://www.cve.org/CVERecord?id=CVE-2026-68189 Référence CVE CVE-2026-68192 https://www.cve.org/CVERecord?id=CVE-2026-68192 Référence CVE CVE-2026-68193 https://www.cve.org/CVERecord?id=CVE-2026-68193 Référence CVE CVE-2026-68194 https://www.cve.org/CVERecord?id=CVE-2026-68194 Référence CVE CVE-2026-68195 https://www.cve.org/CVERecord?id=CVE-2026-68195 Référence CVE CVE-2026-68196 https://www.cve.org/CVERecord?id=CVE-2026-68196 Référence CVE CVE-2026-68197 https://www.cve.org/CVERecord?id=CVE-2026-68197 Référence CVE CVE-2026-68199 https://www.cve.org/CVERecord?id=CVE-2026-68199 Référence CVE CVE-2026-68202 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1163Multiples vulnérabilités dans le noyau Linux de Debian LTS

d?id=CVE-2026-68176 Référence CVE CVE-2026-68180 https://www.cve.org/CVERecord?id=CVE-2026-68180 Référence CVE CVE-2026-68181 https://www.cve.org/CVERecord?id=CVE-2026-68181 Référence CVE CVE-2026-68182 https://www.cve.org/CVERecord?id=CVE-2026-68182 Référence CVE CVE-2026-68183 https://www.cve.org/CVERecord?id=CVE-2026-68183 Référence CVE CVE-2026-68184 https://www.cve.org/CVERecord?id=CVE-2026-68184 Référence CVE CVE-2026-68186 https://www.cve.org/CVERecord?id=CVE-2026-68186 Référence CVE CVE-2026-68187 https://www.cve.org/CVERecord?id=CVE-2026-68187 Référence CVE CVE-2026-68188 https://www.cve.org/CVERecord?id=CVE-2026-68188 Référence CVE CVE-2026-68189 https://www.cve.org/CVERecord?id=CVE-2026-68189 Référence CVE CVE-2026-68190 https://www.cve.org/CVERecord?id=CVE-2026-68190 Référence CVE CVE-2026-68192 https://www.cve.org/CVERecord?id=CVE-2026-68192 Référence CVE CVE-2026-68194 https://www.cve.org/CVERecord?id=CVE-2026-68194 Référence CVE CVE-2026-68195 https://www.cve.org/CVERecord?id=CVE-2026-68195 Référence CVE CVE-2026-68196 https://www.cve.org/CVERecord?id=CVE-2026-68196 Référence CVE CVE-2026-68197 https://www.cve.org/CVERecord?id=CVE-2026-68197 Référence CVE CVE-2026-68198 https://www.cve.org/CVERecord?id=CVE-2026-68198 Référence CVE CVE-2026-68199 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1164Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2026-68160 Référence CVE CVE-2026-68161 https://www.cve.org/CVERecord?id=CVE-2026-68161 Référence CVE CVE-2026-68162 https://www.cve.org/CVERecord?id=CVE-2026-68162 Référence CVE CVE-2026-68166 https://www.cve.org/CVERecord?id=CVE-2026-68166 Référence CVE CVE-2026-68180 https://www.cve.org/CVERecord?id=CVE-2026-68180 Référence CVE CVE-2026-68181 https://www.cve.org/CVERecord?id=CVE-2026-68181 Référence CVE CVE-2026-68182 https://www.cve.org/CVERecord?id=CVE-2026-68182 Référence CVE CVE-2026-68184 https://www.cve.org/CVERecord?id=CVE-2026-68184 Référence CVE CVE-2026-68188 https://www.cve.org/CVERecord?id=CVE-2026-68188 Référence CVE CVE-2026-68189 https://www.cve.org/CVERecord?id=CVE-2026-68189 Référence CVE CVE-2026-68192 https://www.cve.org/CVERecord?id=CVE-2026-68192 Référence CVE CVE-2026-68193 https://www.cve.org/CVERecord?id=CVE-2026-68193 Référence CVE CVE-2026-68194 https://www.cve.org/CVERecord?id=CVE-2026-68194 Référence CVE CVE-2026-68195 https://www.cve.org/CVERecord?id=CVE-2026-68195 Référence CVE CVE-2026-68196 https://www.cve.org/CVERecord?id=CVE-2026-68196 Référence CVE CVE-2026-68197 https://www.cve.org/CVERecord?id=CVE-2026-68197 Référence CVE CVE-2026-68199 https://www.cve.org/CVERecord?id=CVE-2026-68199 Référence CVE CVE-2026-68202 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1069Multiples vulnérabilités dans le noyau Linux de Debian LTS

d?id=CVE-2026-68180 Référence CVE CVE-2026-68181 https://www.cve.org/CVERecord?id=CVE-2026-68181 Référence CVE CVE-2026-68182 https://www.cve.org/CVERecord?id=CVE-2026-68182 Référence CVE CVE-2026-68183 https://www.cve.org/CVERecord?id=CVE-2026-68183 Référence CVE CVE-2026-68184 https://www.cve.org/CVERecord?id=CVE-2026-68184 Référence CVE CVE-2026-68185 https://www.cve.org/CVERecord?id=CVE-2026-68185 Référence CVE CVE-2026-68186 https://www.cve.org/CVERecord?id=CVE-2026-68186 Référence CVE CVE-2026-68187 https://www.cve.org/CVERecord?id=CVE-2026-68187 Référence CVE CVE-2026-68188 https://www.cve.org/CVERecord?id=CVE-2026-68188 Référence CVE CVE-2026-68189 https://www.cve.org/CVERecord?id=CVE-2026-68189 Référence CVE CVE-2026-68190 https://www.cve.org/CVERecord?id=CVE-2026-68190 Référence CVE CVE-2026-68192 https://www.cve.org/CVERecord?id=CVE-2026-68192 Référence CVE CVE-2026-68193 https://www.cve.org/CVERecord?id=CVE-2026-68193 Référence CVE CVE-2026-68194 https://www.cve.org/CVERecord?id=CVE-2026-68194 Référence CVE CVE-2026-68195 https://www.cve.org/CVERecord?id=CVE-2026-68195 Référence CVE CVE-2026-68196 https://www.cve.org/CVERecord?id=CVE-2026-68196 Référence CVE CVE-2026-68197 https://www.cve.org/CVERecord?id=CVE-2026-68197 Référence CVE CVE-2026-68199 https://www.cve.org/CVERecord?id=

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix availability varies by product
Affected
Fixed
Linux: < 5.17, 6.1.183 ≤ 6.1.*, 6.6.148 ≤ 6.6.*, 6.12.101 ≤ 6.12.*, 6.18.42 ≤ 6.18.*, 7.1.6 ≤ 7.1.*, 7.2 ≤ *
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
Workaround
No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04

Evidence and provenance

Published 10 Aug 2026 · Last source change 19 Aug 2026, 16:31 UTC · CWE not yet assigned

CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2026-55290
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceUnavailable
NVD statusNVD received

Missing structured fields: CWE classification. Missing data is not evidence of low risk; review the primary advisory.

Material change intelligence

What changed after publication

View recent updates ↗
  1. Vendor guidanceAuthoritative vendor guidance changed: added remediation: git.kernel.org/30bc6248f035a792d1b1f4cc761b32fd5827b55f; removed remediation: git.kernel.org/e4fa2c5c261d736b8e58759fdef3a968d510630c.
    Before
    remediation: git.kernel.org/e4fa2c5c261d736b8e58759fdef3a968d510630c
    After
    remediation: git.kernel.org/30bc6248f035a792d1b1f4cc761b32fd5827b55f
    CNA ↗
  2. Affected versionsThe structured affected or fixed version information changed.
    Before
    161510ccf91c961638940b03abb1ee804be53a97 < e4fa2c5c261d736b8e58759fdef3a968d510630c; 161510ccf91c961638940b03abb1ee804be53a97 < a351f68fb24828b23a971e00b8238ee0e8a40380; 161510ccf91c961638940b03abb1ee804be53a97 < a42f5536ea9c00e13f0c0fbb330feed95e2365ca; 161510ccf91c961638940b03abb1ee804be53a97 < fe13adc258df88d95789e5673c7ba5178b5f8b28; 161510ccf91c961638940b03abb1ee804be53a97 < e9027ffbf5a0f3c12ca8900822e884eae9f0821b; 5.17 · Fixed: < 5.17; 6.6.148 ≤ 6.6.*; 6.12.101 ≤ 6.12.*; 6.18.42 ≤ 6.18.*; 7.1.6 ≤ 7.1.*; 7.2 ≤ *
    After
    161510ccf91c961638940b03abb1ee804be53a97 < 30bc6248f035a792d1b1f4cc761b32fd5827b55f; 161510ccf91c961638940b03abb1ee804be53a97 < e4fa2c5c261d736b8e58759fdef3a968d510630c; 161510ccf91c961638940b03abb1ee804be53a97 < a351f68fb24828b23a971e00b8238ee0e8a40380; 161510ccf91c961638940b03abb1ee804be53a97 < a42f5536ea9c00e13f0c0fbb330feed95e2365ca; 161510ccf91c961638940b03abb1ee804be53a97 < fe13adc258df88d95789e5673c7ba5178b5f8b28; 161510ccf91c961638940b03abb1ee804be53a97 < e9027ffbf5a0f3c12ca8900822e884eae9f0821b; 5.17 · Fixed: < 5.17; 6.1.183 ≤ 6.1.*; 6.6.148 ≤ 6.6.*; 6.12.101 ≤ 6.12.*; 6.18.42 ≤ 6.18.*; 7.1.6 ≤ 7.1.*; 7.2 ≤ *
    CNA ↗
  3. Affected versionsThe structured affected or fixed version information changed.
    Before
    161510ccf91c961638940b03abb1ee804be53a97 < e4fa2c5c261d736b8e58759fdef3a968d510630c; 161510ccf91c961638940b03abb1ee804be53a97 < a351f68fb24828b23a971e00b8238ee0e8a40380; 161510ccf91c961638940b03abb1ee804be53a97 < a42f5536ea9c00e13f0c0fbb330feed95e2365ca; 161510ccf91c961638940b03abb1ee804be53a97 < fe13adc258df88d95789e5673c7ba5178b5f8b28; 161510ccf91c961638940b03abb1ee804be53a97 < e9027ffbf5a0f3c12ca8900822e884eae9f0821b; 5.17 · Fixed: < 5.17; 6.6.148 ≤ 6.6.*; 6.12.101 ≤ 6.12.*; 6.18.42 ≤ 6.18.*; 7.1.6 ≤ 7.1.*; 7.2-rc5 ≤ *
    After
    161510ccf91c961638940b03abb1ee804be53a97 < e4fa2c5c261d736b8e58759fdef3a968d510630c; 161510ccf91c961638940b03abb1ee804be53a97 < a351f68fb24828b23a971e00b8238ee0e8a40380; 161510ccf91c961638940b03abb1ee804be53a97 < a42f5536ea9c00e13f0c0fbb330feed95e2365ca; 161510ccf91c961638940b03abb1ee804be53a97 < fe13adc258df88d95789e5673c7ba5178b5f8b28; 161510ccf91c961638940b03abb1ee804be53a97 < e9027ffbf5a0f3c12ca8900822e884eae9f0821b; 5.17 · Fixed: < 5.17; 6.6.148 ≤ 6.6.*; 6.12.101 ≤ 6.12.*; 6.18.42 ≤ 6.18.*; 7.1.6 ≤ 7.1.*; 7.2 ≤ *
    CNA ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
ENISA EUVD · EUVD-2026-55290↗Vendor CSAF · SUSE Product Security Team↗CVE authority or vendor reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2026-68189 · cve.blacktree.nl