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

Bluetooth: hci_sync: Fix advertising data UAFs

Linux · Linux

8.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 252 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:High, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • EPSS is 0.39% 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: Within 30 daysRemediation target: Within 180 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 252 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.105-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.107-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.8-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.1.8-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.

1 current
CVE-2026-74509 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitykernel: Bluetooth: hci_sync: Fix advertising data UAFs
232 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 Linux kernel's Bluetooth subsystem. Specifically, the `hci_sync` component, which manages Bluetooth advertising data, is susceptible to a Use-After-Free (UAF) vulnerability. This occurs when a pointer to advertising data becomes invalid but is still accessed, particularly during interleaved advertising termination and command synchronization events. An attacker could potentially exploit this memory corruption to cause a denial of service (DoS) or other system instability.
Remediation
To mitigate this issue, disable the Bluetooth service if it is not required. This can be achieved by stopping and disabling the `bluetooth` service: ```bash systemctl stop bluetooth systemctl disable bluetooth ``` This action will prevent the Bluetooth stack from being active, thereby avoiding the vulnerable code path. A system reboot may be required for the changes to take full effect.
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-59702

No EUVD known-exploited evidence

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: hci_sync: Fix advertising data UAFs hci_find_adv_instance() returns an adv_info pointer that is valid only while hdev->lock is held. The advertising command-sync paths perform instance lookups without that lock and, in some cases, retain the pointer while waiting for a controller response. An advertising termination event can therefore interleave as follows: hci_cmd_sync_work hci_rx_work hci_find_adv_instance() __hci_cmd_sync_status() wait for controller reply hci_dev_lock() hci_remove_adv_instance() kfree(adv) adv->scan_rsp_changed = false KASAN reported: BUG: KASAN: slab-use-after-free in hci_set_ext_scan_rsp_data_sync+0x2e1/0x300 Write of size 1 at addr ffff88810a45d21d by task kworker/u17:0/88 Workqueue: hci0 hci_cmd_sync_work Call Trace: hci_set_ext_scan_rsp_data_sync+0x2e1/0x300 hci_schedule_adv_instance_sync+0x390/0x4c0 hci_cmd_sync_work+0x173/0x300 Allocated by task 87: hci_add_adv_instance+0x538/0xac0 add_advertising+0x885/0x1160 Freed by task 89: kfree+0x131/0x3c0 hci_remove_adv_instance+0x1d8/0x3b0 hci_le_ext_adv_term_evt+0x17b/0x730 Protect the instance lookup and payload construction in the extended advertising, scan response, and periodic advertising data paths. Snapshot the advertising parameters under hdev->lock, but release the lock before waiting for the controller. Clear advertising-data dirty bits before issuing their commands and restore them after a failure using a fresh lookup. Likewise, update the reported transmit power through a fresh lookup after the parameter command completes. No adv_info pointer then survives an HCI command wait.

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
8.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 252 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: Fix advertising data UAFs hci_find_adv_instance() returns an adv_info pointer that is valid only while hdev->lock is held. The advertising command-sync paths perform instance lookups without that lock and, in some cases, retain the pointer while waiting for a controller response. An advertising termination event can therefore interleave as follows: hci_cmd_sync_work hci_rx_work hci_find_adv_instance() __hci_cmd_sync_status() wait for controller reply hci_dev_lock() hci_remove_adv_instance() kfree(adv) adv->scan_rsp_changed = false KASAN reported: BUG: KASAN: slab-use-after-free in hci_set_ext_scan_rsp_data_sync+0x2e1/0x300 Write of size 1 at addr ffff88810a45d21d by task kworker/u17:0/88 Workqueue: hci0 hci_cmd_sync_work Call Trace: hci_set_ext_scan_rsp_data_sync+0x2e1/0x300 hci_schedule_adv_instance_sync+0x390/0x4c0 hci_cmd_sync_work+0x173/0x300 Allocated by task 87: hci_add_adv_instance+0x538/0xac0 add_advertising+0x885/0x1160 Freed by task 89: kfree+0x131/0x3c0 hci_remove_adv_instance+0x1d8/0x3b0 hci_le_ext_adv_term_evt+0x17b/0x730 Protect the instance lookup and payload construction in the extended advertising, scan response, and periodic advertising data paths. Snapshot the advertising parameters under hdev->lock, but release the lock before waiting for the controller. Clear advertising-data dirty bits before issuing their commands and restore them after a failure using a fresh lookup. Likewise, update the reported transmit power through a fresh lookup after the parameter command completes. No adv_info pointer then survives an HCI command wait.

