BlackTreeIndependent security intelligence
← Back to the CVE catalogue
Full vulnerability report · 2026
CVE-2026-22979High confidence

net: fix memory leak in skb_segment_list for GRO packets

Linux · Linux

5.5MediumCVSS 3.1
Recommended action
Scheduled

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.

Patch available
Distribution package intelligence

Ubuntu vendor package status

Canonical’s release and source-package findings are shown separately from local repository availability.

20 package states
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.

Ubuntu releaseSource packageVendor stateFixed versionEvidence
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 record ↗Source updated 9 Sept 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 record ↗Source updated 9 Sept 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 record ↗Source updated 9 Sept 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 record ↗Source updated 9 Sept 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 record ↗Source updated 9 Sept 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 record ↗Source updated 9 Sept 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 record ↗Source updated 9 Sept 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 record ↗Source updated 9 Sept 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 record ↗Source updated 9 Sept 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 record ↗Source updated 9 Sept 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 record ↗Source updated 9 Sept 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 record ↗Source updated 9 Sept 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 record ↗Source updated 9 Sept 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 record ↗Source updated 9 Sept 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 record ↗Source updated 9 Sept 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 record ↗Source updated 9 Sept 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 record ↗Source updated 9 Sept 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 record ↗Source updated 9 Sept 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 record ↗Source updated 9 Sept 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 record ↗Source updated 9 Sept 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
SSA-019113 · CSAF 2.0 · revision 2 · interimSiemens ProductCERTSSA-019113: Vulnerabilities in the additional GNU/Linux subsystem of the SIMATIC S7-1500 CPU 1518(F)-4 PN/DP MFP V3.1.6
5 known affected

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

  • SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (6ES7518-4AX00-1AB0) >= V3.1.6
  • SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (6ES7518-4AX00-1AC0) >= V3.1.6
  • SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (6ES7518-4FX00-1AB0) >= V3.1.6
  • SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (6ES7518-4FX00-1AC0) >= V3.1.6
  • SIPLUS S7-1500 CPU 1518-4 PN/DP MFP (6AG1518-4AX00-4AC0) >= V3.1.6
Summary
In the Linux kernel, the following vulnerability has been resolved: net: fix memory leak in skb_segment_list for GRO packets When skb_segment_list() is called during packet forwarding, it handles packets that were aggregated by the GRO engine. Historically, the segmentation logic in skb_segment_list assumes that individual segments are split from a parent SKB and may need to carry their own socket memory accounting. Accordingly, the code transfers truesize from the parent to the newly created segments. Prior to commit ed4cccef64c1 ("gro: fix ownership transfer"), this truesize subtraction in skb_segment_list() was valid because fragments still carry a reference to the original socket. However, commit ed4cccef64c1 ("gro: fix ownership transfer") changed this behavior by ensuring that fraglist entries are explicitly orphaned (skb->sk = NULL) to prevent illegal orphaning later in the stack. This change meant that the entire socket memory charge remained with the head SKB, but the corresponding accounting logic in skb_segment_list() was never updated. As a result, the current code unconditionally adds each fragment's truesize to delta_truesize and subtracts it from the parent SKB. Since the fragments are no longer charged to the socket, this subtraction results in an effective under-count of memory when the head is freed. This causes sk_wmem_alloc to remain non-zero, preventing socket destruction and leading to a persistent memory leak. The leak can be observed via KMEMLEAK when tearing down the networking environment: unreferenced object 0xffff8881e6eb9100 (size 2048): comm "ping", pid 6720, jiffies 4295492526 backtrace: kmem_cache_alloc_noprof+0x5c6/0x800 sk_prot_alloc+0x5b/0x220 sk_alloc+0x35/0xa00 inet6_create.part.0+0x303/0x10d0 __sock_create+0x248/0x640 __sys_socket+0x11b/0x1d0 Since skb_segment_list() is exclusively used for SKB_GSO_FRAGLIST packets constructed by GRO, the truesize adjustment is removed. The call to skb_release_head_state() must be preserved. As documented in commit cf673ed0e057 ("net: fix fraglist segmentation reference count leak"), it is still required to correctly drop references to SKB extensions that may be overwritten during __copy_skb_header().
Remediation
Limit access to the interactive shell of the additional GNU/Linux subssytem to trusted personnel only.
CVE-2026-22979 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitykernel: Linux kernel: Memory leak in networking due to incorrect GRO packet handling
160 known affected

The vendor explicitly identifies these products as 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 networking component. Incorrect memory accounting when handling Generic Receive Offload (GRO) packets can lead to a persistent memory leak. This occurs because the system incorrectly tracks memory usage for network packets, preventing proper cleanup of network resources. Over time, this can lead to a denial of service (DoS) as system memory is gradually exhausted.
Remediation
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.
Optional official sources

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

Select the national-authority views to include. The exact source language is shown on each matched advisory. Your choice is remembered on this device and encoded in the shareable URL.

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-4307

No EUVD known-exploited evidence

