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

nfsd: fix heap overflow in NFSv4.0 LOCK replay cache

Linux · Linux

9.8CriticalCVSS 3.1
Recommended action
Within 72 hours

Critical technical impact with a remotely reachable, unauthenticated path; no CISA KEV confirmation is currently recorded.

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 8 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 8 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 8 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 8 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 8 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 8 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 8 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 8 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 8 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 8 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 8 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 8 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 8 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 8 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 8 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 8 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 8 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 8 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 8 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 8 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: nfsd: fix heap overflow in NFSv4.0 LOCK replay cache The NFSv4.0 replay cache uses a fixed 112-byte inline buffer (rp_ibuf[NFSD4_REPLAY_ISIZE]) to store encoded operation responses. This size was calculated based on OPEN responses and does not account for LOCK denied responses, which include the conflicting lock owner as a variable-length field up to 1024 bytes (NFS4_OPAQUE_LIMIT). When a LOCK operation is denied due to a conflict with an existing lock that has a large owner, nfsd4_encode_operation() copies the full encoded response into the undersized replay buffer via read_bytes_from_xdr_buf() with no bounds check. This results in a slab-out-of-bounds write of up to 944 bytes past the end of the buffer, corrupting adjacent heap memory. This can be triggered remotely by an unauthenticated attacker with two cooperating NFSv4.0 clients: one sets a lock with a large owner string, then the other requests a conflicting lock to provoke the denial. We could fix this by increasing NFSD4_REPLAY_ISIZE to allow for a full opaque, but that would increase the size of every stateowner, when most lockowners are not that large. Instead, fix this by checking the encoded response length against NFSD4_REPLAY_ISIZE before copying into the replay buffer. If the response is too large, set rp_buflen to 0 to skip caching the replay payload. The status is still cached, and the client already received the correct response on the original request.
Remediation
Limit access to the interactive shell of the additional GNU/Linux subssytem to trusted personnel only.
SSA-082556 · CSAF 2.0 · revision 7 · interimSiemens ProductCERTSSA-082556: Vulnerabilities in the additional GNU/Linux subsystem of the SIMATIC S7-1500 CPU 1518(F)-4 PN/DP MFP V3.1.5
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.5
  • SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (6ES7518-4AX00-1AC0) >= V3.1.5
  • SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (6ES7518-4FX00-1AB0) >= V3.1.5
  • SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (6ES7518-4FX00-1AC0) >= V3.1.5
  • SIPLUS S7-1500 CPU 1518-4 PN/DP MFP (6AG1518-4AX00-4AC0) >= V3.1.5
Summary
In the Linux kernel, the following vulnerability has been resolved: nfsd: fix heap overflow in NFSv4.0 LOCK replay cache The NFSv4.0 replay cache uses a fixed 112-byte inline buffer (rp_ibuf[NFSD4_REPLAY_ISIZE]) to store encoded operation responses. This size was calculated based on OPEN responses and does not account for LOCK denied responses, which include the conflicting lock owner as a variable-length field up to 1024 bytes (NFS4_OPAQUE_LIMIT). When a LOCK operation is denied due to a conflict with an existing lock that has a large owner, nfsd4_encode_operation() copies the full encoded response into the undersized replay buffer via read_bytes_from_xdr_buf() with no bounds check. This results in a slab-out-of-bounds write of up to 944 bytes past the end of the buffer, corrupting adjacent heap memory. This can be triggered remotely by an unauthenticated attacker with two cooperating NFSv4.0 clients: one sets a lock with a large owner string, then the other requests a conflicting lock to provoke the denial. We could fix this by increasing NFSD4_REPLAY_ISIZE to allow for a full opaque, but that would increase the size of every stateowner, when most lockowners are not that large. Instead, fix this by checking the encoded response length against NFSD4_REPLAY_ISIZE before copying into the replay buffer. If the response is too large, set rp_buflen to 0 to skip caching the replay payload. The status is still cached, and the client already received the correct response on the original request.
Remediation
Limit access to the interactive shell of the additional GNU/Linux subssytem to trusted personnel only.
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-18786

No EUVD known-exploited evidence

In the Linux kernel, the following vulnerability has been resolved: nfsd: fix heap overflow in NFSv4.0 LOCK replay cache The NFSv4.0 replay cache uses a fixed 112-byte inline buffer (rp_ibuf[NFSD4_REPLAY_ISIZE]) to store encoded operation responses. This size was calculated based on OPEN responses and does not account for LOCK denied responses, which include the conflicting lock owner as a variable-length field up to 1024 bytes (NFS4_OPAQUE_LIMIT). When a LOCK operation is denied due to a conflict with an existing lock that has a large owner, nfsd4_encode_operation() copies the full encoded response into the undersized replay buffer via read_bytes_from_xdr_buf() with no bounds check. This results in a slab-out-of-bounds write of up to 944 bytes past the end of the buffer, corrupting adjacent heap memory. This can be triggered remotely by an unauthenticated attacker with two cooperating NFSv4.0 clients: one sets a lock with a large owner string, then the other requests a conflicting lock to provoke the denial. We could fix this by increasing NFSD4_REPLAY_ISIZE to allow for a full opaque, but that would increase the size of every stateowner, when most lockowners are not that large. Instead, fix this by checking the encoded response length against NFSD4_REPLAY_ISIZE before copying into the replay buffer. If the response is too large, set rp_buflen to 0 to skip caching the replay payload. The status is still cached, and the client already received the correct response on the original request.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
9.8 · CVSS 3.1
Advisory evidence
No linked advisory details stored yet
Recommended actionWithin 72 hours

Critical technical impact with a remotely reachable, unauthenticated path; no CISA KEV confirmation is currently recorded.

Patch available
01

What, why and how

