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

Bluetooth: SCO: Fix use-after-free in sco_recv_frame() due to missing sock_hold

Linux · Linux

8.8HighCVSS 3.1
Recommended action
Within 7 days

High technical severity; prioritise exposed affected systems while verifying vendor guidance.

Patch available
Distribution package intelligence

Ubuntu vendor package status

Canonical’s release and source-package findings are shown separately from local repository availability.

20 package states
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.

Ubuntu releaseSource packageVendor stateFixed versionEvidence
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 record ↗Source updated 11 Sept 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 record ↗Source updated 11 Sept 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 record ↗Source updated 11 Sept 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 record ↗Source updated 11 Sept 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 record ↗Source updated 11 Sept 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 record ↗Source updated 11 Sept 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 record ↗Source updated 11 Sept 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 record ↗Source updated 11 Sept 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 record ↗Source updated 11 Sept 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 record ↗Source updated 11 Sept 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 record ↗Source updated 11 Sept 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 record ↗Source updated 11 Sept 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 record ↗Source updated 11 Sept 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 record ↗Source updated 11 Sept 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 record ↗Source updated 11 Sept 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 record ↗Source updated 11 Sept 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 record ↗Source updated 11 Sept 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 record ↗Source updated 11 Sept 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 record ↗Source updated 11 Sept 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 record ↗Source updated 11 Sept 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-31408 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitykernel: Bluetooth: SCO: Fix use-after-free in sco_recv_frame() due to missing sock_hold
64 known affected

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

  • kernel as a component of Red Hat Enterprise Linux 6
  • kernel-abi-whitelists as a component of Red Hat Enterprise Linux 6
  • kernel-bootwrapper as a component of Red Hat Enterprise Linux 6
  • kernel-debug as a component of Red Hat Enterprise Linux 6
  • kernel-debug-devel as a component of Red Hat Enterprise Linux 6
  • kernel-devel as a component of Red Hat Enterprise Linux 6
  • kernel-doc as a component of Red Hat Enterprise Linux 6
  • kernel-firmware as a component of Red Hat Enterprise Linux 6
  • kernel-headers as a component of Red Hat Enterprise Linux 6
  • kernel-kdump as a component of Red Hat Enterprise Linux 6
  • kernel-kdump-devel as a component of Red Hat Enterprise Linux 6
  • kernel.src as a component of Red Hat Enterprise Linux 6
Summary
A flaw was found in the Linux kernel's Bluetooth SCO (Synchronous Connection-Oriented) protocol implementation. The `sco_recv_frame()` function fails to properly hold a reference to a socket after releasing a lock. This oversight allows a concurrent operation to free the socket while it is still being accessed, leading to a use-after-free vulnerability. A local attacker could potentially exploit this to cause memory corruption or a denial of service.
Remediation
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.
Optional official sources

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

Select the national-authority views to include. The exact source language is shown on each matched advisory. Your choice is remembered on this device and encoded in the shareable URL.

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-19196

No EUVD known-exploited evidence

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: SCO: Fix use-after-free in sco_recv_frame() due to missing sock_hold sco_recv_frame() reads conn->sk under sco_conn_lock() but immediately releases the lock without holding a reference to the socket. A concurrent close() can free the socket between the lock release and the subsequent sk->sk_state access, resulting in a use-after-free. Other functions in the same file (sco_sock_timeout(), sco_conn_del()) correctly use sco_sock_hold() to safely hold a reference under the lock. Fix by using sco_sock_hold() to take a reference before releasing the lock, and adding sock_put() on all exit paths.

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 actionWithin 7 days

High technical severity; prioritise exposed affected systems while verifying vendor guidance.

Patch available
01

What, why and how

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: SCO: Fix use-after-free in sco_recv_frame() due to missing sock_hold sco_recv_frame() reads conn->sk under sco_conn_lock() but immediately releases the lock without holding a reference to the socket. A concurrent close() can free the socket between the lock release and the subsequent sk->sk_state access, resulting in a use-after-free. Other functions in the same file (sco_sock_timeout(), sco_conn_del()) correctly use sco_sock_hold() to safely hold a reference under the lock. Fix by using sco_sock_hold() to take a reference before releasing the lock, and adding sock_put() on all exit paths.