In the Linux kernel, the following vulnerability has been resolved: net: fix memory leak in skb_segment_list for GRO packets When skb_segment_list() is called during packet forwarding, it handles packets that were aggregated by the GRO engine. Historically, the segmentation logic in skb_segment_list assumes that individual segments are split from a parent SKB and may need to carry their own socket memory accounting. Accordingly, the code transfers truesize from the parent to the newly created segments. Prior to commit ed4cccef64c1 ("gro: fix ownership transfer"), this truesize subtraction in skb_segment_list() was valid because fragments still carry a reference to the original socket. However, commit ed4cccef64c1 ("gro: fix ownership transfer") changed this behavior by ensuring that fraglist entries are explicitly orphaned (skb->sk = NULL) to prevent illegal orphaning later in the stack. This change meant that the entire socket memory charge remained with the head SKB, but the corresponding accounting logic in skb_segment_list() was never updated. As a result, the current code unconditionally adds each fragment's truesize to delta_truesize and subtracts it from the parent SKB. Since the fragments are no longer charged to the socket, this subtraction results in an effective under-count of memory when the head is freed. This causes sk_wmem_alloc to remain non-zero, preventing socket destruction and leading to a persistent memory leak. The leak can be observed via KMEMLEAK when tearing down the networking environment: unreferenced object 0xffff8881e6eb9100 (size 2048): comm "ping", pid 6720, jiffies 4295492526 backtrace: kmem_cache_alloc_noprof+0x5c6/0x800 sk_prot_alloc+0x5b/0x220 sk_alloc+0x35/0xa00 inet6_create.part.0+0x303/0x10d0 __sock_create+0x248/0x640 __sys_socket+0x11b/0x1d0 Since skb_segment_list() is exclusively used for SKB_GSO_FRAGLIST packets constructed by GRO, the truesize adjustment is removed. The call to skb_release_head_state() must be preserved. As documented in commit cf673ed0e057 ("net: fix fraglist segmentation reference count leak"), it is still required to correctly drop references to SKB extensions that may be overwritten during __copy_skb_header().

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
0.0
Advisory evidence
No linked advisory details stored yet
Recommended actionScheduled

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.

Patch available
01

What, why and how

In the Linux kernel, the following vulnerability has been resolved: net: fix memory leak in skb_segment_list for GRO packets When skb_segment_list() is called during packet forwarding, it handles packets that were aggregated by the GRO engine. Historically, the segmentation logic in skb_segment_list assumes that individual segments are split from a parent SKB and may need to carry their own socket memory accounting. Accordingly, the code transfers truesize from the parent to the newly created segments. Prior to commit ed4cccef64c1 ("gro: fix ownership transfer"), this truesize subtraction in skb_segment_list() was valid because fragments still carry a reference to the original socket. However, commit ed4cccef64c1 ("gro: fix ownership transfer") changed this behavior by ensuring that fraglist entries are explicitly orphaned (skb->sk = NULL) to prevent illegal orphaning later in the stack. This change meant that the entire socket memory charge remained with the head SKB, but the corresponding accounting logic in skb_segment_list() was never updated. As a result, the current code unconditionally adds each fragment's truesize to delta_truesize and subtracts it from the parent SKB. Since the fragments are no longer charged to the socket, this subtraction results in an effective under-count of memory when the head is freed. This causes sk_wmem_alloc to remain non-zero, preventing socket destruction and leading to a persistent memory leak. The leak can be observed via KMEMLEAK when tearing down the networking environment: unreferenced object 0xffff8881e6eb9100 (size 2048): comm "ping", pid 6720, jiffies 4295492526 backtrace: kmem_cache_alloc_noprof+0x5c6/0x800 sk_prot_alloc+0x5b/0x220 sk_alloc+0x35/0xa00 inet6_create.part.0+0x303/0x10d0 __sock_create+0x248/0x640 __sys_socket+0x11b/0x1d0 Since skb_segment_list() is exclusively used for SKB_GSO_FRAGLIST packets constructed by GRO, the truesize adjustment is removed. The call to skb_release_head_state() must be preserved. As documented in commit cf673ed0e057 ("net: fix fraglist segmentation reference count leak"), it is still required to correctly drop references to SKB extensions that may be overwritten during __copy_skb_header().

What

In the Linux kernel, the following vulnerability has been resolved: net: fix memory leak in skb_segment_list for GRO packets When skb_segment_list() is called during packet forwarding, it handles packets that were aggregated by the GRO engine. Historically, the segmentation logic in skb_segment_list assumes that individual segments are split from a parent SKB and may need to carry their own socket memory accounting. Accordingly, the code transfers truesize from the parent to the newly created segments. Prior to commit ed4cccef64c1 ("gro: fix ownership transfer"), this truesize subtraction in skb_segment_list() was valid because fragments still carry a reference to the original socket. However, commit ed4cccef64c1 ("gro: fix ownership transfer") changed this behavior by ensuring that fraglist entries are explicitly orphaned (skb->sk = NULL) to prevent illegal orphaning later in the stack. This change meant that the entire socket memory charge remained with the head SKB, but the corresponding accounting logic in skb_segment_list() was never updated. As a result, the current code unconditionally adds each fragment's truesize to delta_truesize and subtracts it from the parent SKB. Since the fragments are no longer charged to the socket, this subtraction results in an effective under-count of memory when the head is freed. This causes sk_wmem_alloc to remain non-zero, preventing socket destruction and leading to a persistent memory leak. The leak can be observed via KMEMLEAK when tearing down the networking environment: unreferenced object 0xffff8881e6eb9100 (size 2048): comm "ping", pid 6720, jiffies 4295492526 backtrace: kmem_cache_alloc_noprof+0x5c6/0x800 sk_prot_alloc+0x5b/0x220 sk_alloc+0x35/0xa00 inet6_create.part.0+0x303/0x10d0 __sock_create+0x248/0x640 __sys_socket+0x11b/0x1d0 Since skb_segment_list() is exclusively used for SKB_GSO_FRAGLIST packets constructed by GRO, the truesize adjustment is removed. The call to skb_release_head_state() must be preserved. As documented in commit cf673ed0e057 ("net: fix fraglist segmentation reference count leak"), it is still required to correctly drop references to SKB extensions that may be overwritten during __copy_skb_header().

Why