In the Linux kernel, the following vulnerability has been resolved: nfsd: fix heap overflow in NFSv4.0 LOCK replay cache The NFSv4.0 replay cache uses a fixed 112-byte inline buffer (rp_ibuf[NFSD4_REPLAY_ISIZE]) to store encoded operation responses. This size was calculated based on OPEN responses and does not account for LOCK denied responses, which include the conflicting lock owner as a variable-length field up to 1024 bytes (NFS4_OPAQUE_LIMIT). When a LOCK operation is denied due to a conflict with an existing lock that has a large owner, nfsd4_encode_operation() copies the full encoded response into the undersized replay buffer via read_bytes_from_xdr_buf() with no bounds check. This results in a slab-out-of-bounds write of up to 944 bytes past the end of the buffer, corrupting adjacent heap memory. This can be triggered remotely by an unauthenticated attacker with two cooperating NFSv4.0 clients: one sets a lock with a large owner string, then the other requests a conflicting lock to provoke the denial. We could fix this by increasing NFSD4_REPLAY_ISIZE to allow for a full opaque, but that would increase the size of every stateowner, when most lockowners are not that large. Instead, fix this by checking the encoded response length against NFSD4_REPLAY_ISIZE before copying into the replay buffer. If the response is too large, set rp_buflen to 0 to skip caching the replay payload. The status is still cached, and the client already received the correct response on the original request.

What

In the Linux kernel, the following vulnerability has been resolved: nfsd: fix heap overflow in NFSv4.0 LOCK replay cache The NFSv4.0 replay cache uses a fixed 112-byte inline buffer (rp_ibuf[NFSD4_REPLAY_ISIZE]) to store encoded operation responses. This size was calculated based on OPEN responses and does not account for LOCK denied responses, which include the conflicting lock owner as a variable-length field up to 1024 bytes (NFS4_OPAQUE_LIMIT). When a LOCK operation is denied due to a conflict with an existing lock that has a large owner, nfsd4_encode_operation() copies the full encoded response into the undersized replay buffer via read_bytes_from_xdr_buf() with no bounds check. This results in a slab-out-of-bounds write of up to 944 bytes past the end of the buffer, corrupting adjacent heap memory. This can be triggered remotely by an unauthenticated attacker with two cooperating NFSv4.0 clients: one sets a lock with a large owner string, then the other requests a conflicting lock to provoke the denial. We could fix this by increasing NFSD4_REPLAY_ISIZE to allow for a full opaque, but that would increase the size of every stateowner, when most lockowners are not that large. Instead, fix this by checking the encoded response length against NFSD4_REPLAY_ISIZE before copying into the replay buffer. If the response is too large, set rp_buflen to 0 to skip caching the replay payload. The status is still cached, and the client already received the correct response on the original request.

Why

A bounds error lets data be written beyond the intended memory region, potentially corrupting control data.

How

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

What

In the Linux kernel, the following vulnerability has been resolved: nfsd: fix heap overflow in NFSv4.0 LOCK replay cache The NFSv4.0 replay cache uses a fixed 112-byte inline buffer (rp_ibuf[NFSD4_REPLAY_ISIZE]) to store encoded operation responses. This size was calculated based on OPEN responses and does not account for LOCK denied responses, which include the conflicting lock owner as a variable-length field up to 1024 bytes (NFS4_OPAQUE_LIMIT). When a LOCK operation is denied due to a conflict with an existing lock that has a large owner, nfsd4_encode_operation() copies the full encoded response into the undersized replay buffer via read_bytes_from_xdr_buf() with no bounds check. This results in a slab-out-of-bounds write of up to 944 bytes past the end of the buffer, corrupting adjacent heap memory. This can be triggered remotely by an unauthenticated attacker with two cooperating NFSv4.0 clients: one sets a lock with a large owner string, then the other requests a conflicting lock to provoke the denial. We could fix this by increasing NFSD4_REPLAY_ISIZE to allow for a full opaque, but that would increase the size of every stateowner, when most lockowners are not that large. Instead, fix this by checking the encoded response length against NFSD4_REPLAY_ISIZE before copying into the replay buffer. If the response is too large, set rp_buflen to 0 to skip caching the replay payload. The status is still cached, and the client already received the correct response on the original request.

Why

A bounds error lets data be written beyond the intended memory region, potentially corrupting control data.

How

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

02

Exploit reality and attack path

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

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

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

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

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

Likely attack path
a network path → Out-of-bounds Write → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Network
Privileges required
None: unauthenticated exploitation is possible
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-787 ↗

CWE-787: Out-of-bounds Write. The product writes data past the end, or before the beginning, of the intended buffer.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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

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

Official authority intelligence

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

ENISA EUVD · EUVD-2026-18786Official EUVD mapping

In the Linux kernel, the following vulnerability has been resolved: nfsd: fix heap overflow in NFSv4.0 LOCK replay cache The NFSv4.0 replay cache uses a fixed 112-byte inline buffer (rp_ibuf[NFSD4_REPLAY_ISIZE]) to store encoded operation responses. This size was calculated based on OPEN responses and does not account for LOCK denied responses, which include the conflicting lock owner as a variable-length field up to 1024 bytes (NFS4_OPAQUE_LIMIT). When a LOCK operation is denied due to a conflict with an existing lock that has a large owner, nfsd4_encode_operation() copies the full encoded response into the undersized replay buffer via read_bytes_from_xdr_buf() with no bounds check. This results in a slab-out-of-bounds write of up to 944 bytes past the end of the buffer, corrupting adjacent heap memory. This can be triggered remotely by an unauthenticated attacker with two cooperating NFSv4.0 clients: one sets a lock with a large owner string, then the other requests a conflicting lock to provoke the denial. We could fix this by increasing NFSD4_REPLAY_ISIZE to allow for a full opaque, but that would increase the size of every stateowner, when most lockowners are not that large. Instead, fix this by checking the encoded response length against NFSD4_REPLAY_ISIZE before copying into the replay buffer. If the response is too large, set rp_buflen to 0 to skip caching the replay payload. The status is still cached, and the client already received the correct response on the original request.

