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

l2tp: use refcount_inc_not_zero in l2tp_session_get_by_ifname

Linux · Linux

7.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 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 severityHighOperational priority:Medium, lowered one band.downgradedsince 5 Aug 2026

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • Exploitation requires an existing local or physical foothold with privileges.
  • EPSS is 0.16% 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: As exposure requiresRemediation target: Within 365 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 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 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 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 7 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 7 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 7 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 7 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 7 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 7 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 7 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 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-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 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
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-63918 · CSAF 2.0 · revision 6 · interimSUSE Product Security TeamCVE-2026-63918
372 known affected

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

  • kernel-default as component of SUSE Linux Enterprise Desktop 15 SP7
  • kernel-default-devel as component of SUSE Linux Enterprise Desktop 15 SP7
  • kernel-default-extra as component of SUSE Linux Enterprise Desktop 15 SP7
  • kernel-devel as component of SUSE Linux Enterprise Desktop 15 SP7
  • kernel-macros as component of SUSE Linux Enterprise Desktop 15 SP7
  • kernel-source as component of SUSE Linux Enterprise Desktop 15 SP7
  • cluster-md-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • dlm-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • gfs2-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • kernel-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • kernel-source as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • ocfs2-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
Summary
In the Linux kernel, the following vulnerability has been resolved: l2tp: use refcount_inc_not_zero in l2tp_session_get_by_ifname A reader in l2tp_session_get_by_ifname() can return a pointer to a session whose refcount has reached zero. The getter takes its reference with plain refcount_inc(), but every other session getter in the same file (l2tp_v2_session_get, l2tp_v3_session_get, and the corresponding _get_next variants) uses refcount_inc_not_zero() because the IDR/RCU lookup can race with refcount_dec_and_test() -> l2tp_session_free() -> kfree_rcu(). The ifname getter is the only outlier; the inconsistency was raised on-list after 979c017803c4 ("l2tp: use list_del_rcu in l2tp_session_unhash"). A reader inside rcu_read_lock_bh() that matches session->ifname can be preempted between the strcmp() and the refcount_inc(). If the last reference drops on another CPU in that window, the reader's refcount_inc() runs on a counter that has reached zero. refcount_t catches the addition-on-zero, prints "refcount_t: addition on 0; use-after-free", saturates the counter, and returns the saturated pointer to the caller. Session memory is held live by the in-flight RCU read section, but the kfree_rcu() callback queued from l2tp_session_free() will free it once the grace period closes; a caller that dereferences the returned session past that point hits a slab-use-after-free. On PREEMPT_RT local_bh_disable() is a per-CPU sleeping lock and the preemption window is real; on stock PREEMPT kernels local_bh_disable() is a preempt_count increment that closes the cross-CPU race in practice (see below). Use refcount_inc_not_zero() and continue the list walk on failure, matching the other session getters in the file. The ifname getter is the only session getter in net/l2tp/ that still uses the bare refcount_inc() pattern; this change restores file-internal consistency. The success path is unchanged.
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-45691

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 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 refcount_inc_not_zero in l2tp_session_get_by_ifname A reader in l2tp_session_get_by_ifname() can return a pointer to a session whose refcount has reached zero. The getter takes its reference with plain refcount_inc(), but every other session getter in the same file (l2tp_v2_session_get, l2tp_v3_session_get, and the corresponding _get_next variants) uses refcount_inc_not_zero() because the IDR/RCU lookup can race with refcount_dec_and_test() -> l2tp_session_free() -> kfree_rcu(). The ifname getter is the only outlier; the inconsistency was raised on-list after 979c017803c4 ("l2tp: use list_del_rcu in l2tp_session_unhash"). A reader inside rcu_read_lock_bh() that matches session->ifname can be preempted between the strcmp() and the refcount_inc(). If the last reference drops on another CPU in that window, the reader's refcount_inc() runs on a counter that has reached zero. refcount_t catches the addition-on-zero, prints "refcount_t: addition on 0; use-after-free", saturates the counter, and returns the saturated pointer to the caller. Session memory is held live by the in-flight RCU read section, but the kfree_rcu() callback queued from l2tp_session_free() will free it once the grace period closes; a caller that dereferences the returned session past that point hits a slab-use-after-free. On PREEMPT_RT local_bh_disable() is a per-CPU sleeping lock and the preemption window is real; on stock PREEMPT kernels local_bh_disable() is a preempt_count increment that closes the cross-CPU race in practice (see below). Use refcount_inc_not_zero() and continue the list walk on failure, matching the other session getters in the file. The ifname getter is the only session getter in net/l2tp/ that still uses the bare refcount_inc() pattern; this change restores file-internal consistency. The success path is unchanged.

