cve.bz

CVE-2026-46275 linux linux kernel: Race Condition

7.8 highEPSS 0.2%Fix available

High (7.8) in linux linux kernel. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.

On this page
In the Linux kernel, the following vulnerability has been resolved: Bluetooth: hci_uart: fix UAFs and race conditions in close and init paths Vulnerabilities leading to Use-After-Free (UAF) and Null Pointer Dereference (NPD) conditions were observed in the lifecycle management of hci_uart. The primary issue arises because the workqueues (init_ready and write_work) are only flushed/cancelled if the HCI_UART_PROTO_READY flag is set during TTY close. If a hangup occurs before setup completes, hci_uart_tty_close() skips the teardown of these workqueues and proceeds to free the `hu` struct. When the scheduled work executes later, it blindly dereferences the freed `hu` struct. Furthermore, several data races and UAFs were identified in the teardown sequence: 1. Calling hci_uart_flush() from hci_uart_close() without effectively disabling write_work causes a race condition where both can concurrently double-free hu->tx_skb. This happens because protocol timers can concurrently invoke hci_uart_tx_wakeup() and requeue write_work. 2. Calling hci_free_dev(hdev) before hu->proto->close(hu) causes a UAF when vendor specific protocol close callbacks dereference hu->hdev. 3. In the initialization error paths, failing to take the proto_lock write lock before clearing PROTO_READY leads to races with active readers. Additionally, hci_uart_tty_receive() accesses hu->hdev outside the read lock, leading to UAFs if the initialization error path frees hdev concurrently. Fix these synchronization and lifecycle issues by: 1. Re-ordering hci_uart_tty_close() to clear HCI_UART_PROTO_READY first, followed immediately by a cancel_work_sync(&hu->write_work). Clearing the flag locks out concurrent protocol timers from successfully invoking hci_uart_tx_wakeup(), effectively rendering the cancellation permanent and preventing the tx_skb double-free. 2. Note: Clearing PROTO_READY early causes hci_uart_close() to skip hu->proto->flush(). This is perfectly safe in the tty_close path because hu->proto->close() executes shortly after, which intrinsically purges all protocol SKB queues and tears down the state. 3. Relocating hu->proto->close(hu) strictly prior to hci_free_dev(hdev) across all close and error paths to prevent vendor-level UAFs. 4. Moving the hdev->stat.byte_rx increment in hci_uart_tty_receive() inside the proto_lock read-side critical section to safely synchronize with device unregistration. 5. Adding cancel_work_sync(&hu->write_work) to hci_uart_close() to safely flush the workqueue before hci_uart_flush() is invoked via the HCI core. 6. Utilizing cancel_work_sync() instead of disable_work_sync() across all paths to prevent permanently breaking user-space retry capabilities.

Severity

CVSS 3.1