Official EUVD record
BSI · German · WID-SEC-W-2026-2253IBM Security Verify Access: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in IBM Security Verify Access ausnutzen, um erweiterte Berechtigungen zu erlangen, beliebigen Code auszuführen, Sicherheitsmaßnahmen zu umgehen, Daten zu manipulieren, sensible Informationen offenzulegen und andere, nicht näher bezeichnete Angriffe durchzuführen.

Official advisory
BSI · German · WID-SEC-W-2026-1666IBM QRadar SIEM: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in IBM QRadar SIEM ausnutzen, um beliebigen Programmcode auszuführen, um seine Privilegien zu erhöhen, um einen Denial of Service Angriff durchzuführen, um Informationen offenzulegen, und um Sicherheitsvorkehrungen zu umgehen.

Official advisory
BSI · German · WID-SEC-W-2026-0985Linux Kernel: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um unter anderem einen Denial of Service-Angriff auszuführen oder um Sicherheitsmechanismen zu umgehen.

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

d?id=CVE-2026-23458 Référence CVE CVE-2026-23460 https://www.cve.org/CVERecord?id=CVE-2026-23460 Référence CVE CVE-2026-23462 https://www.cve.org/CVERecord?id=CVE-2026-23462 Référence CVE CVE-2026-23463 https://www.cve.org/CVERecord?id=CVE-2026-23463 Référence CVE CVE-2026-23474 https://www.cve.org/CVERecord?id=CVE-2026-23474 Référence CVE CVE-2026-31393 https://www.cve.org/CVERecord?id=CVE-2026-31393 Référence CVE CVE-2026-31396 https://www.cve.org/CVERecord?id=CVE-2026-31396 Référence CVE CVE-2026-31399 https://www.cve.org/CVERecord?id=CVE-2026-31399 Référence CVE CVE-2026-31400 https://www.cve.org/CVERecord?id=CVE-2026-31400 Référence CVE CVE-2026-31402 https://www.cve.org/CVERecord?id=CVE-2026-31402 Référence CVE CVE-2026-31405 https://www.cve.org/CVERecord?id=CVE-2026-31405 Référence CVE CVE-2026-31407 https://www.cve.org/CVERecord?id=CVE-2026-31407 Référence CVE CVE-2026-31408 https://www.cve.org/CVERecord?id=CVE-2026-31408 Référence CVE CVE-2026-31409 https://www.cve.org/CVERecord?id=CVE-2026-31409 Référence CVE CVE-2026-31411 https://www.cve.org/CVERecord?id=CVE-2026-31411 Référence CVE CVE-2026-31414 https://www.cve.org/CVERecord?id=CVE-2026-31414 Référence CVE CVE-2026-31415 https://www.cve.org/CVERecord?id=CVE-2026-31415 Référence CVE CVE-2026-31416 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2021-47202 Référence CVE CVE-2021-47354 https://www.cve.org/CVERecord?id=CVE-2021-47354 Référence CVE CVE-2021-47378 https://www.cve.org/CVERecord?id=CVE-2021-47378 Référence CVE CVE-2023-52646 https://www.cve.org/CVERecord?id=CVE-2023-52646 Référence CVE CVE-2024-38612 https://www.cve.org/CVERecord?id=CVE-2024-38612 Référence CVE CVE-2024-56643 https://www.cve.org/CVERecord?id=CVE-2024-56643 Référence CVE CVE-2025-27558 https://www.cve.org/CVERecord?id=CVE-2025-27558 Référence CVE CVE-2026-23272 https://www.cve.org/CVERecord?id=CVE-2026-23272 Référence CVE CVE-2026-23455 https://www.cve.org/CVERecord?id=CVE-2026-23455 Référence CVE CVE-2026-31402 https://www.cve.org/CVERecord?id=CVE-2026-31402 Référence CVE CVE-2026-31405 https://www.cve.org/CVERecord?id=CVE-2026-31405 Référence CVE CVE-2026-31414 https://www.cve.org/CVERecord?id=CVE-2026-31414 Référence CVE CVE-2026-31448 https://www.cve.org/CVERecord?id=CVE-2026-31448 Référence CVE CVE-2026-31501 https://www.cve.org/CVERecord?id=CVE-2026-31501 Référence CVE CVE-2026-31589 https://www.cve.org/CVERecord?id=CVE-2026-31589 Référence CVE CVE-2026-31607 https://www.cve.org/CVERecord?id=CVE-2026-31607 Référence CVE CVE-2026-31633 https://www.cve.org/CVERecord?id=CVE-2026-31633 Référence CVE CVE-2026-31636 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-23475 Référence CVE CVE-2026-31389 https://www.cve.org/CVERecord?id=CVE-2026-31389 Référence CVE CVE-2026-31391 https://www.cve.org/CVERecord?id=CVE-2026-31391 Référence CVE CVE-2026-31392 https://www.cve.org/CVERecord?id=CVE-2026-31392 Référence CVE CVE-2026-31393 https://www.cve.org/CVERecord?id=CVE-2026-31393 Référence CVE CVE-2026-31394 https://www.cve.org/CVERecord?id=CVE-2026-31394 Référence CVE CVE-2026-31396 https://www.cve.org/CVERecord?id=CVE-2026-31396 Référence CVE CVE-2026-31399 https://www.cve.org/CVERecord?id=CVE-2026-31399 Référence CVE CVE-2026-31400 https://www.cve.org/CVERecord?id=CVE-2026-31400 Référence CVE CVE-2026-31402 https://www.cve.org/CVERecord?id=CVE-2026-31402 Référence CVE CVE-2026-31403 https://www.cve.org/CVERecord?id=CVE-2026-31403 Référence CVE CVE-2026-31405 https://www.cve.org/CVERecord?id=CVE-2026-31405 Référence CVE CVE-2026-31407 https://www.cve.org/CVERecord?id=CVE-2026-31407 Référence CVE CVE-2026-31408 https://www.cve.org/CVERecord?id=CVE-2026-31408 Référence CVE CVE-2026-31409 https://www.cve.org/CVERecord?id=CVE-2026-31409 Référence CVE CVE-2026-31411 https://www.cve.org/CVERecord?id=CVE-2026-31411 Référence CVE CVE-2026-31412 https://www.cve.org/CVERecord?id=CVE-2026-31412 Référence CVE CVE-2026-31413 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-23475 Référence CVE CVE-2026-31389 https://www.cve.org/CVERecord?id=CVE-2026-31389 Référence CVE CVE-2026-31391 https://www.cve.org/CVERecord?id=CVE-2026-31391 Référence CVE CVE-2026-31392 https://www.cve.org/CVERecord?id=CVE-2026-31392 Référence CVE CVE-2026-31393 https://www.cve.org/CVERecord?id=CVE-2026-31393 Référence CVE CVE-2026-31394 https://www.cve.org/CVERecord?id=CVE-2026-31394 Référence CVE CVE-2026-31396 https://www.cve.org/CVERecord?id=CVE-2026-31396 Référence CVE CVE-2026-31399 https://www.cve.org/CVERecord?id=CVE-2026-31399 Référence CVE CVE-2026-31400 https://www.cve.org/CVERecord?id=CVE-2026-31400 Référence CVE CVE-2026-31402 https://www.cve.org/CVERecord?id=CVE-2026-31402 Référence CVE CVE-2026-31403 https://www.cve.org/CVERecord?id=CVE-2026-31403 Référence CVE CVE-2026-31405 https://www.cve.org/CVERecord?id=CVE-2026-31405 Référence CVE CVE-2026-31407 https://www.cve.org/CVERecord?id=CVE-2026-31407 Référence CVE CVE-2026-31408 https://www.cve.org/CVERecord?id=CVE-2026-31408 Référence CVE CVE-2026-31409 https://www.cve.org/CVERecord?id=CVE-2026-31409 Référence CVE CVE-2026-31411 https://www.cve.org/CVERecord?id=CVE-2026-31411 Référence CVE CVE-2026-31412 https://www.cve.org/CVERecord?id=CVE-2026-31412 Référence CVE CVE-2026-31413 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-23258 Référence CVE CVE-2026-23262 https://www.cve.org/CVERecord?id=CVE-2026-23262 Référence CVE CVE-2026-23272 https://www.cve.org/CVERecord?id=CVE-2026-23272 Référence CVE CVE-2026-23278 https://www.cve.org/CVERecord?id=CVE-2026-23278 Référence CVE CVE-2026-23392 https://www.cve.org/CVERecord?id=CVE-2026-23392 Référence CVE CVE-2026-23427 https://www.cve.org/CVERecord?id=CVE-2026-23427 Référence CVE CVE-2026-23428 https://www.cve.org/CVERecord?id=CVE-2026-23428 Référence CVE CVE-2026-23450 https://www.cve.org/CVERecord?id=CVE-2026-23450 Référence CVE CVE-2026-23455 https://www.cve.org/CVERecord?id=CVE-2026-23455 Référence CVE CVE-2026-31402 https://www.cve.org/CVERecord?id=CVE-2026-31402 Référence CVE CVE-2026-31418 https://www.cve.org/CVERecord?id=CVE-2026-31418 Référence CVE CVE-2026-31436 https://www.cve.org/CVERecord?id=CVE-2026-31436 Référence CVE CVE-2026-31448 https://www.cve.org/CVERecord?id=CVE-2026-31448 Référence CVE CVE-2026-31478 https://www.cve.org/CVERecord?id=CVE-2026-31478 Référence CVE CVE-2026-31607 https://www.cve.org/CVERecord?id=CVE-2026-31607 Référence CVE CVE-2026-31635 https://www.cve.org/CVERecord?id=CVE-2026-31635 Référence CVE CVE-2026-31637 https://www.cve.org/CVERecord?id=CVE-2026-31637 Référence CVE CVE-2026-31649 https://www.cve.org/CVERecord?id=

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