What

In the Linux kernel, the following vulnerability has been resolved: l2tp: use refcount_inc_not_zero in l2tp_session_get_by_ifname A reader in l2tp_session_get_by_ifname() can return a pointer to a session whose refcount has reached zero. The getter takes its reference with plain refcount_inc(), but every other session getter in the same file (l2tp_v2_session_get, l2tp_v3_session_get, and the corresponding _get_next variants) uses refcount_inc_not_zero() because the IDR/RCU lookup can race with refcount_dec_and_test() -> l2tp_session_free() -> kfree_rcu(). The ifname getter is the only outlier; the inconsistency was raised on-list after 979c017803c4 ("l2tp: use list_del_rcu in l2tp_session_unhash"). A reader inside rcu_read_lock_bh() that matches session->ifname can be preempted between the strcmp() and the refcount_inc(). If the last reference drops on another CPU in that window, the reader's refcount_inc() runs on a counter that has reached zero. refcount_t catches the addition-on-zero, prints "refcount_t: addition on 0; use-after-free", saturates the counter, and returns the saturated pointer to the caller. Session memory is held live by the in-flight RCU read section, but the kfree_rcu() callback queued from l2tp_session_free() will free it once the grace period closes; a caller that dereferences the returned session past that point hits a slab-use-after-free. On PREEMPT_RT local_bh_disable() is a per-CPU sleeping lock and the preemption window is real; on stock PREEMPT kernels local_bh_disable() is a preempt_count increment that closes the cross-CPU race in practice (see below). Use refcount_inc_not_zero() and continue the list walk on failure, matching the other session getters in the file. The ifname getter is the only session getter in net/l2tp/ that still uses the bare refcount_inc() pattern; this change restores file-internal consistency. The success path is unchanged.

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 refcount_inc_not_zero in l2tp_session_get_by_ifname A reader in l2tp_session_get_by_ifname() can return a pointer to a session whose refcount has reached zero. The getter takes its reference with plain refcount_inc(), but every other session getter in the same file (l2tp_v2_session_get, l2tp_v3_session_get, and the corresponding _get_next variants) uses refcount_inc_not_zero() because the IDR/RCU lookup can race with refcount_dec_and_test() -> l2tp_session_free() -> kfree_rcu(). The ifname getter is the only outlier; the inconsistency was raised on-list after 979c017803c4 ("l2tp: use list_del_rcu in l2tp_session_unhash"). A reader inside rcu_read_lock_bh() that matches session->ifname can be preempted between the strcmp() and the refcount_inc(). If the last reference drops on another CPU in that window, the reader's refcount_inc() runs on a counter that has reached zero. refcount_t catches the addition-on-zero, prints "refcount_t: addition on 0; use-after-free", saturates the counter, and returns the saturated pointer to the caller. Session memory is held live by the in-flight RCU read section, but the kfree_rcu() callback queued from l2tp_session_free() will free it once the grace period closes; a caller that dereferences the returned session past that point hits a slab-use-after-free. On PREEMPT_RT local_bh_disable() is a per-CPU sleeping lock and the preemption window is real; on stock PREEMPT kernels local_bh_disable() is a preempt_count increment that closes the cross-CPU race in practice (see below). Use refcount_inc_not_zero() and continue the list walk on failure, matching the other session getters in the file. The ifname getter is the only session getter in net/l2tp/ that still uses the bare refcount_inc() pattern; this change restores file-internal consistency. The success path is unchanged.

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:H/I:H/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.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
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-63909 Référence CVE CVE-2026-63910 https://www.cve.org/CVERecord?id=CVE-2026-63910 Référence CVE CVE-2026-63911 https://www.cve.org/CVERecord?id=CVE-2026-63911 Référence CVE CVE-2026-63912 https://www.cve.org/CVERecord?id=CVE-2026-63912 Référence CVE CVE-2026-63913 https://www.cve.org/CVERecord?id=CVE-2026-63913 Référence CVE CVE-2026-63914 https://www.cve.org/CVERecord?id=CVE-2026-63914 Référence CVE CVE-2026-63915 https://www.cve.org/CVERecord?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-63918 https://www.cve.org/CVERecord?id=CVE-2026-63918 Référence CVE CVE-2026-63919 https://www.cve.org/CVERecord?id=CVE-2026-63919 Référence CVE CVE-2026-63920 https://www.cve.org/CVERecord?id=CVE-2026-63920 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-63923 https://www.cve.org/CVERecord?id=CVE-2026-63923 Référence CVE CVE-2026-63924 https://www.cve.org/CVERecord?id=CVE-2026-63924 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=

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