What

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: hci_sync: Fix advertising data UAFs hci_find_adv_instance() returns an adv_info pointer that is valid only while hdev->lock is held. The advertising command-sync paths perform instance lookups without that lock and, in some cases, retain the pointer while waiting for a controller response. An advertising termination event can therefore interleave as follows: hci_cmd_sync_work hci_rx_work hci_find_adv_instance() __hci_cmd_sync_status() wait for controller reply hci_dev_lock() hci_remove_adv_instance() kfree(adv) adv->scan_rsp_changed = false KASAN reported: BUG: KASAN: slab-use-after-free in hci_set_ext_scan_rsp_data_sync+0x2e1/0x300 Write of size 1 at addr ffff88810a45d21d by task kworker/u17:0/88 Workqueue: hci0 hci_cmd_sync_work Call Trace: hci_set_ext_scan_rsp_data_sync+0x2e1/0x300 hci_schedule_adv_instance_sync+0x390/0x4c0 hci_cmd_sync_work+0x173/0x300 Allocated by task 87: hci_add_adv_instance+0x538/0xac0 add_advertising+0x885/0x1160 Freed by task 89: kfree+0x131/0x3c0 hci_remove_adv_instance+0x1d8/0x3b0 hci_le_ext_adv_term_evt+0x17b/0x730 Protect the instance lookup and payload construction in the extended advertising, scan response, and periodic advertising data paths. Snapshot the advertising parameters under hdev->lock, but release the lock before waiting for the controller. Clear advertising-data dirty bits before issuing their commands and restore them after a failure using a fresh lookup. Likewise, update the reported transmit power through a fresh lookup after the parameter command completes. No adv_info pointer then survives an HCI command wait.

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 an adjacent network may attempt exploitation without authentication or user interaction. 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: Fix advertising data UAFs hci_find_adv_instance() returns an adv_info pointer that is valid only while hdev->lock is held. The advertising command-sync paths perform instance lookups without that lock and, in some cases, retain the pointer while waiting for a controller response. An advertising termination event can therefore interleave as follows: hci_cmd_sync_work hci_rx_work hci_find_adv_instance() __hci_cmd_sync_status() wait for controller reply hci_dev_lock() hci_remove_adv_instance() kfree(adv) adv->scan_rsp_changed = false KASAN reported: BUG: KASAN: slab-use-after-free in hci_set_ext_scan_rsp_data_sync+0x2e1/0x300 Write of size 1 at addr ffff88810a45d21d by task kworker/u17:0/88 Workqueue: hci0 hci_cmd_sync_work Call Trace: hci_set_ext_scan_rsp_data_sync+0x2e1/0x300 hci_schedule_adv_instance_sync+0x390/0x4c0 hci_cmd_sync_work+0x173/0x300 Allocated by task 87: hci_add_adv_instance+0x538/0xac0 add_advertising+0x885/0x1160 Freed by task 89: kfree+0x131/0x3c0 hci_remove_adv_instance+0x1d8/0x3b0 hci_le_ext_adv_term_evt+0x17b/0x730 Protect the instance lookup and payload construction in the extended advertising, scan response, and periodic advertising data paths. Snapshot the advertising parameters under hdev->lock, but release the lock before waiting for the controller. Clear advertising-data dirty bits before issuing their commands and restore them after a failure using a fresh lookup. Likewise, update the reported transmit power through a fresh lookup after the parameter command completes. No adv_info pointer then survives an HCI command wait.

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 an adjacent network may attempt exploitation without authentication or user interaction. 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
an adjacent network → vulnerable operation → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Adjacent
Privileges required
None: unauthenticated exploitation is possible
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:A/AC:L/PR:N/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.

