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

l2tp: use list_del_rcu in l2tp_session_unhash

Linux · Linux

5.5MediumCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 13 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 severityMediumOperational priority:Low, lowered one band.downgradedsince 19 Jul 2026

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • Exploitation requires an existing local or physical foothold with privileges.
  • EPSS is 0.12% 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: No default targetRemediation target: Normal maintenance

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

17 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 13 affected package states shown here. Treat those rows as affected with no fix until that distribution publishes a fixed version.

Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.12.94-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourcelinuxNot affectedDebian marks this release not affected (fixed-version marker 0).Not published in this feedDebian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.0.12-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.0.12-1Debian Security Tracker ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-aws-6.14Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azure-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 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azure-fde-6.14Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azure-nvidia-6.14Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gcp-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 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-hwe-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 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-lowlatency-hwe-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 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidia-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 6 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 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oracle-6.14Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 6 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 6 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 6 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 6 Oct 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

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

1 current
CVE-2026-64119 · CSAF 2.0 · revision 6 · interimSUSE Product Security TeamCVE-2026-64119
31 known affected

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

  • kernel-default as component of SUSE Linux Enterprise High Availability Extension 16.0
  • kernel-source as component of SUSE Linux Enterprise High Availability Extension 16.0
  • kernel-default as component of SUSE Linux Enterprise High Availability Extension 16.1
  • kernel-source as component of SUSE Linux Enterprise High Availability Extension 16.1
  • kernel-default as component of SUSE Linux Enterprise Server 16.0
  • kernel-devel as component of SUSE Linux Enterprise Server 16.0
  • kernel-macros as component of SUSE Linux Enterprise Server 16.0
  • kernel-source as component of SUSE Linux Enterprise Server 16.0
  • kernel-source-vanilla as component of SUSE Linux Enterprise Server 16.0
  • kernel-default as component of SUSE Linux Enterprise Server 16.1
  • kernel-devel as component of SUSE Linux Enterprise Server 16.1
  • kernel-macros as component of SUSE Linux Enterprise Server 16.1
Summary
In the Linux kernel, the following vulnerability has been resolved: l2tp: use list_del_rcu in l2tp_session_unhash An unprivileged local user can pin a host CPU indefinitely in l2tp_session_get_by_ifname() by issuing L2TP_CMD_SESSION_GET on L2TP_ATTR_IFNAME concurrently with L2TP_CMD_SESSION_CREATE and L2TP_CMD_SESSION_DELETE on the same tunnel. All three commands take GENL_UNS_ADMIN_PERM, so CAP_NET_ADMIN in the netns user namespace suffices; on any host that has l2tp_core loaded the trigger is reachable from a standard `unshare -Urn` sandbox. l2tp_session_unhash() removes a session from tunnel->session_list with list_del_init(), but that list is walked by l2tp_session_get_by_ifname() with list_for_each_entry_rcu() under rcu_read_lock_bh(). list_del_init() leaves the deleted entry's next/prev self-pointing; a reader that has loaded the entry and then advances pos->list.next reads &session->list, container_of()s back to the same session, and list_for_each_entry_rcu() never reaches the list head. The CPU stays in strcmp() inside the walker, with BH and preemption disabled, so RCU grace periods on the host stall behind it and the wedged thread cannot be killed (SIGKILL is delivered on syscall return). Use list_del_rcu() to match the existing list_add_rcu() in l2tp_session_register(); the deleted session remains visible to in-flight walkers with consistent next/prev pointers until kfree_rcu() in l2tp_session_free() releases it. tunnel->session_list has exactly one list_del_init() call site; the list_del_init (&session->clist) at l2tp_core.c:533 operates on the per-collision list, which is not walked under RCU. list_empty(&session->list) is not used anywhere in net/l2tp/ after the unhash point, so dropping the post-delete self-init is safe; the fix has no userspace-visible behavior change.
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
Optional official sources

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

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2026-45804

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

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 13 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: l2tp: use list_del_rcu in l2tp_session_unhash An unprivileged local user can pin a host CPU indefinitely in l2tp_session_get_by_ifname() by issuing L2TP_CMD_SESSION_GET on L2TP_ATTR_IFNAME concurrently with L2TP_CMD_SESSION_CREATE and L2TP_CMD_SESSION_DELETE on the same tunnel. All three commands take GENL_UNS_ADMIN_PERM, so CAP_NET_ADMIN in the netns user namespace suffices; on any host that has l2tp_core loaded the trigger is reachable from a standard `unshare -Urn` sandbox. l2tp_session_unhash() removes a session from tunnel->session_list with list_del_init(), but that list is walked by l2tp_session_get_by_ifname() with list_for_each_entry_rcu() under rcu_read_lock_bh(). list_del_init() leaves the deleted entry's next/prev self-pointing; a reader that has loaded the entry and then advances pos->list.next reads &session->list, container_of()s back to the same session, and list_for_each_entry_rcu() never reaches the list head. The CPU stays in strcmp() inside the walker, with BH and preemption disabled, so RCU grace periods on the host stall behind it and the wedged thread cannot be killed (SIGKILL is delivered on syscall return). Use list_del_rcu() to match the existing list_add_rcu() in l2tp_session_register(); the deleted session remains visible to in-flight walkers with consistent next/prev pointers until kfree_rcu() in l2tp_session_free() releases it. tunnel->session_list has exactly one list_del_init() call site; the list_del_init (&session->clist) at l2tp_core.c:533 operates on the per-collision list, which is not walked under RCU. list_empty(&session->list) is not used anywhere in net/l2tp/ after the unhash point, so dropping the post-delete self-init is safe; the fix has no userspace-visible behavior change.