The product does not sufficiently track and release allocated memory after it has been used, making the memory unavailable for reallocation and reuse.

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: net: fix memory leak in skb_segment_list for GRO packets When skb_segment_list() is called during packet forwarding, it handles packets that were aggregated by the GRO engine. Historically, the segmentation logic in skb_segment_list assumes that individual segments are split from a parent SKB and may need to carry their own socket memory accounting. Accordingly, the code transfers truesize from the parent to the newly created segments. Prior to commit ed4cccef64c1 ("gro: fix ownership transfer"), this truesize subtraction in skb_segment_list() was valid because fragments still carry a reference to the original socket. However, commit ed4cccef64c1 ("gro: fix ownership transfer") changed this behavior by ensuring that fraglist entries are explicitly orphaned (skb->sk = NULL) to prevent illegal orphaning later in the stack. This change meant that the entire socket memory charge remained with the head SKB, but the corresponding accounting logic in skb_segment_list() was never updated. As a result, the current code unconditionally adds each fragment's truesize to delta_truesize and subtracts it from the parent SKB. Since the fragments are no longer charged to the socket, this subtraction results in an effective under-count of memory when the head is freed. This causes sk_wmem_alloc to remain non-zero, preventing socket destruction and leading to a persistent memory leak. The leak can be observed via KMEMLEAK when tearing down the networking environment: unreferenced object 0xffff8881e6eb9100 (size 2048): comm "ping", pid 6720, jiffies 4295492526 backtrace: kmem_cache_alloc_noprof+0x5c6/0x800 sk_prot_alloc+0x5b/0x220 sk_alloc+0x35/0xa00 inet6_create.part.0+0x303/0x10d0 __sock_create+0x248/0x640 __sys_socket+0x11b/0x1d0 Since skb_segment_list() is exclusively used for SKB_GSO_FRAGLIST packets constructed by GRO, the truesize adjustment is removed. The call to skb_release_head_state() must be preserved. As documented in commit cf673ed0e057 ("net: fix fraglist segmentation reference count leak"), it is still required to correctly drop references to SKB extensions that may be overwritten during __copy_skb_header().

Why

The product does not sufficiently track and release allocated memory after it has been used, making the memory unavailable for reallocation and reuse.

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 → Missing Release of Memory after Effective Lifetime → 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: a standard category for the underlying weakness.
CWE-401 ↗

CWE-401: Missing Release of Memory after Effective Lifetime. The product does not sufficiently track and release allocated memory after it has been used, making the memory unavailable for reallocation and reuse.

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.
CWE-401
A

Official authority intelligence

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

ENISA EUVD · EUVD-2026-4307Official EUVD mapping

In the Linux kernel, the following vulnerability has been resolved: net: fix memory leak in skb_segment_list for GRO packets When skb_segment_list() is called during packet forwarding, it handles packets that were aggregated by the GRO engine. Historically, the segmentation logic in skb_segment_list assumes that individual segments are split from a parent SKB and may need to carry their own socket memory accounting. Accordingly, the code transfers truesize from the parent to the newly created segments. Prior to commit ed4cccef64c1 ("gro: fix ownership transfer"), this truesize subtraction in skb_segment_list() was valid because fragments still carry a reference to the original socket. However, commit ed4cccef64c1 ("gro: fix ownership transfer") changed this behavior by ensuring that fraglist entries are explicitly orphaned (skb->sk = NULL) to prevent illegal orphaning later in the stack. This change meant that the entire socket memory charge remained with the head SKB, but the corresponding accounting logic in skb_segment_list() was never updated. As a result, the current code unconditionally adds each fragment's truesize to delta_truesize and subtracts it from the parent SKB. Since the fragments are no longer charged to the socket, this subtraction results in an effective under-count of memory when the head is freed. This causes sk_wmem_alloc to remain non-zero, preventing socket destruction and leading to a persistent memory leak. The leak can be observed via KMEMLEAK when tearing down the networking environment: unreferenced object 0xffff8881e6eb9100 (size 2048): comm "ping", pid 6720, jiffies 4295492526 backtrace: kmem_cache_alloc_noprof+0x5c6/0x800 sk_prot_alloc+0x5b/0x220 sk_alloc+0x35/0xa00 inet6_create.part.0+0x303/0x10d0 __sock_create+0x248/0x640 __sys_socket+0x11b/0x1d0 Since skb_segment_list() is exclusively used for SKB_GSO_FRAGLIST packets constructed by GRO, the truesize adjustment is removed. The call to skb_release_head_state() must be preserved. As documented in commit cf673ed0e057 ("net: fix fraglist segmentation reference count leak"), it is still required to correctly drop references to SKB extensions that may be overwritten during __copy_skb_header().

Official EUVD record
BSI · German · WID-SEC-W-2026-0215Linux Kernel: Mehrere Schwachstellen

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

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

