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

Bluetooth: hci_sync: fix UAF in hci_le_create_cis_sync

Linux · Linux

8.8HighCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 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:High, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • EPSS is 0.33% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict local access and enforce least privilege on affected hosts.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs Linux Linux and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: Within 30 daysRemediation target: Within 180 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 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 7 Oct 2026
Debian bookwormbookworm · sourcelinuxNot affectedDebian marks this release not affected (fixed-version marker 0).Not published in this feedDebian Security Tracker ↗Source updated 7 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.0.12-1Debian Security Tracker ↗Source updated 7 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.0.12-1Debian Security Tracker ↗Source updated 7 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 7 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 7 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 7 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 7 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 7 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 7 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 7 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 7 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 7 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 7 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 7 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 7 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 7 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 7 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 7 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 7 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 7 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 7 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 7 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 7 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-2026-63944 · CSAF 2.0 · revision 21 · interimSUSE Product Security TeamCVE-2026-63944
56 known affected

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

  • SUSE Linux Enterprise Server 16.0:kernel-livepatch-6_12_0-160000_26-default
  • SUSE Linux Enterprise Server 16.0:kernel-livepatch-6_12_0-160000_27-default
  • SUSE Linux Enterprise Server 16.0:kernel-livepatch-6_12_0-160000_28-default
  • SUSE Linux Enterprise Server 16.0:kernel-livepatch-6_12_0-160000_29-default
  • SUSE Linux Enterprise Server 16.0:kernel-livepatch-6_12_0-160000_30-default
  • SUSE Linux Enterprise Server 16.0:kernel-livepatch-6_12_0-160000_31-default
  • SUSE Linux Enterprise Server 16.0:kernel-livepatch-6_12_0-160000_32-default
  • SUSE Linux Enterprise Server 16.0:kernel-livepatch-6_12_0-160000_33-default
  • SUSE Linux Enterprise Server 16.0:kernel-livepatch-6_12_0-160000_5-default
  • SUSE Linux Enterprise Server 16.0:kernel-livepatch-6_12_0-160000_6-default
  • SUSE Linux Enterprise Server 16.0:kernel-livepatch-6_12_0-160000_7-default
  • SUSE Linux Enterprise Server 16.0:kernel-livepatch-6_12_0-160000_8-default