What

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: SCO: Fix use-after-free in sco_recv_frame() due to missing sock_hold sco_recv_frame() reads conn->sk under sco_conn_lock() but immediately releases the lock without holding a reference to the socket. A concurrent close() can free the socket between the lock release and the subsequent sk->sk_state access, resulting in a use-after-free. Other functions in the same file (sco_sock_timeout(), sco_conn_del()) correctly use sco_sock_hold() to safely hold a reference under the lock. Fix by using sco_sock_hold() to take a reference before releasing the lock, and adding sock_put() on all exit paths.

Why

The program can continue using memory after it has been released, producing unsafe and attacker-influenceable behaviour.

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: SCO: Fix use-after-free in sco_recv_frame() due to missing sock_hold sco_recv_frame() reads conn->sk under sco_conn_lock() but immediately releases the lock without holding a reference to the socket. A concurrent close() can free the socket between the lock release and the subsequent sk->sk_state access, resulting in a use-after-free. Other functions in the same file (sco_sock_timeout(), sco_conn_del()) correctly use sco_sock_hold() to safely hold a reference under the lock. Fix by using sco_sock_hold() to take a reference before releasing the lock, and adding sock_put() on all exit paths.

Why

The program can continue using memory after it has been released, producing unsafe and attacker-influenceable behaviour.

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 → Use After Free → 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: a standard category for the underlying weakness.
CWE-416 ↗

CWE-416: Use After Free. The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory belongs to the code that operates on the new pointer.

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.
UnauthenticatedCWE-416
A

Official authority intelligence

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

ENISA EUVD · EUVD-2026-19196Official EUVD mapping

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: SCO: Fix use-after-free in sco_recv_frame() due to missing sock_hold sco_recv_frame() reads conn->sk under sco_conn_lock() but immediately releases the lock without holding a reference to the socket. A concurrent close() can free the socket between the lock release and the subsequent sk->sk_state access, resulting in a use-after-free. Other functions in the same file (sco_sock_timeout(), sco_conn_del()) correctly use sco_sock_hold() to safely hold a reference under the lock. Fix by using sco_sock_hold() to take a reference before releasing the lock, and adding sock_put() on all exit paths.

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

Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um unter anderem einen Denial of Service-Angriff auszuführen oder um Sicherheitsmechanismen zu umgehen.

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

d?id=CVE-2026-23463 Référence CVE CVE-2026-23474 https://www.cve.org/CVERecord?id=CVE-2026-23474 Référence CVE CVE-2026-31393 https://www.cve.org/CVERecord?id=CVE-2026-31393 Référence CVE CVE-2026-31396 https://www.cve.org/CVERecord?id=CVE-2026-31396 Référence CVE CVE-2026-31399 https://www.cve.org/CVERecord?id=CVE-2026-31399 Référence CVE CVE-2026-31400 https://www.cve.org/CVERecord?id=CVE-2026-31400 Référence CVE CVE-2026-31402 https://www.cve.org/CVERecord?id=CVE-2026-31402 Référence CVE CVE-2026-31405 https://www.cve.org/CVERecord?id=CVE-2026-31405 Référence CVE CVE-2026-31407 https://www.cve.org/CVERecord?id=CVE-2026-31407 Référence CVE CVE-2026-31408 https://www.cve.org/CVERecord?id=CVE-2026-31408 Référence CVE CVE-2026-31409 https://www.cve.org/CVERecord?id=CVE-2026-31409 Référence CVE CVE-2026-31411 https://www.cve.org/CVERecord?id=CVE-2026-31411 Référence CVE CVE-2026-31414 https://www.cve.org/CVERecord?id=CVE-2026-31414 Référence CVE CVE-2026-31415 https://www.cve.org/CVERecord?id=CVE-2026-31415 Référence CVE CVE-2026-31416 https://www.cve.org/CVERecord?id=CVE-2026-31416 Référence CVE CVE-2026-31417 https://www.cve.org/CVERecord?id=CVE-2026-31417 Référence CVE CVE-2026-31421 https://www.cve.org/CVERecord?id=CVE-2026-31421 Référence CVE CVE-2026-31422 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-31392 Référence CVE CVE-2026-31393 https://www.cve.org/CVERecord?id=CVE-2026-31393 Référence CVE CVE-2026-31394 https://www.cve.org/CVERecord?id=CVE-2026-31394 Référence CVE CVE-2026-31396 https://www.cve.org/CVERecord?id=CVE-2026-31396 Référence CVE CVE-2026-31399 https://www.cve.org/CVERecord?id=CVE-2026-31399 Référence CVE CVE-2026-31400 https://www.cve.org/CVERecord?id=CVE-2026-31400 Référence CVE CVE-2026-31403 https://www.cve.org/CVERecord?id=CVE-2026-31403 Référence CVE CVE-2026-31405 https://www.cve.org/CVERecord?id=CVE-2026-31405 Référence CVE CVE-2026-31407 https://www.cve.org/CVERecord?id=CVE-2026-31407 Référence CVE CVE-2026-31408 https://www.cve.org/CVERecord?id=CVE-2026-31408 Référence CVE CVE-2026-31409 https://www.cve.org/CVERecord?id=CVE-2026-31409 Référence CVE CVE-2026-31412 https://www.cve.org/CVERecord?id=CVE-2026-31412 Référence CVE CVE-2026-31413 https://www.cve.org/CVERecord?id=CVE-2026-31413 Référence CVE CVE-2026-31414 https://www.cve.org/CVERecord?id=CVE-2026-31414 Référence CVE CVE-2026-31415 https://www.cve.org/CVERecord?id=CVE-2026-31415 Référence CVE CVE-2026-31416 https://www.cve.org/CVERecord?id=CVE-2026-31416 Référence CVE CVE-2026-31417 https://www.cve.org/CVERecord?id=CVE-2026-31417 Référence CVE CVE-2026-31421 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0986Multiples vulnérabilités dans les produits IBM

ERecord?id=CVE-2026-23243 Référence CVE CVE-2026-23270 https://www.cve.org/CVERecord?id=CVE-2026-23270 Référence CVE CVE-2026-23392 https://www.cve.org/CVERecord?id=CVE-2026-23392 Référence CVE CVE-2026-23455 https://www.cve.org/CVERecord?id=CVE-2026-23455 Référence CVE CVE-2026-2482 https://www.cve.org/CVERecord?id=CVE-2026-2482 Référence CVE CVE-2026-28390 https://www.cve.org/CVERecord?id=CVE-2026-28390 Référence CVE CVE-2026-29518 https://www.cve.org/CVERecord?id=CVE-2026-29518 Référence CVE CVE-2026-3012 https://www.cve.org/CVERecord?id=CVE-2026-3012 Référence CVE CVE-2026-3039 https://www.cve.org/CVERecord?id=CVE-2026-3039 Référence CVE CVE-2026-31408 https://www.cve.org/CVERecord?id=CVE-2026-31408 Référence CVE CVE-2026-31532 https://www.cve.org/CVERecord?id=CVE-2026-31532 Référence CVE CVE-2026-31581 https://www.cve.org/CVERecord?id=CVE-2026-31581 Référence CVE CVE-2026-31613 https://www.cve.org/CVERecord?id=CVE-2026-31613 Référence CVE CVE-2026-31669 https://www.cve.org/CVERecord?id=CVE-2026-31669 Référence CVE CVE-2026-31684 https://www.cve.org/CVERecord?id=CVE-2026-31684 Référence CVE CVE-2026-31685 https://www.cve.org/CVERecord?id=CVE-2026-31685 Référence CVE CVE-2026-31709 https://www.cve.org/CVERecord?id=CVE-2026-31709 Référence CVE CVE-2026-31786 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-23462 Référence CVE CVE-2026-23463 https://www.cve.org/CVERecord?id=CVE-2026-23463 Référence CVE CVE-2026-23474 https://www.cve.org/CVERecord?id=CVE-2026-23474 Référence CVE CVE-2026-31393 https://www.cve.org/CVERecord?id=CVE-2026-31393 Référence CVE CVE-2026-31396 https://www.cve.org/CVERecord?id=CVE-2026-31396 Référence CVE CVE-2026-31399 https://www.cve.org/CVERecord?id=CVE-2026-31399 Référence CVE CVE-2026-31400 https://www.cve.org/CVERecord?id=CVE-2026-31400 Référence CVE CVE-2026-31405 https://www.cve.org/CVERecord?id=CVE-2026-31405 Référence CVE CVE-2026-31407 https://www.cve.org/CVERecord?id=CVE-2026-31407 Référence CVE CVE-2026-31408 https://www.cve.org/CVERecord?id=CVE-2026-31408 Référence CVE CVE-2026-31409 https://www.cve.org/CVERecord?id=CVE-2026-31409 Référence CVE CVE-2026-31411 https://www.cve.org/CVERecord?id=CVE-2026-31411 Référence CVE CVE-2026-31415 https://www.cve.org/CVERecord?id=CVE-2026-31415 Référence CVE CVE-2026-31416 https://www.cve.org/CVERecord?id=CVE-2026-31416 Référence CVE CVE-2026-31417 https://www.cve.org/CVERecord?id=CVE-2026-31417 Référence CVE CVE-2026-31421 https://www.cve.org/CVERecord?id=CVE-2026-31421 Référence CVE CVE-2026-31422 https://www.cve.org/CVERecord?id=CVE-2026-31422 Référence CVE CVE-2026-31423 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-31393 Référence CVE CVE-2026-31394 https://www.cve.org/CVERecord?id=CVE-2026-31394 Référence CVE CVE-2026-31396 https://www.cve.org/CVERecord?id=CVE-2026-31396 Référence CVE CVE-2026-31399 https://www.cve.org/CVERecord?id=CVE-2026-31399 Référence CVE CVE-2026-31400 https://www.cve.org/CVERecord?id=CVE-2026-31400 Référence CVE CVE-2026-31402 https://www.cve.org/CVERecord?id=CVE-2026-31402 Référence CVE CVE-2026-31403 https://www.cve.org/CVERecord?id=CVE-2026-31403 Référence CVE CVE-2026-31405 https://www.cve.org/CVERecord?id=CVE-2026-31405 Référence CVE CVE-2026-31407 https://www.cve.org/CVERecord?id=CVE-2026-31407 Référence CVE CVE-2026-31408 https://www.cve.org/CVERecord?id=CVE-2026-31408 Référence CVE CVE-2026-31409 https://www.cve.org/CVERecord?id=CVE-2026-31409 Référence CVE CVE-2026-31411 https://www.cve.org/CVERecord?id=CVE-2026-31411 Référence CVE CVE-2026-31412 https://www.cve.org/CVERecord?id=CVE-2026-31412 Référence CVE CVE-2026-31413 https://www.cve.org/CVERecord?id=CVE-2026-31413 Référence CVE CVE-2026-31414 https://www.cve.org/CVERecord?id=CVE-2026-31414 Référence CVE CVE-2026-31415 https://www.cve.org/CVERecord?id=CVE-2026-31415 Référence CVE CVE-2026-31416 https://www.cve.org/CVERecord?id=CVE-2026-31416 Référence CVE CVE-2026-31417 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-31393 Référence CVE CVE-2026-31394 https://www.cve.org/CVERecord?id=CVE-2026-31394 Référence CVE CVE-2026-31396 https://www.cve.org/CVERecord?id=CVE-2026-31396 Référence CVE CVE-2026-31399 https://www.cve.org/CVERecord?id=CVE-2026-31399 Référence CVE CVE-2026-31400 https://www.cve.org/CVERecord?id=CVE-2026-31400 Référence CVE CVE-2026-31402 https://www.cve.org/CVERecord?id=CVE-2026-31402 Référence CVE CVE-2026-31403 https://www.cve.org/CVERecord?id=CVE-2026-31403 Référence CVE CVE-2026-31405 https://www.cve.org/CVERecord?id=CVE-2026-31405 Référence CVE CVE-2026-31407 https://www.cve.org/CVERecord?id=CVE-2026-31407 Référence CVE CVE-2026-31408 https://www.cve.org/CVERecord?id=CVE-2026-31408 Référence CVE CVE-2026-31409 https://www.cve.org/CVERecord?id=CVE-2026-31409 Référence CVE CVE-2026-31411 https://www.cve.org/CVERecord?id=CVE-2026-31411 Référence CVE CVE-2026-31412 https://www.cve.org/CVERecord?id=CVE-2026-31412 Référence CVE CVE-2026-31413 https://www.cve.org/CVERecord?id=CVE-2026-31413 Référence CVE CVE-2026-31414 https://www.cve.org/CVERecord?id=CVE-2026-31414 Référence CVE CVE-2026-31415 https://www.cve.org/CVERecord?id=CVE-2026-31415 Référence CVE CVE-2026-31416 https://www.cve.org/CVERecord?id=CVE-2026-31416 Référence CVE CVE-2026-31417 https://www.cve.org/CVERecord?id=

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

m/errata/RHSA-2026:40425 Bulletin de sécurité Red Hat RHSA-2026:40760 du 16 juillet 2026 https://access.redhat.com/errata/RHSA-2026:40760 Bulletin de sécurité Red Hat RHSA-2026:41229 du 17 juillet 2026 https://access.redhat.com/errata/RHSA-2026:41229 Référence CVE CVE-2025-38653 https://www.cve.org/CVERecord?id=CVE-2025-38653 Référence CVE CVE-2025-68183 https://www.cve.org/CVERecord?id=CVE-2025-68183 Référence CVE CVE-2025-68724 https://www.cve.org/CVERecord?id=CVE-2025-68724 Référence CVE CVE-2025-71066 https://www.cve.org/CVERecord?id=CVE-2025-71066 Référence CVE CVE-2025-71089 https://www.cve.org/CVERecord?id=CVE-2025-71089 Référence CVE CVE-2026-31408 https://www.cve.org/CVERecord?id=CVE-2026-31408 Référence CVE CVE-2026-31411 https://www.cve.org/CVERecord?id=CVE-2026-31411 Référence CVE CVE-2026-31613 https://www.cve.org/CVERecord?id=CVE-2026-31613 Référence CVE CVE-2026-31684 https://www.cve.org/CVERecord?id=CVE-2026-31684 Référence CVE CVE-2026-43027 https://www.cve.org/CVERecord?id=CVE-2026-43027 Référence CVE CVE-2026-43074 https://www.cve.org/CVERecord?id=CVE-2026-43074 Référence CVE CVE-2026-43279 https://www.cve.org/CVERecord?id=CVE-2026-43279 Référence CVE CVE-2026-43330 https://www.cve.org/CVERecord?id=CVE-2026-43330 Référence CVE CVE-2026-43414 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-68183 Référence CVE CVE-2025-71066 https://www.cve.org/CVERecord?id=CVE-2025-71066 Référence CVE CVE-2025-71116 https://www.cve.org/CVERecord?id=CVE-2025-71116 Référence CVE CVE-2026-22984 https://www.cve.org/CVERecord?id=CVE-2026-22984 Référence CVE CVE-2026-22990 https://www.cve.org/CVERecord?id=CVE-2026-22990 Référence CVE CVE-2026-23191 https://www.cve.org/CVERecord?id=CVE-2026-23191 Référence CVE CVE-2026-23216 https://www.cve.org/CVERecord?id=CVE-2026-23216 Référence CVE CVE-2026-23270 https://www.cve.org/CVERecord?id=CVE-2026-23270 Référence CVE CVE-2026-23455 https://www.cve.org/CVERecord?id=CVE-2026-23455 Référence CVE CVE-2026-31408 https://www.cve.org/CVERecord?id=CVE-2026-31408 Référence CVE CVE-2026-31669 https://www.cve.org/CVERecord?id=CVE-2026-31669 Référence CVE CVE-2026-35385 https://www.cve.org/CVERecord?id=CVE-2026-35385 Référence CVE CVE-2026-35535 https://www.cve.org/CVERecord?id=CVE-2026-35535 Référence CVE CVE-2026-39979 https://www.cve.org/CVERecord?id=CVE-2026-39979 Référence CVE CVE-2026-40164 https://www.cve.org/CVERecord?id=CVE-2026-40164 Référence CVE CVE-2026-41035 https://www.cve.org/CVERecord?id=CVE-2026-41035 Référence CVE CVE-2026-43027 https://www.cve.org/CVERecord?id=CVE-2026-43027 Référence CVE CVE-2026-43037 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-31394 Référence CVE CVE-2026-31395 https://www.cve.org/CVERecord?id=CVE-2026-31395 Référence CVE CVE-2026-31400 https://www.cve.org/CVERecord?id=CVE-2026-31400 Référence CVE CVE-2026-31402 https://www.cve.org/CVERecord?id=CVE-2026-31402 Référence CVE CVE-2026-31403 https://www.cve.org/CVERecord?id=CVE-2026-31403 Référence CVE CVE-2026-31404 https://www.cve.org/CVERecord?id=CVE-2026-31404 Référence CVE CVE-2026-31405 https://www.cve.org/CVERecord?id=CVE-2026-31405 Référence CVE CVE-2026-31406 https://www.cve.org/CVERecord?id=CVE-2026-31406 Référence CVE CVE-2026-31407 https://www.cve.org/CVERecord?id=CVE-2026-31407 Référence CVE CVE-2026-31408 https://www.cve.org/CVERecord?id=CVE-2026-31408 Référence CVE CVE-2026-31411 https://www.cve.org/CVERecord?id=CVE-2026-31411 Référence CVE CVE-2026-31412 https://www.cve.org/CVERecord?id=CVE-2026-31412 Référence CVE CVE-2026-31415 https://www.cve.org/CVERecord?id=CVE-2026-31415 Référence CVE CVE-2026-31416 https://www.cve.org/CVERecord?id=CVE-2026-31416 Référence CVE CVE-2026-31417 https://www.cve.org/CVERecord?id=CVE-2026-31417 Référence CVE CVE-2026-31420 https://www.cve.org/CVERecord?id=CVE-2026-31420 Référence CVE CVE-2026-31421 https://www.cve.org/CVERecord?id=CVE-2026-31421 Référence CVE CVE-2026-31422 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-23461 Référence CVE CVE-2026-23462 https://www.cve.org/CVERecord?id=CVE-2026-23462 Référence CVE CVE-2026-23468 https://www.cve.org/CVERecord?id=CVE-2026-23468 Référence CVE CVE-2026-23472 https://www.cve.org/CVERecord?id=CVE-2026-23472 Référence CVE CVE-2026-31393 https://www.cve.org/CVERecord?id=CVE-2026-31393 Référence CVE CVE-2026-31400 https://www.cve.org/CVERecord?id=CVE-2026-31400 Référence CVE CVE-2026-31402 https://www.cve.org/CVERecord?id=CVE-2026-31402 Référence CVE CVE-2026-31403 https://www.cve.org/CVERecord?id=CVE-2026-31403 Référence CVE CVE-2026-31407 https://www.cve.org/CVERecord?id=CVE-2026-31407 Référence CVE CVE-2026-31408 https://www.cve.org/CVERecord?id=CVE-2026-31408 Référence CVE CVE-2026-31411 https://www.cve.org/CVERecord?id=CVE-2026-31411 Référence CVE CVE-2026-31416 https://www.cve.org/CVERecord?id=CVE-2026-31416 Référence CVE CVE-2026-31422 https://www.cve.org/CVERecord?id=CVE-2026-31422 Référence CVE CVE-2026-31423 https://www.cve.org/CVERecord?id=CVE-2026-31423 Référence CVE CVE-2026-31424 https://www.cve.org/CVERecord?id=CVE-2026-31424 Référence CVE CVE-2026-31425 https://www.cve.org/CVERecord?id=CVE-2026-31425 Référence CVE CVE-2026-31427 https://www.cve.org/CVERecord?id=CVE-2026-31427 Référence CVE CVE-2026-31428 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-39981 Référence CVE CVE-2025-68183 https://www.cve.org/CVERecord?id=CVE-2025-68183 Référence CVE CVE-2025-68347 https://www.cve.org/CVERecord?id=CVE-2025-68347 Référence CVE CVE-2025-68366 https://www.cve.org/CVERecord?id=CVE-2025-68366 Référence CVE CVE-2025-68741 https://www.cve.org/CVERecord?id=CVE-2025-68741 Référence CVE CVE-2025-71116 https://www.cve.org/CVERecord?id=CVE-2025-71116 Référence CVE CVE-2026-23243 https://www.cve.org/CVERecord?id=CVE-2026-23243 Référence CVE CVE-2026-23270 https://www.cve.org/CVERecord?id=CVE-2026-23270 Référence CVE CVE-2026-23455 https://www.cve.org/CVERecord?id=CVE-2026-23455 Référence CVE CVE-2026-31408 https://www.cve.org/CVERecord?id=CVE-2026-31408 Référence CVE CVE-2026-31419 https://www.cve.org/CVERecord?id=CVE-2026-31419 Référence CVE CVE-2026-31532 https://www.cve.org/CVERecord?id=CVE-2026-31532 Référence CVE CVE-2026-31684 https://www.cve.org/CVERecord?id=CVE-2026-31684 Référence CVE CVE-2026-31685 https://www.cve.org/CVERecord?id=CVE-2026-31685 Référence CVE CVE-2026-31709 https://www.cve.org/CVERecord?id=CVE-2026-31709 Référence CVE CVE-2026-43020 https://www.cve.org/CVERecord?id=CVE-2026-43020 Référence CVE CVE-2026-43027 https://www.cve.org/CVERecord?id=CVE-2026-43027 Référence CVE CVE-2026-43051 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-31391 Référence CVE CVE-2026-31392 https://www.cve.org/CVERecord?id=CVE-2026-31392 Référence CVE CVE-2026-31393 https://www.cve.org/CVERecord?id=CVE-2026-31393 Référence CVE CVE-2026-31396 https://www.cve.org/CVERecord?id=CVE-2026-31396 Référence CVE CVE-2026-31399 https://www.cve.org/CVERecord?id=CVE-2026-31399 Référence CVE CVE-2026-31400 https://www.cve.org/CVERecord?id=CVE-2026-31400 Référence CVE CVE-2026-31402 https://www.cve.org/CVERecord?id=CVE-2026-31402 Référence CVE CVE-2026-31403 https://www.cve.org/CVERecord?id=CVE-2026-31403 Référence CVE CVE-2026-31405 https://www.cve.org/CVERecord?id=CVE-2026-31405 Référence CVE CVE-2026-31408 https://www.cve.org/CVERecord?id=CVE-2026-31408 Référence CVE CVE-2026-31409 https://www.cve.org/CVERecord?id=CVE-2026-31409 Référence CVE CVE-2026-31411 https://www.cve.org/CVERecord?id=CVE-2026-31411 Référence CVE CVE-2026-31412 https://www.cve.org/CVERecord?id=CVE-2026-31412 Référence CVE CVE-2026-31414 https://www.cve.org/CVERecord?id=CVE-2026-31414 Référence CVE CVE-2026-31415 https://www.cve.org/CVERecord?id=CVE-2026-31415 Référence CVE CVE-2026-31416 https://www.cve.org/CVERecord?id=CVE-2026-31416 Référence CVE CVE-2026-31417 https://www.cve.org/CVERecord?id=CVE-2026-31417 Référence CVE CVE-2026-31418 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-31396 Référence CVE CVE-2026-31399 https://www.cve.org/CVERecord?id=CVE-2026-31399 Référence CVE CVE-2026-31400 https://www.cve.org/CVERecord?id=CVE-2026-31400 Référence CVE CVE-2026-31401 https://www.cve.org/CVERecord?id=CVE-2026-31401 Référence CVE CVE-2026-31402 https://www.cve.org/CVERecord?id=CVE-2026-31402 Référence CVE CVE-2026-31403 https://www.cve.org/CVERecord?id=CVE-2026-31403 Référence CVE CVE-2026-31405 https://www.cve.org/CVERecord?id=CVE-2026-31405 Référence CVE CVE-2026-31406 https://www.cve.org/CVERecord?id=CVE-2026-31406 Référence CVE CVE-2026-31407 https://www.cve.org/CVERecord?id=CVE-2026-31407 Référence CVE CVE-2026-31408 https://www.cve.org/CVERecord?id=CVE-2026-31408 Référence CVE CVE-2026-31409 https://www.cve.org/CVERecord?id=CVE-2026-31409 Référence CVE CVE-2026-31410 https://www.cve.org/CVERecord?id=CVE-2026-31410 Référence CVE CVE-2026-31411 https://www.cve.org/CVERecord?id=CVE-2026-31411 Référence CVE CVE-2026-31412 https://www.cve.org/CVERecord?id=CVE-2026-31412 Référence CVE CVE-2026-31414 https://www.cve.org/CVERecord?id=CVE-2026-31414 Référence CVE CVE-2026-31415 https://www.cve.org/CVERecord?id=CVE-2026-31415 Référence CVE CVE-2026-31416 https://www.cve.org/CVERecord?id=CVE-2026-31416 Référence CVE CVE-2026-31417 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0463Multiples vulnérabilités dans les produits Microsoft

ire suivie par: CERT-FR Avis du CERT-FR Objet: Multiples vulnérabilités dans les produits Microsoft Gestion du document Référence CERTFR-2026-AVI-0463 Titre Multiples vulnérabilités dans les produits Microsoft Date de la première version 20 avril 2026 Date de la dernière version 20 avril 2026 Source(s) Bulletin de sécurité Microsoft CVE-2026-27447 du 05 avril 2026 Bulletin de sécurité Microsoft CVE-2026-34978 du 05 avril 2026 Bulletin de sécurité Microsoft CVE-2026-34979 du 05 avril 2026 Bulletin de sécurité Microsoft CVE-2026-34980 du 05 avril 2026 Bulletin de sécurité Microsoft CVE-2026-34990 du 05 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31408 du 07 avril 2026 Bulletin de sécurité Microsoft CVE-2026-34445 du 09 avril 2026 Bulletin de sécurité Microsoft CVE-2026-34446 du 09 avril 2026 Bulletin de sécurité Microsoft CVE-2026-39314 du 09 avril 2026 Bulletin de sécurité Microsoft CVE-2026-39316 du 09 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31414 du 14 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31416 du 14 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31417 du 14 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31418 du 14 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31421 du 14 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31422 du 14 avril 2026 Bu

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2026-016733LinuxのLinux Kernelにおける解放済みメモリの使用に関する脆弱性