d?id=CVE-2025-71266 Référence CVE CVE-2025-71267 https://www.cve.org/CVERecord?id=CVE-2025-71267 Référence CVE CVE-2025-71274 https://www.cve.org/CVERecord?id=CVE-2025-71274 Référence CVE CVE-2025-71287 https://www.cve.org/CVERecord?id=CVE-2025-71287 Référence CVE CVE-2025-71292 https://www.cve.org/CVERecord?id=CVE-2025-71292 Référence CVE CVE-2025-71304 https://www.cve.org/CVERecord?id=CVE-2025-71304 Référence CVE CVE-2026-22976 https://www.cve.org/CVERecord?id=CVE-2026-22976 Référence CVE CVE-2026-22977 https://www.cve.org/CVERecord?id=CVE-2026-22977 Référence CVE CVE-2026-22978 https://www.cve.org/CVERecord?id=CVE-2026-22978 Référence CVE CVE-2026-22979 https://www.cve.org/CVERecord?id=CVE-2026-22979 Référence CVE CVE-2026-22980 https://www.cve.org/CVERecord?id=CVE-2026-22980 Référence CVE CVE-2026-22981 https://www.cve.org/CVERecord?id=CVE-2026-22981 Référence CVE CVE-2026-22982 https://www.cve.org/CVERecord?id=CVE-2026-22982 Référence CVE CVE-2026-22985 https://www.cve.org/CVERecord?id=CVE-2026-22985 Référence CVE CVE-2026-22986 https://www.cve.org/CVERecord?id=CVE-2026-22986 Référence CVE CVE-2026-22987 https://www.cve.org/CVERecord?id=CVE-2026-22987 Référence CVE CVE-2026-22989 https://www.cve.org/CVERecord?id=CVE-2026-22989 Référence CVE CVE-2026-22990 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-2025-71292 Référence CVE CVE-2025-71294 https://www.cve.org/CVERecord?id=CVE-2025-71294 Référence CVE CVE-2025-71295 https://www.cve.org/CVERecord?id=CVE-2025-71295 Référence CVE CVE-2025-71297 https://www.cve.org/CVERecord?id=CVE-2025-71297 Référence CVE CVE-2025-71304 https://www.cve.org/CVERecord?id=CVE-2025-71304 Référence CVE CVE-2025-71305 https://www.cve.org/CVERecord?id=CVE-2025-71305 Référence CVE CVE-2026-22976 https://www.cve.org/CVERecord?id=CVE-2026-22976 Référence CVE CVE-2026-22977 https://www.cve.org/CVERecord?id=CVE-2026-22977 Référence CVE CVE-2026-22978 https://www.cve.org/CVERecord?id=CVE-2026-22978 Référence CVE CVE-2026-22979 https://www.cve.org/CVERecord?id=CVE-2026-22979 Référence CVE CVE-2026-22980 https://www.cve.org/CVERecord?id=CVE-2026-22980 Référence CVE CVE-2026-22981 https://www.cve.org/CVERecord?id=CVE-2026-22981 Référence CVE CVE-2026-22982 https://www.cve.org/CVERecord?id=CVE-2026-22982 Référence CVE CVE-2026-22984 https://www.cve.org/CVERecord?id=CVE-2026-22984 Référence CVE CVE-2026-22985 https://www.cve.org/CVERecord?id=CVE-2026-22985 Référence CVE CVE-2026-22986 https://www.cve.org/CVERecord?id=CVE-2026-22986 Référence CVE CVE-2026-22987 https://www.cve.org/CVERecord?id=CVE-2026-22987 Référence CVE CVE-2026-22989 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-2025-71269 Référence CVE CVE-2025-71274 https://www.cve.org/CVERecord?id=CVE-2025-71274 Référence CVE CVE-2025-71287 https://www.cve.org/CVERecord?id=CVE-2025-71287 Référence CVE CVE-2025-71288 https://www.cve.org/CVERecord?id=CVE-2025-71288 Référence CVE CVE-2025-71292 https://www.cve.org/CVERecord?id=CVE-2025-71292 Référence CVE CVE-2025-71304 https://www.cve.org/CVERecord?id=CVE-2025-71304 Référence CVE CVE-2026-22976 https://www.cve.org/CVERecord?id=CVE-2026-22976 Référence CVE CVE-2026-22977 https://www.cve.org/CVERecord?id=CVE-2026-22977 Référence CVE CVE-2026-22978 https://www.cve.org/CVERecord?id=CVE-2026-22978 Référence CVE CVE-2026-22979 https://www.cve.org/CVERecord?id=CVE-2026-22979 Référence CVE CVE-2026-22980 https://www.cve.org/CVERecord?id=CVE-2026-22980 Référence CVE CVE-2026-22981 https://www.cve.org/CVERecord?id=CVE-2026-22981 Référence CVE CVE-2026-22982 https://www.cve.org/CVERecord?id=CVE-2026-22982 Référence CVE CVE-2026-22984 https://www.cve.org/CVERecord?id=CVE-2026-22984 Référence CVE CVE-2026-22985 https://www.cve.org/CVERecord?id=CVE-2026-22985 Référence CVE CVE-2026-22986 https://www.cve.org/CVERecord?id=CVE-2026-22986 Référence CVE CVE-2026-22987 https://www.cve.org/CVERecord?id=CVE-2026-22987 Référence CVE CVE-2026-22989 https://www.cve.org/CVERecord?id=

Official advisory
CERT-FR · French · CERTFR-2026-AVI-0880Multiples vulnérabilités dans les produits Siemens