7.8 high
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS
0.2% (unchanged from 0.2% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 13th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-10-16. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-362 Concurrent Execution using Shared Resource with Improper Synchronization (Race Condition)
OWASP Top 10
A06:2025 Insecure Design
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-46275 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-46275?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-46275?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-46275 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Linuxfrom 4.14.203 before 4.15
Linuxfrom 4.19.153 before 4.20
Linuxfrom 5.4.73 before 5.5
Linuxfrom 5.8.17 before 5.9
Linuxfrom 5.9.2 before 5.10
Linux5.10 and later

Fixed in

ProductRelease lineFixed in
Linux5.105.10.258
Linux5.155.15.209
Linux6.16.1.175
Linux6.66.6.142
Linux6.126.12.92
Linux6.186.18.34
Linux7.07.0.11
Linuxlater releases7.1

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12linux6.1.176-1DEBIAN-CVE-2026-46275
Debian13linux6.12.94-1DEBIAN-CVE-2026-46275
Debian14linux7.0.12-1DEBIAN-CVE-2026-46275
Ubuntu16.04:LTSlinux-hwe-edgeno fix listedUBUNTU-CVE-2026-46275
Ubuntu18.04:LTSlinux-gcp, linux-hwe, linux-oem and 12 moreno fix listedUBUNTU-CVE-2026-46275
Ubuntu20.04:LTSlinux-gke, linux-gkeop, linux-riscv and 26 moreno fix listedUBUNTU-CVE-2026-46275
Ubuntu22.04:LTSlinux5.15.0-186.196UBUNTU-CVE-2026-46275 USN-8575-1
Ubuntu22.04:LTSlinux-aws5.15.0-1112.119UBUNTU-CVE-2026-46275 USN-8575-2
Ubuntu22.04:LTSlinux-aws-6.86.8.0-1064.67~22.04.1UBUNTU-CVE-2026-46275 USN-8729-6
Ubuntu22.04:LTSlinux-azure, linux-azure-fde5.15.0-1117.126UBUNTU-CVE-2026-46275 USN-8575-3 USN-8610-1
Ubuntu22.04:LTSlinux-azure-fde-6.86.8.0-1065.72~22.04.1UBUNTU-CVE-2026-46275 USN-8793-2
Ubuntu22.04:LTSlinux-gcp5.15.0-1112.122UBUNTU-CVE-2026-46275 USN-8575-1
Ubuntu22.04:LTSlinux-gcp-6.8, linux-azure-6.86.8.0-1067.75~22.04.1UBUNTU-CVE-2026-46275 USN-8729-3 USN-8761-3
Ubuntu22.04:LTSlinux-gke5.15.0-1108.114UBUNTU-CVE-2026-46275 USN-8575-1
Ubuntu22.04:LTSlinux-gkeop5.15.0-1095.103UBUNTU-CVE-2026-46275 USN-8575-1
80 more for Ubuntu in the JSON and on Ubuntu's page.
Red Hatenterprise_linux:9::appstreamrv, perf, rtla and 29 more0:5.14.0-687.55.1.el9_8RHSA-2026:76739
Red Hatenterprise_linux:9::baseoskernel, kernel-64k, kernel-core and 45 more0:5.14.0-687.55.1.el9_8RHSA-2026:76739
Red Hatenterprise_linux:9::crblibperf, perf-debuginfo, kernel-debuginfo and 16 more0:5.14.0-687.55.1.el9_8RHSA-2026:76739
Red Hatenterprise_linux:9::nfvkernel-rt, kernel-rt-core, perf-debuginfo and 18 more0:5.14.0-687.55.1.el9_8RHSA-2026:76739
Red Hatenterprise_linux:9::realtimekernel-rt, kernel-rt-64k, kernel-rt-core and 35 more0:5.14.0-687.55.1.el9_8RHSA-2026:76739
Red Hatenterprise_linux:10.2rv, perf, rtla and 88 more0:6.12.0-211.63.1.el10_2RHSA-2026:76738
Red Hatshadow_migration_toolkit:10::el10kernel-modules-internal0:6.12.0-211.63.1.el10_2RHSA-2026:76738
SUSELinux Enterprise High Availability Extension 15 SP7, Linux Enterprise Live Patching 15 SP7, Linux Enterprise Module for Legacy 15 SP7 and 1 morekernel-default6.4.0-150700.53.73.2SUSE-SU-2026:3166-1
SUSELinux Enterprise High Availability Extension 16.0kernel-default6.12.0-160000.37.1SUSE-SU-2026:23237-1
SUSELinux Enterprise Live Patching 12 SP5kernel-default4.12.14-122.320.1SUSE-SU-2026:2914-1
SUSELinux Enterprise Live Patching 12 SP5kgraft-patch-SLE12-SP5_Update_851-8.3.1SUSE-SU-2026:2914-1
SUSELinux Enterprise Live Patching 15 SP7kernel-livepatch-SLE15-SP7-RT_Update_181-150700.1.5.1SUSE-SU-2026:3130-1
SUSELinux Enterprise Live Patching 15 SP7kernel-livepatch-SLE15-SP7_Update_191-150700.15.3.4SUSE-SU-2026:3166-1
SUSELinux Enterprise Module for Basesystem 15 SP7kernel-64kb, kernel-default, kernel-zfcpdump6.4.0-150700.53.73.2SUSE-SU-2026:3166-1
SUSELinux Enterprise Module for Basesystem 15 SP7kernel-default-base6.4.0-150700.53.73.2.150700.17.41.4SUSE-SU-2026:3166-1
SUSELinux Enterprise Module for Basesystem 15 SP7kernel-source6.4.0-150700.53.73.1SUSE-SU-2026:3166-1
SUSELinux Enterprise Module for Development Tools 15 SP7kernel-docs, kernel-syms, kernel-source6.4.0-150700.53.73.1SUSE-SU-2026:3166-1
SUSELinux Enterprise Module for Development Tools 15 SP7kernel-obs-build6.4.0-150700.53.73.2SUSE-SU-2026:3166-1
SUSELinux Enterprise Module for Public Cloud 15 SP7kernel-azure6.4.0-150700.53.73.2SUSE-SU-2026:3166-1
11 more for SUSE in the JSON and on SUSE's page.
openSUSELeap 16.0kernel-default-base6.12.0-160000.37.1.160000.2.19openSUSE-SU-2026:21555-1
openSUSELeap 16.0kernel-rt, dtb-aarch64, kernel-64kb and 9 more6.12.0-160000.37.1openSUSE-SU-2026:21555-1
openSUSETumbleweedkernel-source7.0.12-1.1openSUSE-SU-2026:11014-1
AlmaLinux10rv, perf, rtla and 72 more6.12.0-211.63.1.el10_2ALSA-2026:76738
Azure Linux3kernel6.6.143.1-1AZL-89600
Alpaquita23linux-lts6.1.175-r0BELL-CVE-2026-46275
Alpaquita25linux-lts6.12.92-r0BELL-CVE-2026-46275
Alpaquitastreamlinux-lts6.18.35-r1BELL-CVE-2026-46275

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; Red Hat Security Data © Red Hat, Inc., CC BY 4.0; SUSE security data, CC BY 4.0; AlmaLinux's OSV database, MIT; Microsoft's Azure Linux vulnerability data, MIT; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · Red Hat · SUSE · openSUSE · Alpaquita.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

Bluetooth hci_uart has lifecycle races in the close and init paths where init_ready or write_work can remain scheduled after the hu object or the hdev object is torn down. A local attacker who can interact with the relevant Bluetooth UART TTY path may trigger a hangup or close during initialization, allowing later workqueue execution to dereference freed state. The same teardown area also includes a possible double free of hu tx_skb and a vendor close callback UAF when hci_free_dev runs before proto close. For the CVSS the PR:L is used for the paranoid score because reliable triggering needs local code execution or access to the affected TTY or Bluetooth UART control path, but it does not necessarily require full host administrator privileges in all deployments. The issue is not directly network reachable.

Red Hat's mitigation

Mitigation for this issue is either not available or the currently available options don't meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 10kernel-0:6.12.0-211.63.1.el10_2Fixed 2026-10-08RHSA-2026:76738
Red Hat Enterprise Linux 9kernel-0:5.14.0-687.55.1.el9_8Fixed 2026-10-08RHSA-2026:76739
Shadow Migration Toolkit for Virtualization for RHEL 10kernel-0:6.12.0-211.63.1.el10_2Fixed 2026-10-08RHSA-2026:76738
Red Hat Enterprise Linux 6kernelOut of support scope
Red Hat Enterprise Linux 7kernelNot affected
Red Hat Enterprise Linux 7kernel-rtNot affected
Red Hat Enterprise Linux 8kernelAffected
Red Hat Enterprise Linux 8kernel-rtAffected
Red Hat Enterprise Linux 9kernel-rtAffected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-46275.

ICS advisories (CISA)

AdvisoryTitlePublishedSectorsAffectedFixed
ICSA-26-295-16Siemens SIMATIC S7-1500 TM MFP2026-10-13Critical Manufacturing, Transportation Systems, Energy, Healthcare and Public Health, Financial Services, Government Services and FacilitiesSIMATIC S7-1500 TM MFP - GNU/Linux subsystemnone listed

From CISA's ICS advisories (CSAF), provided under CISA's notification. Only the facts are shown; each advisory is on CISA's page. Credits.

Attack patterns (CAPEC)

  • CAPEC-26 Leveraging Race Conditions Likelihood: High · Severity: High
  • CAPEC-29 Leveraging Time-of-Check and Time-of-Use (TOCTOU) Race Conditions Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON