BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2025
CVE-2025-68305High confidence

Bluetooth: hci_sock: Prevent race in socket write iter and sock bind

Linux · Linux

…UnscoredAssess manually
Recommended action
Patch only the product branches with a verified fix

No CVSS base score is available from the CNA, CISA ADP or NIST. Absence of a score is not evidence of low risk; review the vendor advisory, affected exposure and exploit evidence. Verified remediation exists for at least one product or source, but 19 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 severityUnscoredOperational priority:Needs assessment, manual assessment needed.unscored

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • EPSS is 0.19% 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: Manual assessmentRemediation target: Manual assessment

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

23 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 19 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.63-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcelinuxNot affectedDebian marks this release not affected (fixed-version marker 0).Not published in this feedDebian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.17.11-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.17.11-1Debian Security Tracker ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinuxAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-awsAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azureAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azure-fde-6.14Affected, 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-nvidia-6.14Affected, 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-oem-6.11Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oracleAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-raspiAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-raspi-realtimeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-realtimeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-riscvAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-xilinxAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

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

2 current
CVE-2025-68305 · CSAF 2.0 · revision 43 · interimSUSE Product Security TeamCVE-2025-68305
17 known affected

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

  • SUSE Linux Micro Extras 6.2:kernel-obs-build
  • SUSE Linux Micro Extras 6.2:kernel-syms
  • SLES 15 SP1 CHOST Images for Amazon EC2
  • SLES 15 SP2 CHOST Images for Amazon EC2
  • SLES 15 SP3 CHOST Images for Amazon EC2
  • SLES 15 SP4 CHOST Images for Amazon EC2
  • SLES 15 SP5 CHOST Images for Amazon EC2
  • SLES 15 SP1 CHOST Images for Google
  • SLES 15 SP2 CHOST Images for Google
  • SLES 15 SP3 CHOST Images for Google
  • SLES 15 SP4 CHOST Images for Google
  • SLES 15 SP5 CHOST Images for Google
Summary
In the Linux kernel, the following vulnerability has been resolved: Bluetooth: hci_sock: Prevent race in socket write iter and sock bind There is a potential race condition between sock bind and socket write iter. bind may free the same cmd via mgmt_pending before write iter sends the cmd, just as syzbot reported in UAF[1]. Here we use hci_dev_lock to synchronize the two, thereby avoiding the UAF mentioned in [1]. [1] syzbot reported: BUG: KASAN: slab-use-after-free in mgmt_pending_remove+0x3b/0x210 net/bluetooth/mgmt_util.c:316 Read of size 8 at addr ffff888077164818 by task syz.0.17/5989 Call Trace: mgmt_pending_remove+0x3b/0x210 net/bluetooth/mgmt_util.c:316 set_link_security+0x5c2/0x710 net/bluetooth/mgmt.c:1918 hci_mgmt_cmd+0x9c9/0xef0 net/bluetooth/hci_sock.c:1719 hci_sock_sendmsg+0x6ca/0xef0 net/bluetooth/hci_sock.c:1839 sock_sendmsg_nosec net/socket.c:727 [inline] __sock_sendmsg+0x21c/0x270 net/socket.c:742 sock_write_iter+0x279/0x360 net/socket.c:1195 Allocated by task 5989: mgmt_pending_add+0x35/0x140 net/bluetooth/mgmt_util.c:296 set_link_security+0x557/0x710 net/bluetooth/mgmt.c:1910 hci_mgmt_cmd+0x9c9/0xef0 net/bluetooth/hci_sock.c:1719 hci_sock_sendmsg+0x6ca/0xef0 net/bluetooth/hci_sock.c:1839 sock_sendmsg_nosec net/socket.c:727 [inline] __sock_sendmsg+0x21c/0x270 net/socket.c:742 sock_write_iter+0x279/0x360 net/socket.c:1195 Freed by task 5991: mgmt_pending_free net/bluetooth/mgmt_util.c:311 [inline] mgmt_pending_foreach+0x30d/0x380 net/bluetooth/mgmt_util.c:257 mgmt_index_removed+0x112/0x2f0 net/bluetooth/mgmt.c:9477 hci_sock_bind+0xbe9/0x1000 net/bluetooth/hci_sock.c:1314
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
CVE-2025-68305 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitykernel: Bluetooth: hci_sock: Prevent race in socket write iter and sock bind
22 known affected

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

  • kernel-rt as a component of Red Hat Enterprise Linux 9
  • kernel-rt-core as a component of Red Hat Enterprise Linux 9
  • kernel-rt-debug as a component of Red Hat Enterprise Linux 9
  • kernel-rt-debug-core as a component of Red Hat Enterprise Linux 9
  • kernel-rt-debug-devel as a component of Red Hat Enterprise Linux 9
  • kernel-rt-debug-devel-matched as a component of Red Hat Enterprise Linux 9
  • kernel-rt-debug-kvm as a component of Red Hat Enterprise Linux 9
  • kernel-rt-debug-modules as a component of Red Hat Enterprise Linux 9
  • kernel-rt-debug-modules-core as a component of Red Hat Enterprise Linux 9
  • kernel-rt-debug-modules-extra as a component of Red Hat Enterprise Linux 9
  • kernel-rt-debug-modules-internal as a component of Red Hat Enterprise Linux 9
  • kernel-rt-debug-modules-partner as a component of Red Hat Enterprise Linux 9
Summary
A use-after-free vulnerability was found in the Linux kernel's Bluetooth HCI socket implementation. A race condition between socket bind and write operations allows mgmt_pending to free a command structure while write_iter is still attempting to send it, resulting in use-after-free when the freed memory is accessed.
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.

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-2025-203775

No EUVD known-exploited evidence

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: hci_sock: Prevent race in socket write iter and sock bind There is a potential race condition between sock bind and socket write iter. bind may free the same cmd via mgmt_pending before write iter sends the cmd, just as syzbot reported in UAF[1]. Here we use hci_dev_lock to synchronize the two, thereby avoiding the UAF mentioned in [1]. [1] syzbot reported: BUG: KASAN: slab-use-after-free in mgmt_pending_remove+0x3b/0x210 net/bluetooth/mgmt_util.c:316 Read of size 8 at addr ffff888077164818 by task syz.0.17/5989 Call Trace: mgmt_pending_remove+0x3b/0x210 net/bluetooth/mgmt_util.c:316 set_link_security+0x5c2/0x710 net/bluetooth/mgmt.c:1918 hci_mgmt_cmd+0x9c9/0xef0 net/bluetooth/hci_sock.c:1719 hci_sock_sendmsg+0x6ca/0xef0 net/bluetooth/hci_sock.c:1839 sock_sendmsg_nosec net/socket.c:727 [inline] __sock_sendmsg+0x21c/0x270 net/socket.c:742 sock_write_iter+0x279/0x360 net/socket.c:1195 Allocated by task 5989: mgmt_pending_add+0x35/0x140 net/bluetooth/mgmt_util.c:296 set_link_security+0x557/0x710 net/bluetooth/mgmt.c:1910 hci_mgmt_cmd+0x9c9/0xef0 net/bluetooth/hci_sock.c:1719 hci_sock_sendmsg+0x6ca/0xef0 net/bluetooth/hci_sock.c:1839 sock_sendmsg_nosec net/socket.c:727 [inline] __sock_sendmsg+0x21c/0x270 net/socket.c:742 sock_write_iter+0x279/0x360 net/socket.c:1195 Freed by task 5991: mgmt_pending_free net/bluetooth/mgmt_util.c:311 [inline] mgmt_pending_foreach+0x30d/0x380 net/bluetooth/mgmt_util.c:257 mgmt_index_removed+0x112/0x2f0 net/bluetooth/mgmt.c:9477 hci_sock_bind+0xbe9/0x1000 net/bluetooth/hci_sock.c:1314

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
0.0
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

No CVSS base score is available from the CNA, CISA ADP or NIST. Absence of a score is not evidence of low risk; review the vendor advisory, affected exposure and exploit evidence. Verified remediation exists for at least one product or source, but 19 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_sock: Prevent race in socket write iter and sock bind There is a potential race condition between sock bind and socket write iter. bind may free the same cmd via mgmt_pending before write iter sends the cmd, just as syzbot reported in UAF[1]. Here we use hci_dev_lock to synchronize the two, thereby avoiding the UAF mentioned in [1]. [1] syzbot reported: BUG: KASAN: slab-use-after-free in mgmt_pending_remove+0x3b/0x210 net/bluetooth/mgmt_util.c:316 Read of size 8 at addr ffff888077164818 by task syz.0.17/5989 Call Trace: mgmt_pending_remove+0x3b/0x210 net/bluetooth/mgmt_util.c:316 set_link_security+0x5c2/0x710 net/bluetooth/mgmt.c:1918 hci_mgmt_cmd+0x9c9/0xef0 net/bluetooth/hci_sock.c:1719 hci_sock_sendmsg+0x6ca/0xef0 net/bluetooth/hci_sock.c:1839 sock_sendmsg_nosec net/socket.c:727 [inline] __sock_sendmsg+0x21c/0x270 net/socket.c:742 sock_write_iter+0x279/0x360 net/socket.c:1195 Allocated by task 5989: mgmt_pending_add+0x35/0x140 net/bluetooth/mgmt_util.c:296 set_link_security+0x557/0x710 net/bluetooth/mgmt.c:1910 hci_mgmt_cmd+0x9c9/0xef0 net/bluetooth/hci_sock.c:1719 hci_sock_sendmsg+0x6ca/0xef0 net/bluetooth/hci_sock.c:1839 sock_sendmsg_nosec net/socket.c:727 [inline] __sock_sendmsg+0x21c/0x270 net/socket.c:742 sock_write_iter+0x279/0x360 net/socket.c:1195 Freed by task 5991: mgmt_pending_free net/bluetooth/mgmt_util.c:311 [inline] mgmt_pending_foreach+0x30d/0x380 net/bluetooth/mgmt_util.c:257 mgmt_index_removed+0x112/0x2f0 net/bluetooth/mgmt.c:9477 hci_sock_bind+0xbe9/0x1000 net/bluetooth/hci_sock.c:1314

What

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: hci_sock: Prevent race in socket write iter and sock bind There is a potential race condition between sock bind and socket write iter. bind may free the same cmd via mgmt_pending before write iter sends the cmd, just as syzbot reported in UAF[1]. Here we use hci_dev_lock to synchronize the two, thereby avoiding the UAF mentioned in [1]. [1] syzbot reported: BUG: KASAN: slab-use-after-free in mgmt_pending_remove+0x3b/0x210 net/bluetooth/mgmt_util.c:316 Read of size 8 at addr ffff888077164818 by task syz.0.17/5989 Call Trace: mgmt_pending_remove+0x3b/0x210 net/bluetooth/mgmt_util.c:316 set_link_security+0x5c2/0x710 net/bluetooth/mgmt.c:1918 hci_mgmt_cmd+0x9c9/0xef0 net/bluetooth/hci_sock.c:1719 hci_sock_sendmsg+0x6ca/0xef0 net/bluetooth/hci_sock.c:1839 sock_sendmsg_nosec net/socket.c:727 [inline] __sock_sendmsg+0x21c/0x270 net/socket.c:742 sock_write_iter+0x279/0x360 net/socket.c:1195 Allocated by task 5989: mgmt_pending_add+0x35/0x140 net/bluetooth/mgmt_util.c:296 set_link_security+0x557/0x710 net/bluetooth/mgmt.c:1910 hci_mgmt_cmd+0x9c9/0xef0 net/bluetooth/hci_sock.c:1719 hci_sock_sendmsg+0x6ca/0xef0 net/bluetooth/hci_sock.c:1839 sock_sendmsg_nosec net/socket.c:727 [inline] __sock_sendmsg+0x21c/0x270 net/socket.c:742 sock_write_iter+0x279/0x360 net/socket.c:1195 Freed by task 5991: mgmt_pending_free net/bluetooth/mgmt_util.c:311 [inline] mgmt_pending_foreach+0x30d/0x380 net/bluetooth/mgmt_util.c:257 mgmt_index_removed+0x112/0x2f0 net/bluetooth/mgmt.c:9477 hci_sock_bind+0xbe9/0x1000 net/bluetooth/hci_sock.c:1314

Why

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

How

An attacker operating through the affected interface may attempt exploitation when the stated preconditions are met. 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_sock: Prevent race in socket write iter and sock bind There is a potential race condition between sock bind and socket write iter. bind may free the same cmd via mgmt_pending before write iter sends the cmd, just as syzbot reported in UAF[1]. Here we use hci_dev_lock to synchronize the two, thereby avoiding the UAF mentioned in [1]. [1] syzbot reported: BUG: KASAN: slab-use-after-free in mgmt_pending_remove+0x3b/0x210 net/bluetooth/mgmt_util.c:316 Read of size 8 at addr ffff888077164818 by task syz.0.17/5989 Call Trace: mgmt_pending_remove+0x3b/0x210 net/bluetooth/mgmt_util.c:316 set_link_security+0x5c2/0x710 net/bluetooth/mgmt.c:1918 hci_mgmt_cmd+0x9c9/0xef0 net/bluetooth/hci_sock.c:1719 hci_sock_sendmsg+0x6ca/0xef0 net/bluetooth/hci_sock.c:1839 sock_sendmsg_nosec net/socket.c:727 [inline] __sock_sendmsg+0x21c/0x270 net/socket.c:742 sock_write_iter+0x279/0x360 net/socket.c:1195 Allocated by task 5989: mgmt_pending_add+0x35/0x140 net/bluetooth/mgmt_util.c:296 set_link_security+0x557/0x710 net/bluetooth/mgmt.c:1910 hci_mgmt_cmd+0x9c9/0xef0 net/bluetooth/hci_sock.c:1719 hci_sock_sendmsg+0x6ca/0xef0 net/bluetooth/hci_sock.c:1839 sock_sendmsg_nosec net/socket.c:727 [inline] __sock_sendmsg+0x21c/0x270 net/socket.c:742 sock_write_iter+0x279/0x360 net/socket.c:1195 Freed by task 5991: mgmt_pending_free net/bluetooth/mgmt_util.c:311 [inline] mgmt_pending_foreach+0x30d/0x380 net/bluetooth/mgmt_util.c:257 mgmt_index_removed+0x112/0x2f0 net/bluetooth/mgmt.c:9477 hci_sock_bind+0xbe9/0x1000 net/bluetooth/hci_sock.c:1314

Why

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

How

An attacker operating through the affected interface may attempt exploitation when the stated preconditions are met. 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
the affected interface → vulnerable operation → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Unspecified
Privileges required
Not stated in the selected CVSS metric
User interaction
Not stated in the selected CVSS metric
Attack complexity
Not stated in the selected CVSS metric
Security boundary
Not stated in the selected CVSS metric
Weakness
?CWE means Common Weakness Enumeration.
CWE not yet assigned
CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
Not available from the selected scoring authority.
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.
A

Official authority intelligence

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

ENISA EUVD · EUVD-2025-203775Official EUVD mapping

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: hci_sock: Prevent race in socket write iter and sock bind There is a potential race condition between sock bind and socket write iter. bind may free the same cmd via mgmt_pending before write iter sends the cmd, just as syzbot reported in UAF[1]. Here we use hci_dev_lock to synchronize the two, thereby avoiding the UAF mentioned in [1]. [1] syzbot reported: BUG: KASAN: slab-use-after-free in mgmt_pending_remove+0x3b/0x210 net/bluetooth/mgmt_util.c:316 Read of size 8 at addr ffff888077164818 by task syz.0.17/5989 Call Trace: mgmt_pending_remove+0x3b/0x210 net/bluetooth/mgmt_util.c:316 set_link_security+0x5c2/0x710 net/bluetooth/mgmt.c:1918 hci_mgmt_cmd+0x9c9/0xef0 net/bluetooth/hci_sock.c:1719 hci_sock_sendmsg+0x6ca/0xef0 net/bluetooth/hci_sock.c:1839 sock_sendmsg_nosec net/socket.c:727 [inline] __sock_sendmsg+0x21c/0x270 net/socket.c:742 sock_write_iter+0x279/0x360 net/socket.c:1195 Allocated by task 5989: mgmt_pending_add+0x35/0x140 net/bluetooth/mgmt_util.c:296 set_link_security+0x557/0x710 net/bluetooth/mgmt.c:1910 hci_mgmt_cmd+0x9c9/0xef0 net/bluetooth/hci_sock.c:1719 hci_sock_sendmsg+0x6ca/0xef0 net/bluetooth/hci_sock.c:1839 sock_sendmsg_nosec net/socket.c:727 [inline] __sock_sendmsg+0x21c/0x270 net/socket.c:742 sock_write_iter+0x279/0x360 net/socket.c:1195 Freed by task 5991: mgmt_pending_free net/bluetooth/mgmt_util.c:311 [inline] mgmt_pending_foreach+0x30d/0x380 net/bluetooth/mgmt_util.c:257 mgmt_index_removed+0x112/0x2f0 net/bluetooth/mgmt.c:9477 hci_sock_bind+0xbe9/0x1000 net/bluetooth/hci_sock.c:1314

Official EUVD record ↗
BSI · German · WID-SEC-2026-2253IBM Security Verify Access: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in IBM Security Verify Access ausnutzen, um erweiterte Berechtigungen zu erlangen, beliebigen Code auszuführen, Sicherheitsmaßnahmen zu umgehen, Daten zu manipulieren, sensible Informationen offenzulegen und andere, nicht näher bezeichnete Angriffe durchzuführen.

Official advisory ↗
BSI · German · WID-SEC-2025-2868Linux Kernel: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um nicht näher spezifizierte Angriffe durchzuführen, die möglicherweise zu einer Denial-of-Service- Bedingung führen oder eine Speicherbeschädigung verursachen können.

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