d?id=CVE-2026-63887 Référence CVE CVE-2026-63888 https://www.cve.org/CVERecord?id=CVE-2026-63888 Référence CVE CVE-2026-63889 https://www.cve.org/CVERecord?id=CVE-2026-63889 Référence CVE CVE-2026-63890 https://www.cve.org/CVERecord?id=CVE-2026-63890 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-63901 https://www.cve.org/CVERecord?id=CVE-2026-63901 Référence CVE CVE-2026-63906 https://www.cve.org/CVERecord?id=CVE-2026-63906 Référence CVE CVE-2026-63917 https://www.cve.org/CVERecord?id=CVE-2026-63917 Référence CVE CVE-2026-63918 https://www.cve.org/CVERecord?id=CVE-2026-63918 Référence CVE CVE-2026-63920 https://www.cve.org/CVERecord?id=CVE-2026-63920 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-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-63941 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-63909 Référence CVE CVE-2026-63910 https://www.cve.org/CVERecord?id=CVE-2026-63910 Référence CVE CVE-2026-63911 https://www.cve.org/CVERecord?id=CVE-2026-63911 Référence CVE CVE-2026-63912 https://www.cve.org/CVERecord?id=CVE-2026-63912 Référence CVE CVE-2026-63913 https://www.cve.org/CVERecord?id=CVE-2026-63913 Référence CVE CVE-2026-63914 https://www.cve.org/CVERecord?id=CVE-2026-63914 Référence CVE CVE-2026-63915 https://www.cve.org/CVERecord?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-63918 https://www.cve.org/CVERecord?id=CVE-2026-63918 Référence CVE CVE-2026-63919 https://www.cve.org/CVERecord?id=CVE-2026-63919 Référence CVE CVE-2026-63920 https://www.cve.org/CVERecord?id=CVE-2026-63920 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-63923 https://www.cve.org/CVERecord?id=CVE-2026-63923 Référence CVE CVE-2026-63924 https://www.cve.org/CVERecord?id=CVE-2026-63924 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=

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

d?id=CVE-2026-63909 Référence CVE CVE-2026-63910 https://www.cve.org/CVERecord?id=CVE-2026-63910 Référence CVE CVE-2026-63911 https://www.cve.org/CVERecord?id=CVE-2026-63911 Référence CVE CVE-2026-63912 https://www.cve.org/CVERecord?id=CVE-2026-63912 Référence CVE CVE-2026-63913 https://www.cve.org/CVERecord?id=CVE-2026-63913 Référence CVE CVE-2026-63914 https://www.cve.org/CVERecord?id=CVE-2026-63914 Référence CVE CVE-2026-63915 https://www.cve.org/CVERecord?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-63918 https://www.cve.org/CVERecord?id=CVE-2026-63918 Référence CVE CVE-2026-63919 https://www.cve.org/CVERecord?id=CVE-2026-63919 Référence CVE CVE-2026-63920 https://www.cve.org/CVERecord?id=CVE-2026-63920 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-63923 https://www.cve.org/CVERecord?id=CVE-2026-63923 Référence CVE CVE-2026-63924 https://www.cve.org/CVERecord?id=CVE-2026-63924 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=

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