Summary
In the Linux kernel, the following vulnerability has been resolved: Bluetooth: hci_sync: fix UAF in hci_le_create_cis_sync hci_le_create_cis_sync() dereferences conn->conn_timeout after releasing both rcu_read_lock() and hci_dev_lock(hdev). The conn pointer was obtained from an RCU-protected iteration over hdev->conn_hash.list and is not valid once these locks are dropped. A concurrent disconnect can free the hci_conn between the unlock and the dereference, causing a use-after-free read. The cancellation mechanism in hci_conn_del() cannot prevent this because hci_le_create_cis_pending() queues hci_create_cis_sync with data=NULL: hci_cmd_sync_queue(hdev, hci_create_cis_sync, NULL, NULL); While hci_conn_del() dequeues with data=conn: hci_cmd_sync_dequeue(hdev, NULL, conn, NULL); Since NULL != conn, the lookup in _hci_cmd_sync_lookup_entry() never matches, and the pending work item is not cancelled. Fix this by saving conn->conn_timeout into a local variable while the locks are still held, so the stale conn pointer is never dereferenced after unlock. This is the same class of bug as the one fixed by commit 035c25007c9e ("Bluetooth: hci_sync: Fix UAF on le_read_features_complete") which addressed the identical pattern in a different function. This vulnerability was identified using 0sec.ai, an open-source automated security auditing platform (https://github.com/0sec-labs).
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
CVE-2026-63944 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitykernel: Bluetooth: hci_sync: fix UAF in hci_le_create_cis_sync
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 flaw was found in the Linux kernel's Bluetooth subsystem. This vulnerability, a Use-After-Free (UAF), allows an attacker to access memory after it has been freed. This can lead to a system crash, resulting in a Denial of Service (DoS), or potentially enable an attacker to execute malicious code. The flaw occurs due to improper handling of connection timeouts during concurrent disconnections.
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. Red Hat recommends treating all kernel errata as security-relevant. Given the kernel's fundamental role, any bug has a higher chance of impacting system security, even if that impact only becomes clear after a fix is published. Therefore, Red Hat prioritizes delivering fixes that improve our customers' overall security posture. Because of this proactive approach, a patch may be associated with a CVE assignment at a future date. Retroactive CVE assignments are always documented in the corresponding errata and on Red Hat's CVE pages. We strongly advise against delaying updates, as doing so may leave your system exposed when protections are already available.
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-45717

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_sync: fix UAF in hci_le_create_cis_sync hci_le_create_cis_sync() dereferences conn->conn_timeout after releasing both rcu_read_lock() and hci_dev_lock(hdev). The conn pointer was obtained from an RCU-protected iteration over hdev->conn_hash.list and is not valid once these locks are dropped. A concurrent disconnect can free the hci_conn between the unlock and the dereference, causing a use-after-free read. The cancellation mechanism in hci_conn_del() cannot prevent this because hci_le_create_cis_pending() queues hci_create_cis_sync with data=NULL: hci_cmd_sync_queue(hdev, hci_create_cis_sync, NULL, NULL); While hci_conn_del() dequeues with data=conn: hci_cmd_sync_dequeue(hdev, NULL, conn, NULL); Since NULL != conn, the lookup in _hci_cmd_sync_lookup_entry() never matches, and the pending work item is not cancelled. Fix this by saving conn->conn_timeout into a local variable while the locks are still held, so the stale conn pointer is never dereferenced after unlock. This is the same class of bug as the one fixed by commit 035c25007c9e ("Bluetooth: hci_sync: Fix UAF on le_read_features_complete") which addressed the identical pattern in a different function. This vulnerability was identified using 0sec.ai, an open-source automated security auditing platform (https://github.com/0sec-labs).

What

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: hci_sync: fix UAF in hci_le_create_cis_sync hci_le_create_cis_sync() dereferences conn->conn_timeout after releasing both rcu_read_lock() and hci_dev_lock(hdev). The conn pointer was obtained from an RCU-protected iteration over hdev->conn_hash.list and is not valid once these locks are dropped. A concurrent disconnect can free the hci_conn between the unlock and the dereference, causing a use-after-free read. The cancellation mechanism in hci_conn_del() cannot prevent this because hci_le_create_cis_pending() queues hci_create_cis_sync with data=NULL: hci_cmd_sync_queue(hdev, hci_create_cis_sync, NULL, NULL); While hci_conn_del() dequeues with data=conn: hci_cmd_sync_dequeue(hdev, NULL, conn, NULL); Since NULL != conn, the lookup in _hci_cmd_sync_lookup_entry() never matches, and the pending work item is not cancelled. Fix this by saving conn->conn_timeout into a local variable while the locks are still held, so the stale conn pointer is never dereferenced after unlock. This is the same class of bug as the one fixed by commit 035c25007c9e ("Bluetooth: hci_sync: Fix UAF on le_read_features_complete") which addressed the identical pattern in a different function. This vulnerability was identified using 0sec.ai, an open-source automated security auditing platform (https://github.com/0sec-labs).

Why

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

How

An attacker operating through an adjacent network may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: hci_sync: fix UAF in hci_le_create_cis_sync hci_le_create_cis_sync() dereferences conn->conn_timeout after releasing both rcu_read_lock() and hci_dev_lock(hdev). The conn pointer was obtained from an RCU-protected iteration over hdev->conn_hash.list and is not valid once these locks are dropped. A concurrent disconnect can free the hci_conn between the unlock and the dereference, causing a use-after-free read. The cancellation mechanism in hci_conn_del() cannot prevent this because hci_le_create_cis_pending() queues hci_create_cis_sync with data=NULL: hci_cmd_sync_queue(hdev, hci_create_cis_sync, NULL, NULL); While hci_conn_del() dequeues with data=conn: hci_cmd_sync_dequeue(hdev, NULL, conn, NULL); Since NULL != conn, the lookup in _hci_cmd_sync_lookup_entry() never matches, and the pending work item is not cancelled. Fix this by saving conn->conn_timeout into a local variable while the locks are still held, so the stale conn pointer is never dereferenced after unlock. This is the same class of bug as the one fixed by commit 035c25007c9e ("Bluetooth: hci_sync: Fix UAF on le_read_features_complete") which addressed the identical pattern in a different function. This vulnerability was identified using 0sec.ai, an open-source automated security auditing platform (https://github.com/0sec-labs).

Why

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

How

An attacker operating through an adjacent network may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
an adjacent network → vulnerable operation → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Adjacent
Privileges required
None: unauthenticated exploitation is possible
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration.
CWE not yet assigned
CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVAdjacentAttack vector: The attacker must be on an adjacent or logically close network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CHighConfidentiality impact: A successful attack can cause a major loss.IHighIntegrity impact: A successful attack can cause a major loss.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
Unauthenticated
A

Official authority intelligence

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

BSI · German · WID-SEC-2026-2403Linux Kernel: Mehrere Schwachstellen ermöglichen nicht spezifizierten Angriff

Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, möglicherweise Sicherheitsmaßnahmen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen oder vertrauliche Informationen offenzulegen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20260722Security Bulletin 22 Jul 2026

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 22 Jul 2026, published on 22 July 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-63935 Référence CVE CVE-2026-63936 https://www.cve.org/CVERecord?id=CVE-2026-63936 Référence CVE CVE-2026-63937 https://www.cve.org/CVERecord?id=CVE-2026-63937 Référence CVE CVE-2026-63938 https://www.cve.org/CVERecord?id=CVE-2026-63938 Référence CVE CVE-2026-63939 https://www.cve.org/CVERecord?id=CVE-2026-63939 Référence CVE CVE-2026-63940 https://www.cve.org/CVERecord?id=CVE-2026-63940 Référence CVE CVE-2026-63941 https://www.cve.org/CVERecord?id=CVE-2026-63941 Référence CVE CVE-2026-63942 https://www.cve.org/CVERecord?id=CVE-2026-63942 Référence CVE CVE-2026-63943 https://www.cve.org/CVERecord?id=CVE-2026-63943 Référence CVE CVE-2026-63944 https://www.cve.org/CVERecord?id=CVE-2026-63944 Référence CVE CVE-2026-63945 https://www.cve.org/CVERecord?id=CVE-2026-63945 Référence CVE CVE-2026-63946 https://www.cve.org/CVERecord?id=CVE-2026-63946 Référence CVE CVE-2026-63947 https://www.cve.org/CVERecord?id=CVE-2026-63947 Référence CVE CVE-2026-63948 https://www.cve.org/CVERecord?id=CVE-2026-63948 Référence CVE CVE-2026-63949 https://www.cve.org/CVERecord?id=CVE-2026-63949 Référence CVE CVE-2026-63950 https://www.cve.org/CVERecord?id=CVE-2026-63950 Référence CVE CVE-2026-63951 https://www.cve.org/CVERecord?id=CVE-2026-63951 Référence CVE CVE-2026-63952 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-63935 Référence CVE CVE-2026-63936 https://www.cve.org/CVERecord?id=CVE-2026-63936 Référence CVE CVE-2026-63937 https://www.cve.org/CVERecord?id=CVE-2026-63937 Référence CVE CVE-2026-63938 https://www.cve.org/CVERecord?id=CVE-2026-63938 Référence CVE CVE-2026-63939 https://www.cve.org/CVERecord?id=CVE-2026-63939 Référence CVE CVE-2026-63940 https://www.cve.org/CVERecord?id=CVE-2026-63940 Référence CVE CVE-2026-63941 https://www.cve.org/CVERecord?id=CVE-2026-63941 Référence CVE CVE-2026-63942 https://www.cve.org/CVERecord?id=CVE-2026-63942 Référence CVE CVE-2026-63943 https://www.cve.org/CVERecord?id=CVE-2026-63943 Référence CVE CVE-2026-63944 https://www.cve.org/CVERecord?id=CVE-2026-63944 Référence CVE CVE-2026-63945 https://www.cve.org/CVERecord?id=CVE-2026-63945 Référence CVE CVE-2026-63946 https://www.cve.org/CVERecord?id=CVE-2026-63946 Référence CVE CVE-2026-63947 https://www.cve.org/CVERecord?id=CVE-2026-63947 Référence CVE CVE-2026-63948 https://www.cve.org/CVERecord?id=CVE-2026-63948 Référence CVE CVE-2026-63949 https://www.cve.org/CVERecord?id=CVE-2026-63949 Référence CVE CVE-2026-63950 https://www.cve.org/CVERecord?id=CVE-2026-63950 Référence CVE CVE-2026-63951 https://www.cve.org/CVERecord?id=CVE-2026-63951 Référence CVE CVE-2026-63952 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-63889 Référence CVE CVE-2026-63891 https://www.cve.org/CVERecord?id=CVE-2026-63891 Référence CVE CVE-2026-63898 https://www.cve.org/CVERecord?id=CVE-2026-63898 Référence CVE CVE-2026-63920 https://www.cve.org/CVERecord?id=CVE-2026-63920 Référence CVE CVE-2026-63923 https://www.cve.org/CVERecord?id=CVE-2026-63923 Référence CVE CVE-2026-63925 https://www.cve.org/CVERecord?id=CVE-2026-63925 Référence CVE CVE-2026-63926 https://www.cve.org/CVERecord?id=CVE-2026-63926 Référence CVE CVE-2026-63928 https://www.cve.org/CVERecord?id=CVE-2026-63928 Référence CVE CVE-2026-63937 https://www.cve.org/CVERecord?id=CVE-2026-63937 Référence CVE CVE-2026-63944 https://www.cve.org/CVERecord?id=CVE-2026-63944 Référence CVE CVE-2026-63969 https://www.cve.org/CVERecord?id=CVE-2026-63969 Référence CVE CVE-2026-63970 https://www.cve.org/CVERecord?id=CVE-2026-63970 Référence CVE CVE-2026-63972 https://www.cve.org/CVERecord?id=CVE-2026-63972 Référence CVE CVE-2026-63973 https://www.cve.org/CVERecord?id=CVE-2026-63973 Référence CVE CVE-2026-63980 https://www.cve.org/CVERecord?id=CVE-2026-63980 Référence CVE CVE-2026-63985 https://www.cve.org/CVERecord?id=CVE-2026-63985 Référence CVE CVE-2026-63990 https://www.cve.org/CVERecord?id=CVE-2026-63990 Référence CVE CVE-2026-63992 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-63915 Référence CVE CVE-2026-63916 https://www.cve.org/CVERecord?id=CVE-2026-63916 Référence CVE CVE-2026-63917 https://www.cve.org/CVERecord?id=CVE-2026-63917 Référence CVE CVE-2026-63919 https://www.cve.org/CVERecord?id=CVE-2026-63919 Référence CVE CVE-2026-63921 https://www.cve.org/CVERecord?id=CVE-2026-63921 Référence CVE CVE-2026-63922 https://www.cve.org/CVERecord?id=CVE-2026-63922 Référence CVE CVE-2026-63924 https://www.cve.org/CVERecord?id=CVE-2026-63924 Référence CVE CVE-2026-63926 https://www.cve.org/CVERecord?id=CVE-2026-63926 Référence CVE CVE-2026-63940 https://www.cve.org/CVERecord?id=CVE-2026-63940 Référence CVE CVE-2026-63944 https://www.cve.org/CVERecord?id=CVE-2026-63944 Référence CVE CVE-2026-63945 https://www.cve.org/CVERecord?id=CVE-2026-63945 Référence CVE CVE-2026-63946 https://www.cve.org/CVERecord?id=CVE-2026-63946 Référence CVE CVE-2026-63947 https://www.cve.org/CVERecord?id=CVE-2026-63947 Référence CVE CVE-2026-63948 https://www.cve.org/CVERecord?id=CVE-2026-63948 Référence CVE CVE-2026-63952 https://www.cve.org/CVERecord?id=CVE-2026-63952 Référence CVE CVE-2026-63974 https://www.cve.org/CVERecord?id=CVE-2026-63974 Référence CVE CVE-2026-63975 https://www.cve.org/CVERecord?id=CVE-2026-63975 Référence CVE CVE-2026-63976 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-63935 Référence CVE CVE-2026-63936 https://www.cve.org/CVERecord?id=CVE-2026-63936 Référence CVE CVE-2026-63937 https://www.cve.org/CVERecord?id=CVE-2026-63937 Référence CVE CVE-2026-63938 https://www.cve.org/CVERecord?id=CVE-2026-63938 Référence CVE CVE-2026-63939 https://www.cve.org/CVERecord?id=CVE-2026-63939 Référence CVE CVE-2026-63940 https://www.cve.org/CVERecord?id=CVE-2026-63940 Référence CVE CVE-2026-63941 https://www.cve.org/CVERecord?id=CVE-2026-63941 Référence CVE CVE-2026-63942 https://www.cve.org/CVERecord?id=CVE-2026-63942 Référence CVE CVE-2026-63943 https://www.cve.org/CVERecord?id=CVE-2026-63943 Référence CVE CVE-2026-63944 https://www.cve.org/CVERecord?id=CVE-2026-63944 Référence CVE CVE-2026-63945 https://www.cve.org/CVERecord?id=CVE-2026-63945 Référence CVE CVE-2026-63946 https://www.cve.org/CVERecord?id=CVE-2026-63946 Référence CVE CVE-2026-63947 https://www.cve.org/CVERecord?id=CVE-2026-63947 Référence CVE CVE-2026-63948 https://www.cve.org/CVERecord?id=CVE-2026-63948 Référence CVE CVE-2026-63949 https://www.cve.org/CVERecord?id=CVE-2026-63949 Référence CVE CVE-2026-63950 https://www.cve.org/CVERecord?id=CVE-2026-63950 Référence CVE CVE-2026-63951 https://www.cve.org/CVERecord?id=CVE-2026-63951 Référence CVE CVE-2026-63952 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-63889 Référence CVE CVE-2026-63891 https://www.cve.org/CVERecord?id=CVE-2026-63891 Référence CVE CVE-2026-63898 https://www.cve.org/CVERecord?id=CVE-2026-63898 Référence CVE CVE-2026-63920 https://www.cve.org/CVERecord?id=CVE-2026-63920 Référence CVE CVE-2026-63923 https://www.cve.org/CVERecord?id=CVE-2026-63923 Référence CVE CVE-2026-63925 https://www.cve.org/CVERecord?id=CVE-2026-63925 Référence CVE CVE-2026-63926 https://www.cve.org/CVERecord?id=CVE-2026-63926 Référence CVE CVE-2026-63928 https://www.cve.org/CVERecord?id=CVE-2026-63928 Référence CVE CVE-2026-63937 https://www.cve.org/CVERecord?id=CVE-2026-63937 Référence CVE CVE-2026-63944 https://www.cve.org/CVERecord?id=CVE-2026-63944 Référence CVE CVE-2026-63969 https://www.cve.org/CVERecord?id=CVE-2026-63969 Référence CVE CVE-2026-63970 https://www.cve.org/CVERecord?id=CVE-2026-63970 Référence CVE CVE-2026-63972 https://www.cve.org/CVERecord?id=CVE-2026-63972 Référence CVE CVE-2026-63973 https://www.cve.org/CVERecord?id=CVE-2026-63973 Référence CVE CVE-2026-63980 https://www.cve.org/CVERecord?id=CVE-2026-63980 Référence CVE CVE-2026-63985 https://www.cve.org/CVERecord?id=CVE-2026-63985 Référence CVE CVE-2026-63990 https://www.cve.org/CVERecord?id=CVE-2026-63990 Référence CVE CVE-2026-63992 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-63935 Référence CVE CVE-2026-63936 https://www.cve.org/CVERecord?id=CVE-2026-63936 Référence CVE CVE-2026-63937 https://www.cve.org/CVERecord?id=CVE-2026-63937 Référence CVE CVE-2026-63938 https://www.cve.org/CVERecord?id=CVE-2026-63938 Référence CVE CVE-2026-63939 https://www.cve.org/CVERecord?id=CVE-2026-63939 Référence CVE CVE-2026-63940 https://www.cve.org/CVERecord?id=CVE-2026-63940 Référence CVE CVE-2026-63941 https://www.cve.org/CVERecord?id=CVE-2026-63941 Référence CVE CVE-2026-63942 https://www.cve.org/CVERecord?id=CVE-2026-63942 Référence CVE CVE-2026-63943 https://www.cve.org/CVERecord?id=CVE-2026-63943 Référence CVE CVE-2026-63944 https://www.cve.org/CVERecord?id=CVE-2026-63944 Référence CVE CVE-2026-63945 https://www.cve.org/CVERecord?id=CVE-2026-63945 Référence CVE CVE-2026-63946 https://www.cve.org/CVERecord?id=CVE-2026-63946 Référence CVE CVE-2026-63947 https://www.cve.org/CVERecord?id=CVE-2026-63947 Référence CVE CVE-2026-63948 https://www.cve.org/CVERecord?id=CVE-2026-63948 Référence CVE CVE-2026-63949 https://www.cve.org/CVERecord?id=CVE-2026-63949 Référence CVE CVE-2026-63950 https://www.cve.org/CVERecord?id=CVE-2026-63950 Référence CVE CVE-2026-63951 https://www.cve.org/CVERecord?id=CVE-2026-63951 Référence CVE CVE-2026-63952 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-63933 Référence CVE CVE-2026-63934 https://www.cve.org/CVERecord?id=CVE-2026-63934 Référence CVE CVE-2026-63936 https://www.cve.org/CVERecord?id=CVE-2026-63936 Référence CVE CVE-2026-63937 https://www.cve.org/CVERecord?id=CVE-2026-63937 Référence CVE CVE-2026-63938 https://www.cve.org/CVERecord?id=CVE-2026-63938 Référence CVE CVE-2026-63939 https://www.cve.org/CVERecord?id=CVE-2026-63939 Référence CVE CVE-2026-63940 https://www.cve.org/CVERecord?id=CVE-2026-63940 Référence CVE CVE-2026-63942 https://www.cve.org/CVERecord?id=CVE-2026-63942 Référence CVE CVE-2026-63943 https://www.cve.org/CVERecord?id=CVE-2026-63943 Référence CVE CVE-2026-63944 https://www.cve.org/CVERecord?id=CVE-2026-63944 Référence CVE CVE-2026-63945 https://www.cve.org/CVERecord?id=CVE-2026-63945 Référence CVE CVE-2026-63946 https://www.cve.org/CVERecord?id=CVE-2026-63946 Référence CVE CVE-2026-63947 https://www.cve.org/CVERecord?id=CVE-2026-63947 Référence CVE CVE-2026-63948 https://www.cve.org/CVERecord?id=CVE-2026-63948 Référence CVE CVE-2026-63949 https://www.cve.org/CVERecord?id=CVE-2026-63949 Référence CVE CVE-2026-63952 https://www.cve.org/CVERecord?id=CVE-2026-63952 Référence CVE CVE-2026-63957 https://www.cve.org/CVERecord?id=CVE-2026-63957 Référence CVE CVE-2026-63958 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-63935 Référence CVE CVE-2026-63936 https://www.cve.org/CVERecord?id=CVE-2026-63936 Référence CVE CVE-2026-63937 https://www.cve.org/CVERecord?id=CVE-2026-63937 Référence CVE CVE-2026-63938 https://www.cve.org/CVERecord?id=CVE-2026-63938 Référence CVE CVE-2026-63939 https://www.cve.org/CVERecord?id=CVE-2026-63939 Référence CVE CVE-2026-63940 https://www.cve.org/CVERecord?id=CVE-2026-63940 Référence CVE CVE-2026-63941 https://www.cve.org/CVERecord?id=CVE-2026-63941 Référence CVE CVE-2026-63942 https://www.cve.org/CVERecord?id=CVE-2026-63942 Référence CVE CVE-2026-63943 https://www.cve.org/CVERecord?id=CVE-2026-63943 Référence CVE CVE-2026-63944 https://www.cve.org/CVERecord?id=CVE-2026-63944 Référence CVE CVE-2026-63945 https://www.cve.org/CVERecord?id=CVE-2026-63945 Référence CVE CVE-2026-63946 https://www.cve.org/CVERecord?id=CVE-2026-63946 Référence CVE CVE-2026-63947 https://www.cve.org/CVERecord?id=CVE-2026-63947 Référence CVE CVE-2026-63948 https://www.cve.org/CVERecord?id=CVE-2026-63948 Référence CVE CVE-2026-63949 https://www.cve.org/CVERecord?id=CVE-2026-63949 Référence CVE CVE-2026-63950 https://www.cve.org/CVERecord?id=CVE-2026-63950 Référence CVE CVE-2026-63951 https://www.cve.org/CVERecord?id=CVE-2026-63951 Référence CVE CVE-2026-63952 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-63935 Référence CVE CVE-2026-63936 https://www.cve.org/CVERecord?id=CVE-2026-63936 Référence CVE CVE-2026-63937 https://www.cve.org/CVERecord?id=CVE-2026-63937 Référence CVE CVE-2026-63938 https://www.cve.org/CVERecord?id=CVE-2026-63938 Référence CVE CVE-2026-63939 https://www.cve.org/CVERecord?id=CVE-2026-63939 Référence CVE CVE-2026-63940 https://www.cve.org/CVERecord?id=CVE-2026-63940 Référence CVE CVE-2026-63941 https://www.cve.org/CVERecord?id=CVE-2026-63941 Référence CVE CVE-2026-63942 https://www.cve.org/CVERecord?id=CVE-2026-63942 Référence CVE CVE-2026-63943 https://www.cve.org/CVERecord?id=CVE-2026-63943 Référence CVE CVE-2026-63944 https://www.cve.org/CVERecord?id=CVE-2026-63944 Référence CVE CVE-2026-63945 https://www.cve.org/CVERecord?id=CVE-2026-63945 Référence CVE CVE-2026-63946 https://www.cve.org/CVERecord?id=CVE-2026-63946 Référence CVE CVE-2026-63947 https://www.cve.org/CVERecord?id=CVE-2026-63947 Référence CVE CVE-2026-63948 https://www.cve.org/CVERecord?id=CVE-2026-63948 Référence CVE CVE-2026-63949 https://www.cve.org/CVERecord?id=CVE-2026-63949 Référence CVE CVE-2026-63950 https://www.cve.org/CVERecord?id=CVE-2026-63950 Référence CVE CVE-2026-63951 https://www.cve.org/CVERecord?id=CVE-2026-63951 Référence CVE CVE-2026-63952 https://www.cve.org/CVERecord?id=

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix availability varies by product
Affected
Fixed
Linux: < 6.4, 6.6.143 ≤ 6.6.*, 6.12.93 ≤ 6.12.*, 6.18.35 ≤ 6.18.*, 7.0.12 ≤ 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 19 Jul 2026 · Last source change 5 Aug 2026, 12:37 UTC · CWE not yet assigned

CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2026-45717
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceUnavailable
NVD statusNVD awaiting enrichment

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

Material change intelligence

What changed after publication

View recent updates ↗
  1. Affected versionsThe structured affected or fixed version information changed.
    Before
    SUSE Linux Enterprise Live Patching 15 SP6:kernel-livepatch-6_4_0-150600_23_130-default; SUSE Linux Enterprise Live Patching 15 SP6:kernel-livepatch-6_4_0-150600_23_92-default; SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_53_16-default; SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_53_19-default; SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_53_22-default; SUSE Linux Enterprise Server 16.0:kernel-livepatch-6_12_0-160000_28-default; SUSE Linux Enterprise Server 16.0:kernel-livepatch-6_12_0-160000_29-default; SUSE Linux Enterprise Server 16.0:kernel-livepatch-6_12_0-160000_31-default; SUSE Linux Enterprise Server 16.0:kernel-livepatch-6_12_0-160000_32-default; SUSE Linux Enterprise Server 16.0:kernel-livepatch-6_12_0-160000_33-default; SUSE Linux Enterprise Server for SAP applications 16.0:kernel-livepatch-6_12_0-160000_28-default; SUSE Linux Enterprise Server for SAP applications 16.0:kernel-livepatch-6_12_0-160000_29-default; SUSE Linux Enterprise Server for SAP applications 16.0:kernel-livepatch-6_12_0-160000_31-default; SUSE Linux Enterprise Server for SAP applications 16.0:kernel-livepatch-6_12_0-160000_32-default; SUSE Linux Enterprise Server for SAP applications 16.0:kernel-livepatch-6_12_0-160000_33-default; SUSE Linux Micro 6.2:kernel-livepatch-6_12_0-160000_28-default; SUSE Linux Micro 6.2:kernel-livepatch-6_12_0-160000_29-default; SUSE Linux Micro 6.2:kernel-livepatch-6_12_0-160000_31-default; SUSE Linux Micro 6.2:kernel-livepatch-6_12_0-160000_32-default; SUSE Linux Micro 6.2:kernel-livepatch-6_12_0-160000_33-default; 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; and 7 more
    After
    SUSE Linux Enterprise Server 16.0:kernel-livepatch-6_12_0-160000_26-default; SUSE Linux Enterprise Server 16.0:kernel-livepatch-6_12_0-160000_27-default; SUSE Linux Enterprise Server 16.0:kernel-livepatch-6_12_0-160000_28-default; SUSE Linux Enterprise Server 16.0:kernel-livepatch-6_12_0-160000_29-default; SUSE Linux Enterprise Server 16.0:kernel-livepatch-6_12_0-160000_30-default; SUSE Linux Enterprise Server 16.0:kernel-livepatch-6_12_0-160000_31-default; SUSE Linux Enterprise Server 16.0:kernel-livepatch-6_12_0-160000_32-default; SUSE Linux Enterprise Server 16.0:kernel-livepatch-6_12_0-160000_33-default; SUSE Linux Enterprise Server 16.0:kernel-livepatch-6_12_0-160000_5-default; SUSE Linux Enterprise Server 16.0:kernel-livepatch-6_12_0-160000_6-default; SUSE Linux Enterprise Server 16.0:kernel-livepatch-6_12_0-160000_7-default; SUSE Linux Enterprise Server 16.0:kernel-livepatch-6_12_0-160000_8-default; SUSE Linux Enterprise Server 16.0:kernel-livepatch-6_12_0-160000_9-default; SUSE Linux Enterprise Server for SAP applications 16.0:kernel-livepatch-6_12_0-160000_26-default; SUSE Linux Enterprise Server for SAP applications 16.0:kernel-livepatch-6_12_0-160000_27-default; SUSE Linux Enterprise Server for SAP applications 16.0:kernel-livepatch-6_12_0-160000_28-default; SUSE Linux Enterprise Server for SAP applications 16.0:kernel-livepatch-6_12_0-160000_29-default; SUSE Linux Enterprise Server for SAP applications 16.0:kernel-livepatch-6_12_0-160000_30-default; SUSE Linux Enterprise Server for SAP applications 16.0:kernel-livepatch-6_12_0-160000_31-default; SUSE Linux Enterprise Server for SAP applications 16.0:kernel-livepatch-6_12_0-160000_32-default; SUSE Linux Enterprise Server for SAP applications 16.0:kernel-livepatch-6_12_0-160000_33-default; SUSE Linux Enterprise Server for SAP applications 16.0:kernel-livepatch-6_12_0-160000_5-default; SUSE Linux Enterprise Server for SAP applications 16.0:kernel-livepatch-6_12_0-160000_6-default; SUSE Linux Enterprise Server for SAP applications 16.0:kernel-livepatch-6_12_0-160000_7-default; SUSE Linux Enterprise Server for SAP applications 16.0:kernel-livepatch-6_12_0-160000_8-default; SUSE Linux Enterprise Server for SAP applications 16.0:kernel-livepatch-6_12_0-160000_9-default; SUSE Linux Micro 6.2:kernel-livepatch-6_12_0-160000_26-default; SUSE Linux Micro 6.2:kernel-livepatch-6_12_0-160000_27-default; SUSE Linux Micro 6.2:kernel-livepatch-6_12_0-160000_28-default; SUSE Linux Micro 6.2:kernel-livepatch-6_12_0-160000_29-default; and 26 more
    SUSE Product Security Team ↗
  2. Affected versionsThe structured affected or fixed version information changed.
    Before
    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; SLES 15 SP1 CHOST Images for Microsoft Azure; SLES 15 SP2 CHOST Images for Microsoft Azure; SLES 15 SP3 CHOST Images for Microsoft Azure; SLES 15 SP4 CHOST Images for Microsoft Azure; SLES 15 SP5 CHOST Images for Microsoft Azure
    After
    SUSE Linux Enterprise Live Patching 15 SP6:kernel-livepatch-6_4_0-150600_23_130-default; SUSE Linux Enterprise Live Patching 15 SP6:kernel-livepatch-6_4_0-150600_23_92-default; SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_53_16-default; SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_53_19-default; SUSE Linux Enterprise Live Patching 15 SP7:kernel-livepatch-6_4_0-150700_53_22-default; SUSE Linux Enterprise Server 16.0:kernel-livepatch-6_12_0-160000_28-default; SUSE Linux Enterprise Server 16.0:kernel-livepatch-6_12_0-160000_29-default; SUSE Linux Enterprise Server 16.0:kernel-livepatch-6_12_0-160000_31-default; SUSE Linux Enterprise Server 16.0:kernel-livepatch-6_12_0-160000_32-default; SUSE Linux Enterprise Server 16.0:kernel-livepatch-6_12_0-160000_33-default; SUSE Linux Enterprise Server for SAP applications 16.0:kernel-livepatch-6_12_0-160000_28-default; SUSE Linux Enterprise Server for SAP applications 16.0:kernel-livepatch-6_12_0-160000_29-default; SUSE Linux Enterprise Server for SAP applications 16.0:kernel-livepatch-6_12_0-160000_31-default; SUSE Linux Enterprise Server for SAP applications 16.0:kernel-livepatch-6_12_0-160000_32-default; SUSE Linux Enterprise Server for SAP applications 16.0:kernel-livepatch-6_12_0-160000_33-default; SUSE Linux Micro 6.2:kernel-livepatch-6_12_0-160000_28-default; SUSE Linux Micro 6.2:kernel-livepatch-6_12_0-160000_29-default; SUSE Linux Micro 6.2:kernel-livepatch-6_12_0-160000_31-default; SUSE Linux Micro 6.2:kernel-livepatch-6_12_0-160000_32-default; SUSE Linux Micro 6.2:kernel-livepatch-6_12_0-160000_33-default; 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; and 7 more
    SUSE Product Security Team ↗
  3. Affected versionsThe structured affected or fixed version information changed.
    Before
    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; SLES 15 SP1 CHOST Images for Microsoft Azure; SLES 15 SP2 CHOST Images for Microsoft Azure; SLES 15 SP3 CHOST Images for Microsoft Azure; SLES 15 SP4 CHOST Images for Microsoft Azure; SLES 15 SP5 CHOST Images for Microsoft Azure · Fixed: kernel-obs-build-6.12.0-160000.37.1 as component of SUSE Linux Micro Extras 6.2; kernel-syms-6.12.0-160000.37.1 as component of SUSE Linux Micro Extras 6.2
    After
    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; SLES 15 SP1 CHOST Images for Microsoft Azure; SLES 15 SP2 CHOST Images for Microsoft Azure; SLES 15 SP3 CHOST Images for Microsoft Azure; SLES 15 SP4 CHOST Images for Microsoft Azure; SLES 15 SP5 CHOST Images for Microsoft Azure
    SUSE Product Security Team ↗
  4. Affected versionsThe structured affected or fixed version information changed.
    Before
    bpftool as a component of Red Hat Enterprise Linux 9; kernel as a component of Red Hat Enterprise Linux 9; kernel-64k as a component of Red Hat Enterprise Linux 9; kernel-64k-core as a component of Red Hat Enterprise Linux 9; kernel-64k-debug as a component of Red Hat Enterprise Linux 9; kernel-64k-debug-core as a component of Red Hat Enterprise Linux 9; kernel-64k-debug-devel as a component of Red Hat Enterprise Linux 9; kernel-64k-debug-devel-matched as a component of Red Hat Enterprise Linux 9; kernel-64k-debug-modules as a component of Red Hat Enterprise Linux 9; kernel-64k-debug-modules-core as a component of Red Hat Enterprise Linux 9; kernel-64k-debug-modules-extra as a component of Red Hat Enterprise Linux 9; kernel-64k-debug-modules-internal as a component of Red Hat Enterprise Linux 9; kernel-64k-debug-modules-partner as a component of Red Hat Enterprise Linux 9; kernel-64k-devel as a component of Red Hat Enterprise Linux 9; kernel-64k-devel-matched as a component of Red Hat Enterprise Linux 9; kernel-64k-modules as a component of Red Hat Enterprise Linux 9; kernel-64k-modules-core as a component of Red Hat Enterprise Linux 9; kernel-64k-modules-extra as a component of Red Hat Enterprise Linux 9; kernel-64k-modules-internal as a component of Red Hat Enterprise Linux 9; kernel-64k-modules-partner as a component of Red Hat Enterprise Linux 9; kernel-abi-stablelists as a component of Red Hat Enterprise Linux 9; kernel-core as a component of Red Hat Enterprise Linux 9; kernel-cross-headers as a component of Red Hat Enterprise Linux 9; kernel-debug as a component of Red Hat Enterprise Linux 9; kernel-debug-core as a component of Red Hat Enterprise Linux 9; kernel-debug-devel as a component of Red Hat Enterprise Linux 9; kernel-debug-devel-matched as a component of Red Hat Enterprise Linux 9; kernel-debug-modules as a component of Red Hat Enterprise Linux 9; kernel-debug-modules-core as a component of Red Hat Enterprise Linux 9; kernel-debug-modules-extra as a component of Red Hat Enterprise Linux 9; and 78 more · Fixed: kernel-64k-debug-debuginfo-0:6.12.0-211.53.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-64k-debug-devel-0:6.12.0-211.53.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-64k-debug-devel-matched-0:6.12.0-211.53.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-64k-debuginfo-0:6.12.0-211.53.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-64k-devel-0:6.12.0-211.53.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-64k-devel-matched-0:6.12.0-211.53.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-debuginfo-0:6.12.0-211.53.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-debuginfo-0:6.12.0-211.53.1.el10_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-debuginfo-0:6.12.0-211.53.1.el10_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-debuginfo-0:6.12.0-211.53.1.el10_2.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-devel-0:6.12.0-211.53.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-devel-0:6.12.0-211.53.1.el10_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-devel-0:6.12.0-211.53.1.el10_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-devel-0:6.12.0-211.53.1.el10_2.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-devel-matched-0:6.12.0-211.53.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-devel-matched-0:6.12.0-211.53.1.el10_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-devel-matched-0:6.12.0-211.53.1.el10_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-devel-matched-0:6.12.0-211.53.1.el10_2.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debuginfo-0:6.12.0-211.53.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debuginfo-0:6.12.0-211.53.1.el10_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debuginfo-0:6.12.0-211.53.1.el10_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debuginfo-0:6.12.0-211.53.1.el10_2.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debuginfo-common-aarch64-0:6.12.0-211.53.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debuginfo-common-ppc64le-0:6.12.0-211.53.1.el10_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debuginfo-common-s390x-0:6.12.0-211.53.1.el10_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debuginfo-common-x86_64-0:6.12.0-211.53.1.el10_2.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-devel-0:6.12.0-211.53.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-devel-0:6.12.0-211.53.1.el10_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-devel-0:6.12.0-211.53.1.el10_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-devel-0:6.12.0-211.53.1.el10_2.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); and 279 more
    After
    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; kernel-rt-devel as a component of Red Hat Enterprise Linux 9; kernel-rt-devel-matched as a component of Red Hat Enterprise Linux 9; kernel-rt-kvm as a component of Red Hat Enterprise Linux 9; kernel-rt-modules as a component of Red Hat Enterprise Linux 9; kernel-rt-modules-core as a component of Red Hat Enterprise Linux 9; kernel-rt-modules-extra as a component of Red Hat Enterprise Linux 9; kernel-rt-modules-internal as a component of Red Hat Enterprise Linux 9; kernel-rt-modules-partner as a component of Red Hat Enterprise Linux 9; kernel-rt-selftests-internal as a component of Red Hat Enterprise Linux 9; kernel-rt.src as a component of Red Hat Enterprise Linux 9 · Fixed: kernel-64k-debug-debuginfo-0:6.12.0-211.53.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-64k-debug-devel-0:6.12.0-211.53.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-64k-debug-devel-matched-0:6.12.0-211.53.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-64k-debuginfo-0:6.12.0-211.53.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-64k-devel-0:6.12.0-211.53.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-64k-devel-matched-0:6.12.0-211.53.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-debuginfo-0:6.12.0-211.53.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-debuginfo-0:6.12.0-211.53.1.el10_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-debuginfo-0:6.12.0-211.53.1.el10_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-debuginfo-0:6.12.0-211.53.1.el10_2.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-devel-0:6.12.0-211.53.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-devel-0:6.12.0-211.53.1.el10_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-devel-0:6.12.0-211.53.1.el10_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-devel-0:6.12.0-211.53.1.el10_2.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-devel-matched-0:6.12.0-211.53.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-devel-matched-0:6.12.0-211.53.1.el10_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-devel-matched-0:6.12.0-211.53.1.el10_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-devel-matched-0:6.12.0-211.53.1.el10_2.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debuginfo-0:6.12.0-211.53.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debuginfo-0:6.12.0-211.53.1.el10_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debuginfo-0:6.12.0-211.53.1.el10_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debuginfo-0:6.12.0-211.53.1.el10_2.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debuginfo-common-aarch64-0:6.12.0-211.53.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debuginfo-common-ppc64le-0:6.12.0-211.53.1.el10_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debuginfo-common-s390x-0:6.12.0-211.53.1.el10_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debuginfo-common-x86_64-0:6.12.0-211.53.1.el10_2.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-devel-0:6.12.0-211.53.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-devel-0:6.12.0-211.53.1.el10_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-devel-0:6.12.0-211.53.1.el10_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-devel-0:6.12.0-211.53.1.el10_2.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); and 582 more
    Red Hat Product Security ↗
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-45717↗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-2026-63944 · cve.blacktree.nl