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

Bluetooth: hci_uart: fix UAFs and race conditions in close and init paths

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 20 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 5 Aug 2026

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • Exploitation requires an existing local or physical foothold with privileges.
  • EPSS is 0.13% 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 20 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.

24 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.94-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.176-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.0.12-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.0.12-1Debian Security Tracker ↗Source updated 6 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-46275 · CSAF 2.0 · revision 12 · interimSUSE Product Security TeamCVE-2026-46275
201 known affected

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

  • kernel-default as component of SUSE Linux Enterprise High Performance Computing 15 SP2
  • kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP2
  • kernel-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP2
  • kernel-macros as component of SUSE Linux Enterprise High Performance Computing 15 SP2
  • kernel-source as component of SUSE Linux Enterprise High Performance Computing 15 SP2
  • reiserfs-kmp-default as component of SUSE Linux Enterprise High Performance Computing 15 SP2
  • kernel-default as component of SUSE Linux Enterprise High Performance Computing 15 SP3
  • kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP3
  • kernel-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP3
  • kernel-macros as component of SUSE Linux Enterprise High Performance Computing 15 SP3
  • kernel-source as component of SUSE Linux Enterprise High Performance Computing 15 SP3
  • reiserfs-kmp-default as component of SUSE Linux Enterprise High Performance Computing 15 SP3
Summary
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.
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
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-35079

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

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
Not supplied in the stored EUVD record
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 20 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_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.

What

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.

Why

The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently.

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

Why

The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently.

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 → Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition') → 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: a standard category for the underlying weakness.
CWE-362 ↗

CWE-362: Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition'). The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently.

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.
CWE-362
A

Official authority intelligence

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