26-23293, CVE-2026-23300, CVE-2026-23304, CVE-2026-23319, CVE-2026-23321, CVE-2026-23335, CVE-2026-23340, CVE-2026-23343, CVE-2026-23351, CVE-2026-23359, CVE-2026-23365, CVE-2026-23368, CVE-2026-23370, CVE-2026-23378, CVE-2026-23379, CVE-2026-23381, CVE-2026-23391, CVE-2026-23392, CVE-2026-23397, CVE-2026-23398, CVE-2026-23414, CVE-2026-23422, CVE-2026-23434, CVE-2026-23438, CVE-2026-23439, CVE-2026-23446, CVE-2026-23449, CVE-2026-23450, CVE-2026-23452, CVE-2026-23454, CVE-2026-23455, CVE-2026-23456, CVE-2026-23457, CVE-2026-23458, CVE-2026-23463, CVE-2026-23474, CVE-2026-23475, CVE-2026-27135, CVE-2026-31389, CVE-2026-31391, CVE-2026-31396, CVE-2026-31402, CVE-2026-31403, CVE-2026-31411, CVE-2026-31414, CVE-2026-31415, CVE-2026-31416, CVE-2026-31417, CVE-2026-31418, CVE-2026-31421, CVE-2026-31422, CVE-2026-31423, CVE-2026-31424, CVE-2026-31427, CVE-2026-31428, CVE-2026-31431, CVE-2026-31441, CVE-2026-31446, CVE-2026-31447, CVE-2026-31448, CVE-2026-31450, CVE-2026-31452, CVE-2026-31466, CVE-2026-31469, CVE-2026-31485, CVE-2026-31494, CVE-2026-31495, CVE-2026-31496, CVE-2026-31503, CVE-2026-31504, CVE-2026-31507, CVE-2026-31508, CVE-2026-31515, CVE-2026-31518, CVE-2026-31521, CVE-2026-31533, CVE-2026-31546, CVE-2026-31555, CVE-2026-31563, CVE-2026-31565, CVE-2026-31628, CVE-2026-31634, CVE-2026

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