What

In the Linux kernel, the following vulnerability has been resolved: l2tp: use list_del_rcu in l2tp_session_unhash An unprivileged local user can pin a host CPU indefinitely in l2tp_session_get_by_ifname() by issuing L2TP_CMD_SESSION_GET on L2TP_ATTR_IFNAME concurrently with L2TP_CMD_SESSION_CREATE and L2TP_CMD_SESSION_DELETE on the same tunnel. All three commands take GENL_UNS_ADMIN_PERM, so CAP_NET_ADMIN in the netns user namespace suffices; on any host that has l2tp_core loaded the trigger is reachable from a standard `unshare -Urn` sandbox. l2tp_session_unhash() removes a session from tunnel->session_list with list_del_init(), but that list is walked by l2tp_session_get_by_ifname() with list_for_each_entry_rcu() under rcu_read_lock_bh(). list_del_init() leaves the deleted entry's next/prev self-pointing; a reader that has loaded the entry and then advances pos->list.next reads &session->list, container_of()s back to the same session, and list_for_each_entry_rcu() never reaches the list head. The CPU stays in strcmp() inside the walker, with BH and preemption disabled, so RCU grace periods on the host stall behind it and the wedged thread cannot be killed (SIGKILL is delivered on syscall return). Use list_del_rcu() to match the existing list_add_rcu() in l2tp_session_register(); the deleted session remains visible to in-flight walkers with consistent next/prev pointers until kfree_rcu() in l2tp_session_free() releases it. tunnel->session_list has exactly one list_del_init() call site; the list_del_init (&session->clist) at l2tp_core.c:533 operates on the per-collision list, which is not walked under RCU. list_empty(&session->list) is not used anywhere in net/l2tp/ after the unhash point, so dropping the post-delete self-init is safe; the fix has no userspace-visible behavior change.

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 local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

In the Linux kernel, the following vulnerability has been resolved: l2tp: use list_del_rcu in l2tp_session_unhash An unprivileged local user can pin a host CPU indefinitely in l2tp_session_get_by_ifname() by issuing L2TP_CMD_SESSION_GET on L2TP_ATTR_IFNAME concurrently with L2TP_CMD_SESSION_CREATE and L2TP_CMD_SESSION_DELETE on the same tunnel. All three commands take GENL_UNS_ADMIN_PERM, so CAP_NET_ADMIN in the netns user namespace suffices; on any host that has l2tp_core loaded the trigger is reachable from a standard `unshare -Urn` sandbox. l2tp_session_unhash() removes a session from tunnel->session_list with list_del_init(), but that list is walked by l2tp_session_get_by_ifname() with list_for_each_entry_rcu() under rcu_read_lock_bh(). list_del_init() leaves the deleted entry's next/prev self-pointing; a reader that has loaded the entry and then advances pos->list.next reads &session->list, container_of()s back to the same session, and list_for_each_entry_rcu() never reaches the list head. The CPU stays in strcmp() inside the walker, with BH and preemption disabled, so RCU grace periods on the host stall behind it and the wedged thread cannot be killed (SIGKILL is delivered on syscall return). Use list_del_rcu() to match the existing list_add_rcu() in l2tp_session_register(); the deleted session remains visible to in-flight walkers with consistent next/prev pointers until kfree_rcu() in l2tp_session_free() releases it. tunnel->session_list has exactly one list_del_init() call site; the list_del_init (&session->clist) at l2tp_core.c:533 operates on the per-collision list, which is not walked under RCU. list_empty(&session->list) is not used anywhere in net/l2tp/ after the unhash point, so dropping the post-delete self-init is safe; the fix has no userspace-visible behavior change.

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 local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

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

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

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

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

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