AVAdjacentAttack vector: The attacker must be on an adjacent or logically close network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing 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
No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
Unauthenticated
A

Official authority intelligence

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

ENISA EUVD · EUVD-2026-59702Official EUVD mapping

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: hci_sync: Fix advertising data UAFs hci_find_adv_instance() returns an adv_info pointer that is valid only while hdev->lock is held. The advertising command-sync paths perform instance lookups without that lock and, in some cases, retain the pointer while waiting for a controller response. An advertising termination event can therefore interleave as follows: hci_cmd_sync_work hci_rx_work hci_find_adv_instance() __hci_cmd_sync_status() wait for controller reply hci_dev_lock() hci_remove_adv_instance() kfree(adv) adv->scan_rsp_changed = false KASAN reported: BUG: KASAN: slab-use-after-free in hci_set_ext_scan_rsp_data_sync+0x2e1/0x300 Write of size 1 at addr ffff88810a45d21d by task kworker/u17:0/88 Workqueue: hci0 hci_cmd_sync_work Call Trace: hci_set_ext_scan_rsp_data_sync+0x2e1/0x300 hci_schedule_adv_instance_sync+0x390/0x4c0 hci_cmd_sync_work+0x173/0x300 Allocated by task 87: hci_add_adv_instance+0x538/0xac0 add_advertising+0x885/0x1160 Freed by task 89: kfree+0x131/0x3c0 hci_remove_adv_instance+0x1d8/0x3b0 hci_le_ext_adv_term_evt+0x17b/0x730 Protect the instance lookup and payload construction in the extended advertising, scan response, and periodic advertising data paths. Snapshot the advertising parameters under hdev->lock, but release the lock before waiting for the controller. Clear advertising-data dirty bits before issuing their commands and restore them after a failure using a fresh lookup. Likewise, update the reported transmit power through a fresh lookup after the parameter command completes. No adv_info pointer then survives an HCI command wait.

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

Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um root Rechte zu erlangen, um einen Denial of Service herbeizuführen oder einen nicht näher spezifizierten Angriff durchzuführen.

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