025-68776, CVE-2025-68782, CVE-2025-68787, CVE-2025-68788, CVE-2025-68798, CVE-2025-68803, CVE-2025-68814, CVE-2025-68816, CVE-2025-68818, CVE-2025-68820, CVE-2025-71064, CVE-2025-71075, CVE-2025-71079, CVE-2025-71085, CVE-2025-71086, CVE-2025-71088, CVE-2025-71095, CVE-2025-71097, CVE-2025-71098, CVE-2025-71104, CVE-2025-71112, CVE-2025-71113, CVE-2025-71114, CVE-2025-71120, CVE-2025-71123, CVE-2025-71131, CVE-2025-71161, CVE-2025-71162, CVE-2025-71163, CVE-2025-71185, CVE-2025-71186, CVE-2025-71189, CVE-2025-71190, CVE-2025-71191, CVE-2025-71197, CVE-2025-71221, CVE-2025-71265, CVE-2025-71266, CVE-2025-71267, CVE-2026-3497, CVE-2026-22977, CVE-2026-22979, CVE-2026-22980, CVE-2026-22982, CVE-2026-22992, CVE-2026-22994, CVE-2026-23003, CVE-2026-23005, CVE-2026-23010, CVE-2026-23011, CVE-2026-23019, CVE-2026-23026, CVE-2026-23038, CVE-2026-23054, CVE-2026-23060, CVE-2026-23083, CVE-2026-23084, CVE-2026-23086, CVE-2026-23087, CVE-2026-23095, CVE-2026-23100, CVE-2026-23103, CVE-2026-23110, CVE-2026-23111, CVE-2026-23113, CVE-2026-23154, CVE-2026-23204, CVE-2026-23231, CVE-2026-23242, CVE-2026-23243, CVE-2026-23245, CVE-2026-23270, CVE-2026-23271, CVE-2026-23273, CVE-2026-23274, CVE-2026-23277, CVE-2026-23284, CVE-2026-23287, CVE-2026-23290, CVE-2026-23293, CVE-2026-23300, CVE-2026-23304, CVE-2026

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

d?id=CVE-2025-71292 Référence CVE CVE-2025-71294 https://www.cve.org/CVERecord?id=CVE-2025-71294 Référence CVE CVE-2025-71295 https://www.cve.org/CVERecord?id=CVE-2025-71295 Référence CVE CVE-2025-71297 https://www.cve.org/CVERecord?id=CVE-2025-71297 Référence CVE CVE-2025-71304 https://www.cve.org/CVERecord?id=CVE-2025-71304 Référence CVE CVE-2025-71305 https://www.cve.org/CVERecord?id=CVE-2025-71305 Référence CVE CVE-2026-22976 https://www.cve.org/CVERecord?id=CVE-2026-22976 Référence CVE CVE-2026-22977 https://www.cve.org/CVERecord?id=CVE-2026-22977 Référence CVE CVE-2026-22978 https://www.cve.org/CVERecord?id=CVE-2026-22978 Référence CVE CVE-2026-22979 https://www.cve.org/CVERecord?id=CVE-2026-22979 Référence CVE CVE-2026-22980 https://www.cve.org/CVERecord?id=CVE-2026-22980 Référence CVE CVE-2026-22982 https://www.cve.org/CVERecord?id=CVE-2026-22982 Référence CVE CVE-2026-22984 https://www.cve.org/CVERecord?id=CVE-2026-22984 Référence CVE CVE-2026-22990 https://www.cve.org/CVERecord?id=CVE-2026-22990 Référence CVE CVE-2026-22991 https://www.cve.org/CVERecord?id=CVE-2026-22991 Référence CVE CVE-2026-22992 https://www.cve.org/CVERecord?id=CVE-2026-22992 Référence CVE CVE-2026-22994 https://www.cve.org/CVERecord?id=CVE-2026-22994 Référence CVE CVE-2026-22996 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-71200 Référence CVE CVE-2025-71220 https://www.cve.org/CVERecord?id=CVE-2025-71220 Référence CVE CVE-2025-71222 https://www.cve.org/CVERecord?id=CVE-2025-71222 Référence CVE CVE-2025-71224 https://www.cve.org/CVERecord?id=CVE-2025-71224 Référence CVE CVE-2025-71225 https://www.cve.org/CVERecord?id=CVE-2025-71225 Référence CVE CVE-2025-71268 https://www.cve.org/CVERecord?id=CVE-2025-71268 Référence CVE CVE-2026-22976 https://www.cve.org/CVERecord?id=CVE-2026-22976 Référence CVE CVE-2026-22977 https://www.cve.org/CVERecord?id=CVE-2026-22977 Référence CVE CVE-2026-22978 https://www.cve.org/CVERecord?id=CVE-2026-22978 Référence CVE CVE-2026-22979 https://www.cve.org/CVERecord?id=CVE-2026-22979 Référence CVE CVE-2026-22980 https://www.cve.org/CVERecord?id=CVE-2026-22980 Référence CVE CVE-2026-22982 https://www.cve.org/CVERecord?id=CVE-2026-22982 Référence CVE CVE-2026-22984 https://www.cve.org/CVERecord?id=CVE-2026-22984 Référence CVE CVE-2026-22990 https://www.cve.org/CVERecord?id=CVE-2026-22990 Référence CVE CVE-2026-22991 https://www.cve.org/CVERecord?id=CVE-2026-22991 Référence CVE CVE-2026-22992 https://www.cve.org/CVERecord?id=CVE-2026-22992 Référence CVE CVE-2026-22994 https://www.cve.org/CVERecord?id=CVE-2026-22994 Référence CVE CVE-2026-22996 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-71200 Référence CVE CVE-2025-71220 https://www.cve.org/CVERecord?id=CVE-2025-71220 Référence CVE CVE-2025-71222 https://www.cve.org/CVERecord?id=CVE-2025-71222 Référence CVE CVE-2025-71224 https://www.cve.org/CVERecord?id=CVE-2025-71224 Référence CVE CVE-2025-71225 https://www.cve.org/CVERecord?id=CVE-2025-71225 Référence CVE CVE-2025-71268 https://www.cve.org/CVERecord?id=CVE-2025-71268 Référence CVE CVE-2026-22976 https://www.cve.org/CVERecord?id=CVE-2026-22976 Référence CVE CVE-2026-22977 https://www.cve.org/CVERecord?id=CVE-2026-22977 Référence CVE CVE-2026-22978 https://www.cve.org/CVERecord?id=CVE-2026-22978 Référence CVE CVE-2026-22979 https://www.cve.org/CVERecord?id=CVE-2026-22979 Référence CVE CVE-2026-22980 https://www.cve.org/CVERecord?id=CVE-2026-22980 Référence CVE CVE-2026-22982 https://www.cve.org/CVERecord?id=CVE-2026-22982 Référence CVE CVE-2026-22984 https://www.cve.org/CVERecord?id=CVE-2026-22984 Référence CVE CVE-2026-22990 https://www.cve.org/CVERecord?id=CVE-2026-22990 Référence CVE CVE-2026-22991 https://www.cve.org/CVERecord?id=CVE-2026-22991 Référence CVE CVE-2026-22992 https://www.cve.org/CVERecord?id=CVE-2026-22992 Référence CVE CVE-2026-22994 https://www.cve.org/CVERecord?id=CVE-2026-22994 Référence CVE CVE-2026-22996 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-71200 Référence CVE CVE-2025-71220 https://www.cve.org/CVERecord?id=CVE-2025-71220 Référence CVE CVE-2025-71222 https://www.cve.org/CVERecord?id=CVE-2025-71222 Référence CVE CVE-2025-71224 https://www.cve.org/CVERecord?id=CVE-2025-71224 Référence CVE CVE-2025-71225 https://www.cve.org/CVERecord?id=CVE-2025-71225 Référence CVE CVE-2025-71268 https://www.cve.org/CVERecord?id=CVE-2025-71268 Référence CVE CVE-2026-22976 https://www.cve.org/CVERecord?id=CVE-2026-22976 Référence CVE CVE-2026-22977 https://www.cve.org/CVERecord?id=CVE-2026-22977 Référence CVE CVE-2026-22978 https://www.cve.org/CVERecord?id=CVE-2026-22978 Référence CVE CVE-2026-22979 https://www.cve.org/CVERecord?id=CVE-2026-22979 Référence CVE CVE-2026-22980 https://www.cve.org/CVERecord?id=CVE-2026-22980 Référence CVE CVE-2026-22982 https://www.cve.org/CVERecord?id=CVE-2026-22982 Référence CVE CVE-2026-22984 https://www.cve.org/CVERecord?id=CVE-2026-22984 Référence CVE CVE-2026-22990 https://www.cve.org/CVERecord?id=CVE-2026-22990 Référence CVE CVE-2026-22991 https://www.cve.org/CVERecord?id=CVE-2026-22991 Référence CVE CVE-2026-22992 https://www.cve.org/CVERecord?id=CVE-2026-22992 Référence CVE CVE-2026-22994 https://www.cve.org/CVERecord?id=CVE-2026-22994 Référence CVE CVE-2026-22996 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-71200 Référence CVE CVE-2025-71220 https://www.cve.org/CVERecord?id=CVE-2025-71220 Référence CVE CVE-2025-71222 https://www.cve.org/CVERecord?id=CVE-2025-71222 Référence CVE CVE-2025-71224 https://www.cve.org/CVERecord?id=CVE-2025-71224 Référence CVE CVE-2025-71225 https://www.cve.org/CVERecord?id=CVE-2025-71225 Référence CVE CVE-2025-71268 https://www.cve.org/CVERecord?id=CVE-2025-71268 Référence CVE CVE-2026-22976 https://www.cve.org/CVERecord?id=CVE-2026-22976 Référence CVE CVE-2026-22977 https://www.cve.org/CVERecord?id=CVE-2026-22977 Référence CVE CVE-2026-22978 https://www.cve.org/CVERecord?id=CVE-2026-22978 Référence CVE CVE-2026-22979 https://www.cve.org/CVERecord?id=CVE-2026-22979 Référence CVE CVE-2026-22980 https://www.cve.org/CVERecord?id=CVE-2026-22980 Référence CVE CVE-2026-22982 https://www.cve.org/CVERecord?id=CVE-2026-22982 Référence CVE CVE-2026-22984 https://www.cve.org/CVERecord?id=CVE-2026-22984 Référence CVE CVE-2026-22990 https://www.cve.org/CVERecord?id=CVE-2026-22990 Référence CVE CVE-2026-22991 https://www.cve.org/CVERecord?id=CVE-2026-22991 Référence CVE CVE-2026-22992 https://www.cve.org/CVERecord?id=CVE-2026-22992 Référence CVE CVE-2026-22994 https://www.cve.org/CVERecord?id=CVE-2026-22994 Référence CVE CVE-2026-22996 https://www.cve.org/CVERecord?id=

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