Likely attack path
local access → vulnerable operation → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Local
Privileges required
Low: a basic authenticated account is required
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration.
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:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

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

AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRLowPrivileges required: The attacker needs basic user-level privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CNoneConfidentiality impact: No direct loss is represented by this metric.INoneIntegrity impact: No direct loss is represented by this metric.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.
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-64110 Référence CVE CVE-2026-64111 https://www.cve.org/CVERecord?id=CVE-2026-64111 Référence CVE CVE-2026-64112 https://www.cve.org/CVERecord?id=CVE-2026-64112 Référence CVE CVE-2026-64113 https://www.cve.org/CVERecord?id=CVE-2026-64113 Référence CVE CVE-2026-64114 https://www.cve.org/CVERecord?id=CVE-2026-64114 Référence CVE CVE-2026-64115 https://www.cve.org/CVERecord?id=CVE-2026-64115 Référence CVE CVE-2026-64116 https://www.cve.org/CVERecord?id=CVE-2026-64116 Référence CVE CVE-2026-64117 https://www.cve.org/CVERecord?id=CVE-2026-64117 Référence CVE CVE-2026-64118 https://www.cve.org/CVERecord?id=CVE-2026-64118 Référence CVE CVE-2026-64119 https://www.cve.org/CVERecord?id=CVE-2026-64119 Référence CVE CVE-2026-64120 https://www.cve.org/CVERecord?id=CVE-2026-64120 Référence CVE CVE-2026-64121 https://www.cve.org/CVERecord?id=CVE-2026-64121 Référence CVE CVE-2026-64122 https://www.cve.org/CVERecord?id=CVE-2026-64122 Référence CVE CVE-2026-64123 https://www.cve.org/CVERecord?id=CVE-2026-64123 Référence CVE CVE-2026-64124 https://www.cve.org/CVERecord?id=CVE-2026-64124 Référence CVE CVE-2026-64125 https://www.cve.org/CVERecord?id=CVE-2026-64125 Référence CVE CVE-2026-64126 https://www.cve.org/CVERecord?id=CVE-2026-64126 Référence CVE CVE-2026-64127 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-64104 Référence CVE CVE-2026-64105 https://www.cve.org/CVERecord?id=CVE-2026-64105 Référence CVE CVE-2026-64109 https://www.cve.org/CVERecord?id=CVE-2026-64109 Référence CVE CVE-2026-64111 https://www.cve.org/CVERecord?id=CVE-2026-64111 Référence CVE CVE-2026-64112 https://www.cve.org/CVERecord?id=CVE-2026-64112 Référence CVE CVE-2026-64113 https://www.cve.org/CVERecord?id=CVE-2026-64113 Référence CVE CVE-2026-64114 https://www.cve.org/CVERecord?id=CVE-2026-64114 Référence CVE CVE-2026-64115 https://www.cve.org/CVERecord?id=CVE-2026-64115 Référence CVE CVE-2026-64118 https://www.cve.org/CVERecord?id=CVE-2026-64118 Référence CVE CVE-2026-64119 https://www.cve.org/CVERecord?id=CVE-2026-64119 Référence CVE CVE-2026-64121 https://www.cve.org/CVERecord?id=CVE-2026-64121 Référence CVE CVE-2026-64125 https://www.cve.org/CVERecord?id=CVE-2026-64125 Référence CVE CVE-2026-64126 https://www.cve.org/CVERecord?id=CVE-2026-64126 Référence CVE CVE-2026-64127 https://www.cve.org/CVERecord?id=CVE-2026-64127 Référence CVE CVE-2026-64128 https://www.cve.org/CVERecord?id=CVE-2026-64128 Référence CVE CVE-2026-64131 https://www.cve.org/CVERecord?id=CVE-2026-64131 Référence CVE CVE-2026-64133 https://www.cve.org/CVERecord?id=CVE-2026-64133 Référence CVE CVE-2026-64134 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-64110 Référence CVE CVE-2026-64111 https://www.cve.org/CVERecord?id=CVE-2026-64111 Référence CVE CVE-2026-64112 https://www.cve.org/CVERecord?id=CVE-2026-64112 Référence CVE CVE-2026-64113 https://www.cve.org/CVERecord?id=CVE-2026-64113 Référence CVE CVE-2026-64114 https://www.cve.org/CVERecord?id=CVE-2026-64114 Référence CVE CVE-2026-64115 https://www.cve.org/CVERecord?id=CVE-2026-64115 Référence CVE CVE-2026-64116 https://www.cve.org/CVERecord?id=CVE-2026-64116 Référence CVE CVE-2026-64117 https://www.cve.org/CVERecord?id=CVE-2026-64117 Référence CVE CVE-2026-64118 https://www.cve.org/CVERecord?id=CVE-2026-64118 Référence CVE CVE-2026-64119 https://www.cve.org/CVERecord?id=CVE-2026-64119 Référence CVE CVE-2026-64120 https://www.cve.org/CVERecord?id=CVE-2026-64120 Référence CVE CVE-2026-64121 https://www.cve.org/CVERecord?id=CVE-2026-64121 Référence CVE CVE-2026-64122 https://www.cve.org/CVERecord?id=CVE-2026-64122 Référence CVE CVE-2026-64123 https://www.cve.org/CVERecord?id=CVE-2026-64123 Référence CVE CVE-2026-64124 https://www.cve.org/CVERecord?id=CVE-2026-64124 Référence CVE CVE-2026-64125 https://www.cve.org/CVERecord?id=CVE-2026-64125 Référence CVE CVE-2026-64126 https://www.cve.org/CVERecord?id=CVE-2026-64126 Référence CVE CVE-2026-64127 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-64110 Référence CVE CVE-2026-64111 https://www.cve.org/CVERecord?id=CVE-2026-64111 Référence CVE CVE-2026-64112 https://www.cve.org/CVERecord?id=CVE-2026-64112 Référence CVE CVE-2026-64113 https://www.cve.org/CVERecord?id=CVE-2026-64113 Référence CVE CVE-2026-64114 https://www.cve.org/CVERecord?id=CVE-2026-64114 Référence CVE CVE-2026-64115 https://www.cve.org/CVERecord?id=CVE-2026-64115 Référence CVE CVE-2026-64116 https://www.cve.org/CVERecord?id=CVE-2026-64116 Référence CVE CVE-2026-64117 https://www.cve.org/CVERecord?id=CVE-2026-64117 Référence CVE CVE-2026-64118 https://www.cve.org/CVERecord?id=CVE-2026-64118 Référence CVE CVE-2026-64119 https://www.cve.org/CVERecord?id=CVE-2026-64119 Référence CVE CVE-2026-64120 https://www.cve.org/CVERecord?id=CVE-2026-64120 Référence CVE CVE-2026-64121 https://www.cve.org/CVERecord?id=CVE-2026-64121 Référence CVE CVE-2026-64122 https://www.cve.org/CVERecord?id=CVE-2026-64122 Référence CVE CVE-2026-64123 https://www.cve.org/CVERecord?id=CVE-2026-64123 Référence CVE CVE-2026-64124 https://www.cve.org/CVERecord?id=CVE-2026-64124 Référence CVE CVE-2026-64125 https://www.cve.org/CVERecord?id=CVE-2026-64125 Référence CVE CVE-2026-64126 https://www.cve.org/CVERecord?id=CVE-2026-64126 Référence CVE CVE-2026-64127 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-64110 Référence CVE CVE-2026-64111 https://www.cve.org/CVERecord?id=CVE-2026-64111 Référence CVE CVE-2026-64112 https://www.cve.org/CVERecord?id=CVE-2026-64112 Référence CVE CVE-2026-64113 https://www.cve.org/CVERecord?id=CVE-2026-64113 Référence CVE CVE-2026-64114 https://www.cve.org/CVERecord?id=CVE-2026-64114 Référence CVE CVE-2026-64115 https://www.cve.org/CVERecord?id=CVE-2026-64115 Référence CVE CVE-2026-64116 https://www.cve.org/CVERecord?id=CVE-2026-64116 Référence CVE CVE-2026-64117 https://www.cve.org/CVERecord?id=CVE-2026-64117 Référence CVE CVE-2026-64118 https://www.cve.org/CVERecord?id=CVE-2026-64118 Référence CVE CVE-2026-64119 https://www.cve.org/CVERecord?id=CVE-2026-64119 Référence CVE CVE-2026-64120 https://www.cve.org/CVERecord?id=CVE-2026-64120 Référence CVE CVE-2026-64121 https://www.cve.org/CVERecord?id=CVE-2026-64121 Référence CVE CVE-2026-64122 https://www.cve.org/CVERecord?id=CVE-2026-64122 Référence CVE CVE-2026-64123 https://www.cve.org/CVERecord?id=CVE-2026-64123 Référence CVE CVE-2026-64124 https://www.cve.org/CVERecord?id=CVE-2026-64124 Référence CVE CVE-2026-64125 https://www.cve.org/CVERecord?id=CVE-2026-64125 Référence CVE CVE-2026-64126 https://www.cve.org/CVERecord?id=CVE-2026-64126 Référence CVE CVE-2026-64127 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-64110 Référence CVE CVE-2026-64111 https://www.cve.org/CVERecord?id=CVE-2026-64111 Référence CVE CVE-2026-64112 https://www.cve.org/CVERecord?id=CVE-2026-64112 Référence CVE CVE-2026-64113 https://www.cve.org/CVERecord?id=CVE-2026-64113 Référence CVE CVE-2026-64114 https://www.cve.org/CVERecord?id=CVE-2026-64114 Référence CVE CVE-2026-64115 https://www.cve.org/CVERecord?id=CVE-2026-64115 Référence CVE CVE-2026-64116 https://www.cve.org/CVERecord?id=CVE-2026-64116 Référence CVE CVE-2026-64117 https://www.cve.org/CVERecord?id=CVE-2026-64117 Référence CVE CVE-2026-64118 https://www.cve.org/CVERecord?id=CVE-2026-64118 Référence CVE CVE-2026-64119 https://www.cve.org/CVERecord?id=CVE-2026-64119 Référence CVE CVE-2026-64120 https://www.cve.org/CVERecord?id=CVE-2026-64120 Référence CVE CVE-2026-64121 https://www.cve.org/CVERecord?id=CVE-2026-64121 Référence CVE CVE-2026-64122 https://www.cve.org/CVERecord?id=CVE-2026-64122 Référence CVE CVE-2026-64123 https://www.cve.org/CVERecord?id=CVE-2026-64123 Référence CVE CVE-2026-64124 https://www.cve.org/CVERecord?id=CVE-2026-64124 Référence CVE CVE-2026-64125 https://www.cve.org/CVERecord?id=CVE-2026-64125 Référence CVE CVE-2026-64126 https://www.cve.org/CVERecord?id=CVE-2026-64126 Référence CVE CVE-2026-64127 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-64110 Référence CVE CVE-2026-64111 https://www.cve.org/CVERecord?id=CVE-2026-64111 Référence CVE CVE-2026-64112 https://www.cve.org/CVERecord?id=CVE-2026-64112 Référence CVE CVE-2026-64113 https://www.cve.org/CVERecord?id=CVE-2026-64113 Référence CVE CVE-2026-64114 https://www.cve.org/CVERecord?id=CVE-2026-64114 Référence CVE CVE-2026-64115 https://www.cve.org/CVERecord?id=CVE-2026-64115 Référence CVE CVE-2026-64116 https://www.cve.org/CVERecord?id=CVE-2026-64116 Référence CVE CVE-2026-64117 https://www.cve.org/CVERecord?id=CVE-2026-64117 Référence CVE CVE-2026-64118 https://www.cve.org/CVERecord?id=CVE-2026-64118 Référence CVE CVE-2026-64119 https://www.cve.org/CVERecord?id=CVE-2026-64119 Référence CVE CVE-2026-64120 https://www.cve.org/CVERecord?id=CVE-2026-64120 Référence CVE CVE-2026-64121 https://www.cve.org/CVERecord?id=CVE-2026-64121 Référence CVE CVE-2026-64122 https://www.cve.org/CVERecord?id=CVE-2026-64122 Référence CVE CVE-2026-64123 https://www.cve.org/CVERecord?id=CVE-2026-64123 Référence CVE CVE-2026-64124 https://www.cve.org/CVERecord?id=CVE-2026-64124 Référence CVE CVE-2026-64125 https://www.cve.org/CVERecord?id=CVE-2026-64125 Référence CVE CVE-2026-64126 https://www.cve.org/CVERecord?id=CVE-2026-64126 Référence CVE CVE-2026-64127 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2026-028288LinuxのLinux Kernelにおける不特定の脆弱性