BSI · German · WID-SEC-2026-1827Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service

Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder nicht bekannte Auswirkungen zu erzielen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20260610Security Bulletin 10 Jun 2026

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

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1252Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-46238 Référence CVE CVE-2026-46239 https://www.cve.org/CVERecord?id=CVE-2026-46239 Référence CVE CVE-2026-46240 https://www.cve.org/CVERecord?id=CVE-2026-46240 Référence CVE CVE-2026-46241 https://www.cve.org/CVERecord?id=CVE-2026-46241 Référence CVE CVE-2026-46242 https://www.cve.org/CVERecord?id=CVE-2026-46242 Référence CVE CVE-2026-46243 https://www.cve.org/CVERecord?id=CVE-2026-46243 Référence CVE CVE-2026-46244 https://www.cve.org/CVERecord?id=CVE-2026-46244 Référence CVE CVE-2026-46273 https://www.cve.org/CVERecord?id=CVE-2026-46273 Référence CVE CVE-2026-46274 https://www.cve.org/CVERecord?id=CVE-2026-46274 Référence CVE CVE-2026-46275 https://www.cve.org/CVERecord?id=CVE-2026-46275 Référence CVE CVE-2026-46289 https://www.cve.org/CVERecord?id=CVE-2026-46289 Référence CVE CVE-2026-46290 https://www.cve.org/CVERecord?id=CVE-2026-46290 Référence CVE CVE-2026-46291 https://www.cve.org/CVERecord?id=CVE-2026-46291 Référence CVE CVE-2026-46292 https://www.cve.org/CVERecord?id=CVE-2026-46292 Référence CVE CVE-2026-46293 https://www.cve.org/CVERecord?id=CVE-2026-46293 Référence CVE CVE-2026-46294 https://www.cve.org/CVERecord?id=CVE-2026-46294 Référence CVE CVE-2026-46295 https://www.cve.org/CVERecord?id=CVE-2026-46295 Référence CVE CVE-2026-46296 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1229Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-46249 Référence CVE CVE-2026-46250 https://www.cve.org/CVERecord?id=CVE-2026-46250 Référence CVE CVE-2026-46253 https://www.cve.org/CVERecord?id=CVE-2026-46253 Référence CVE CVE-2026-46259 https://www.cve.org/CVERecord?id=CVE-2026-46259 Référence CVE CVE-2026-46266 https://www.cve.org/CVERecord?id=CVE-2026-46266 Référence CVE CVE-2026-46267 https://www.cve.org/CVERecord?id=CVE-2026-46267 Référence CVE CVE-2026-46270 https://www.cve.org/CVERecord?id=CVE-2026-46270 Référence CVE CVE-2026-46273 https://www.cve.org/CVERecord?id=CVE-2026-46273 Référence CVE CVE-2026-46274 https://www.cve.org/CVERecord?id=CVE-2026-46274 Référence CVE CVE-2026-46275 https://www.cve.org/CVERecord?id=CVE-2026-46275 Référence CVE CVE-2026-46285 https://www.cve.org/CVERecord?id=CVE-2026-46285 Référence CVE CVE-2026-46289 https://www.cve.org/CVERecord?id=CVE-2026-46289 Référence CVE CVE-2026-46290 https://www.cve.org/CVERecord?id=CVE-2026-46290 Référence CVE CVE-2026-46291 https://www.cve.org/CVERecord?id=CVE-2026-46291 Référence CVE CVE-2026-46292 https://www.cve.org/CVERecord?id=CVE-2026-46292 Référence CVE CVE-2026-46293 https://www.cve.org/CVERecord?id=CVE-2026-46293 Référence CVE CVE-2026-46294 https://www.cve.org/CVERecord?id=CVE-2026-46294 Référence CVE CVE-2026-46295 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1203Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-45944 Référence CVE CVE-2026-46054 https://www.cve.org/CVERecord?id=CVE-2026-46054 Référence CVE CVE-2026-46130 https://www.cve.org/CVERecord?id=CVE-2026-46130 Référence CVE CVE-2026-46158 https://www.cve.org/CVERecord?id=CVE-2026-46158 Référence CVE CVE-2026-46170 https://www.cve.org/CVERecord?id=CVE-2026-46170 Référence CVE CVE-2026-46175 https://www.cve.org/CVERecord?id=CVE-2026-46175 Référence CVE CVE-2026-46181 https://www.cve.org/CVERecord?id=CVE-2026-46181 Référence CVE CVE-2026-46203 https://www.cve.org/CVERecord?id=CVE-2026-46203 Référence CVE CVE-2026-46266 https://www.cve.org/CVERecord?id=CVE-2026-46266 Référence CVE CVE-2026-46275 https://www.cve.org/CVERecord?id=CVE-2026-46275 Référence CVE CVE-2026-46315 https://www.cve.org/CVERecord?id=CVE-2026-46315 Référence CVE CVE-2026-46320 https://www.cve.org/CVERecord?id=CVE-2026-46320 Référence CVE CVE-2026-46324 https://www.cve.org/CVERecord?id=CVE-2026-46324 Référence CVE CVE-2026-46330 https://www.cve.org/CVERecord?id=CVE-2026-46330 Référence CVE CVE-2026-46331 https://www.cve.org/CVERecord?id=CVE-2026-46331 Référence CVE CVE-2026-52908 https://www.cve.org/CVERecord?id=CVE-2026-52908 Référence CVE CVE-2026-52909 https://www.cve.org/CVERecord?id=CVE-2026-52909 Référence CVE CVE-2026-52910 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1162Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-46238 Référence CVE CVE-2026-46239 https://www.cve.org/CVERecord?id=CVE-2026-46239 Référence CVE CVE-2026-46240 https://www.cve.org/CVERecord?id=CVE-2026-46240 Référence CVE CVE-2026-46241 https://www.cve.org/CVERecord?id=CVE-2026-46241 Référence CVE CVE-2026-46242 https://www.cve.org/CVERecord?id=CVE-2026-46242 Référence CVE CVE-2026-46243 https://www.cve.org/CVERecord?id=CVE-2026-46243 Référence CVE CVE-2026-46244 https://www.cve.org/CVERecord?id=CVE-2026-46244 Référence CVE CVE-2026-46273 https://www.cve.org/CVERecord?id=CVE-2026-46273 Référence CVE CVE-2026-46274 https://www.cve.org/CVERecord?id=CVE-2026-46274 Référence CVE CVE-2026-46275 https://www.cve.org/CVERecord?id=CVE-2026-46275 Référence CVE CVE-2026-46289 https://www.cve.org/CVERecord?id=CVE-2026-46289 Référence CVE CVE-2026-46290 https://www.cve.org/CVERecord?id=CVE-2026-46290 Référence CVE CVE-2026-46291 https://www.cve.org/CVERecord?id=CVE-2026-46291 Référence CVE CVE-2026-46292 https://www.cve.org/CVERecord?id=CVE-2026-46292 Référence CVE CVE-2026-46293 https://www.cve.org/CVERecord?id=CVE-2026-46293 Référence CVE CVE-2026-46294 https://www.cve.org/CVERecord?id=CVE-2026-46294 Référence CVE CVE-2026-46295 https://www.cve.org/CVERecord?id=CVE-2026-46295 Référence CVE CVE-2026-46296 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1093Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-46249 Référence CVE CVE-2026-46250 https://www.cve.org/CVERecord?id=CVE-2026-46250 Référence CVE CVE-2026-46253 https://www.cve.org/CVERecord?id=CVE-2026-46253 Référence CVE CVE-2026-46259 https://www.cve.org/CVERecord?id=CVE-2026-46259 Référence CVE CVE-2026-46266 https://www.cve.org/CVERecord?id=CVE-2026-46266 Référence CVE CVE-2026-46267 https://www.cve.org/CVERecord?id=CVE-2026-46267 Référence CVE CVE-2026-46270 https://www.cve.org/CVERecord?id=CVE-2026-46270 Référence CVE CVE-2026-46273 https://www.cve.org/CVERecord?id=CVE-2026-46273 Référence CVE CVE-2026-46274 https://www.cve.org/CVERecord?id=CVE-2026-46274 Référence CVE CVE-2026-46275 https://www.cve.org/CVERecord?id=CVE-2026-46275 Référence CVE CVE-2026-46285 https://www.cve.org/CVERecord?id=CVE-2026-46285 Référence CVE CVE-2026-46290 https://www.cve.org/CVERecord?id=CVE-2026-46290 Référence CVE CVE-2026-46294 https://www.cve.org/CVERecord?id=CVE-2026-46294 Référence CVE CVE-2026-46301 https://www.cve.org/CVERecord?id=CVE-2026-46301 Référence CVE CVE-2026-46303 https://www.cve.org/CVERecord?id=CVE-2026-46303 Référence CVE CVE-2026-46304 https://www.cve.org/CVERecord?id=CVE-2026-46304 Référence CVE CVE-2026-46307 https://www.cve.org/CVERecord?id=CVE-2026-46307 Référence CVE CVE-2026-46317 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1066Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-46236 Référence CVE CVE-2026-46238 https://www.cve.org/CVERecord?id=CVE-2026-46238 Référence CVE CVE-2026-46239 https://www.cve.org/CVERecord?id=CVE-2026-46239 Référence CVE CVE-2026-46240 https://www.cve.org/CVERecord?id=CVE-2026-46240 Référence CVE CVE-2026-46241 https://www.cve.org/CVERecord?id=CVE-2026-46241 Référence CVE CVE-2026-46242 https://www.cve.org/CVERecord?id=CVE-2026-46242 Référence CVE CVE-2026-46266 https://www.cve.org/CVERecord?id=CVE-2026-46266 Référence CVE CVE-2026-46273 https://www.cve.org/CVERecord?id=CVE-2026-46273 Référence CVE CVE-2026-46274 https://www.cve.org/CVERecord?id=CVE-2026-46274 Référence CVE CVE-2026-46275 https://www.cve.org/CVERecord?id=CVE-2026-46275 Référence CVE CVE-2026-46280 https://www.cve.org/CVERecord?id=CVE-2026-46280 Référence CVE CVE-2026-46282 https://www.cve.org/CVERecord?id=CVE-2026-46282 Référence CVE CVE-2026-46285 https://www.cve.org/CVERecord?id=CVE-2026-46285 Référence CVE CVE-2026-46286 https://www.cve.org/CVERecord?id=CVE-2026-46286 Référence CVE CVE-2026-46287 https://www.cve.org/CVERecord?id=CVE-2026-46287 Référence CVE CVE-2026-46290 https://www.cve.org/CVERecord?id=CVE-2026-46290 Référence CVE CVE-2026-46291 https://www.cve.org/CVERecord?id=CVE-2026-46291 Référence CVE CVE-2026-46292 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-46252 Référence CVE CVE-2026-46255 https://www.cve.org/CVERecord?id=CVE-2026-46255 Référence CVE CVE-2026-46261 https://www.cve.org/CVERecord?id=CVE-2026-46261 Référence CVE CVE-2026-46263 https://www.cve.org/CVERecord?id=CVE-2026-46263 Référence CVE CVE-2026-46265 https://www.cve.org/CVERecord?id=CVE-2026-46265 Référence CVE CVE-2026-46267 https://www.cve.org/CVERecord?id=CVE-2026-46267 Référence CVE CVE-2026-46270 https://www.cve.org/CVERecord?id=CVE-2026-46270 Référence CVE CVE-2026-46273 https://www.cve.org/CVERecord?id=CVE-2026-46273 Référence CVE CVE-2026-46274 https://www.cve.org/CVERecord?id=CVE-2026-46274 Référence CVE CVE-2026-46275 https://www.cve.org/CVERecord?id=CVE-2026-46275 Référence CVE CVE-2026-46276 https://www.cve.org/CVERecord?id=CVE-2026-46276 Référence CVE CVE-2026-46282 https://www.cve.org/CVERecord?id=CVE-2026-46282 Référence CVE CVE-2026-46283 https://www.cve.org/CVERecord?id=CVE-2026-46283 Référence CVE CVE-2026-46285 https://www.cve.org/CVERecord?id=CVE-2026-46285 Référence CVE CVE-2026-46286 https://www.cve.org/CVERecord?id=CVE-2026-46286 Référence CVE CVE-2026-46287 https://www.cve.org/CVERecord?id=CVE-2026-46287 Référence CVE CVE-2026-46292 https://www.cve.org/CVERecord?id=CVE-2026-46292 Référence CVE CVE-2026-46294 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0985Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-46238 Référence CVE CVE-2026-46249 https://www.cve.org/CVERecord?id=CVE-2026-46249 Référence CVE CVE-2026-46250 https://www.cve.org/CVERecord?id=CVE-2026-46250 Référence CVE CVE-2026-46253 https://www.cve.org/CVERecord?id=CVE-2026-46253 Référence CVE CVE-2026-46259 https://www.cve.org/CVERecord?id=CVE-2026-46259 Référence CVE CVE-2026-46267 https://www.cve.org/CVERecord?id=CVE-2026-46267 Référence CVE CVE-2026-46270 https://www.cve.org/CVERecord?id=CVE-2026-46270 Référence CVE CVE-2026-46273 https://www.cve.org/CVERecord?id=CVE-2026-46273 Référence CVE CVE-2026-46274 https://www.cve.org/CVERecord?id=CVE-2026-46274 Référence CVE CVE-2026-46275 https://www.cve.org/CVERecord?id=CVE-2026-46275 Référence CVE CVE-2026-46285 https://www.cve.org/CVERecord?id=CVE-2026-46285 Référence CVE CVE-2026-46294 https://www.cve.org/CVERecord?id=CVE-2026-46294 Référence CVE CVE-2026-46301 https://www.cve.org/CVERecord?id=CVE-2026-46301 Référence CVE CVE-2026-46303 https://www.cve.org/CVERecord?id=CVE-2026-46303 Référence CVE CVE-2026-46304 https://www.cve.org/CVERecord?id=CVE-2026-46304 Référence CVE CVE-2026-46307 https://www.cve.org/CVERecord?id=CVE-2026-46307 Référence CVE CVE-2026-46319 https://www.cve.org/CVERecord?id=CVE-2026-46319 Référence CVE CVE-2026-46328 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0954Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-46259 Référence CVE CVE-2026-46260 https://www.cve.org/CVERecord?id=CVE-2026-46260 Référence CVE CVE-2026-46261 https://www.cve.org/CVERecord?id=CVE-2026-46261 Référence CVE CVE-2026-46265 https://www.cve.org/CVERecord?id=CVE-2026-46265 Référence CVE CVE-2026-46266 https://www.cve.org/CVERecord?id=CVE-2026-46266 Référence CVE CVE-2026-46267 https://www.cve.org/CVERecord?id=CVE-2026-46267 Référence CVE CVE-2026-46270 https://www.cve.org/CVERecord?id=CVE-2026-46270 Référence CVE CVE-2026-46273 https://www.cve.org/CVERecord?id=CVE-2026-46273 Référence CVE CVE-2026-46274 https://www.cve.org/CVERecord?id=CVE-2026-46274 Référence CVE CVE-2026-46275 https://www.cve.org/CVERecord?id=CVE-2026-46275 Référence CVE CVE-2026-46276 https://www.cve.org/CVERecord?id=CVE-2026-46276 Référence CVE CVE-2026-46277 https://www.cve.org/CVERecord?id=CVE-2026-46277 Référence CVE CVE-2026-46278 https://www.cve.org/CVERecord?id=CVE-2026-46278 Référence CVE CVE-2026-46279 https://www.cve.org/CVERecord?id=CVE-2026-46279 Référence CVE CVE-2026-46280 https://www.cve.org/CVERecord?id=CVE-2026-46280 Référence CVE CVE-2026-46281 https://www.cve.org/CVERecord?id=CVE-2026-46281 Référence CVE CVE-2026-46282 https://www.cve.org/CVERecord?id=CVE-2026-46282 Référence CVE CVE-2026-46283 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-46253 Référence CVE CVE-2026-46254 https://www.cve.org/CVERecord?id=CVE-2026-46254 Référence CVE CVE-2026-46259 https://www.cve.org/CVERecord?id=CVE-2026-46259 Référence CVE CVE-2026-46261 https://www.cve.org/CVERecord?id=CVE-2026-46261 Référence CVE CVE-2026-46263 https://www.cve.org/CVERecord?id=CVE-2026-46263 Référence CVE CVE-2026-46266 https://www.cve.org/CVERecord?id=CVE-2026-46266 Référence CVE CVE-2026-46267 https://www.cve.org/CVERecord?id=CVE-2026-46267 Référence CVE CVE-2026-46270 https://www.cve.org/CVERecord?id=CVE-2026-46270 Référence CVE CVE-2026-46274 https://www.cve.org/CVERecord?id=CVE-2026-46274 Référence CVE CVE-2026-46275 https://www.cve.org/CVERecord?id=CVE-2026-46275 Référence CVE CVE-2026-46276 https://www.cve.org/CVERecord?id=CVE-2026-46276 Référence CVE CVE-2026-46285 https://www.cve.org/CVERecord?id=CVE-2026-46285 Référence CVE CVE-2026-46286 https://www.cve.org/CVERecord?id=CVE-2026-46286 Référence CVE CVE-2026-46289 https://www.cve.org/CVERecord?id=CVE-2026-46289 Référence CVE CVE-2026-46291 https://www.cve.org/CVERecord?id=CVE-2026-46291 Référence CVE CVE-2026-46294 https://www.cve.org/CVERecord?id=CVE-2026-46294 Référence CVE CVE-2026-46307 https://www.cve.org/CVERecord?id=CVE-2026-46307 Référence CVE CVE-2026-46312 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0926Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-46249 Référence CVE CVE-2026-46250 https://www.cve.org/CVERecord?id=CVE-2026-46250 Référence CVE CVE-2026-46253 https://www.cve.org/CVERecord?id=CVE-2026-46253 Référence CVE CVE-2026-46259 https://www.cve.org/CVERecord?id=CVE-2026-46259 Référence CVE CVE-2026-46266 https://www.cve.org/CVERecord?id=CVE-2026-46266 Référence CVE CVE-2026-46267 https://www.cve.org/CVERecord?id=CVE-2026-46267 Référence CVE CVE-2026-46270 https://www.cve.org/CVERecord?id=CVE-2026-46270 Référence CVE CVE-2026-46273 https://www.cve.org/CVERecord?id=CVE-2026-46273 Référence CVE CVE-2026-46274 https://www.cve.org/CVERecord?id=CVE-2026-46274 Référence CVE CVE-2026-46275 https://www.cve.org/CVERecord?id=CVE-2026-46275 Référence CVE CVE-2026-46276 https://www.cve.org/CVERecord?id=CVE-2026-46276 Référence CVE CVE-2026-46277 https://www.cve.org/CVERecord?id=CVE-2026-46277 Référence CVE CVE-2026-46278 https://www.cve.org/CVERecord?id=CVE-2026-46278 Référence CVE CVE-2026-46279 https://www.cve.org/CVERecord?id=CVE-2026-46279 Référence CVE CVE-2026-46280 https://www.cve.org/CVERecord?id=CVE-2026-46280 Référence CVE CVE-2026-46281 https://www.cve.org/CVERecord?id=CVE-2026-46281 Référence CVE CVE-2026-46282 https://www.cve.org/CVERecord?id=CVE-2026-46282 Référence CVE CVE-2026-46283 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-46173 Référence CVE CVE-2026-46197 https://www.cve.org/CVERecord?id=CVE-2026-46197 Référence CVE CVE-2026-46227 https://www.cve.org/CVERecord?id=CVE-2026-46227 Référence CVE CVE-2026-46229 https://www.cve.org/CVERecord?id=CVE-2026-46229 Référence CVE CVE-2026-46243 https://www.cve.org/CVERecord?id=CVE-2026-46243 Référence CVE CVE-2026-46253 https://www.cve.org/CVERecord?id=CVE-2026-46253 Référence CVE CVE-2026-46254 https://www.cve.org/CVERecord?id=CVE-2026-46254 Référence CVE CVE-2026-46266 https://www.cve.org/CVERecord?id=CVE-2026-46266 Référence CVE CVE-2026-46274 https://www.cve.org/CVERecord?id=CVE-2026-46274 Référence CVE CVE-2026-46275 https://www.cve.org/CVERecord?id=CVE-2026-46275 Référence CVE CVE-2026-46299 https://www.cve.org/CVERecord?id=CVE-2026-46299 Référence CVE CVE-2026-46319 https://www.cve.org/CVERecord?id=CVE-2026-46319 Référence CVE CVE-2026-46320 https://www.cve.org/CVERecord?id=CVE-2026-46320 Référence CVE CVE-2026-46328 https://www.cve.org/CVERecord?id=CVE-2026-46328 Référence CVE CVE-2026-46330 https://www.cve.org/CVERecord?id=CVE-2026-46330 Référence CVE CVE-2026-46331 https://www.cve.org/CVERecord?id=CVE-2026-46331 Référence CVE CVE-2026-52909 https://www.cve.org/CVERecord?id=CVE-2026-52909 Référence CVE CVE-2026-52918 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-46231 Référence CVE CVE-2026-46233 https://www.cve.org/CVERecord?id=CVE-2026-46233 Référence CVE CVE-2026-46234 https://www.cve.org/CVERecord?id=CVE-2026-46234 Référence CVE CVE-2026-46235 https://www.cve.org/CVERecord?id=CVE-2026-46235 Référence CVE CVE-2026-46236 https://www.cve.org/CVERecord?id=CVE-2026-46236 Référence CVE CVE-2026-46238 https://www.cve.org/CVERecord?id=CVE-2026-46238 Référence CVE CVE-2026-46242 https://www.cve.org/CVERecord?id=CVE-2026-46242 Référence CVE CVE-2026-46252 https://www.cve.org/CVERecord?id=CVE-2026-46252 Référence CVE CVE-2026-46273 https://www.cve.org/CVERecord?id=CVE-2026-46273 Référence CVE CVE-2026-46275 https://www.cve.org/CVERecord?id=CVE-2026-46275 Référence CVE CVE-2026-46276 https://www.cve.org/CVERecord?id=CVE-2026-46276 Référence CVE CVE-2026-46280 https://www.cve.org/CVERecord?id=CVE-2026-46280 Référence CVE CVE-2026-46285 https://www.cve.org/CVERecord?id=CVE-2026-46285 Référence CVE CVE-2026-46291 https://www.cve.org/CVERecord?id=CVE-2026-46291 Référence CVE CVE-2026-46292 https://www.cve.org/CVERecord?id=CVE-2026-46292 Référence CVE CVE-2026-46294 https://www.cve.org/CVERecord?id=CVE-2026-46294 Référence CVE CVE-2026-46296 https://www.cve.org/CVERecord?id=CVE-2026-46296 Référence CVE CVE-2026-46299 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-46117 Référence CVE CVE-2026-46137 https://www.cve.org/CVERecord?id=CVE-2026-46137 Référence CVE CVE-2026-46158 https://www.cve.org/CVERecord?id=CVE-2026-46158 Référence CVE CVE-2026-46160 https://www.cve.org/CVERecord?id=CVE-2026-46160 Référence CVE CVE-2026-46170 https://www.cve.org/CVERecord?id=CVE-2026-46170 Référence CVE CVE-2026-46203 https://www.cve.org/CVERecord?id=CVE-2026-46203 Référence CVE CVE-2026-46216 https://www.cve.org/CVERecord?id=CVE-2026-46216 Référence CVE CVE-2026-46244 https://www.cve.org/CVERecord?id=CVE-2026-46244 Référence CVE CVE-2026-46274 https://www.cve.org/CVERecord?id=CVE-2026-46274 Référence CVE CVE-2026-46275 https://www.cve.org/CVERecord?id=CVE-2026-46275 Référence CVE CVE-2026-46315 https://www.cve.org/CVERecord?id=CVE-2026-46315 Référence CVE CVE-2026-46316 https://www.cve.org/CVERecord?id=CVE-2026-46316 Référence CVE CVE-2026-46319 https://www.cve.org/CVERecord?id=CVE-2026-46319 Référence CVE CVE-2026-46320 https://www.cve.org/CVERecord?id=CVE-2026-46320 Référence CVE CVE-2026-46321 https://www.cve.org/CVERecord?id=CVE-2026-46321 Référence CVE CVE-2026-46322 https://www.cve.org/CVERecord?id=CVE-2026-46322 Référence CVE CVE-2026-46323 https://www.cve.org/CVERecord?id=CVE-2026-46323 Référence CVE CVE-2026-46331 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0802Multiples vulnérabilités dans Microsoft Azure Linux