d?id=CVE-2025-71294 Référence CVE CVE-2026-23278 https://www.cve.org/CVERecord?id=CVE-2026-23278 Référence CVE CVE-2026-23303 https://www.cve.org/CVERecord?id=CVE-2026-23303 Référence CVE CVE-2026-23327 https://www.cve.org/CVERecord?id=CVE-2026-23327 Référence CVE CVE-2026-23359 https://www.cve.org/CVERecord?id=CVE-2026-23359 Référence CVE CVE-2026-23438 https://www.cve.org/CVERecord?id=CVE-2026-23438 Référence CVE CVE-2026-23444 https://www.cve.org/CVERecord?id=CVE-2026-23444 Référence CVE CVE-2026-23451 https://www.cve.org/CVERecord?id=CVE-2026-23451 Référence CVE CVE-2026-31396 https://www.cve.org/CVERecord?id=CVE-2026-31396 Référence CVE CVE-2026-31402 https://www.cve.org/CVERecord?id=CVE-2026-31402 Référence CVE CVE-2026-31414 https://www.cve.org/CVERecord?id=CVE-2026-31414 Référence CVE CVE-2026-31429 https://www.cve.org/CVERecord?id=CVE-2026-31429 Référence CVE CVE-2026-31446 https://www.cve.org/CVERecord?id=CVE-2026-31446 Référence CVE CVE-2026-31448 https://www.cve.org/CVERecord?id=CVE-2026-31448 Référence CVE CVE-2026-31450 https://www.cve.org/CVERecord?id=CVE-2026-31450 Référence CVE CVE-2026-31452 https://www.cve.org/CVERecord?id=CVE-2026-31452 Référence CVE CVE-2026-31453 https://www.cve.org/CVERecord?id=CVE-2026-31453 Référence CVE CVE-2026-31454 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-23274 Référence CVE CVE-2026-23278 https://www.cve.org/CVERecord?id=CVE-2026-23278 Référence CVE CVE-2026-23351 https://www.cve.org/CVERecord?id=CVE-2026-23351 Référence CVE CVE-2026-23392 https://www.cve.org/CVERecord?id=CVE-2026-23392 Référence CVE CVE-2026-23394 https://www.cve.org/CVERecord?id=CVE-2026-23394 Référence CVE CVE-2026-23427 https://www.cve.org/CVERecord?id=CVE-2026-23427 Référence CVE CVE-2026-23428 https://www.cve.org/CVERecord?id=CVE-2026-23428 Référence CVE CVE-2026-23450 https://www.cve.org/CVERecord?id=CVE-2026-23450 Référence CVE CVE-2026-23455 https://www.cve.org/CVERecord?id=CVE-2026-23455 Référence CVE CVE-2026-31402 https://www.cve.org/CVERecord?id=CVE-2026-31402 Référence CVE CVE-2026-31411 https://www.cve.org/CVERecord?id=CVE-2026-31411 Référence CVE CVE-2026-31418 https://www.cve.org/CVERecord?id=CVE-2026-31418 Référence CVE CVE-2026-31419 https://www.cve.org/CVERecord?id=CVE-2026-31419 Référence CVE CVE-2026-31431 https://www.cve.org/CVERecord?id=CVE-2026-31431 Référence CVE CVE-2026-31436 https://www.cve.org/CVERecord?id=CVE-2026-31436 Référence CVE CVE-2026-31448 https://www.cve.org/CVERecord?id=CVE-2026-31448 Référence CVE CVE-2026-31478 https://www.cve.org/CVERecord?id=CVE-2026-31478 Référence CVE CVE-2026-31504 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-68822 Référence CVE CVE-2026-23278 https://www.cve.org/CVERecord?id=CVE-2026-23278 Référence CVE CVE-2026-23303 https://www.cve.org/CVERecord?id=CVE-2026-23303 Référence CVE CVE-2026-23327 https://www.cve.org/CVERecord?id=CVE-2026-23327 Référence CVE CVE-2026-23359 https://www.cve.org/CVERecord?id=CVE-2026-23359 Référence CVE CVE-2026-23392 https://www.cve.org/CVERecord?id=CVE-2026-23392 Référence CVE CVE-2026-23438 https://www.cve.org/CVERecord?id=CVE-2026-23438 Référence CVE CVE-2026-23444 https://www.cve.org/CVERecord?id=CVE-2026-23444 Référence CVE CVE-2026-31396 https://www.cve.org/CVERecord?id=CVE-2026-31396 Référence CVE CVE-2026-31402 https://www.cve.org/CVERecord?id=CVE-2026-31402 Référence CVE CVE-2026-31405 https://www.cve.org/CVERecord?id=CVE-2026-31405 Référence CVE CVE-2026-31414 https://www.cve.org/CVERecord?id=CVE-2026-31414 Référence CVE CVE-2026-31429 https://www.cve.org/CVERecord?id=CVE-2026-31429 Référence CVE CVE-2026-31446 https://www.cve.org/CVERecord?id=CVE-2026-31446 Référence CVE CVE-2026-31448 https://www.cve.org/CVERecord?id=CVE-2026-31448 Référence CVE CVE-2026-31452 https://www.cve.org/CVERecord?id=CVE-2026-31452 Référence CVE CVE-2026-31453 https://www.cve.org/CVERecord?id=CVE-2026-31453 Référence CVE CVE-2026-31454 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-23274 Référence CVE CVE-2026-23278 https://www.cve.org/CVERecord?id=CVE-2026-23278 Référence CVE CVE-2026-23351 https://www.cve.org/CVERecord?id=CVE-2026-23351 Référence CVE CVE-2026-23392 https://www.cve.org/CVERecord?id=CVE-2026-23392 Référence CVE CVE-2026-23394 https://www.cve.org/CVERecord?id=CVE-2026-23394 Référence CVE CVE-2026-23427 https://www.cve.org/CVERecord?id=CVE-2026-23427 Référence CVE CVE-2026-23428 https://www.cve.org/CVERecord?id=CVE-2026-23428 Référence CVE CVE-2026-23450 https://www.cve.org/CVERecord?id=CVE-2026-23450 Référence CVE CVE-2026-23455 https://www.cve.org/CVERecord?id=CVE-2026-23455 Référence CVE CVE-2026-31402 https://www.cve.org/CVERecord?id=CVE-2026-31402 Référence CVE CVE-2026-31411 https://www.cve.org/CVERecord?id=CVE-2026-31411 Référence CVE CVE-2026-31418 https://www.cve.org/CVERecord?id=CVE-2026-31418 Référence CVE CVE-2026-31419 https://www.cve.org/CVERecord?id=CVE-2026-31419 Référence CVE CVE-2026-31431 https://www.cve.org/CVERecord?id=CVE-2026-31431 Référence CVE CVE-2026-31436 https://www.cve.org/CVERecord?id=CVE-2026-31436 Référence CVE CVE-2026-31448 https://www.cve.org/CVERecord?id=CVE-2026-31448 Référence CVE CVE-2026-31478 https://www.cve.org/CVERecord?id=CVE-2026-31478 Référence CVE CVE-2026-31504 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-68324 Référence CVE CVE-2026-23278 https://www.cve.org/CVERecord?id=CVE-2026-23278 Référence CVE CVE-2026-23303 https://www.cve.org/CVERecord?id=CVE-2026-23303 Référence CVE CVE-2026-23327 https://www.cve.org/CVERecord?id=CVE-2026-23327 Référence CVE CVE-2026-23359 https://www.cve.org/CVERecord?id=CVE-2026-23359 Référence CVE CVE-2026-23392 https://www.cve.org/CVERecord?id=CVE-2026-23392 Référence CVE CVE-2026-23438 https://www.cve.org/CVERecord?id=CVE-2026-23438 Référence CVE CVE-2026-23444 https://www.cve.org/CVERecord?id=CVE-2026-23444 Référence CVE CVE-2026-31396 https://www.cve.org/CVERecord?id=CVE-2026-31396 Référence CVE CVE-2026-31402 https://www.cve.org/CVERecord?id=CVE-2026-31402 Référence CVE CVE-2026-31405 https://www.cve.org/CVERecord?id=CVE-2026-31405 Référence CVE CVE-2026-31446 https://www.cve.org/CVERecord?id=CVE-2026-31446 Référence CVE CVE-2026-31448 https://www.cve.org/CVERecord?id=CVE-2026-31448 Référence CVE CVE-2026-31454 https://www.cve.org/CVERecord?id=CVE-2026-31454 Référence CVE CVE-2026-31455 https://www.cve.org/CVERecord?id=CVE-2026-31455 Référence CVE CVE-2026-31464 https://www.cve.org/CVERecord?id=CVE-2026-31464 Référence CVE CVE-2026-31473 https://www.cve.org/CVERecord?id=CVE-2026-31473 Référence CVE CVE-2026-31480 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-54518 Référence CVE CVE-2026-23243 https://www.cve.org/CVERecord?id=CVE-2026-23243 Référence CVE CVE-2026-23271 https://www.cve.org/CVERecord?id=CVE-2026-23271 Référence CVE CVE-2026-23274 https://www.cve.org/CVERecord?id=CVE-2026-23274 Référence CVE CVE-2026-23317 https://www.cve.org/CVERecord?id=CVE-2026-23317 Référence CVE CVE-2026-23359 https://www.cve.org/CVERecord?id=CVE-2026-23359 Référence CVE CVE-2026-23380 https://www.cve.org/CVERecord?id=CVE-2026-23380 Référence CVE CVE-2026-23437 https://www.cve.org/CVERecord?id=CVE-2026-23437 Référence CVE CVE-2026-23444 https://www.cve.org/CVERecord?id=CVE-2026-23444 Référence CVE CVE-2026-31402 https://www.cve.org/CVERecord?id=CVE-2026-31402 Référence CVE CVE-2026-31405 https://www.cve.org/CVERecord?id=CVE-2026-31405 Référence CVE CVE-2026-31406 https://www.cve.org/CVERecord?id=CVE-2026-31406 Référence CVE CVE-2026-31464 https://www.cve.org/CVERecord?id=CVE-2026-31464 Référence CVE CVE-2026-31473 https://www.cve.org/CVERecord?id=CVE-2026-31473 Référence CVE CVE-2026-31480 https://www.cve.org/CVERecord?id=CVE-2026-31480 Référence CVE CVE-2026-31483 https://www.cve.org/CVERecord?id=CVE-2026-31483 Référence CVE CVE-2026-31493 https://www.cve.org/CVERecord?id=CVE-2026-31493 Référence CVE CVE-2026-3150 https://www.cve.org/CVERecord?id=C

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