Linuxカーネルにおいて、以下の脆弱性が修正されました。l2tp: l2tp_session_unhashにおけるlist_del_rcuの使用に関して、権限を持たないローカルユーザが、同じトンネル上でL2TP_CMD_SESSION_GETをL2TP_ATTR_IFNAME付きで同時に発行するとともに、L2TP_CMD_SESSION_CREATEおよびL2TP_CMD_SESSION_DELETEを発行することで、l2tp_session_get_by_ifname()内でホストCPUを無期限に固定できる問題です。これら3つのコマンドはいずれもGENL_UNS_ADMIN_PERM権限を必要とするため、netnsユーザ名前空間内のCAP_NET_ADMIN権限があれば十分です。l2tp_coreがロードされている任意のホストでは、標準的な`unshare -Urn`サンドボックスからこのトリガーを実行可能です。l2tp_session_unhash()はlist_del_init()でセッションをtunnel-＞session_listから削除しますが、このリストはrcu_read_lock_bh()の下でl2tp_session_get_by_ifname()によってlist_for_each_entry_rcu()で走査されます。list_del_init()は削除されたエントリのnextおよびprevポインタを自己参照状態にします。エントリを読み込んだリーダがpos-＞list.nextを次に進めた場合、&session-＞listを読み取り、container_of()によって同じセッションに戻ってしまい、list_for_each_entry_rcu()はリストの先頭に達しません。walker内のstrcmp()でCPUが停止し、BHおよびプリエンプションが無効になるため、ホスト上のRCUグレース期間がそこにて停止し、停止したスレッドはkillできません（シグナルSIGKILLはシステムコールの戻り時に配信されます）。l2tp_session_register()の既存のlist_add_rcu()に合わせてlist_del_rcu()の使用に変更しました。削除されたセッションはl2tp_session_free()内のkfree_rcu()が解放するまで、一貫性のあるnextおよびprevポインタでフライト中のwalkerに対して可視のまま残ります。tunnel-＞session_listにはlist_del_init()の呼び出しは1箇所だけであり、l2tp_core.cの533行目にあるlist_del_init(&session-＞clist)はRCU下で走査されないper-collisionリストに対して行われています。unhashポイント以降ではnet/l2tp/内においてlist_empty(&session-＞list)はどこでも使用されていないため、削除後の自己初期化の破棄は安全です。この修正によりユーザ空間に見える振る舞いに変更はありません。

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.12, 6.12.92 ≤ 6.12.*, 6.18.34 ≤ 6.18.*, 7.0.11 ≤ 7.0.*, 7.1 ≤ *
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
Workaround
No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04