ord?id=CVE-2025-71231 Référence CVE CVE-2025-71232 https://www.cve.org/CVERecord?id=CVE-2025-71232 Référence CVE CVE-2025-71234 https://www.cve.org/CVERecord?id=CVE-2025-71234 Référence CVE CVE-2025-71235 https://www.cve.org/CVERecord?id=CVE-2025-71235 Référence CVE CVE-2025-71236 https://www.cve.org/CVERecord?id=CVE-2025-71236 Référence CVE CVE-2025-7709 https://www.cve.org/CVERecord?id=CVE-2025-7709 Référence CVE CVE-2026-22976 https://www.cve.org/CVERecord?id=CVE-2026-22976 Référence CVE CVE-2026-22977 https://www.cve.org/CVERecord?id=CVE-2026-22977 Référence CVE CVE-2026-22978 https://www.cve.org/CVERecord?id=CVE-2026-22978 Référence CVE CVE-2026-22979 https://www.cve.org/CVERecord?id=CVE-2026-22979 Référence CVE CVE-2026-22982 https://www.cve.org/CVERecord?id=CVE-2026-22982 Référence CVE CVE-2026-22984 https://www.cve.org/CVERecord?id=CVE-2026-22984 Référence CVE CVE-2026-22985 https://www.cve.org/CVERecord?id=CVE-2026-22985 Référence CVE CVE-2026-22988 https://www.cve.org/CVERecord?id=CVE-2026-22988 Référence CVE CVE-2026-22989 https://www.cve.org/CVERecord?id=CVE-2026-22989 Référence CVE CVE-2026-22990 https://www.cve.org/CVERecord?id=CVE-2026-22990 Référence CVE CVE-2026-22991 https://www.cve.org/CVERecord?id=CVE-2026-22991 Référence CVE CVE-2026-22992 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-71222 Référence CVE CVE-2025-71224 https://www.cve.org/CVERecord?id=CVE-2025-71224 Référence CVE CVE-2025-71225 https://www.cve.org/CVERecord?id=CVE-2025-71225 Référence CVE CVE-2025-71229 https://www.cve.org/CVERecord?id=CVE-2025-71229 Référence CVE CVE-2025-71231 https://www.cve.org/CVERecord?id=CVE-2025-71231 Référence CVE CVE-2025-71232 https://www.cve.org/CVERecord?id=CVE-2025-71232 Référence CVE CVE-2025-71234 https://www.cve.org/CVERecord?id=CVE-2025-71234 Référence CVE CVE-2025-71235 https://www.cve.org/CVERecord?id=CVE-2025-71235 Référence CVE CVE-2025-71236 https://www.cve.org/CVERecord?id=CVE-2025-71236 Référence CVE CVE-2026-22979 https://www.cve.org/CVERecord?id=CVE-2026-22979 Référence CVE CVE-2026-22982 https://www.cve.org/CVERecord?id=CVE-2026-22982 Référence CVE CVE-2026-22998 https://www.cve.org/CVERecord?id=CVE-2026-22998 Référence CVE CVE-2026-23003 https://www.cve.org/CVERecord?id=CVE-2026-23003 Référence CVE CVE-2026-23004 https://www.cve.org/CVERecord?id=CVE-2026-23004 Référence CVE CVE-2026-23017 https://www.cve.org/CVERecord?id=CVE-2026-23017 Référence CVE CVE-2026-23021 https://www.cve.org/CVERecord?id=CVE-2026-23021 Référence CVE CVE-2026-23026 https://www.cve.org/CVERecord?id=CVE-2026-23026 Référence CVE CVE-2026-23033 https://www.cve.org/CVERecord?id=