d?id=CVE-2026-23460 Référence CVE CVE-2026-23462 https://www.cve.org/CVERecord?id=CVE-2026-23462 Référence CVE CVE-2026-23463 https://www.cve.org/CVERecord?id=CVE-2026-23463 Référence CVE CVE-2026-23474 https://www.cve.org/CVERecord?id=CVE-2026-23474 Référence CVE CVE-2026-31391 https://www.cve.org/CVERecord?id=CVE-2026-31391 Référence CVE CVE-2026-31393 https://www.cve.org/CVERecord?id=CVE-2026-31393 Référence CVE CVE-2026-31396 https://www.cve.org/CVERecord?id=CVE-2026-31396 Référence CVE CVE-2026-31399 https://www.cve.org/CVERecord?id=CVE-2026-31399 Référence CVE CVE-2026-31400 https://www.cve.org/CVERecord?id=CVE-2026-31400 Référence CVE CVE-2026-31402 https://www.cve.org/CVERecord?id=CVE-2026-31402 Référence CVE CVE-2026-31403 https://www.cve.org/CVERecord?id=CVE-2026-31403 Référence CVE CVE-2026-31405 https://www.cve.org/CVERecord?id=CVE-2026-31405 Référence CVE CVE-2026-31411 https://www.cve.org/CVERecord?id=CVE-2026-31411 Référence CVE CVE-2026-31415 https://www.cve.org/CVERecord?id=CVE-2026-31415 Référence CVE CVE-2026-31416 https://www.cve.org/CVERecord?id=CVE-2026-31416 Référence CVE CVE-2026-31417 https://www.cve.org/CVERecord?id=CVE-2026-31417 Référence CVE CVE-2026-31418 https://www.cve.org/CVERecord?id=CVE-2026-31418 Référence CVE CVE-2026-31421 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-23473 Référence CVE CVE-2026-23474 https://www.cve.org/CVERecord?id=CVE-2026-23474 Référence CVE CVE-2026-23475 https://www.cve.org/CVERecord?id=CVE-2026-23475 Référence CVE CVE-2026-31389 https://www.cve.org/CVERecord?id=CVE-2026-31389 Référence CVE CVE-2026-31392 https://www.cve.org/CVERecord?id=CVE-2026-31392 Référence CVE CVE-2026-31393 https://www.cve.org/CVERecord?id=CVE-2026-31393 Référence CVE CVE-2026-31394 https://www.cve.org/CVERecord?id=CVE-2026-31394 Référence CVE CVE-2026-31395 https://www.cve.org/CVERecord?id=CVE-2026-31395 Référence CVE CVE-2026-31400 https://www.cve.org/CVERecord?id=CVE-2026-31400 Référence CVE CVE-2026-31402 https://www.cve.org/CVERecord?id=CVE-2026-31402 Référence CVE CVE-2026-31403 https://www.cve.org/CVERecord?id=CVE-2026-31403 Référence CVE CVE-2026-31404 https://www.cve.org/CVERecord?id=CVE-2026-31404 Référence CVE CVE-2026-31405 https://www.cve.org/CVERecord?id=CVE-2026-31405 Référence CVE CVE-2026-31406 https://www.cve.org/CVERecord?id=CVE-2026-31406 Référence CVE CVE-2026-31407 https://www.cve.org/CVERecord?id=CVE-2026-31407 Référence CVE CVE-2026-31408 https://www.cve.org/CVERecord?id=CVE-2026-31408 Référence CVE CVE-2026-31411 https://www.cve.org/CVERecord?id=CVE-2026-31411 Référence CVE CVE-2026-31412 https://www.cve.org/CVERecord?id=

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