De multiples vulnérabilités ont été découvertes dans Microsoft Azure Linux. Elles permettent à un attaquant de provoquer un problème de sécurité non spécifié par l'éditeur.

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2026-022936LinuxのLinux Kernelにおける競合状態に関する脆弱性

Linuxカーネルにおいて、以下の脆弱性が修正されました。Bluetoothのhci_uartにおけるcloseおよびinitパスに関連したUse-After-Free（UAF）および競合状態の問題です。hci_uartのライフサイクル管理において、Use-After-Free（UAF）およびヌルポインタ参照（NPD）につながる脆弱性が確認されました。主な問題は、TTYのクローズ時にHCI_UART_PROTO_READYフラグが設定されている場合にのみ、workqueue（init_readyおよびwrite_work）がフラッシュ・キャンセルされている点にあります。セットアップ完了前にハングアップが発生した場合、hci_uart_tty_close()はこれらのworkqueueの解体をスキップして`hu`構造体を解放してしまいます。その後、スケジュールされたworkが実行されると、解放済みの`hu`構造体を盲目的に参照してしまいます。さらに、解体シーケンス内で複数のデータ競合およびUAFが特定されました。第一に、hci_uart_close()からhci_uart_flush()を呼び出す際にwrite_workが効果的に無効化されていないため、両者が同時にhu-＞tx_skbを二重解放する競合状態が発生しています。これはプロトコルタイマーが同時にhci_uart_tx_wakeup()を呼び出してwrite_workを再キューイングするためです。第二に、hu-＞proto-＞close(hu)の前にhci_free_dev(hdev)を呼ぶと、ベンダー固有のプロトコルクローズコールバックがhu-＞hdevを参照してUAFが発生します。第三に、初期化エラー経路でproto_lockの書き込みロックを取得せずにPROTO_READYをクリアすると、アクティブなリーダーとの競合が発生します。さらに、hci_uart_tty_receive()が読取りロック外でhu-＞hdevにアクセスするため、初期化エラー経路でhdevが同時に解放されるとUAFが生じます。これらの同期およびライフサイクル問題は以下のように修正されました。まず、hci_uart_tty_close()の処理順序を変更し、最初にHCI_UART_PROTO_READYをクリアした後、即座にcancel_work_sync(&hu-＞write_work)を実行するようにしました。フラグをクリアすることでプロトコルタイマーがhci_uart_tx_wakeup()を正しく呼び出せなくなり、キャンセルが確実に機能してtx_skbの二重解放を防止しています。次に、PROTO_READYを早期にクリアするとhci_uart_close()がhu-＞proto-＞flush()をスキップしますが、tty_closeパス内でhu-＞proto-＞close()が直後に実行されるため、これは安全な動作です。close()の呼び出しにより、全プロトコルSKBキューが抹消され、状態が解体されます。さらに、hu-＞proto-＞close(hu)をすべてのクローズおよびエラー経路でhci_free_dev(hdev)の直前に移動し、ベンダーレベルのUAFを防止しています。また、hci_uart_tty_receive()内のhdev-＞stat.byte_rxのインクリメント処理をproto_lockの読取り側クリティカルセクション内に移動し、デバイス登録解除との同期を安全に行うようにしました。加えて、hci_uart_close()にcancel_work_sync(&hu-＞write_work)を追加し、HCIコアからhci_uart_flush()が呼ばれる前にworkqueueを安全にフラッシュできるようにしています。最後に、すべてのパスでdisable_work_sync()の代わりにcancel_work_sync()を使用することで、ユーザースペースのリトライ機能が永久に失われるのを防止しています。

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.10, 5.10.258 ≤ 5.10.*, 5.15.209 ≤ 5.15.*, 6.1.175 ≤ 6.1.*, 6.6.142 ≤ 6.6.*, 6.12.92 ≤ 6.12.*, 6.18.34 ≤ 6.18.*, 7.0.11 ≤ 7.0.*, 7.1 ≤ *
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 8 Jun 2026 · Last source change 5 Aug 2026, 12:30 UTC · CWE-362 · Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')

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-35079
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceNIST NVD
NVD statusNVD enriched

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗

No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.

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-35079↗Vendor CSAF · SUSE Product Security Team↗CVE authority or vendor reference↗Patch or update reference↗Patch or update reference↗Patch or update 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-46275 · cve.blacktree.nl