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

net/x25: fix use-after-free in x25_kill_by_neigh()

Linux · Linux

9.8CriticalCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

Critical technical impact with a remotely reachable, unauthenticated path; no CISA KEV confirmation is currently recorded. 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 severityCriticalOperational priority:Critical, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
  • EPSS is 0.73% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict the affected network interface to trusted sources where business-safe.
  • 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 3 daysRemediation target: Within 90 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.

25 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.101-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.187-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcelinux-6.12Vendor fix publishedDebian records a fixed source-package version for this release.6.12.101-1~deb12u1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.1.6-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.1.6-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-fdeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azure-nvidiaAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gcpAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gkeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gkeopAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-ibmAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-lowlatencyAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidiaAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidia-lowlatencyAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidia-tegraAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oem-6.11Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oracleAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-raspiAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-raspi-realtimeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-realtimeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-riscvAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-xilinxAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

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

2 current
CVE-2026-68137 · CSAF 2.0 · revision 10 · interimSUSE Product Security TeamCVE-2026-68137
294 known affected

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

  • cluster-md-kmp-default as component of SUSE Linux Enterprise High Performance Computing 12 SP5
  • dlm-kmp-default as component of SUSE Linux Enterprise High Performance Computing 12 SP5
  • gfs2-kmp-default as component of SUSE Linux Enterprise High Performance Computing 12 SP5
  • kernel-default as component of SUSE Linux Enterprise High Performance Computing 12 SP5
  • kernel-default-base as component of SUSE Linux Enterprise High Performance Computing 12 SP5
  • kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 12 SP5
  • kernel-default-man as component of SUSE Linux Enterprise High Performance Computing 12 SP5
  • kernel-devel as component of SUSE Linux Enterprise High Performance Computing 12 SP5
  • kernel-macros as component of SUSE Linux Enterprise High Performance Computing 12 SP5
  • kernel-source as component of SUSE Linux Enterprise High Performance Computing 12 SP5
  • ocfs2-kmp-default as component of SUSE Linux Enterprise High Performance Computing 12 SP5
  • kernel-default as component of SUSE Linux Enterprise High Performance Computing 15 SP1
Summary
In the Linux kernel, the following vulnerability has been resolved: net/x25: fix use-after-free in x25_kill_by_neigh() x25_kill_by_neigh() walks the global X.25 socket list looking for sockets attached to a terminating neighbour. x25_list_lock protects list membership while the lookup is in progress, but it does not pin a socket's lifetime after the lock is dropped. The function currently drops x25_list_lock before calling lock_sock(s). A concurrent close can run x25_release(), remove the same socket from x25_list, and drop the last socket reference in that window. The neighbour teardown path can then lock or inspect a freed struct sock/struct x25_sock. Take sock_hold(s) while x25_list_lock still proves that the list entry is live, then drop the temporary reference after the socket has been locked, rechecked, and released. Recheck x25_sk(s)->neighbour after lock_sock(), because another path may have disconnected the socket before this path acquired the socket lock. Restart the list walk after each disconnect because the list lock was dropped and the previous iterator state may no longer be valid. A QEMU/KASAN run against origin/master reproduced a slab-use-after-free in x25_kill_by_neigh().
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
CVE-2026-68137 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitykernel: net/x25: fix use-after-free in x25_kill_by_neigh()
277 known not affected

The vendor explicitly states that these products are not affected by this CVE.

  • kernel as a component of Red Hat Enterprise Linux 10
  • kernel-64k as a component of Red Hat Enterprise Linux 10
  • kernel-64k-core as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-core as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-devel as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-devel-matched as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-modules as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-modules-core as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-modules-extra as a component of Red Hat Enterprise Linux 10
  • kernel-64k-devel as a component of Red Hat Enterprise Linux 10
  • kernel-64k-devel-matched as a component of Red Hat Enterprise Linux 10
Summary
A flaw was found in the Linux kernel's X.25 networking component. This vulnerability, a use-after-free, occurs in the `x25_kill_by_neigh()` function when a network socket is prematurely released while still being referenced. A local attacker could exploit this to cause system instability, leading to a denial of service, or potentially achieve arbitrary code execution.
Remediation
No remediation text is recorded.
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-55518

No EUVD known-exploited evidence