ord?id=CVE-2026-27980 Référence CVE CVE-2026-28417 https://www.cve.org/CVERecord?id=CVE-2026-28417 Référence CVE CVE-2026-28421 https://www.cve.org/CVERecord?id=CVE-2026-28421 Référence CVE CVE-2026-29057 https://www.cve.org/CVERecord?id=CVE-2026-29057 Référence CVE CVE-2026-29063 https://www.cve.org/CVERecord?id=CVE-2026-29063 Référence CVE CVE-2026-2950 https://www.cve.org/CVERecord?id=CVE-2026-2950 Référence CVE CVE-2026-29786 https://www.cve.org/CVERecord?id=CVE-2026-29786 Référence CVE CVE-2026-30922 https://www.cve.org/CVERecord?id=CVE-2026-30922 Référence CVE CVE-2026-30951 https://www.cve.org/CVERecord?id=CVE-2026-30951 Référence CVE CVE-2026-31402 https://www.cve.org/CVERecord?id=CVE-2026-31402 Référence CVE CVE-2026-31431 https://www.cve.org/CVERecord?id=CVE-2026-31431 Référence CVE CVE-2026-31802 https://www.cve.org/CVERecord?id=CVE-2026-31802 Référence CVE CVE-2026-31808 https://www.cve.org/CVERecord?id=CVE-2026-31808 Référence CVE CVE-2026-31988 https://www.cve.org/CVERecord?id=CVE-2026-31988 Référence CVE CVE-2026-32141 https://www.cve.org/CVERecord?id=CVE-2026-32141 Référence CVE CVE-2026-32597 https://www.cve.org/CVERecord?id=CVE-2026-32597 Référence CVE CVE-2026-32874 https://www.cve.org/CVERecord?id=CVE-2026-32874 Référence CVE CVE-2026-32875 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-23456 Référence CVE CVE-2026-23457 https://www.cve.org/CVERecord?id=CVE-2026-23457 Référence CVE CVE-2026-23458 https://www.cve.org/CVERecord?id=CVE-2026-23458 Référence CVE CVE-2026-23461 https://www.cve.org/CVERecord?id=CVE-2026-23461 Référence CVE CVE-2026-23462 https://www.cve.org/CVERecord?id=CVE-2026-23462 Référence CVE CVE-2026-23468 https://www.cve.org/CVERecord?id=CVE-2026-23468 Référence CVE CVE-2026-23472 https://www.cve.org/CVERecord?id=CVE-2026-23472 Référence CVE CVE-2026-31393 https://www.cve.org/CVERecord?id=CVE-2026-31393 Référence CVE CVE-2026-31400 https://www.cve.org/CVERecord?id=CVE-2026-31400 Référence CVE CVE-2026-31402 https://www.cve.org/CVERecord?id=CVE-2026-31402 Référence CVE CVE-2026-31403 https://www.cve.org/CVERecord?id=CVE-2026-31403 Référence CVE CVE-2026-31407 https://www.cve.org/CVERecord?id=CVE-2026-31407 Référence CVE CVE-2026-31408 https://www.cve.org/CVERecord?id=CVE-2026-31408 Référence CVE CVE-2026-31411 https://www.cve.org/CVERecord?id=CVE-2026-31411 Référence CVE CVE-2026-31416 https://www.cve.org/CVERecord?id=CVE-2026-31416 Référence CVE CVE-2026-31422 https://www.cve.org/CVERecord?id=CVE-2026-31422 Référence CVE CVE-2026-31423 https://www.cve.org/CVERecord?id=CVE-2026-31423 Référence CVE CVE-2026-31424 https://www.cve.org/CVERecord?id=

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