d?id=CVE-2026-63909 Référence CVE CVE-2026-63910 https://www.cve.org/CVERecord?id=CVE-2026-63910 Référence CVE CVE-2026-63911 https://www.cve.org/CVERecord?id=CVE-2026-63911 Référence CVE CVE-2026-63912 https://www.cve.org/CVERecord?id=CVE-2026-63912 Référence CVE CVE-2026-63913 https://www.cve.org/CVERecord?id=CVE-2026-63913 Référence CVE CVE-2026-63914 https://www.cve.org/CVERecord?id=CVE-2026-63914 Référence CVE CVE-2026-63915 https://www.cve.org/CVERecord?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-63918 https://www.cve.org/CVERecord?id=CVE-2026-63918 Référence CVE CVE-2026-63919 https://www.cve.org/CVERecord?id=CVE-2026-63919 Référence CVE CVE-2026-63920 https://www.cve.org/CVERecord?id=CVE-2026-63920 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-63923 https://www.cve.org/CVERecord?id=CVE-2026-63923 Référence CVE CVE-2026-63924 https://www.cve.org/CVERecord?id=CVE-2026-63924 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=

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

d?id=CVE-2026-63909 Référence CVE CVE-2026-63910 https://www.cve.org/CVERecord?id=CVE-2026-63910 Référence CVE CVE-2026-63911 https://www.cve.org/CVERecord?id=CVE-2026-63911 Référence CVE CVE-2026-63912 https://www.cve.org/CVERecord?id=CVE-2026-63912 Référence CVE CVE-2026-63913 https://www.cve.org/CVERecord?id=CVE-2026-63913 Référence CVE CVE-2026-63914 https://www.cve.org/CVERecord?id=CVE-2026-63914 Référence CVE CVE-2026-63915 https://www.cve.org/CVERecord?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-63918 https://www.cve.org/CVERecord?id=CVE-2026-63918 Référence CVE CVE-2026-63919 https://www.cve.org/CVERecord?id=CVE-2026-63919 Référence CVE CVE-2026-63920 https://www.cve.org/CVERecord?id=CVE-2026-63920 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-63923 https://www.cve.org/CVERecord?id=CVE-2026-63923 Référence CVE CVE-2026-63924 https://www.cve.org/CVERecord?id=CVE-2026-63924 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=

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

d?id=CVE-2026-63909 Référence CVE CVE-2026-63910 https://www.cve.org/CVERecord?id=CVE-2026-63910 Référence CVE CVE-2026-63911 https://www.cve.org/CVERecord?id=CVE-2026-63911 Référence CVE CVE-2026-63912 https://www.cve.org/CVERecord?id=CVE-2026-63912 Référence CVE CVE-2026-63913 https://www.cve.org/CVERecord?id=CVE-2026-63913 Référence CVE CVE-2026-63914 https://www.cve.org/CVERecord?id=CVE-2026-63914 Référence CVE CVE-2026-63915 https://www.cve.org/CVERecord?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-63918 https://www.cve.org/CVERecord?id=CVE-2026-63918 Référence CVE CVE-2026-63919 https://www.cve.org/CVERecord?id=CVE-2026-63919 Référence CVE CVE-2026-63920 https://www.cve.org/CVERecord?id=CVE-2026-63920 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-63923 https://www.cve.org/CVERecord?id=CVE-2026-63923 Référence CVE CVE-2026-63924 https://www.cve.org/CVERecord?id=CVE-2026-63924 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=

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.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-45691
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 ↗

No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.

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-45691↗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-63918 · cve.blacktree.nl