d?id=CVE-2025-68288 Référence CVE CVE-2025-68289 https://www.cve.org/CVERecord?id=CVE-2025-68289 Référence CVE CVE-2025-68290 https://www.cve.org/CVERecord?id=CVE-2025-68290 Référence CVE CVE-2025-68291 https://www.cve.org/CVERecord?id=CVE-2025-68291 Référence CVE CVE-2025-68295 https://www.cve.org/CVERecord?id=CVE-2025-68295 Référence CVE CVE-2025-68297 https://www.cve.org/CVERecord?id=CVE-2025-68297 Référence CVE CVE-2025-68301 https://www.cve.org/CVERecord?id=CVE-2025-68301 Référence CVE CVE-2025-68302 https://www.cve.org/CVERecord?id=CVE-2025-68302 Référence CVE CVE-2025-68303 https://www.cve.org/CVERecord?id=CVE-2025-68303 Référence CVE CVE-2025-68305 https://www.cve.org/CVERecord?id=CVE-2025-68305 Référence CVE CVE-2025-68307 https://www.cve.org/CVERecord?id=CVE-2025-68307 Référence CVE CVE-2025-68308 https://www.cve.org/CVERecord?id=CVE-2025-68308 Référence CVE CVE-2025-68310 https://www.cve.org/CVERecord?id=CVE-2025-68310 Référence CVE CVE-2025-68311 https://www.cve.org/CVERecord?id=CVE-2025-68311 Référence CVE CVE-2025-68312 https://www.cve.org/CVERecord?id=CVE-2025-68312 Référence CVE CVE-2025-68313 https://www.cve.org/CVERecord?id=CVE-2025-68313 Référence CVE CVE-2025-68315 https://www.cve.org/CVERecord?id=CVE-2025-68315 Référence CVE CVE-2025-68320 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-68296 Référence CVE CVE-2025-68297 https://www.cve.org/CVERecord?id=CVE-2025-68297 Référence CVE CVE-2025-68298 https://www.cve.org/CVERecord?id=CVE-2025-68298 Référence CVE CVE-2025-68299 https://www.cve.org/CVERecord?id=CVE-2025-68299 Référence CVE CVE-2025-68300 https://www.cve.org/CVERecord?id=CVE-2025-68300 Référence CVE CVE-2025-68301 https://www.cve.org/CVERecord?id=CVE-2025-68301 Référence CVE CVE-2025-68302 https://www.cve.org/CVERecord?id=CVE-2025-68302 Référence CVE CVE-2025-68303 https://www.cve.org/CVERecord?id=CVE-2025-68303 Référence CVE CVE-2025-68304 https://www.cve.org/CVERecord?id=CVE-2025-68304 Référence CVE CVE-2025-68305 https://www.cve.org/CVERecord?id=CVE-2025-68305 Référence CVE CVE-2025-68306 https://www.cve.org/CVERecord?id=CVE-2025-68306 Référence CVE CVE-2025-68307 https://www.cve.org/CVERecord?id=CVE-2025-68307 Référence CVE CVE-2025-68308 https://www.cve.org/CVERecord?id=CVE-2025-68308 Référence CVE CVE-2025-68310 https://www.cve.org/CVERecord?id=CVE-2025-68310 Référence CVE CVE-2025-68311 https://www.cve.org/CVERecord?id=CVE-2025-68311 Référence CVE CVE-2025-68312 https://www.cve.org/CVERecord?id=CVE-2025-68312 Référence CVE CVE-2025-68313 https://www.cve.org/CVERecord?id=CVE-2025-68313 Référence CVE CVE-2025-68315 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-68296 Référence CVE CVE-2025-68297 https://www.cve.org/CVERecord?id=CVE-2025-68297 Référence CVE CVE-2025-68298 https://www.cve.org/CVERecord?id=CVE-2025-68298 Référence CVE CVE-2025-68299 https://www.cve.org/CVERecord?id=CVE-2025-68299 Référence CVE CVE-2025-68300 https://www.cve.org/CVERecord?id=CVE-2025-68300 Référence CVE CVE-2025-68301 https://www.cve.org/CVERecord?id=CVE-2025-68301 Référence CVE CVE-2025-68302 https://www.cve.org/CVERecord?id=CVE-2025-68302 Référence CVE CVE-2025-68303 https://www.cve.org/CVERecord?id=CVE-2025-68303 Référence CVE CVE-2025-68304 https://www.cve.org/CVERecord?id=CVE-2025-68304 Référence CVE CVE-2025-68305 https://www.cve.org/CVERecord?id=CVE-2025-68305 Référence CVE CVE-2025-68306 https://www.cve.org/CVERecord?id=CVE-2025-68306 Référence CVE CVE-2025-68307 https://www.cve.org/CVERecord?id=CVE-2025-68307 Référence CVE CVE-2025-68308 https://www.cve.org/CVERecord?id=CVE-2025-68308 Référence CVE CVE-2025-68310 https://www.cve.org/CVERecord?id=CVE-2025-68310 Référence CVE CVE-2025-68311 https://www.cve.org/CVERecord?id=CVE-2025-68311 Référence CVE CVE-2025-68312 https://www.cve.org/CVERecord?id=CVE-2025-68312 Référence CVE CVE-2025-68313 https://www.cve.org/CVERecord?id=CVE-2025-68313 Référence CVE CVE-2025-68315 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-68296 Référence CVE CVE-2025-68297 https://www.cve.org/CVERecord?id=CVE-2025-68297 Référence CVE CVE-2025-68298 https://www.cve.org/CVERecord?id=CVE-2025-68298 Référence CVE CVE-2025-68299 https://www.cve.org/CVERecord?id=CVE-2025-68299 Référence CVE CVE-2025-68300 https://www.cve.org/CVERecord?id=CVE-2025-68300 Référence CVE CVE-2025-68301 https://www.cve.org/CVERecord?id=CVE-2025-68301 Référence CVE CVE-2025-68302 https://www.cve.org/CVERecord?id=CVE-2025-68302 Référence CVE CVE-2025-68303 https://www.cve.org/CVERecord?id=CVE-2025-68303 Référence CVE CVE-2025-68304 https://www.cve.org/CVERecord?id=CVE-2025-68304 Référence CVE CVE-2025-68305 https://www.cve.org/CVERecord?id=CVE-2025-68305 Référence CVE CVE-2025-68306 https://www.cve.org/CVERecord?id=CVE-2025-68306 Référence CVE CVE-2025-68307 https://www.cve.org/CVERecord?id=CVE-2025-68307 Référence CVE CVE-2025-68308 https://www.cve.org/CVERecord?id=CVE-2025-68308 Référence CVE CVE-2025-68310 https://www.cve.org/CVERecord?id=CVE-2025-68310 Référence CVE CVE-2025-68311 https://www.cve.org/CVERecord?id=CVE-2025-68311 Référence CVE CVE-2025-68312 https://www.cve.org/CVERecord?id=CVE-2025-68312 Référence CVE CVE-2025-68313 https://www.cve.org/CVERecord?id=CVE-2025-68313 Référence CVE CVE-2025-68315 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-68286 Référence CVE CVE-2025-68287 https://www.cve.org/CVERecord?id=CVE-2025-68287 Référence CVE CVE-2025-68289 https://www.cve.org/CVERecord?id=CVE-2025-68289 Référence CVE CVE-2025-68290 https://www.cve.org/CVERecord?id=CVE-2025-68290 Référence CVE CVE-2025-68295 https://www.cve.org/CVERecord?id=CVE-2025-68295 Référence CVE CVE-2025-68296 https://www.cve.org/CVERecord?id=CVE-2025-68296 Référence CVE CVE-2025-68297 https://www.cve.org/CVERecord?id=CVE-2025-68297 Référence CVE CVE-2025-68301 https://www.cve.org/CVERecord?id=CVE-2025-68301 Référence CVE CVE-2025-68303 https://www.cve.org/CVERecord?id=CVE-2025-68303 Référence CVE CVE-2025-68305 https://www.cve.org/CVERecord?id=CVE-2025-68305 Référence CVE CVE-2025-68307 https://www.cve.org/CVERecord?id=CVE-2025-68307 Référence CVE CVE-2025-68308 https://www.cve.org/CVERecord?id=CVE-2025-68308 Référence CVE CVE-2025-68312 https://www.cve.org/CVERecord?id=CVE-2025-68312 Référence CVE CVE-2025-68313 https://www.cve.org/CVERecord?id=CVE-2025-68313 Référence CVE CVE-2025-68320 https://www.cve.org/CVERecord?id=CVE-2025-68320 Référence CVE CVE-2025-68325 https://www.cve.org/CVERecord?id=CVE-2025-68325 Référence CVE CVE-2025-68327 https://www.cve.org/CVERecord?id=CVE-2025-68327 Référence CVE CVE-2025-68328 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-68296 Référence CVE CVE-2025-68297 https://www.cve.org/CVERecord?id=CVE-2025-68297 Référence CVE CVE-2025-68298 https://www.cve.org/CVERecord?id=CVE-2025-68298 Référence CVE CVE-2025-68299 https://www.cve.org/CVERecord?id=CVE-2025-68299 Référence CVE CVE-2025-68300 https://www.cve.org/CVERecord?id=CVE-2025-68300 Référence CVE CVE-2025-68301 https://www.cve.org/CVERecord?id=CVE-2025-68301 Référence CVE CVE-2025-68302 https://www.cve.org/CVERecord?id=CVE-2025-68302 Référence CVE CVE-2025-68303 https://www.cve.org/CVERecord?id=CVE-2025-68303 Référence CVE CVE-2025-68304 https://www.cve.org/CVERecord?id=CVE-2025-68304 Référence CVE CVE-2025-68305 https://www.cve.org/CVERecord?id=CVE-2025-68305 Référence CVE CVE-2025-68306 https://www.cve.org/CVERecord?id=CVE-2025-68306 Référence CVE CVE-2025-68307 https://www.cve.org/CVERecord?id=CVE-2025-68307 Référence CVE CVE-2025-68308 https://www.cve.org/CVERecord?id=CVE-2025-68308 Référence CVE CVE-2025-68310 https://www.cve.org/CVERecord?id=CVE-2025-68310 Référence CVE CVE-2025-68311 https://www.cve.org/CVERecord?id=CVE-2025-68311 Référence CVE CVE-2025-68312 https://www.cve.org/CVERecord?id=CVE-2025-68312 Référence CVE CVE-2025-68313 https://www.cve.org/CVERecord?id=CVE-2025-68313 Référence CVE CVE-2025-68315 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-68285 Référence CVE CVE-2025-68286 https://www.cve.org/CVERecord?id=CVE-2025-68286 Référence CVE CVE-2025-68287 https://www.cve.org/CVERecord?id=CVE-2025-68287 Référence CVE CVE-2025-68289 https://www.cve.org/CVERecord?id=CVE-2025-68289 Référence CVE CVE-2025-68290 https://www.cve.org/CVERecord?id=CVE-2025-68290 Référence CVE CVE-2025-68296 https://www.cve.org/CVERecord?id=CVE-2025-68296 Référence CVE CVE-2025-68297 https://www.cve.org/CVERecord?id=CVE-2025-68297 Référence CVE CVE-2025-68301 https://www.cve.org/CVERecord?id=CVE-2025-68301 Référence CVE CVE-2025-68303 https://www.cve.org/CVERecord?id=CVE-2025-68303 Référence CVE CVE-2025-68305 https://www.cve.org/CVERecord?id=CVE-2025-68305 Référence CVE CVE-2025-68307 https://www.cve.org/CVERecord?id=CVE-2025-68307 Référence CVE CVE-2025-68308 https://www.cve.org/CVERecord?id=CVE-2025-68308 Référence CVE CVE-2025-68312 https://www.cve.org/CVERecord?id=CVE-2025-68312 Référence CVE CVE-2025-68313 https://www.cve.org/CVERecord?id=CVE-2025-68313 Référence CVE CVE-2025-68320 https://www.cve.org/CVERecord?id=CVE-2025-68320 Référence CVE CVE-2025-68325 https://www.cve.org/CVERecord?id=CVE-2025-68325 Référence CVE CVE-2025-68327 https://www.cve.org/CVERecord?id=CVE-2025-68327 Référence CVE CVE-2025-68328 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-68285 Référence CVE CVE-2025-68286 https://www.cve.org/CVERecord?id=CVE-2025-68286 Référence CVE CVE-2025-68287 https://www.cve.org/CVERecord?id=CVE-2025-68287 Référence CVE CVE-2025-68289 https://www.cve.org/CVERecord?id=CVE-2025-68289 Référence CVE CVE-2025-68290 https://www.cve.org/CVERecord?id=CVE-2025-68290 Référence CVE CVE-2025-68296 https://www.cve.org/CVERecord?id=CVE-2025-68296 Référence CVE CVE-2025-68297 https://www.cve.org/CVERecord?id=CVE-2025-68297 Référence CVE CVE-2025-68301 https://www.cve.org/CVERecord?id=CVE-2025-68301 Référence CVE CVE-2025-68303 https://www.cve.org/CVERecord?id=CVE-2025-68303 Référence CVE CVE-2025-68305 https://www.cve.org/CVERecord?id=CVE-2025-68305 Référence CVE CVE-2025-68307 https://www.cve.org/CVERecord?id=CVE-2025-68307 Référence CVE CVE-2025-68308 https://www.cve.org/CVERecord?id=CVE-2025-68308 Référence CVE CVE-2025-68312 https://www.cve.org/CVERecord?id=CVE-2025-68312 Référence CVE CVE-2025-68313 https://www.cve.org/CVERecord?id=CVE-2025-68313 Référence CVE CVE-2025-68320 https://www.cve.org/CVERecord?id=CVE-2025-68320 Référence CVE CVE-2025-68325 https://www.cve.org/CVERecord?id=CVE-2025-68325 Référence CVE CVE-2025-68327 https://www.cve.org/CVERecord?id=CVE-2025-68327 Référence CVE CVE-2025-68328 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-68261 Référence CVE CVE-2025-68264 https://www.cve.org/CVERecord?id=CVE-2025-68264 Référence CVE CVE-2025-68284 https://www.cve.org/CVERecord?id=CVE-2025-68284 Référence CVE CVE-2025-68285 https://www.cve.org/CVERecord?id=CVE-2025-68285 Référence CVE CVE-2025-68286 https://www.cve.org/CVERecord?id=CVE-2025-68286 Référence CVE CVE-2025-68296 https://www.cve.org/CVERecord?id=CVE-2025-68296 Référence CVE CVE-2025-68297 https://www.cve.org/CVERecord?id=CVE-2025-68297 Référence CVE CVE-2025-68301 https://www.cve.org/CVERecord?id=CVE-2025-68301 Référence CVE CVE-2025-68303 https://www.cve.org/CVERecord?id=CVE-2025-68303 Référence CVE CVE-2025-68305 https://www.cve.org/CVERecord?id=CVE-2025-68305 Référence CVE CVE-2025-68312 https://www.cve.org/CVERecord?id=CVE-2025-68312 Référence CVE CVE-2025-68320 https://www.cve.org/CVERecord?id=CVE-2025-68320 Référence CVE CVE-2025-68325 https://www.cve.org/CVERecord?id=CVE-2025-68325 Référence CVE CVE-2025-68327 https://www.cve.org/CVERecord?id=CVE-2025-68327 Référence CVE CVE-2025-68337 https://www.cve.org/CVERecord?id=CVE-2025-68337 Référence CVE CVE-2025-68349 https://www.cve.org/CVERecord?id=CVE-2025-68349 Référence CVE CVE-2025-68354 https://www.cve.org/CVERecord?id=CVE-2025-68354 Référence CVE CVE-2025-68362 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-68286 Référence CVE CVE-2025-68287 https://www.cve.org/CVERecord?id=CVE-2025-68287 Référence CVE CVE-2025-68289 https://www.cve.org/CVERecord?id=CVE-2025-68289 Référence CVE CVE-2025-68290 https://www.cve.org/CVERecord?id=CVE-2025-68290 Référence CVE CVE-2025-68293 https://www.cve.org/CVERecord?id=CVE-2025-68293 Référence CVE CVE-2025-68298 https://www.cve.org/CVERecord?id=CVE-2025-68298 Référence CVE CVE-2025-68301 https://www.cve.org/CVERecord?id=CVE-2025-68301 Référence CVE CVE-2025-68302 https://www.cve.org/CVERecord?id=CVE-2025-68302 Référence CVE CVE-2025-68303 https://www.cve.org/CVERecord?id=CVE-2025-68303 Référence CVE CVE-2025-68305 https://www.cve.org/CVERecord?id=CVE-2025-68305 Référence CVE CVE-2025-68306 https://www.cve.org/CVERecord?id=CVE-2025-68306 Référence CVE CVE-2025-68307 https://www.cve.org/CVERecord?id=CVE-2025-68307 Référence CVE CVE-2025-68308 https://www.cve.org/CVERecord?id=CVE-2025-68308 Référence CVE CVE-2025-68311 https://www.cve.org/CVERecord?id=CVE-2025-68311 Référence CVE CVE-2025-68312 https://www.cve.org/CVERecord?id=CVE-2025-68312 Référence CVE CVE-2025-68313 https://www.cve.org/CVERecord?id=CVE-2025-68313 Référence CVE CVE-2025-68317 https://www.cve.org/CVERecord?id=CVE-2025-68317 Référence CVE CVE-2025-68327 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-68259 Référence CVE CVE-2025-68264 https://www.cve.org/CVERecord?id=CVE-2025-68264 Référence CVE CVE-2025-68286 https://www.cve.org/CVERecord?id=CVE-2025-68286 Référence CVE CVE-2025-68287 https://www.cve.org/CVERecord?id=CVE-2025-68287 Référence CVE CVE-2025-68289 https://www.cve.org/CVERecord?id=CVE-2025-68289 Référence CVE CVE-2025-68290 https://www.cve.org/CVERecord?id=CVE-2025-68290 Référence CVE CVE-2025-68298 https://www.cve.org/CVERecord?id=CVE-2025-68298 Référence CVE CVE-2025-68302 https://www.cve.org/CVERecord?id=CVE-2025-68302 Référence CVE CVE-2025-68303 https://www.cve.org/CVERecord?id=CVE-2025-68303 Référence CVE CVE-2025-68305 https://www.cve.org/CVERecord?id=CVE-2025-68305 Référence CVE CVE-2025-68306 https://www.cve.org/CVERecord?id=CVE-2025-68306 Référence CVE CVE-2025-68307 https://www.cve.org/CVERecord?id=CVE-2025-68307 Référence CVE CVE-2025-68308 https://www.cve.org/CVERecord?id=CVE-2025-68308 Référence CVE CVE-2025-68312 https://www.cve.org/CVERecord?id=CVE-2025-68312 Référence CVE CVE-2025-68313 https://www.cve.org/CVERecord?id=CVE-2025-68313 Référence CVE CVE-2025-68328 https://www.cve.org/CVERecord?id=CVE-2025-68328 Référence CVE CVE-2025-68330 https://www.cve.org/CVERecord?id=CVE-2025-68330 Référence CVE CVE-2025-68331 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-39971 Référence CVE CVE-2025-39993 https://www.cve.org/CVERecord?id=CVE-2025-39993 Référence CVE CVE-2025-40141 https://www.cve.org/CVERecord?id=CVE-2025-40141 Référence CVE CVE-2025-40154 https://www.cve.org/CVERecord?id=CVE-2025-40154 Référence CVE CVE-2025-40248 https://www.cve.org/CVERecord?id=CVE-2025-40248 Référence CVE CVE-2025-40258 https://www.cve.org/CVERecord?id=CVE-2025-40258 Référence CVE CVE-2025-40277 https://www.cve.org/CVERecord?id=CVE-2025-40277 Référence CVE CVE-2025-40294 https://www.cve.org/CVERecord?id=CVE-2025-40294 Référence CVE CVE-2025-68301 https://www.cve.org/CVERecord?id=CVE-2025-68301 Référence CVE CVE-2025-68305 https://www.cve.org/CVERecord?id=CVE-2025-68305 Gestion détaillée du document le 30 janvier 2026 Version initiale Alertes Avis Bulletins d’actualités Mentions légales Conditions générales À propos Contact cyber.gouv.fr service-public.fr legifrance.gouv.fr info.gouv.fr france.fr info.gouv.fr/risques Premier Ministre / Secrétariat Général de la Défense et de la Sécurité Nationale / Agence nationale de la sécurité des systèmes d'information

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: < 6.16, 6.6.119 ≤ 6.6.*, 6.12.61 ≤ 6.12.*, 6.17.11 ≤ 6.17.*, 6.18 ≤ *
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 16 Dec 2025 · Last source change 23 Aug 2026, 12:45 UTC · CWE not yet assigned