d?id=CVE-2026-74499 Référence CVE CVE-2026-74500 https://www.cve.org/CVERecord?id=CVE-2026-74500 Référence CVE CVE-2026-74501 https://www.cve.org/CVERecord?id=CVE-2026-74501 Référence CVE CVE-2026-74502 https://www.cve.org/CVERecord?id=CVE-2026-74502 Référence CVE CVE-2026-74503 https://www.cve.org/CVERecord?id=CVE-2026-74503 Référence CVE CVE-2026-74504 https://www.cve.org/CVERecord?id=CVE-2026-74504 Référence CVE CVE-2026-74505 https://www.cve.org/CVERecord?id=CVE-2026-74505 Référence CVE CVE-2026-74507 https://www.cve.org/CVERecord?id=CVE-2026-74507 Référence CVE CVE-2026-74508 https://www.cve.org/CVERecord?id=CVE-2026-74508 Référence CVE CVE-2026-74509 https://www.cve.org/CVERecord?id=CVE-2026-74509 Référence CVE CVE-2026-74510 https://www.cve.org/CVERecord?id=CVE-2026-74510 Référence CVE CVE-2026-74512 https://www.cve.org/CVERecord?id=CVE-2026-74512 Référence CVE CVE-2026-74514 https://www.cve.org/CVERecord?id=CVE-2026-74514 Référence CVE CVE-2026-74515 https://www.cve.org/CVERecord?id=CVE-2026-74515 Référence CVE CVE-2026-74516 https://www.cve.org/CVERecord?id=CVE-2026-74516 Référence CVE CVE-2026-74517 https://www.cve.org/CVERecord?id=CVE-2026-74517 Référence CVE CVE-2026-74518 https://www.cve.org/CVERecord?id=CVE-2026-74518 Référence CVE CVE-2026-74519 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-74394 Référence CVE CVE-2026-74395 https://www.cve.org/CVERecord?id=CVE-2026-74395 Référence CVE CVE-2026-74454 https://www.cve.org/CVERecord?id=CVE-2026-74454 Référence CVE CVE-2026-74474 https://www.cve.org/CVERecord?id=CVE-2026-74474 Référence CVE CVE-2026-74481 https://www.cve.org/CVERecord?id=CVE-2026-74481 Référence CVE CVE-2026-74482 https://www.cve.org/CVERecord?id=CVE-2026-74482 Référence CVE CVE-2026-74488 https://www.cve.org/CVERecord?id=CVE-2026-74488 Référence CVE CVE-2026-74495 https://www.cve.org/CVERecord?id=CVE-2026-74495 Référence CVE CVE-2026-74496 https://www.cve.org/CVERecord?id=CVE-2026-74496 Référence CVE CVE-2026-74509 https://www.cve.org/CVERecord?id=CVE-2026-74509 Référence CVE CVE-2026-74510 https://www.cve.org/CVERecord?id=CVE-2026-74510 Référence CVE CVE-2026-74512 https://www.cve.org/CVERecord?id=CVE-2026-74512 Référence CVE CVE-2026-74516 https://www.cve.org/CVERecord?id=CVE-2026-74516 Référence CVE CVE-2026-74518 https://www.cve.org/CVERecord?id=CVE-2026-74518 Référence CVE CVE-2026-74527 https://www.cve.org/CVERecord?id=CVE-2026-74527 Référence CVE CVE-2026-74537 https://www.cve.org/CVERecord?id=CVE-2026-74537 Référence CVE CVE-2026-74548 https://www.cve.org/CVERecord?id=CVE-2026-74548 Référence CVE CVE-2026-74550 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-74493 Référence CVE CVE-2026-74494 https://www.cve.org/CVERecord?id=CVE-2026-74494 Référence CVE CVE-2026-74495 https://www.cve.org/CVERecord?id=CVE-2026-74495 Référence CVE CVE-2026-74497 https://www.cve.org/CVERecord?id=CVE-2026-74497 Référence CVE CVE-2026-74498 https://www.cve.org/CVERecord?id=CVE-2026-74498 Référence CVE CVE-2026-74499 https://www.cve.org/CVERecord?id=CVE-2026-74499 Référence CVE CVE-2026-74505 https://www.cve.org/CVERecord?id=CVE-2026-74505 Référence CVE CVE-2026-74507 https://www.cve.org/CVERecord?id=CVE-2026-74507 Référence CVE CVE-2026-74508 https://www.cve.org/CVERecord?id=CVE-2026-74508 Référence CVE CVE-2026-74509 https://www.cve.org/CVERecord?id=CVE-2026-74509 Référence CVE CVE-2026-74510 https://www.cve.org/CVERecord?id=CVE-2026-74510 Référence CVE CVE-2026-74512 https://www.cve.org/CVERecord?id=CVE-2026-74512 Référence CVE CVE-2026-74514 https://www.cve.org/CVERecord?id=CVE-2026-74514 Référence CVE CVE-2026-74515 https://www.cve.org/CVERecord?id=CVE-2026-74515 Référence CVE CVE-2026-74516 https://www.cve.org/CVERecord?id=CVE-2026-74516 Référence CVE CVE-2026-74518 https://www.cve.org/CVERecord?id=CVE-2026-74518 Référence CVE CVE-2026-74519 https://www.cve.org/CVERecord?id=CVE-2026-74519 Référence CVE CVE-2026-74522 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-74394 Référence CVE CVE-2026-74395 https://www.cve.org/CVERecord?id=CVE-2026-74395 Référence CVE CVE-2026-74454 https://www.cve.org/CVERecord?id=CVE-2026-74454 Référence CVE CVE-2026-74474 https://www.cve.org/CVERecord?id=CVE-2026-74474 Référence CVE CVE-2026-74481 https://www.cve.org/CVERecord?id=CVE-2026-74481 Référence CVE CVE-2026-74482 https://www.cve.org/CVERecord?id=CVE-2026-74482 Référence CVE CVE-2026-74488 https://www.cve.org/CVERecord?id=CVE-2026-74488 Référence CVE CVE-2026-74495 https://www.cve.org/CVERecord?id=CVE-2026-74495 Référence CVE CVE-2026-74496 https://www.cve.org/CVERecord?id=CVE-2026-74496 Référence CVE CVE-2026-74509 https://www.cve.org/CVERecord?id=CVE-2026-74509 Référence CVE CVE-2026-74510 https://www.cve.org/CVERecord?id=CVE-2026-74510 Référence CVE CVE-2026-74512 https://www.cve.org/CVERecord?id=CVE-2026-74512 Référence CVE CVE-2026-74516 https://www.cve.org/CVERecord?id=CVE-2026-74516 Référence CVE CVE-2026-74518 https://www.cve.org/CVERecord?id=CVE-2026-74518 Référence CVE CVE-2026-74527 https://www.cve.org/CVERecord?id=CVE-2026-74527 Référence CVE CVE-2026-74537 https://www.cve.org/CVERecord?id=CVE-2026-74537 Référence CVE CVE-2026-74548 https://www.cve.org/CVERecord?id=CVE-2026-74548 Référence CVE CVE-2026-74550 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-74499 Référence CVE CVE-2026-74500 https://www.cve.org/CVERecord?id=CVE-2026-74500 Référence CVE CVE-2026-74501 https://www.cve.org/CVERecord?id=CVE-2026-74501 Référence CVE CVE-2026-74502 https://www.cve.org/CVERecord?id=CVE-2026-74502 Référence CVE CVE-2026-74503 https://www.cve.org/CVERecord?id=CVE-2026-74503 Référence CVE CVE-2026-74504 https://www.cve.org/CVERecord?id=CVE-2026-74504 Référence CVE CVE-2026-74505 https://www.cve.org/CVERecord?id=CVE-2026-74505 Référence CVE CVE-2026-74507 https://www.cve.org/CVERecord?id=CVE-2026-74507 Référence CVE CVE-2026-74508 https://www.cve.org/CVERecord?id=CVE-2026-74508 Référence CVE CVE-2026-74509 https://www.cve.org/CVERecord?id=CVE-2026-74509 Référence CVE CVE-2026-74510 https://www.cve.org/CVERecord?id=CVE-2026-74510 Référence CVE CVE-2026-74512 https://www.cve.org/CVERecord?id=CVE-2026-74512 Référence CVE CVE-2026-74514 https://www.cve.org/CVERecord?id=CVE-2026-74514 Référence CVE CVE-2026-74515 https://www.cve.org/CVERecord?id=CVE-2026-74515 Référence CVE CVE-2026-74516 https://www.cve.org/CVERecord?id=CVE-2026-74516 Référence CVE CVE-2026-74517 https://www.cve.org/CVERecord?id=CVE-2026-74517 Référence CVE CVE-2026-74518 https://www.cve.org/CVERecord?id=CVE-2026-74518 Référence CVE CVE-2026-74519 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.184 ≤ 6.1.*, 6.6.154 ≤ 6.6.*, 6.12.103 ≤ 6.12.*, 6.18.44 ≤ 6.18.*, 7.1.8 ≤ 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
To mitigate this issue, disable the Bluetooth service if it is not required. This can be achieved by stopping and disabling the `bluetooth` service: ```bash systemctl stop bluetooth systemctl disable bluetooth ``` This action will prevent the Bluetooth stack from being active, thereby avoiding the vulnerable code path. A system reboot may be required for the changes to take full effect.
04