Linuxカーネルにおいて、以下の脆弱性が修正されました。BluetoothのSCOに関する問題で、sco_recv_frame()関数におけるsock_holdの欠如によるuse-after-freeの脆弱性です。sco_recv_frame()はsco_conn_lock()のロック下でconn-skを読み取りますが、ソケットの参照を保持せずに直ちにロックを解放します。その間に並行処理でclose()がソケットを解放する可能性があり、ロック解放後にsk-sk_stateへアクセスするとuse-after-freeが発生します。同じファイル内の他の関数（sco_sock_timeout()、sco_conn_del()）は、ロック下で安全に参照を保持するために適切にsco_sock_hold()を使用しています。この修正では、ロックを解放する前に参照を取得するためにsco_sock_hold()を使用し、すべての終了パスでsock_put()を呼び出すようにしました。

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.
Patch available
Affected
Fixed
Action
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.
Workaround
No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04

Evidence and provenance

Published 6 Apr 2026 · Last source change 19 Aug 2026, 16:27 UTC · CWE-416 · Use After Free

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-19196
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceNIST NVD
NVD statusNVD modified after enrichment

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

Material change intelligence

What changed after publication

View recent updates ↗
  1. Affected versionsThe structured affected or fixed version information changed.
    Before
    1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < d57384e27d1ebf0047e3f00a6e1181b8be9857a2; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < b0a7da0e3f7442545f071499beb36374714bb9de; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 45aaca995e4a7a05b272a58e7ab2fff4f611b8f1; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 108b81514d8f2535eb16651495cefb2250528db3; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 7197462e90b8ce15caa1ae15d4bc2bb8cd21b11e; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < e76e8f0581ef555eacc11dbb095e602fb30a5361; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 598dbba9919c5e36c54fe1709b557d64120cb94b; 2.6.12 · Fixed: < 2.6.12; 5.15.203 ≤ 5.15.*; 6.1.168 ≤ 6.1.*; 6.6.131 ≤ 6.6.*; 6.12.80 ≤ 6.12.*; 6.18.21 ≤ 6.18.*; 6.19.11 ≤ 6.19.*; 7.0 ≤ *
    After
    1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 37e18bc8c9a70d77bd099e2273f328b3bc7f6d0d; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < d57384e27d1ebf0047e3f00a6e1181b8be9857a2; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < b0a7da0e3f7442545f071499beb36374714bb9de; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 45aaca995e4a7a05b272a58e7ab2fff4f611b8f1; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 108b81514d8f2535eb16651495cefb2250528db3; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 7197462e90b8ce15caa1ae15d4bc2bb8cd21b11e; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < e76e8f0581ef555eacc11dbb095e602fb30a5361; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 598dbba9919c5e36c54fe1709b557d64120cb94b · Fixed: < 2.6.12; 5.10.265 ≤ 5.10.*; 5.15.203 ≤ 5.15.*; 6.1.168 ≤ 6.1.*; 6.6.131 ≤ 6.6.*; 6.12.80 ≤ 6.12.*; 6.18.21 ≤ 6.18.*; 6.19.11 ≤ 6.19.*
    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-19196↗Vendor CSAF · Red Hat Product Security↗Patch or update reference↗Patch or update reference↗Patch or update reference↗Patch or update reference↗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-31408 · cve.blacktree.nl