CVE recordCVE.org · 5.2
CVSS sourceUnavailable
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-2025-203775
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceUnavailable
NVD statusNVD not scheduled

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

Material change intelligence

What changed after publication

View recent updates ↗
  1. Vendor guidanceAuthoritative vendor guidance changed: added remediation: git.kernel.org/7344feaed3c8aa46d397984ae855e6026d3c3e95; removed remediation: git.kernel.org/fe68510fc99bb4b88c9c611f83699749002d515a.
    Before
    remediation: git.kernel.org/fe68510fc99bb4b88c9c611f83699749002d515a
    After
    remediation: git.kernel.org/7344feaed3c8aa46d397984ae855e6026d3c3e95
    CNA ↗
  2. Affected versionsThe structured affected or fixed version information changed.
    Before
    bdd56875c6926d8009914f427df71797693e90d4 < fe68510fc99bb4b88c9c611f83699749002d515a; 4e83f2dbb2bf677e614109df24426c4dded472d4 < e90c05fc5bbea956450a05cc3b36b8fa29cf195e; 6fe26f694c824b8a4dbf50c635bee1302e3f099c < 69fcb0344bc0dd5b13d7e4e98f8b6bf25a6d4ff7; 6fe26f694c824b8a4dbf50c635bee1302e3f099c < 89bb613511cc21ed5ba6bddc1c9b9ae9c0dad392; d7882db79135c829a922daf3571f33ea1e056ae3; 6.6.94 < 6.6.119; 6.12.34 < 6.12.61; 6.15.3 < 6.16 · Fixed: < 6.16; 6.6.119 ≤ 6.6.*; 6.12.61 ≤ 6.12.*; 6.17.11 ≤ 6.17.*; 6.18 ≤ *
    After
    7b5958332f20dc66b19be564c402dbc21b927a81 < 7344feaed3c8aa46d397984ae855e6026d3c3e95; bdd56875c6926d8009914f427df71797693e90d4 < fe68510fc99bb4b88c9c611f83699749002d515a; 4e83f2dbb2bf677e614109df24426c4dded472d4 < e90c05fc5bbea956450a05cc3b36b8fa29cf195e; 6fe26f694c824b8a4dbf50c635bee1302e3f099c < 69fcb0344bc0dd5b13d7e4e98f8b6bf25a6d4ff7; 6fe26f694c824b8a4dbf50c635bee1302e3f099c < 89bb613511cc21ed5ba6bddc1c9b9ae9c0dad392; d7882db79135c829a922daf3571f33ea1e056ae3; 6.6.94 < 6.6.119; 6.12.34 < 6.12.61 · Fixed: < 6.16; 6.6.119 ≤ 6.6.*; 6.12.61 ≤ 6.12.*; 6.17.11 ≤ 6.17.*; 6.18 ≤ *
    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-2025-203775↗Vendor CSAF · SUSE Product Security Team↗CVE authority or vendor reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2025-68305 · cve.blacktree.nl