Official advisory
CERT-FR · French · CERTFR-2026-AVI-0326Multiples vulnérabilités dans les produits VMware

Record?id=CVE-2026-2219 Référence CVE CVE-2026-2243 https://www.cve.org/CVERecord?id=CVE-2026-2243 Référence CVE CVE-2026-22795 https://www.cve.org/CVERecord?id=CVE-2026-22795 Référence CVE CVE-2026-22796 https://www.cve.org/CVERecord?id=CVE-2026-22796 Référence CVE CVE-2026-22860 https://www.cve.org/CVERecord?id=CVE-2026-22860 Référence CVE CVE-2026-2297 https://www.cve.org/CVERecord?id=CVE-2026-2297 Référence CVE CVE-2026-22976 https://www.cve.org/CVERecord?id=CVE-2026-22976 Référence CVE CVE-2026-22977 https://www.cve.org/CVERecord?id=CVE-2026-22977 Référence CVE CVE-2026-22978 https://www.cve.org/CVERecord?id=CVE-2026-22978 Référence CVE CVE-2026-22979 https://www.cve.org/CVERecord?id=CVE-2026-22979 Référence CVE CVE-2026-22980 https://www.cve.org/CVERecord?id=CVE-2026-22980 Référence CVE CVE-2026-22982 https://www.cve.org/CVERecord?id=CVE-2026-22982 Référence CVE CVE-2026-22984 https://www.cve.org/CVERecord?id=CVE-2026-22984 Référence CVE CVE-2026-22990 https://www.cve.org/CVERecord?id=CVE-2026-22990 Référence CVE CVE-2026-22991 https://www.cve.org/CVERecord?id=CVE-2026-22991 Référence CVE CVE-2026-22992 https://www.cve.org/CVERecord?id=CVE-2026-22992 Référence CVE CVE-2026-22996 https://www.cve.org/CVERecord?id=CVE-2026-22996 Référence CVE CVE-2026-22997 https://www.cve.org/CVERecord?id=

Official advisory
CERT-FR · French · CERTFR-2026-AVI-0316Multiples vulnérabilités dans les produits VMware