De multiples vulnérabilités ont été découvertes dans le noyau Linux de Red Hat. Certaines d'entre elles permettent à un attaquant de provoquer une exécution de code arbitraire, une élévation de privilèges et une atteinte à la confidentialité des données.

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

De multiples vulnérabilités ont été découvertes dans le noyau Linux de Red Hat. Certaines d'entre elles permettent à un attaquant de provoquer une exécution de code arbitraire, une élévation de privilèges et un déni de service à distance.

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

d?id=CVE-2026-31389 Référence CVE CVE-2026-31391 https://www.cve.org/CVERecord?id=CVE-2026-31391 Référence CVE CVE-2026-31392 https://www.cve.org/CVERecord?id=CVE-2026-31392 Référence CVE CVE-2026-31393 https://www.cve.org/CVERecord?id=CVE-2026-31393 Référence CVE CVE-2026-31394 https://www.cve.org/CVERecord?id=CVE-2026-31394 Référence CVE CVE-2026-31396 https://www.cve.org/CVERecord?id=CVE-2026-31396 Référence CVE CVE-2026-31399 https://www.cve.org/CVERecord?id=CVE-2026-31399 Référence CVE CVE-2026-31400 https://www.cve.org/CVERecord?id=CVE-2026-31400 Référence CVE CVE-2026-31401 https://www.cve.org/CVERecord?id=CVE-2026-31401 Référence CVE CVE-2026-31402 https://www.cve.org/CVERecord?id=CVE-2026-31402 Référence CVE CVE-2026-31403 https://www.cve.org/CVERecord?id=CVE-2026-31403 Référence CVE CVE-2026-31405 https://www.cve.org/CVERecord?id=CVE-2026-31405 Référence CVE CVE-2026-31406 https://www.cve.org/CVERecord?id=CVE-2026-31406 Référence CVE CVE-2026-31407 https://www.cve.org/CVERecord?id=CVE-2026-31407 Référence CVE CVE-2026-31408 https://www.cve.org/CVERecord?id=CVE-2026-31408 Référence CVE CVE-2026-31409 https://www.cve.org/CVERecord?id=CVE-2026-31409 Référence CVE CVE-2026-31410 https://www.cve.org/CVERecord?id=CVE-2026-31410 Référence CVE CVE-2026-31411 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-23474 Référence CVE CVE-2026-23475 https://www.cve.org/CVERecord?id=CVE-2026-23475 Référence CVE CVE-2026-31389 https://www.cve.org/CVERecord?id=CVE-2026-31389 Référence CVE CVE-2026-31391 https://www.cve.org/CVERecord?id=CVE-2026-31391 Référence CVE CVE-2026-31392 https://www.cve.org/CVERecord?id=CVE-2026-31392 Référence CVE CVE-2026-31393 https://www.cve.org/CVERecord?id=CVE-2026-31393 Référence CVE CVE-2026-31396 https://www.cve.org/CVERecord?id=CVE-2026-31396 Référence CVE CVE-2026-31399 https://www.cve.org/CVERecord?id=CVE-2026-31399 Référence CVE CVE-2026-31400 https://www.cve.org/CVERecord?id=CVE-2026-31400 Référence CVE CVE-2026-31402 https://www.cve.org/CVERecord?id=CVE-2026-31402 Référence CVE CVE-2026-31403 https://www.cve.org/CVERecord?id=CVE-2026-31403 Référence CVE CVE-2026-31405 https://www.cve.org/CVERecord?id=CVE-2026-31405 Référence CVE CVE-2026-31408 https://www.cve.org/CVERecord?id=CVE-2026-31408 Référence CVE CVE-2026-31409 https://www.cve.org/CVERecord?id=CVE-2026-31409 Référence CVE CVE-2026-31411 https://www.cve.org/CVERecord?id=CVE-2026-31411 Référence CVE CVE-2026-31412 https://www.cve.org/CVERecord?id=CVE-2026-31412 Référence CVE CVE-2026-31414 https://www.cve.org/CVERecord?id=CVE-2026-31414 Référence CVE CVE-2026-31415 https://www.cve.org/CVERecord?id=

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

De multiples vulnérabilités ont été découvertes dans le noyau Linux de Red Hat. Certaines d'entre elles permettent à un attaquant de provoquer une exécution de code arbitraire, une élévation de privilèges et un déni de service à distance.

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
< 2.6.12; 5.10.253 ≤ 5.10.*; 5.15.210 ≤ 5.15.*; 6.1.167 ≤ 6.1.*; 6.6.130 ≤ 6.6.*; 6.12.78 ≤ 6.12.*; 6.18.20 ≤ 6.18.*; 6.19.10 ≤ 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 3 Apr 2026 · Last source change 8 Sept 2026, 08:46 UTC · CWE-787 · Out-of-bounds Write

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-18786
Product sourceVendor CSAF · Siemens ProductCERT
Remediation sourceVendor CSAF · Siemens ProductCERT
CWE sourceOther authority
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-18786↗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-31402 · cve.blacktree.nl