Evidence and provenance

Published 15 Aug 2026 · Last source change 27 Aug 2026, 12:39 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-23
European sourceENISA EUVD · EUVD-2026-59702
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
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 from remediation: access.redhat.com/CVE-2026-74509 to remediation: access.redhat.com/CVE-2026-74509.
    Before
    remediation: access.redhat.com/CVE-2026-74509
    After
    remediation: access.redhat.com/CVE-2026-74509
    Red Hat Product Security ↗
  2. Remediation statusRemediation status changed from Awaiting fix to Mitigation available.
    Before
    Awaiting fix
    After
    Mitigation available
    Red Hat Product Security ↗
  3. Affected versionsThe structured affected or fixed version information changed.
    Before
    cba6b758711cab946c787f7c15be92cc749b8e1f < 565971488191bf54a87a417abafab6ad0de72201; cba6b758711cab946c787f7c15be92cc749b8e1f < 95cdcd8c82a501931fd3ae9b3811b0b6da167e94; cba6b758711cab946c787f7c15be92cc749b8e1f < eb1d8318764de7216e6dbba29a24d69f7ce51348; cba6b758711cab946c787f7c15be92cc749b8e1f < b16ebdbebd2d37f4cdc590bc3e9db71fe90350a3; cba6b758711cab946c787f7c15be92cc749b8e1f < cdc36db204ffd97b947d64374cf23a210dc74777; 42fe380baaaccbe635c34ca07b29d19b9ec2498d; 5.15.210 < 5.16; 5.17 · Fixed: < 5.17; 6.1.184 ≤ 6.1.*; 6.12.103 ≤ 6.12.*; 6.18.44 ≤ 6.18.*; 7.1.8 ≤ 7.1.*; 7.2 ≤ *
    After
    cba6b758711cab946c787f7c15be92cc749b8e1f < 565971488191bf54a87a417abafab6ad0de72201; cba6b758711cab946c787f7c15be92cc749b8e1f < c4cec575a6d6f7c36808a3a0017b0675968bb06b; cba6b758711cab946c787f7c15be92cc749b8e1f < 95cdcd8c82a501931fd3ae9b3811b0b6da167e94; cba6b758711cab946c787f7c15be92cc749b8e1f < eb1d8318764de7216e6dbba29a24d69f7ce51348; cba6b758711cab946c787f7c15be92cc749b8e1f < b16ebdbebd2d37f4cdc590bc3e9db71fe90350a3; cba6b758711cab946c787f7c15be92cc749b8e1f < cdc36db204ffd97b947d64374cf23a210dc74777; 42fe380baaaccbe635c34ca07b29d19b9ec2498d; 5.15.210 < 5.16 · Fixed: < 5.17; 6.1.184 ≤ 6.1.*; 6.6.154 ≤ 6.6.*; 6.12.103 ≤ 6.12.*; 6.18.44 ≤ 6.18.*; 7.1.8 ≤ 7.1.*; 7.2 ≤ *
    CNA ↗
  4. Vendor guidanceAuthoritative vendor guidance changed: added remediation: git.kernel.org/565971488191bf54a87a417abafab6ad0de72201; removed remediation: git.kernel.org/95cdcd8c82a501931fd3ae9b3811b0b6da167e94.
    Before
    remediation: git.kernel.org/95cdcd8c82a501931fd3ae9b3811b0b6da167e94
    After
    remediation: git.kernel.org/565971488191bf54a87a417abafab6ad0de72201
    CNA ↗
  5. Affected versionsThe structured affected or fixed version information changed.
    Before
    cba6b758711cab946c787f7c15be92cc749b8e1f < 95cdcd8c82a501931fd3ae9b3811b0b6da167e94; cba6b758711cab946c787f7c15be92cc749b8e1f < eb1d8318764de7216e6dbba29a24d69f7ce51348; cba6b758711cab946c787f7c15be92cc749b8e1f < b16ebdbebd2d37f4cdc590bc3e9db71fe90350a3; cba6b758711cab946c787f7c15be92cc749b8e1f < cdc36db204ffd97b947d64374cf23a210dc74777; 42fe380baaaccbe635c34ca07b29d19b9ec2498d; 5.15.210 < 5.16; 5.17 · Fixed: < 5.17; 6.12.103 ≤ 6.12.*; 6.18.44 ≤ 6.18.*; 7.1.8 ≤ 7.1.*; 7.2 ≤ *
    After
    cba6b758711cab946c787f7c15be92cc749b8e1f < 565971488191bf54a87a417abafab6ad0de72201; cba6b758711cab946c787f7c15be92cc749b8e1f < 95cdcd8c82a501931fd3ae9b3811b0b6da167e94; cba6b758711cab946c787f7c15be92cc749b8e1f < eb1d8318764de7216e6dbba29a24d69f7ce51348; cba6b758711cab946c787f7c15be92cc749b8e1f < b16ebdbebd2d37f4cdc590bc3e9db71fe90350a3; cba6b758711cab946c787f7c15be92cc749b8e1f < cdc36db204ffd97b947d64374cf23a210dc74777; 42fe380baaaccbe635c34ca07b29d19b9ec2498d; 5.15.210 < 5.16; 5.17 · Fixed: < 5.17; 6.1.184 ≤ 6.1.*; 6.12.103 ≤ 6.12.*; 6.18.44 ≤ 6.18.*; 7.1.8 ≤ 7.1.*; 7.2 ≤ *
    CNA ↗
  6. Affected versionsThe structured affected or fixed version information changed.
    Before
    cba6b758711cab946c787f7c15be92cc749b8e1f < 95cdcd8c82a501931fd3ae9b3811b0b6da167e94; cba6b758711cab946c787f7c15be92cc749b8e1f < eb1d8318764de7216e6dbba29a24d69f7ce51348; cba6b758711cab946c787f7c15be92cc749b8e1f < b16ebdbebd2d37f4cdc590bc3e9db71fe90350a3; cba6b758711cab946c787f7c15be92cc749b8e1f < cdc36db204ffd97b947d64374cf23a210dc74777; 42fe380baaaccbe635c34ca07b29d19b9ec2498d; 5.15.210 < 5.16; 5.17 · Fixed: < 5.17; 6.12.103 ≤ 6.12.*; 6.18.44 ≤ 6.18.*; 7.1.8 ≤ 7.1.*; 7.2-rc6 ≤ *
    After
    cba6b758711cab946c787f7c15be92cc749b8e1f < 95cdcd8c82a501931fd3ae9b3811b0b6da167e94; cba6b758711cab946c787f7c15be92cc749b8e1f < eb1d8318764de7216e6dbba29a24d69f7ce51348; cba6b758711cab946c787f7c15be92cc749b8e1f < b16ebdbebd2d37f4cdc590bc3e9db71fe90350a3; cba6b758711cab946c787f7c15be92cc749b8e1f < cdc36db204ffd97b947d64374cf23a210dc74777; 42fe380baaaccbe635c34ca07b29d19b9ec2498d; 5.15.210 < 5.16; 5.17 · Fixed: < 5.17; 6.12.103 ≤ 6.12.*; 6.18.44 ≤ 6.18.*; 7.1.8 ≤ 7.1.*; 7.2 ≤ *
    CNA ↗
  7. SeveritySeverity changed from Unknown to High.
    Before
    Unknown
    After
    High
    CNA ↗
  8. CVSS scoreCVSS score changed from not recorded to 8.8 (CVSS 3.1 · CNA · CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H).
    Before
    not recorded
    After
    8.8 (CVSS 3.1 · CNA · CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H)
    CNA ↗
  9. Catalogue recordCVE added to the BlackTree catalogue.
    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-59702↗Vendor CSAF · Red Hat Product Security↗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-74509 · cve.blacktree.nl