In the Linux kernel, the following vulnerability has been resolved: net/x25: fix use-after-free in x25_kill_by_neigh() x25_kill_by_neigh() walks the global X.25 socket list looking for sockets attached to a terminating neighbour. x25_list_lock protects list membership while the lookup is in progress, but it does not pin a socket's lifetime after the lock is dropped. The function currently drops x25_list_lock before calling lock_sock(s). A concurrent close can run x25_release(), remove the same socket from x25_list, and drop the last socket reference in that window. The neighbour teardown path can then lock or inspect a freed struct sock/struct x25_sock. Take sock_hold(s) while x25_list_lock still proves that the list entry is live, then drop the temporary reference after the socket has been locked, rechecked, and released. Recheck x25_sk(s)->neighbour after lock_sock(), because another path may have disconnected the socket before this path acquired the socket lock. Restart the list walk after each disconnect because the list lock was dropped and the previous iterator state may no longer be valid. A QEMU/KASAN run against origin/master reproduced a slab-use-after-free in x25_kill_by_neigh().

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

Critical technical impact with a remotely reachable, unauthenticated path; no CISA KEV confirmation is currently recorded. 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: net/x25: fix use-after-free in x25_kill_by_neigh() x25_kill_by_neigh() walks the global X.25 socket list looking for sockets attached to a terminating neighbour. x25_list_lock protects list membership while the lookup is in progress, but it does not pin a socket's lifetime after the lock is dropped. The function currently drops x25_list_lock before calling lock_sock(s). A concurrent close can run x25_release(), remove the same socket from x25_list, and drop the last socket reference in that window. The neighbour teardown path can then lock or inspect a freed struct sock/struct x25_sock. Take sock_hold(s) while x25_list_lock still proves that the list entry is live, then drop the temporary reference after the socket has been locked, rechecked, and released. Recheck x25_sk(s)->neighbour after lock_sock(), because another path may have disconnected the socket before this path acquired the socket lock. Restart the list walk after each disconnect because the list lock was dropped and the previous iterator state may no longer be valid. A QEMU/KASAN run against origin/master reproduced a slab-use-after-free in x25_kill_by_neigh().

What

In the Linux kernel, the following vulnerability has been resolved: net/x25: fix use-after-free in x25_kill_by_neigh() x25_kill_by_neigh() walks the global X.25 socket list looking for sockets attached to a terminating neighbour. x25_list_lock protects list membership while the lookup is in progress, but it does not pin a socket's lifetime after the lock is dropped. The function currently drops x25_list_lock before calling lock_sock(s). A concurrent close can run x25_release(), remove the same socket from x25_list, and drop the last socket reference in that window. The neighbour teardown path can then lock or inspect a freed struct sock/struct x25_sock. Take sock_hold(s) while x25_list_lock still proves that the list entry is live, then drop the temporary reference after the socket has been locked, rechecked, and released. Recheck x25_sk(s)->neighbour after lock_sock(), because another path may have disconnected the socket before this path acquired the socket lock. Restart the list walk after each disconnect because the list lock was dropped and the previous iterator state may no longer be valid. A QEMU/KASAN run against origin/master reproduced a slab-use-after-free in x25_kill_by_neigh().

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 a network path 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: net/x25: fix use-after-free in x25_kill_by_neigh() x25_kill_by_neigh() walks the global X.25 socket list looking for sockets attached to a terminating neighbour. x25_list_lock protects list membership while the lookup is in progress, but it does not pin a socket's lifetime after the lock is dropped. The function currently drops x25_list_lock before calling lock_sock(s). A concurrent close can run x25_release(), remove the same socket from x25_list, and drop the last socket reference in that window. The neighbour teardown path can then lock or inspect a freed struct sock/struct x25_sock. Take sock_hold(s) while x25_list_lock still proves that the list entry is live, then drop the temporary reference after the socket has been locked, rechecked, and released. Recheck x25_sk(s)->neighbour after lock_sock(), because another path may have disconnected the socket before this path acquired the socket lock. Restart the list walk after each disconnect because the list lock was dropped and the previous iterator state may no longer be valid. A QEMU/KASAN run against origin/master reproduced a slab-use-after-free in x25_kill_by_neigh().

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 a network path 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
a network path → vulnerable operation → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Network
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:N/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.

AVNetworkAttack vector: The vulnerable component can be reached over a 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.
NetworkUnauthenticated
A

Official authority intelligence

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

ENISA EUVD · EUVD-2026-55518Official EUVD mapping