Evidence and provenance

Published 19 Jul 2026 · Last source change 19 Jul 2026, 15:40 UTC · CWE not yet assigned

CVE recordCVE.org · 5.2
CVSS sourceNIST NVD
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-45804
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceUnavailable
NVD statusNVD enriched

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 from remediation: suse.com/CVE-2026-64119 to remediation: suse.com/CVE-2026-64119.
    Before
    remediation: suse.com/CVE-2026-64119
    After
    remediation: suse.com/CVE-2026-64119
    SUSE Product Security Team ↗
  2. Affected versionsThe structured affected or fixed version information changed.
    Before
    kernel-default as component of SUSE Linux Enterprise High Availability Extension 16.0; kernel-source as component of SUSE Linux Enterprise High Availability Extension 16.0; kernel-default as component of SUSE Linux Enterprise High Availability Extension 16.1; kernel-source as component of SUSE Linux Enterprise High Availability Extension 16.1; kernel-default as component of SUSE Linux Enterprise Server 16.0; kernel-devel as component of SUSE Linux Enterprise Server 16.0; kernel-macros as component of SUSE Linux Enterprise Server 16.0; kernel-source as component of SUSE Linux Enterprise Server 16.0; kernel-source-vanilla as component of SUSE Linux Enterprise Server 16.0; kernel-default as component of SUSE Linux Enterprise Server 16.1; kernel-devel as component of SUSE Linux Enterprise Server 16.1; kernel-macros as component of SUSE Linux Enterprise Server 16.1; kernel-source as component of SUSE Linux Enterprise Server 16.1; kernel-source-vanilla as component of SUSE Linux Enterprise Server 16.1; kernel-default as component of SUSE Linux Enterprise Server for SAP applications 16.0; kernel-devel as component of SUSE Linux Enterprise Server for SAP applications 16.0; kernel-macros as component of SUSE Linux Enterprise Server for SAP applications 16.0; kernel-source as component of SUSE Linux Enterprise Server for SAP applications 16.0; kernel-source-vanilla as component of SUSE Linux Enterprise Server for SAP applications 16.0; kernel-default as component of SUSE Linux Enterprise Server for SAP applications 16.1; kernel-devel as component of SUSE Linux Enterprise Server for SAP applications 16.1; kernel-macros as component of SUSE Linux Enterprise Server for SAP applications 16.1; kernel-source as component of SUSE Linux Enterprise Server for SAP applications 16.1; kernel-source-vanilla as component of SUSE Linux Enterprise Server for SAP applications 16.1; kernel-default as component of SUSE Linux Micro 6.2; kernel-devel as component of SUSE Linux Micro 6.2; kernel-macros as component of SUSE Linux Micro 6.2; kernel-source as component of SUSE Linux Micro 6.2; kernel-source as component of openSUSE Leap 16.0 · Fixed: kernel-64kb-6.12.0-160000.38.1 as component of SUSE Linux Enterprise Server 16.0; kernel-64kb-devel-6.12.0-160000.38.1 as component of SUSE Linux Enterprise Server 16.0; kernel-64kb-extra-6.12.0-160000.38.1 as component of SUSE Linux Enterprise Server 16.0; kernel-azure-6.12.0-160000.38.1 as component of SUSE Linux Enterprise Server 16.0; kernel-azure-devel-6.12.0-160000.38.1 as component of SUSE Linux Enterprise Server 16.0; kernel-azure-extra-6.12.0-160000.38.1 as component of SUSE Linux Enterprise Server 16.0; kernel-azure-vdso-6.12.0-160000.38.1 as component of SUSE Linux Enterprise Server 16.0; kernel-default-6.12.0-160000.38.1 as component of SUSE Linux Enterprise Server 16.0; kernel-default-base-6.12.0-160000.38.1.160000.2.24 as component of SUSE Linux Enterprise Server 16.0; kernel-default-devel-6.12.0-160000.38.1 as component of SUSE Linux Enterprise Server 16.0; kernel-default-extra-6.12.0-160000.38.1 as component of SUSE Linux Enterprise Server 16.0; kernel-default-livepatch-6.12.0-160000.38.1 as component of SUSE Linux Enterprise Server 16.0; kernel-default-vdso-6.12.0-160000.38.1 as component of SUSE Linux Enterprise Server 16.0; kernel-devel-6.12.0-160000.38.1 as component of SUSE Linux Enterprise Server 16.0; kernel-docs-6.12.0-160000.38.1 as component of SUSE Linux Enterprise Server 16.0; kernel-docs-html-6.12.0-160000.38.1 as component of SUSE Linux Enterprise Server 16.0; kernel-kvmsmall-6.12.0-160000.38.1 as component of SUSE Linux Enterprise Server 16.0; kernel-kvmsmall-devel-6.12.0-160000.38.1 as component of SUSE Linux Enterprise Server 16.0; kernel-kvmsmall-vdso-6.12.0-160000.38.1 as component of SUSE Linux Enterprise Server 16.0; kernel-macros-6.12.0-160000.38.1 as component of SUSE Linux Enterprise Server 16.0; kernel-obs-qa-6.12.0-160000.38.1 as component of SUSE Linux Enterprise Server 16.0; kernel-source-6.12.0-160000.38.1 as component of SUSE Linux Enterprise Server 16.0; kernel-source-vanilla-6.12.0-160000.38.1 as component of SUSE Linux Enterprise Server 16.0; kernel-syms-6.12.0-160000.38.1 as component of SUSE Linux Enterprise Server 16.0; kernel-zfcpdump-6.12.0-160000.38.1 as component of SUSE Linux Enterprise Server 16.0; cluster-md-kmp-default-6.12.0-160000.38.1 as component of SUSE Linux Enterprise Server for SAP applications 16.0; dlm-kmp-default-6.12.0-160000.38.1 as component of SUSE Linux Enterprise Server for SAP applications 16.0; gfs2-kmp-default-6.12.0-160000.38.1 as component of SUSE Linux Enterprise Server for SAP applications 16.0; kernel-64kb-6.12.0-160000.38.1 as component of SUSE Linux Enterprise Server for SAP applications 16.0; kernel-64kb-devel-6.12.0-160000.38.1 as component of SUSE Linux Enterprise Server for SAP applications 16.0; and 38 more
    After
    kernel-default as component of SUSE Linux Enterprise High Availability Extension 16.0; kernel-source as component of SUSE Linux Enterprise High Availability Extension 16.0; kernel-default as component of SUSE Linux Enterprise High Availability Extension 16.1; kernel-source as component of SUSE Linux Enterprise High Availability Extension 16.1; kernel-default as component of SUSE Linux Enterprise Server 16.0; kernel-devel as component of SUSE Linux Enterprise Server 16.0; kernel-macros as component of SUSE Linux Enterprise Server 16.0; kernel-source as component of SUSE Linux Enterprise Server 16.0; kernel-source-vanilla as component of SUSE Linux Enterprise Server 16.0; kernel-default as component of SUSE Linux Enterprise Server 16.1; kernel-devel as component of SUSE Linux Enterprise Server 16.1; kernel-macros as component of SUSE Linux Enterprise Server 16.1; kernel-source as component of SUSE Linux Enterprise Server 16.1; kernel-source-vanilla as component of SUSE Linux Enterprise Server 16.1; kernel-default as component of SUSE Linux Enterprise Server for SAP applications 16.0; kernel-devel as component of SUSE Linux Enterprise Server for SAP applications 16.0; kernel-macros as component of SUSE Linux Enterprise Server for SAP applications 16.0; kernel-source as component of SUSE Linux Enterprise Server for SAP applications 16.0; kernel-source-vanilla as component of SUSE Linux Enterprise Server for SAP applications 16.0; kernel-default as component of SUSE Linux Enterprise Server for SAP applications 16.1; kernel-devel as component of SUSE Linux Enterprise Server for SAP applications 16.1; kernel-macros as component of SUSE Linux Enterprise Server for SAP applications 16.1; kernel-source as component of SUSE Linux Enterprise Server for SAP applications 16.1; kernel-source-vanilla as component of SUSE Linux Enterprise Server for SAP applications 16.1; kernel-default as component of SUSE Linux Micro 6.2; kernel-devel as component of SUSE Linux Micro 6.2; kernel-macros as component of SUSE Linux Micro 6.2; kernel-source as component of SUSE Linux Micro 6.2; SUSE Linux Micro Extras 6.2:kernel-obs-build; SUSE Linux Micro Extras 6.2:kernel-syms; and 1 more
    SUSE Product Security Team ↗
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-45804↗Vendor CSAF · SUSE Product Security Team↗CVE authority or vendor reference↗Patch or update reference↗Patch or update reference↗Patch or update reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2026-64119 · cve.blacktree.nl