Record?id=CVE-2026-2219 Référence CVE CVE-2026-2243 https://www.cve.org/CVERecord?id=CVE-2026-2243 Référence CVE CVE-2026-22795 https://www.cve.org/CVERecord?id=CVE-2026-22795 Référence CVE CVE-2026-22796 https://www.cve.org/CVERecord?id=CVE-2026-22796 Référence CVE CVE-2026-22860 https://www.cve.org/CVERecord?id=CVE-2026-22860 Référence CVE CVE-2026-2297 https://www.cve.org/CVERecord?id=CVE-2026-2297 Référence CVE CVE-2026-22976 https://www.cve.org/CVERecord?id=CVE-2026-22976 Référence CVE CVE-2026-22977 https://www.cve.org/CVERecord?id=CVE-2026-22977 Référence CVE CVE-2026-22978 https://www.cve.org/CVERecord?id=CVE-2026-22978 Référence CVE CVE-2026-22979 https://www.cve.org/CVERecord?id=CVE-2026-22979 Référence CVE CVE-2026-22980 https://www.cve.org/CVERecord?id=CVE-2026-22980 Référence CVE CVE-2026-22982 https://www.cve.org/CVERecord?id=CVE-2026-22982 Référence CVE CVE-2026-22984 https://www.cve.org/CVERecord?id=CVE-2026-22984 Référence CVE CVE-2026-22990 https://www.cve.org/CVERecord?id=CVE-2026-22990 Référence CVE CVE-2026-22991 https://www.cve.org/CVERecord?id=CVE-2026-22991 Référence CVE CVE-2026-22992 https://www.cve.org/CVERecord?id=CVE-2026-22992 Référence CVE CVE-2026-22996 https://www.cve.org/CVERecord?id=CVE-2026-22996 Référence CVE CVE-2026-22997 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-71191 Référence CVE CVE-2025-71192 https://www.cve.org/CVERecord?id=CVE-2025-71192 Référence CVE CVE-2025-71194 https://www.cve.org/CVERecord?id=CVE-2025-71194 Référence CVE CVE-2025-71196 https://www.cve.org/CVERecord?id=CVE-2025-71196 Référence CVE CVE-2025-71197 https://www.cve.org/CVERecord?id=CVE-2025-71197 Référence CVE CVE-2025-71199 https://www.cve.org/CVERecord?id=CVE-2025-71199 Référence CVE CVE-2026-22976 https://www.cve.org/CVERecord?id=CVE-2026-22976 Référence CVE CVE-2026-22977 https://www.cve.org/CVERecord?id=CVE-2026-22977 Référence CVE CVE-2026-22978 https://www.cve.org/CVERecord?id=CVE-2026-22978 Référence CVE CVE-2026-22979 https://www.cve.org/CVERecord?id=CVE-2026-22979 Référence CVE CVE-2026-22980 https://www.cve.org/CVERecord?id=CVE-2026-22980 Référence CVE CVE-2026-22982 https://www.cve.org/CVERecord?id=CVE-2026-22982 Référence CVE CVE-2026-22984 https://www.cve.org/CVERecord?id=CVE-2026-22984 Référence CVE CVE-2026-22990 https://www.cve.org/CVERecord?id=CVE-2026-22990 Référence CVE CVE-2026-22991 https://www.cve.org/CVERecord?id=CVE-2026-22991 Référence CVE CVE-2026-22992 https://www.cve.org/CVERecord?id=CVE-2026-22992 Référence CVE CVE-2026-22994 https://www.cve.org/CVERecord?id=CVE-2026-22994 Référence CVE CVE-2026-22997 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-71194 Référence CVE CVE-2025-71195 https://www.cve.org/CVERecord?id=CVE-2025-71195 Référence CVE CVE-2025-71196 https://www.cve.org/CVERecord?id=CVE-2025-71196 Référence CVE CVE-2025-71197 https://www.cve.org/CVERecord?id=CVE-2025-71197 Référence CVE CVE-2025-71198 https://www.cve.org/CVERecord?id=CVE-2025-71198 Référence CVE CVE-2025-71199 https://www.cve.org/CVERecord?id=CVE-2025-71199 Référence CVE CVE-2026-22976 https://www.cve.org/CVERecord?id=CVE-2026-22976 Référence CVE CVE-2026-22977 https://www.cve.org/CVERecord?id=CVE-2026-22977 Référence CVE CVE-2026-22978 https://www.cve.org/CVERecord?id=CVE-2026-22978 Référence CVE CVE-2026-22979 https://www.cve.org/CVERecord?id=CVE-2026-22979 Référence CVE CVE-2026-22980 https://www.cve.org/CVERecord?id=CVE-2026-22980 Référence CVE CVE-2026-22982 https://www.cve.org/CVERecord?id=CVE-2026-22982 Référence CVE CVE-2026-22984 https://www.cve.org/CVERecord?id=CVE-2026-22984 Référence CVE CVE-2026-22989 https://www.cve.org/CVERecord?id=CVE-2026-22989 Référence CVE CVE-2026-22990 https://www.cve.org/CVERecord?id=CVE-2026-22990 Référence CVE CVE-2026-22991 https://www.cve.org/CVERecord?id=CVE-2026-22991 Référence CVE CVE-2026-22992 https://www.cve.org/CVERecord?id=CVE-2026-22992 Référence CVE CVE-2026-22994 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.
Patch available
Affected
SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (6ES7518-4AX00-1AB0) >= V3.1.6; SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (6ES7518-4AX00-1AC0) >= V3.1.6; SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (6ES7518-4FX00-1AB0) >= V3.1.6; SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (6ES7518-4FX00-1AC0) >= V3.1.6; SIPLUS S7-1500 CPU 1518-4 PN/DP MFP (6AG1518-4AX00-4AC0) >= V3.1.6
Fixed
< 6.9; 6.1.161 ≤ 6.1.*; 6.6.121 ≤ 6.6.*; 6.12.66 ≤ 6.12.*; 6.18.6 ≤ 6.18.*; 6.19 ≤ *
Action
Review the linked authoritative reference and apply the recorded fixed release appropriate to the affected product branch.
Workaround
Limit access to the interactive shell of the additional GNU/Linux subssytem to trusted personnel only.
04

Evidence and provenance

Published 23 Jan 2026 · Last source change 8 Sept 2026, 08:44 UTC · CWE-401 · Missing Release of Memory after Effective Lifetime

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-4307
Product sourceVendor CSAF · Siemens ProductCERT
Remediation sourceVendor CSAF · Siemens ProductCERT
CWE sourceNIST NVD
NVD statusNVD modified after enrichment

Core structured fields are present and their contributing authorities are shown above.

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-4307↗Vendor CSAF · Siemens ProductCERT↗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-22979 · cve.blacktree.nl