In the Linux kernel, the following vulnerability has been resolved: net/x25: fix use-after-free in x25_kill_by_neigh() x25_kill_by_neigh() walks the global X.25 socket list looking for sockets attached to a terminating neighbour. x25_list_lock protects list membership while the lookup is in progress, but it does not pin a socket's lifetime after the lock is dropped. The function currently drops x25_list_lock before calling lock_sock(s). A concurrent close can run x25_release(), remove the same socket from x25_list, and drop the last socket reference in that window. The neighbour teardown path can then lock or inspect a freed struct sock/struct x25_sock. Take sock_hold(s) while x25_list_lock still proves that the list entry is live, then drop the temporary reference after the socket has been locked, rechecked, and released. Recheck x25_sk(s)->neighbour after lock_sock(), because another path may have disconnected the socket before this path acquired the socket lock. Restart the list walk after each disconnect because the list lock was dropped and the previous iterator state may no longer be valid. A QEMU/KASAN run against origin/master reproduced a slab-use-after-free in x25_kill_by_neigh().

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

Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, darunter möglicherweise die Ausführung von beliebigem Code, die Ausweitung von Berechtigungen, die Offenlegung von Informationen, die Manipulation von Daten oder Denial-of-Service-Zustände.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20260812Security Bulletin 12 Aug 2026

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

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

d?id=CVE-2026-68125 Référence CVE CVE-2026-68126 https://www.cve.org/CVERecord?id=CVE-2026-68126 Référence CVE CVE-2026-68127 https://www.cve.org/CVERecord?id=CVE-2026-68127 Référence CVE CVE-2026-68128 https://www.cve.org/CVERecord?id=CVE-2026-68128 Référence CVE CVE-2026-68129 https://www.cve.org/CVERecord?id=CVE-2026-68129 Référence CVE CVE-2026-68132 https://www.cve.org/CVERecord?id=CVE-2026-68132 Référence CVE CVE-2026-68133 https://www.cve.org/CVERecord?id=CVE-2026-68133 Référence CVE CVE-2026-68135 https://www.cve.org/CVERecord?id=CVE-2026-68135 Référence CVE CVE-2026-68136 https://www.cve.org/CVERecord?id=CVE-2026-68136 Référence CVE CVE-2026-68137 https://www.cve.org/CVERecord?id=CVE-2026-68137 Référence CVE CVE-2026-68138 https://www.cve.org/CVERecord?id=CVE-2026-68138 Référence CVE CVE-2026-68139 https://www.cve.org/CVERecord?id=CVE-2026-68139 Référence CVE CVE-2026-68141 https://www.cve.org/CVERecord?id=CVE-2026-68141 Référence CVE CVE-2026-68142 https://www.cve.org/CVERecord?id=CVE-2026-68142 Référence CVE CVE-2026-68143 https://www.cve.org/CVERecord?id=CVE-2026-68143 Référence CVE CVE-2026-68144 https://www.cve.org/CVERecord?id=CVE-2026-68144 Référence CVE CVE-2026-68145 https://www.cve.org/CVERecord?id=CVE-2026-68145 Référence CVE CVE-2026-68148 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-68124 Référence CVE CVE-2026-68125 https://www.cve.org/CVERecord?id=CVE-2026-68125 Référence CVE CVE-2026-68126 https://www.cve.org/CVERecord?id=CVE-2026-68126 Référence CVE CVE-2026-68127 https://www.cve.org/CVERecord?id=CVE-2026-68127 Référence CVE CVE-2026-68129 https://www.cve.org/CVERecord?id=CVE-2026-68129 Référence CVE CVE-2026-68132 https://www.cve.org/CVERecord?id=CVE-2026-68132 Référence CVE CVE-2026-68133 https://www.cve.org/CVERecord?id=CVE-2026-68133 Référence CVE CVE-2026-68135 https://www.cve.org/CVERecord?id=CVE-2026-68135 Référence CVE CVE-2026-68136 https://www.cve.org/CVERecord?id=CVE-2026-68136 Référence CVE CVE-2026-68137 https://www.cve.org/CVERecord?id=CVE-2026-68137 Référence CVE CVE-2026-68138 https://www.cve.org/CVERecord?id=CVE-2026-68138 Référence CVE CVE-2026-68139 https://www.cve.org/CVERecord?id=CVE-2026-68139 Référence CVE CVE-2026-68142 https://www.cve.org/CVERecord?id=CVE-2026-68142 Référence CVE CVE-2026-68143 https://www.cve.org/CVERecord?id=CVE-2026-68143 Référence CVE CVE-2026-68145 https://www.cve.org/CVERecord?id=CVE-2026-68145 Référence CVE CVE-2026-68149 https://www.cve.org/CVERecord?id=CVE-2026-68149 Référence CVE CVE-2026-68152 https://www.cve.org/CVERecord?id=CVE-2026-68152 Référence CVE CVE-2026-68153 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-68089 Référence CVE CVE-2026-68090 https://www.cve.org/CVERecord?id=CVE-2026-68090 Référence CVE CVE-2026-68091 https://www.cve.org/CVERecord?id=CVE-2026-68091 Référence CVE CVE-2026-68092 https://www.cve.org/CVERecord?id=CVE-2026-68092 Référence CVE CVE-2026-68117 https://www.cve.org/CVERecord?id=CVE-2026-68117 Référence CVE CVE-2026-68123 https://www.cve.org/CVERecord?id=CVE-2026-68123 Référence CVE CVE-2026-68124 https://www.cve.org/CVERecord?id=CVE-2026-68124 Référence CVE CVE-2026-68127 https://www.cve.org/CVERecord?id=CVE-2026-68127 Référence CVE CVE-2026-68136 https://www.cve.org/CVERecord?id=CVE-2026-68136 Référence CVE CVE-2026-68137 https://www.cve.org/CVERecord?id=CVE-2026-68137 Référence CVE CVE-2026-68138 https://www.cve.org/CVERecord?id=CVE-2026-68138 Référence CVE CVE-2026-68144 https://www.cve.org/CVERecord?id=CVE-2026-68144 Référence CVE CVE-2026-68147 https://www.cve.org/CVERecord?id=CVE-2026-68147 Référence CVE CVE-2026-68152 https://www.cve.org/CVERecord?id=CVE-2026-68152 Référence CVE CVE-2026-68154 https://www.cve.org/CVERecord?id=CVE-2026-68154 Référence CVE CVE-2026-68156 https://www.cve.org/CVERecord?id=CVE-2026-68156 Référence CVE CVE-2026-68158 https://www.cve.org/CVERecord?id=CVE-2026-68158 Référence CVE CVE-2026-68159 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-68124 Référence CVE CVE-2026-68125 https://www.cve.org/CVERecord?id=CVE-2026-68125 Référence CVE CVE-2026-68127 https://www.cve.org/CVERecord?id=CVE-2026-68127 Référence CVE CVE-2026-68129 https://www.cve.org/CVERecord?id=CVE-2026-68129 Référence CVE CVE-2026-68130 https://www.cve.org/CVERecord?id=CVE-2026-68130 Référence CVE CVE-2026-68131 https://www.cve.org/CVERecord?id=CVE-2026-68131 Référence CVE CVE-2026-68132 https://www.cve.org/CVERecord?id=CVE-2026-68132 Référence CVE CVE-2026-68135 https://www.cve.org/CVERecord?id=CVE-2026-68135 Référence CVE CVE-2026-68136 https://www.cve.org/CVERecord?id=CVE-2026-68136 Référence CVE CVE-2026-68137 https://www.cve.org/CVERecord?id=CVE-2026-68137 Référence CVE CVE-2026-68138 https://www.cve.org/CVERecord?id=CVE-2026-68138 Référence CVE CVE-2026-68140 https://www.cve.org/CVERecord?id=CVE-2026-68140 Référence CVE CVE-2026-68141 https://www.cve.org/CVERecord?id=CVE-2026-68141 Référence CVE CVE-2026-68142 https://www.cve.org/CVERecord?id=CVE-2026-68142 Référence CVE CVE-2026-68143 https://www.cve.org/CVERecord?id=CVE-2026-68143 Référence CVE CVE-2026-68144 https://www.cve.org/CVERecord?id=CVE-2026-68144 Référence CVE CVE-2026-68146 https://www.cve.org/CVERecord?id=CVE-2026-68146 Référence CVE CVE-2026-68147 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-68124 Référence CVE CVE-2026-68125 https://www.cve.org/CVERecord?id=CVE-2026-68125 Référence CVE CVE-2026-68126 https://www.cve.org/CVERecord?id=CVE-2026-68126 Référence CVE CVE-2026-68127 https://www.cve.org/CVERecord?id=CVE-2026-68127 Référence CVE CVE-2026-68129 https://www.cve.org/CVERecord?id=CVE-2026-68129 Référence CVE CVE-2026-68132 https://www.cve.org/CVERecord?id=CVE-2026-68132 Référence CVE CVE-2026-68133 https://www.cve.org/CVERecord?id=CVE-2026-68133 Référence CVE CVE-2026-68135 https://www.cve.org/CVERecord?id=CVE-2026-68135 Référence CVE CVE-2026-68136 https://www.cve.org/CVERecord?id=CVE-2026-68136 Référence CVE CVE-2026-68137 https://www.cve.org/CVERecord?id=CVE-2026-68137 Référence CVE CVE-2026-68138 https://www.cve.org/CVERecord?id=CVE-2026-68138 Référence CVE CVE-2026-68139 https://www.cve.org/CVERecord?id=CVE-2026-68139 Référence CVE CVE-2026-68142 https://www.cve.org/CVERecord?id=CVE-2026-68142 Référence CVE CVE-2026-68143 https://www.cve.org/CVERecord?id=CVE-2026-68143 Référence CVE CVE-2026-68145 https://www.cve.org/CVERecord?id=CVE-2026-68145 Référence CVE CVE-2026-68149 https://www.cve.org/CVERecord?id=CVE-2026-68149 Référence CVE CVE-2026-68152 https://www.cve.org/CVERecord?id=CVE-2026-68152 Référence CVE CVE-2026-68153 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-68126 Référence CVE CVE-2026-68127 https://www.cve.org/CVERecord?id=CVE-2026-68127 Référence CVE CVE-2026-68128 https://www.cve.org/CVERecord?id=CVE-2026-68128 Référence CVE CVE-2026-68129 https://www.cve.org/CVERecord?id=CVE-2026-68129 Référence CVE CVE-2026-68130 https://www.cve.org/CVERecord?id=CVE-2026-68130 Référence CVE CVE-2026-68131 https://www.cve.org/CVERecord?id=CVE-2026-68131 Référence CVE CVE-2026-68133 https://www.cve.org/CVERecord?id=CVE-2026-68133 Référence CVE CVE-2026-68135 https://www.cve.org/CVERecord?id=CVE-2026-68135 Référence CVE CVE-2026-68136 https://www.cve.org/CVERecord?id=CVE-2026-68136 Référence CVE CVE-2026-68137 https://www.cve.org/CVERecord?id=CVE-2026-68137 Référence CVE CVE-2026-68139 https://www.cve.org/CVERecord?id=CVE-2026-68139 Référence CVE CVE-2026-68140 https://www.cve.org/CVERecord?id=CVE-2026-68140 Référence CVE CVE-2026-68141 https://www.cve.org/CVERecord?id=CVE-2026-68141 Référence CVE CVE-2026-68142 https://www.cve.org/CVERecord?id=CVE-2026-68142 Référence CVE CVE-2026-68143 https://www.cve.org/CVERecord?id=CVE-2026-68143 Référence CVE CVE-2026-68144 https://www.cve.org/CVERecord?id=CVE-2026-68144 Référence CVE CVE-2026-68145 https://www.cve.org/CVERecord?id=CVE-2026-68145 Référence CVE CVE-2026-68146 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: < 5.18, 5.10.265 ≤ 5.10.*, 5.15.216 ≤ 5.15.*, 6.1.183 ≤ 6.1.*, 6.6.148 ≤ 6.6.*, 6.12.101 ≤ 6.12.*, 6.18.42 ≤ 6.18.*, 7.1.6 ≤ 7.1.*, 7.2 ≤ *
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. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04

Evidence and provenance

Published 10 Aug 2026 · Last source change 19 Aug 2026, 16:29 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-55518
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceUnavailable
NVD statusNVD received

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. Vendor guidanceAuthoritative vendor guidance changed: added remediation: git.kernel.org/db6b04f6d65549bb1c7bc8e64a92e7b7d03be676; removed remediation: git.kernel.org/3f4fe26c20c30bd5a2e2583e80685def0b27858c.
    Before
    remediation: git.kernel.org/3f4fe26c20c30bd5a2e2583e80685def0b27858c
    After
    remediation: git.kernel.org/db6b04f6d65549bb1c7bc8e64a92e7b7d03be676
    CNA ↗
  2. Affected versionsThe structured affected or fixed version information changed.
    Before
    7781607938c8371d4c2b243527430241c62e39c2 < 3f4fe26c20c30bd5a2e2583e80685def0b27858c; 7781607938c8371d4c2b243527430241c62e39c2 < 610678d4be94b619c751572e8a58de705592cd07; 7781607938c8371d4c2b243527430241c62e39c2 < ec6d91a1bf2ebd767d3d43f6d249ee0ed3f4558a; 7781607938c8371d4c2b243527430241c62e39c2 < 9aabda553184346f74810e2ee1d96920b4612e3f; 7781607938c8371d4c2b243527430241c62e39c2 < 5499e0602d2faafd42c580d25f615903c3fbe11b; dffc859d1d9560da594e4282091781b8d2715f00; 858642789ada1b48630f322e59416ca9fca3e6b7; 4c240c5a105557e4546d0836e694868f22fd09b0 · Fixed: < 5.18; 6.6.148 ≤ 6.6.*; 6.12.101 ≤ 6.12.*; 6.18.42 ≤ 6.18.*; 7.1.6 ≤ 7.1.*; 7.2 ≤ *
    After
    5c94b6205e87411dbe9dc1ca088eb36b8837fb47 < db6b04f6d65549bb1c7bc8e64a92e7b7d03be676; 409570a619c1cda2e0fde6018a256b9e3d3ba0ee < 5e8a754ac2009a88a7b99ab61eab6296eed360f3; 7781607938c8371d4c2b243527430241c62e39c2 < c98a454d1a9e1bd09d5fd55a7aa589b199340b88; 7781607938c8371d4c2b243527430241c62e39c2 < 3f4fe26c20c30bd5a2e2583e80685def0b27858c; 7781607938c8371d4c2b243527430241c62e39c2 < 610678d4be94b619c751572e8a58de705592cd07; 7781607938c8371d4c2b243527430241c62e39c2 < ec6d91a1bf2ebd767d3d43f6d249ee0ed3f4558a; 7781607938c8371d4c2b243527430241c62e39c2 < 9aabda553184346f74810e2ee1d96920b4612e3f; 7781607938c8371d4c2b243527430241c62e39c2 < 5499e0602d2faafd42c580d25f615903c3fbe11b · Fixed: < 5.18; 5.10.265 ≤ 5.10.*; 5.15.216 ≤ 5.15.*; 6.1.183 ≤ 6.1.*; 6.6.148 ≤ 6.6.*; 6.12.101 ≤ 6.12.*; 6.18.42 ≤ 6.18.*; 7.1.6 ≤ 7.1.*
    CNA ↗
  3. Affected versionsThe structured affected or fixed version information changed.
    Before
    7781607938c8371d4c2b243527430241c62e39c2 < 3f4fe26c20c30bd5a2e2583e80685def0b27858c; 7781607938c8371d4c2b243527430241c62e39c2 < 610678d4be94b619c751572e8a58de705592cd07; 7781607938c8371d4c2b243527430241c62e39c2 < ec6d91a1bf2ebd767d3d43f6d249ee0ed3f4558a; 7781607938c8371d4c2b243527430241c62e39c2 < 9aabda553184346f74810e2ee1d96920b4612e3f; 7781607938c8371d4c2b243527430241c62e39c2 < 5499e0602d2faafd42c580d25f615903c3fbe11b; dffc859d1d9560da594e4282091781b8d2715f00; 858642789ada1b48630f322e59416ca9fca3e6b7; 4c240c5a105557e4546d0836e694868f22fd09b0 · Fixed: < 5.18; 6.6.148 ≤ 6.6.*; 6.12.101 ≤ 6.12.*; 6.18.42 ≤ 6.18.*; 7.1.6 ≤ 7.1.*; 7.2-rc5 ≤ *
    After
    7781607938c8371d4c2b243527430241c62e39c2 < 3f4fe26c20c30bd5a2e2583e80685def0b27858c; 7781607938c8371d4c2b243527430241c62e39c2 < 610678d4be94b619c751572e8a58de705592cd07; 7781607938c8371d4c2b243527430241c62e39c2 < ec6d91a1bf2ebd767d3d43f6d249ee0ed3f4558a; 7781607938c8371d4c2b243527430241c62e39c2 < 9aabda553184346f74810e2ee1d96920b4612e3f; 7781607938c8371d4c2b243527430241c62e39c2 < 5499e0602d2faafd42c580d25f615903c3fbe11b; dffc859d1d9560da594e4282091781b8d2715f00; 858642789ada1b48630f322e59416ca9fca3e6b7; 4c240c5a105557e4546d0836e694868f22fd09b0 · Fixed: < 5.18; 6.6.148 ≤ 6.6.*; 6.12.101 ≤ 6.12.*; 6.18.42 ≤ 6.18.*; 7.1.6 ≤ 7.1.*; 7.2 ≤ *
    CNA ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
ENISA EUVD · EUVD-2026-55518↗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-68137 · cve.blacktree.nl