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

serial: 8250: fix panic due to PSLVERR

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.

21 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-intelAffected, 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-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: serial: 8250: fix panic due to PSLVERR When the PSLVERR_RESP_EN parameter is set to 1, the device generates an error response if an attempt is made to read an empty RBR (Receive Buffer Register) while the FIFO is enabled. In serial8250_do_startup(), calling serial_port_out(port, UART_LCR, UART_LCR_WLEN8) triggers dw8250_check_lcr(), which invokes dw8250_force_idle() and serial8250_clear_and_reinit_fifos(). The latter function enables the FIFO via serial_out(p, UART_FCR, p->fcr). Execution proceeds to the serial_port_in(port, UART_RX). This satisfies the PSLVERR trigger condition. When another CPU (e.g., using printk()) is accessing the UART (UART is busy), the current CPU fails the check (value & ~UART_LCR_SPAR) == (lcr & ~UART_LCR_SPAR) in dw8250_check_lcr(), causing it to enter dw8250_force_idle(). Put serial_port_out(port, UART_LCR, UART_LCR_WLEN8) under the port->lock to fix this issue. Panic backtrace: [ 0.442336] Oops - unknown exception [#1] [ 0.442343] epc : dw8250_serial_in32+0x1e/0x4a [ 0.442351] ra : serial8250_do_startup+0x2c8/0x88e ... [ 0.442416] console_on_rootfs+0x26/0x70
Remediation
Limit access to the interactive shell of the additional GNU/Linux subssytem to trusted personnel only.
SSA-032379 · CSAF 2.0 · revision 1 · interimSiemens ProductCERTSSA-032379: Multiple Vulnerabilities in SIMATIC CN 4100 Before V5.0
1 known affected

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

  • SIMATIC CN 4100
Summary
In the Linux kernel, the following vulnerability has been resolved: serial: 8250: fix panic due to PSLVERR When the PSLVERR_RESP_EN parameter is set to 1, the device generates an error response if an attempt is made to read an empty RBR (Receive Buffer Register) while the FIFO is enabled. In serial8250_do_startup(), calling serial_port_out(port, UART_LCR, UART_LCR_WLEN8) triggers dw8250_check_lcr(), which invokes dw8250_force_idle() and serial8250_clear_and_reinit_fifos(). The latter function enables the FIFO via serial_out(p, UART_FCR, p->fcr). Execution proceeds to the serial_port_in(port, UART_RX). This satisfies the PSLVERR trigger condition. When another CPU (e.g., using printk()) is accessing the UART (UART is busy), the current CPU fails the check (value & ~UART_LCR_SPAR) == (lcr & ~UART_LCR_SPAR) in dw8250_check_lcr(), causing it to enter dw8250_force_idle(). Put serial_port_out(port, UART_LCR, UART_LCR_WLEN8) under the port->lock to fix this issue. Panic backtrace: [ 0.442336] Oops - unknown exception [#1] [ 0.442343] epc : dw8250_serial_in32+0x1e/0x4a [ 0.442351] ra : serial8250_do_startup+0x2c8/0x88e ... [ 0.442416] console_on_rootfs+0x26/0x70
Remediation
Update to V5.0 or later version
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-2025-31503

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended 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: serial: 8250: fix panic due to PSLVERR When the PSLVERR_RESP_EN parameter is set to 1, the device generates an error response if an attempt is made to read an empty RBR (Receive Buffer Register) while the FIFO is enabled. In serial8250_do_startup(), calling serial_port_out(port, UART_LCR, UART_LCR_WLEN8) triggers dw8250_check_lcr(), which invokes dw8250_force_idle() and serial8250_clear_and_reinit_fifos(). The latter function enables the FIFO via serial_out(p, UART_FCR, p->fcr). Execution proceeds to the serial_port_in(port, UART_RX). This satisfies the PSLVERR trigger condition. When another CPU (e.g., using printk()) is accessing the UART (UART is busy), the current CPU fails the check (value & ~UART_LCR_SPAR) == (lcr & ~UART_LCR_SPAR) in dw8250_check_lcr(), causing it to enter dw8250_force_idle(). Put serial_port_out(port, UART_LCR, UART_LCR_WLEN8) under the port->lock to fix this issue. Panic backtrace: [ 0.442336] Oops - unknown exception [#1] [ 0.442343] epc : dw8250_serial_in32+0x1e/0x4a [ 0.442351] ra : serial8250_do_startup+0x2c8/0x88e ... [ 0.442416] console_on_rootfs+0x26/0x70

What

In the Linux kernel, the following vulnerability has been resolved: serial: 8250: fix panic due to PSLVERR When the PSLVERR_RESP_EN parameter is set to 1, the device generates an error response if an attempt is made to read an empty RBR (Receive Buffer Register) while the FIFO is enabled. In serial8250_do_startup(), calling serial_port_out(port, UART_LCR, UART_LCR_WLEN8) triggers dw8250_check_lcr(), which invokes dw8250_force_idle() and serial8250_clear_and_reinit_fifos(). The latter function enables the FIFO via serial_out(p, UART_FCR, p->fcr). Execution proceeds to the serial_port_in(port, UART_RX). This satisfies the PSLVERR trigger condition. When another CPU (e.g., using printk()) is accessing the UART (UART is busy), the current CPU fails the check (value & ~UART_LCR_SPAR) == (lcr & ~UART_LCR_SPAR) in dw8250_check_lcr(), causing it to enter dw8250_force_idle(). Put serial_port_out(port, UART_LCR, UART_LCR_WLEN8) under the port->lock to fix this issue. Panic backtrace: [ 0.442336] Oops - unknown exception [#1] [ 0.442343] epc : dw8250_serial_in32+0x1e/0x4a [ 0.442351] ra : serial8250_do_startup+0x2c8/0x88e ... [ 0.442416] console_on_rootfs+0x26/0x70

Why

The current structured CVE record identifies a security weakness, but the root cause requires confirmation in the linked vendor material.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

In the Linux kernel, the following vulnerability has been resolved: serial: 8250: fix panic due to PSLVERR When the PSLVERR_RESP_EN parameter is set to 1, the device generates an error response if an attempt is made to read an empty RBR (Receive Buffer Register) while the FIFO is enabled. In serial8250_do_startup(), calling serial_port_out(port, UART_LCR, UART_LCR_WLEN8) triggers dw8250_check_lcr(), which invokes dw8250_force_idle() and serial8250_clear_and_reinit_fifos(). The latter function enables the FIFO via serial_out(p, UART_FCR, p->fcr). Execution proceeds to the serial_port_in(port, UART_RX). This satisfies the PSLVERR trigger condition. When another CPU (e.g., using printk()) is accessing the UART (UART is busy), the current CPU fails the check (value & ~UART_LCR_SPAR) == (lcr & ~UART_LCR_SPAR) in dw8250_check_lcr(), causing it to enter dw8250_force_idle(). Put serial_port_out(port, UART_LCR, UART_LCR_WLEN8) under the port->lock to fix this issue. Panic backtrace: [ 0.442336] Oops - unknown exception [#1] [ 0.442343] epc : dw8250_serial_in32+0x1e/0x4a [ 0.442351] ra : serial8250_do_startup+0x2c8/0x88e ... [ 0.442416] console_on_rootfs+0x26/0x70

Why

The current structured CVE record identifies a security weakness, but the root cause requires confirmation in the linked vendor material.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

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

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

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

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

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

Likely attack path
local access → vulnerable operation → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Local
Privileges required
Low: a basic authenticated account is required
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration.
CWE not yet assigned
CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

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

AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRLowPrivileges required: The attacker needs basic user-level privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CNoneConfidentiality impact: No direct loss is represented by this metric.INoneIntegrity impact: No direct loss is represented by this metric.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.
A

Official authority intelligence

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

BSI · German · WID-SEC-W-2026-0349Dell Avamar und NetWorker: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in Dell Avamar und Dell NetWorker ausnutzen, um Angriffe zu starten, die die Integrität, Vertraulichkeit und Verfügbarkeit von Systemen beeinträchtigen.

Official advisory
BSI · German · WID-SEC-W-2025-1988Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service

Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder nicht näher spezifizierte Auswirkungen zu erzielen.

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

d?id=CVE-2025-39706 Référence CVE CVE-2025-39709 https://www.cve.org/CVERecord?id=CVE-2025-39709 Référence CVE CVE-2025-39710 https://www.cve.org/CVERecord?id=CVE-2025-39710 Référence CVE CVE-2025-39713 https://www.cve.org/CVERecord?id=CVE-2025-39713 Référence CVE CVE-2025-39714 https://www.cve.org/CVERecord?id=CVE-2025-39714 Référence CVE CVE-2025-39715 https://www.cve.org/CVERecord?id=CVE-2025-39715 Référence CVE CVE-2025-39716 https://www.cve.org/CVERecord?id=CVE-2025-39716 Référence CVE CVE-2025-39718 https://www.cve.org/CVERecord?id=CVE-2025-39718 Référence CVE CVE-2025-39719 https://www.cve.org/CVERecord?id=CVE-2025-39719 Référence CVE CVE-2025-39724 https://www.cve.org/CVERecord?id=CVE-2025-39724 Référence CVE CVE-2025-39736 https://www.cve.org/CVERecord?id=CVE-2025-39736 Référence CVE CVE-2025-39737 https://www.cve.org/CVERecord?id=CVE-2025-39737 Référence CVE CVE-2025-39738 https://www.cve.org/CVERecord?id=CVE-2025-39738 Référence CVE CVE-2025-39742 https://www.cve.org/CVERecord?id=CVE-2025-39742 Référence CVE CVE-2025-39743 https://www.cve.org/CVERecord?id=CVE-2025-39743 Référence CVE CVE-2025-39749 https://www.cve.org/CVERecord?id=CVE-2025-39749 Référence CVE CVE-2025-39752 https://www.cve.org/CVERecord?id=CVE-2025-39752 Référence CVE CVE-2025-39756 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-39712 Référence CVE CVE-2025-39713 https://www.cve.org/CVERecord?id=CVE-2025-39713 Référence CVE CVE-2025-39714 https://www.cve.org/CVERecord?id=CVE-2025-39714 Référence CVE CVE-2025-39715 https://www.cve.org/CVERecord?id=CVE-2025-39715 Référence CVE CVE-2025-39716 https://www.cve.org/CVERecord?id=CVE-2025-39716 Référence CVE CVE-2025-39718 https://www.cve.org/CVERecord?id=CVE-2025-39718 Référence CVE CVE-2025-39719 https://www.cve.org/CVERecord?id=CVE-2025-39719 Référence CVE CVE-2025-39720 https://www.cve.org/CVERecord?id=CVE-2025-39720 Référence CVE CVE-2025-39721 https://www.cve.org/CVERecord?id=CVE-2025-39721 Référence CVE CVE-2025-39724 https://www.cve.org/CVERecord?id=CVE-2025-39724 Référence CVE CVE-2025-39726 https://www.cve.org/CVERecord?id=CVE-2025-39726 Référence CVE CVE-2025-39730 https://www.cve.org/CVERecord?id=CVE-2025-39730 Référence CVE CVE-2025-39731 https://www.cve.org/CVERecord?id=CVE-2025-39731 Référence CVE CVE-2025-39732 https://www.cve.org/CVERecord?id=CVE-2025-39732 Référence CVE CVE-2025-39734 https://www.cve.org/CVERecord?id=CVE-2025-39734 Référence CVE CVE-2025-39736 https://www.cve.org/CVERecord?id=CVE-2025-39736 Référence CVE CVE-2025-39737 https://www.cve.org/CVERecord?id=CVE-2025-39737 Référence CVE CVE-2025-39738 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-39712 Référence CVE CVE-2025-39713 https://www.cve.org/CVERecord?id=CVE-2025-39713 Référence CVE CVE-2025-39714 https://www.cve.org/CVERecord?id=CVE-2025-39714 Référence CVE CVE-2025-39715 https://www.cve.org/CVERecord?id=CVE-2025-39715 Référence CVE CVE-2025-39716 https://www.cve.org/CVERecord?id=CVE-2025-39716 Référence CVE CVE-2025-39718 https://www.cve.org/CVERecord?id=CVE-2025-39718 Référence CVE CVE-2025-39719 https://www.cve.org/CVERecord?id=CVE-2025-39719 Référence CVE CVE-2025-39720 https://www.cve.org/CVERecord?id=CVE-2025-39720 Référence CVE CVE-2025-39721 https://www.cve.org/CVERecord?id=CVE-2025-39721 Référence CVE CVE-2025-39724 https://www.cve.org/CVERecord?id=CVE-2025-39724 Référence CVE CVE-2025-39726 https://www.cve.org/CVERecord?id=CVE-2025-39726 Référence CVE CVE-2025-39730 https://www.cve.org/CVERecord?id=CVE-2025-39730 Référence CVE CVE-2025-39731 https://www.cve.org/CVERecord?id=CVE-2025-39731 Référence CVE CVE-2025-39732 https://www.cve.org/CVERecord?id=CVE-2025-39732 Référence CVE CVE-2025-39734 https://www.cve.org/CVERecord?id=CVE-2025-39734 Référence CVE CVE-2025-39736 https://www.cve.org/CVERecord?id=CVE-2025-39736 Référence CVE CVE-2025-39737 https://www.cve.org/CVERecord?id=CVE-2025-39737 Référence CVE CVE-2025-39738 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-39712 Référence CVE CVE-2025-39713 https://www.cve.org/CVERecord?id=CVE-2025-39713 Référence CVE CVE-2025-39714 https://www.cve.org/CVERecord?id=CVE-2025-39714 Référence CVE CVE-2025-39715 https://www.cve.org/CVERecord?id=CVE-2025-39715 Référence CVE CVE-2025-39716 https://www.cve.org/CVERecord?id=CVE-2025-39716 Référence CVE CVE-2025-39718 https://www.cve.org/CVERecord?id=CVE-2025-39718 Référence CVE CVE-2025-39719 https://www.cve.org/CVERecord?id=CVE-2025-39719 Référence CVE CVE-2025-39720 https://www.cve.org/CVERecord?id=CVE-2025-39720 Référence CVE CVE-2025-39721 https://www.cve.org/CVERecord?id=CVE-2025-39721 Référence CVE CVE-2025-39724 https://www.cve.org/CVERecord?id=CVE-2025-39724 Référence CVE CVE-2025-39726 https://www.cve.org/CVERecord?id=CVE-2025-39726 Référence CVE CVE-2025-39730 https://www.cve.org/CVERecord?id=CVE-2025-39730 Référence CVE CVE-2025-39731 https://www.cve.org/CVERecord?id=CVE-2025-39731 Référence CVE CVE-2025-39732 https://www.cve.org/CVERecord?id=CVE-2025-39732 Référence CVE CVE-2025-39734 https://www.cve.org/CVERecord?id=CVE-2025-39734 Référence CVE CVE-2025-39736 https://www.cve.org/CVERecord?id=CVE-2025-39736 Référence CVE CVE-2025-39737 https://www.cve.org/CVERecord?id=CVE-2025-39737 Référence CVE CVE-2025-39738 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-39712 Référence CVE CVE-2025-39713 https://www.cve.org/CVERecord?id=CVE-2025-39713 Référence CVE CVE-2025-39714 https://www.cve.org/CVERecord?id=CVE-2025-39714 Référence CVE CVE-2025-39715 https://www.cve.org/CVERecord?id=CVE-2025-39715 Référence CVE CVE-2025-39716 https://www.cve.org/CVERecord?id=CVE-2025-39716 Référence CVE CVE-2025-39718 https://www.cve.org/CVERecord?id=CVE-2025-39718 Référence CVE CVE-2025-39719 https://www.cve.org/CVERecord?id=CVE-2025-39719 Référence CVE CVE-2025-39720 https://www.cve.org/CVERecord?id=CVE-2025-39720 Référence CVE CVE-2025-39721 https://www.cve.org/CVERecord?id=CVE-2025-39721 Référence CVE CVE-2025-39724 https://www.cve.org/CVERecord?id=CVE-2025-39724 Référence CVE CVE-2025-39726 https://www.cve.org/CVERecord?id=CVE-2025-39726 Référence CVE CVE-2025-39730 https://www.cve.org/CVERecord?id=CVE-2025-39730 Référence CVE CVE-2025-39731 https://www.cve.org/CVERecord?id=CVE-2025-39731 Référence CVE CVE-2025-39732 https://www.cve.org/CVERecord?id=CVE-2025-39732 Référence CVE CVE-2025-39734 https://www.cve.org/CVERecord?id=CVE-2025-39734 Référence CVE CVE-2025-39736 https://www.cve.org/CVERecord?id=CVE-2025-39736 Référence CVE CVE-2025-39737 https://www.cve.org/CVERecord?id=CVE-2025-39737 Référence CVE CVE-2025-39738 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-39712 Référence CVE CVE-2025-39713 https://www.cve.org/CVERecord?id=CVE-2025-39713 Référence CVE CVE-2025-39714 https://www.cve.org/CVERecord?id=CVE-2025-39714 Référence CVE CVE-2025-39715 https://www.cve.org/CVERecord?id=CVE-2025-39715 Référence CVE CVE-2025-39716 https://www.cve.org/CVERecord?id=CVE-2025-39716 Référence CVE CVE-2025-39718 https://www.cve.org/CVERecord?id=CVE-2025-39718 Référence CVE CVE-2025-39719 https://www.cve.org/CVERecord?id=CVE-2025-39719 Référence CVE CVE-2025-39720 https://www.cve.org/CVERecord?id=CVE-2025-39720 Référence CVE CVE-2025-39721 https://www.cve.org/CVERecord?id=CVE-2025-39721 Référence CVE CVE-2025-39724 https://www.cve.org/CVERecord?id=CVE-2025-39724 Référence CVE CVE-2025-39726 https://www.cve.org/CVERecord?id=CVE-2025-39726 Référence CVE CVE-2025-39730 https://www.cve.org/CVERecord?id=CVE-2025-39730 Référence CVE CVE-2025-39731 https://www.cve.org/CVERecord?id=CVE-2025-39731 Référence CVE CVE-2025-39732 https://www.cve.org/CVERecord?id=CVE-2025-39732 Référence CVE CVE-2025-39734 https://www.cve.org/CVERecord?id=CVE-2025-39734 Référence CVE CVE-2025-39736 https://www.cve.org/CVERecord?id=CVE-2025-39736 Référence CVE CVE-2025-39737 https://www.cve.org/CVERecord?id=CVE-2025-39737 Référence CVE CVE-2025-39738 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-39691 Référence CVE CVE-2025-39693 https://www.cve.org/CVERecord?id=CVE-2025-39693 Référence CVE CVE-2025-39697 https://www.cve.org/CVERecord?id=CVE-2025-39697 Référence CVE CVE-2025-39702 https://www.cve.org/CVERecord?id=CVE-2025-39702 Référence CVE CVE-2025-39703 https://www.cve.org/CVERecord?id=CVE-2025-39703 Référence CVE CVE-2025-39709 https://www.cve.org/CVERecord?id=CVE-2025-39709 Référence CVE CVE-2025-39710 https://www.cve.org/CVERecord?id=CVE-2025-39710 Référence CVE CVE-2025-39713 https://www.cve.org/CVERecord?id=CVE-2025-39713 Référence CVE CVE-2025-39714 https://www.cve.org/CVERecord?id=CVE-2025-39714 Référence CVE CVE-2025-39724 https://www.cve.org/CVERecord?id=CVE-2025-39724 Référence CVE CVE-2025-39725 https://www.cve.org/CVERecord?id=CVE-2025-39725 Référence CVE CVE-2025-39726 https://www.cve.org/CVERecord?id=CVE-2025-39726 Référence CVE CVE-2025-39727 https://www.cve.org/CVERecord?id=CVE-2025-39727 Référence CVE CVE-2025-39728 https://www.cve.org/CVERecord?id=CVE-2025-39728 Référence CVE CVE-2025-39730 https://www.cve.org/CVERecord?id=CVE-2025-39730 Référence CVE CVE-2025-39731 https://www.cve.org/CVERecord?id=CVE-2025-39731 Référence CVE CVE-2025-39732 https://www.cve.org/CVERecord?id=CVE-2025-39732 Référence CVE CVE-2025-39734 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-39691 Référence CVE CVE-2025-39693 https://www.cve.org/CVERecord?id=CVE-2025-39693 Référence CVE CVE-2025-39697 https://www.cve.org/CVERecord?id=CVE-2025-39697 Référence CVE CVE-2025-39702 https://www.cve.org/CVERecord?id=CVE-2025-39702 Référence CVE CVE-2025-39703 https://www.cve.org/CVERecord?id=CVE-2025-39703 Référence CVE CVE-2025-39709 https://www.cve.org/CVERecord?id=CVE-2025-39709 Référence CVE CVE-2025-39710 https://www.cve.org/CVERecord?id=CVE-2025-39710 Référence CVE CVE-2025-39713 https://www.cve.org/CVERecord?id=CVE-2025-39713 Référence CVE CVE-2025-39714 https://www.cve.org/CVERecord?id=CVE-2025-39714 Référence CVE CVE-2025-39724 https://www.cve.org/CVERecord?id=CVE-2025-39724 Référence CVE CVE-2025-39725 https://www.cve.org/CVERecord?id=CVE-2025-39725 Référence CVE CVE-2025-39726 https://www.cve.org/CVERecord?id=CVE-2025-39726 Référence CVE CVE-2025-39727 https://www.cve.org/CVERecord?id=CVE-2025-39727 Référence CVE CVE-2025-39730 https://www.cve.org/CVERecord?id=CVE-2025-39730 Référence CVE CVE-2025-39731 https://www.cve.org/CVERecord?id=CVE-2025-39731 Référence CVE CVE-2025-39732 https://www.cve.org/CVERecord?id=CVE-2025-39732 Référence CVE CVE-2025-39734 https://www.cve.org/CVERecord?id=CVE-2025-39734 Référence CVE CVE-2025-39736 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-39711 Référence CVE CVE-2025-39712 https://www.cve.org/CVERecord?id=CVE-2025-39712 Référence CVE CVE-2025-39713 https://www.cve.org/CVERecord?id=CVE-2025-39713 Référence CVE CVE-2025-39714 https://www.cve.org/CVERecord?id=CVE-2025-39714 Référence CVE CVE-2025-39718 https://www.cve.org/CVERecord?id=CVE-2025-39718 Référence CVE CVE-2025-39719 https://www.cve.org/CVERecord?id=CVE-2025-39719 Référence CVE CVE-2025-39721 https://www.cve.org/CVERecord?id=CVE-2025-39721 Référence CVE CVE-2025-39722 https://www.cve.org/CVERecord?id=CVE-2025-39722 Référence CVE CVE-2025-39723 https://www.cve.org/CVERecord?id=CVE-2025-39723 Référence CVE CVE-2025-39724 https://www.cve.org/CVERecord?id=CVE-2025-39724 Référence CVE CVE-2025-39726 https://www.cve.org/CVERecord?id=CVE-2025-39726 Référence CVE CVE-2025-39727 https://www.cve.org/CVERecord?id=CVE-2025-39727 Référence CVE CVE-2025-39730 https://www.cve.org/CVERecord?id=CVE-2025-39730 Référence CVE CVE-2025-39732 https://www.cve.org/CVERecord?id=CVE-2025-39732 Référence CVE CVE-2025-39738 https://www.cve.org/CVERecord?id=CVE-2025-39738 Référence CVE CVE-2025-39739 https://www.cve.org/CVERecord?id=CVE-2025-39739 Référence CVE CVE-2025-39742 https://www.cve.org/CVERecord?id=CVE-2025-39742 Référence CVE CVE-2025-39744 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-38700 Référence CVE CVE-2025-38714 https://www.cve.org/CVERecord?id=CVE-2025-38714 Référence CVE CVE-2025-38718 https://www.cve.org/CVERecord?id=CVE-2025-38718 Référence CVE CVE-2025-38724 https://www.cve.org/CVERecord?id=CVE-2025-38724 Référence CVE CVE-2025-39673 https://www.cve.org/CVERecord?id=CVE-2025-39673 Référence CVE CVE-2025-39676 https://www.cve.org/CVERecord?id=CVE-2025-39676 Référence CVE CVE-2025-39683 https://www.cve.org/CVERecord?id=CVE-2025-39683 Référence CVE CVE-2025-39697 https://www.cve.org/CVERecord?id=CVE-2025-39697 Référence CVE CVE-2025-39702 https://www.cve.org/CVERecord?id=CVE-2025-39702 Référence CVE CVE-2025-39724 https://www.cve.org/CVERecord?id=CVE-2025-39724 Référence CVE CVE-2025-39756 https://www.cve.org/CVERecord?id=CVE-2025-39756 Référence CVE CVE-2025-39772 https://www.cve.org/CVERecord?id=CVE-2025-39772 Référence CVE CVE-2025-39794 https://www.cve.org/CVERecord?id=CVE-2025-39794 Référence CVE CVE-2025-39797 https://www.cve.org/CVERecord?id=CVE-2025-39797 Référence CVE CVE-2025-39812 https://www.cve.org/CVERecord?id=CVE-2025-39812 Référence CVE CVE-2025-39813 https://www.cve.org/CVERecord?id=CVE-2025-39813 Référence CVE CVE-2025-39828 https://www.cve.org/CVERecord?id=CVE-2025-39828 Référence CVE CVE-2025-39841 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-39701 Référence CVE CVE-2025-39702 https://www.cve.org/CVERecord?id=CVE-2025-39702 Référence CVE CVE-2025-39706 https://www.cve.org/CVERecord?id=CVE-2025-39706 Référence CVE CVE-2025-39709 https://www.cve.org/CVERecord?id=CVE-2025-39709 Référence CVE CVE-2025-39710 https://www.cve.org/CVERecord?id=CVE-2025-39710 Référence CVE CVE-2025-39713 https://www.cve.org/CVERecord?id=CVE-2025-39713 Référence CVE CVE-2025-39714 https://www.cve.org/CVERecord?id=CVE-2025-39714 Référence CVE CVE-2025-39719 https://www.cve.org/CVERecord?id=CVE-2025-39719 Référence CVE CVE-2025-39721 https://www.cve.org/CVERecord?id=CVE-2025-39721 Référence CVE CVE-2025-39724 https://www.cve.org/CVERecord?id=CVE-2025-39724 Référence CVE CVE-2025-39726 https://www.cve.org/CVERecord?id=CVE-2025-39726 Référence CVE CVE-2025-39730 https://www.cve.org/CVERecord?id=CVE-2025-39730 Référence CVE CVE-2025-39732 https://www.cve.org/CVERecord?id=CVE-2025-39732 Référence CVE CVE-2025-39739 https://www.cve.org/CVERecord?id=CVE-2025-39739 Référence CVE CVE-2025-39742 https://www.cve.org/CVERecord?id=CVE-2025-39742 Référence CVE CVE-2025-39743 https://www.cve.org/CVERecord?id=CVE-2025-39743 Référence CVE CVE-2025-39750 https://www.cve.org/CVERecord?id=CVE-2025-39750 Référence CVE CVE-2025-39751 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-39701 Référence CVE CVE-2025-39702 https://www.cve.org/CVERecord?id=CVE-2025-39702 Référence CVE CVE-2025-39706 https://www.cve.org/CVERecord?id=CVE-2025-39706 Référence CVE CVE-2025-39709 https://www.cve.org/CVERecord?id=CVE-2025-39709 Référence CVE CVE-2025-39710 https://www.cve.org/CVERecord?id=CVE-2025-39710 Référence CVE CVE-2025-39713 https://www.cve.org/CVERecord?id=CVE-2025-39713 Référence CVE CVE-2025-39714 https://www.cve.org/CVERecord?id=CVE-2025-39714 Référence CVE CVE-2025-39719 https://www.cve.org/CVERecord?id=CVE-2025-39719 Référence CVE CVE-2025-39721 https://www.cve.org/CVERecord?id=CVE-2025-39721 Référence CVE CVE-2025-39724 https://www.cve.org/CVERecord?id=CVE-2025-39724 Référence CVE CVE-2025-39726 https://www.cve.org/CVERecord?id=CVE-2025-39726 Référence CVE CVE-2025-39730 https://www.cve.org/CVERecord?id=CVE-2025-39730 Référence CVE CVE-2025-39732 https://www.cve.org/CVERecord?id=CVE-2025-39732 Référence CVE CVE-2025-39739 https://www.cve.org/CVERecord?id=CVE-2025-39739 Référence CVE CVE-2025-39742 https://www.cve.org/CVERecord?id=CVE-2025-39742 Référence CVE CVE-2025-39743 https://www.cve.org/CVERecord?id=CVE-2025-39743 Référence CVE CVE-2025-39750 https://www.cve.org/CVERecord?id=CVE-2025-39750 Référence CVE CVE-2025-39751 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-39707 Référence CVE CVE-2025-39709 https://www.cve.org/CVERecord?id=CVE-2025-39709 Référence CVE CVE-2025-39710 https://www.cve.org/CVERecord?id=CVE-2025-39710 Référence CVE CVE-2025-39711 https://www.cve.org/CVERecord?id=CVE-2025-39711 Référence CVE CVE-2025-39713 https://www.cve.org/CVERecord?id=CVE-2025-39713 Référence CVE CVE-2025-39714 https://www.cve.org/CVERecord?id=CVE-2025-39714 Référence CVE CVE-2025-39718 https://www.cve.org/CVERecord?id=CVE-2025-39718 Référence CVE CVE-2025-39719 https://www.cve.org/CVERecord?id=CVE-2025-39719 Référence CVE CVE-2025-39721 https://www.cve.org/CVERecord?id=CVE-2025-39721 Référence CVE CVE-2025-39724 https://www.cve.org/CVERecord?id=CVE-2025-39724 Référence CVE CVE-2025-39726 https://www.cve.org/CVERecord?id=CVE-2025-39726 Référence CVE CVE-2025-39730 https://www.cve.org/CVERecord?id=CVE-2025-39730 Référence CVE CVE-2025-39732 https://www.cve.org/CVERecord?id=CVE-2025-39732 Référence CVE CVE-2025-39738 https://www.cve.org/CVERecord?id=CVE-2025-39738 Référence CVE CVE-2025-39739 https://www.cve.org/CVERecord?id=CVE-2025-39739 Référence CVE CVE-2025-39742 https://www.cve.org/CVERecord?id=CVE-2025-39742 Référence CVE CVE-2025-39743 https://www.cve.org/CVERecord?id=CVE-2025-39743 Référence CVE CVE-2025-39744 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-39707 Référence CVE CVE-2025-39709 https://www.cve.org/CVERecord?id=CVE-2025-39709 Référence CVE CVE-2025-39710 https://www.cve.org/CVERecord?id=CVE-2025-39710 Référence CVE CVE-2025-39711 https://www.cve.org/CVERecord?id=CVE-2025-39711 Référence CVE CVE-2025-39713 https://www.cve.org/CVERecord?id=CVE-2025-39713 Référence CVE CVE-2025-39714 https://www.cve.org/CVERecord?id=CVE-2025-39714 Référence CVE CVE-2025-39718 https://www.cve.org/CVERecord?id=CVE-2025-39718 Référence CVE CVE-2025-39719 https://www.cve.org/CVERecord?id=CVE-2025-39719 Référence CVE CVE-2025-39721 https://www.cve.org/CVERecord?id=CVE-2025-39721 Référence CVE CVE-2025-39724 https://www.cve.org/CVERecord?id=CVE-2025-39724 Référence CVE CVE-2025-39726 https://www.cve.org/CVERecord?id=CVE-2025-39726 Référence CVE CVE-2025-39730 https://www.cve.org/CVERecord?id=CVE-2025-39730 Référence CVE CVE-2025-39732 https://www.cve.org/CVERecord?id=CVE-2025-39732 Référence CVE CVE-2025-39738 https://www.cve.org/CVERecord?id=CVE-2025-39738 Référence CVE CVE-2025-39739 https://www.cve.org/CVERecord?id=CVE-2025-39739 Référence CVE CVE-2025-39742 https://www.cve.org/CVERecord?id=CVE-2025-39742 Référence CVE CVE-2025-39743 https://www.cve.org/CVERecord?id=CVE-2025-39743 Référence CVE CVE-2025-39744 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-39706 Référence CVE CVE-2025-39709 https://www.cve.org/CVERecord?id=CVE-2025-39709 Référence CVE CVE-2025-39710 https://www.cve.org/CVERecord?id=CVE-2025-39710 Référence CVE CVE-2025-39713 https://www.cve.org/CVERecord?id=CVE-2025-39713 Référence CVE CVE-2025-39714 https://www.cve.org/CVERecord?id=CVE-2025-39714 Référence CVE CVE-2025-39715 https://www.cve.org/CVERecord?id=CVE-2025-39715 Référence CVE CVE-2025-39716 https://www.cve.org/CVERecord?id=CVE-2025-39716 Référence CVE CVE-2025-39718 https://www.cve.org/CVERecord?id=CVE-2025-39718 Référence CVE CVE-2025-39719 https://www.cve.org/CVERecord?id=CVE-2025-39719 Référence CVE CVE-2025-39724 https://www.cve.org/CVERecord?id=CVE-2025-39724 Référence CVE CVE-2025-39730 https://www.cve.org/CVERecord?id=CVE-2025-39730 Référence CVE CVE-2025-39731 https://www.cve.org/CVERecord?id=CVE-2025-39731 Référence CVE CVE-2025-39734 https://www.cve.org/CVERecord?id=CVE-2025-39734 Référence CVE CVE-2025-39736 https://www.cve.org/CVERecord?id=CVE-2025-39736 Référence CVE CVE-2025-39737 https://www.cve.org/CVERecord?id=CVE-2025-39737 Référence CVE CVE-2025-39738 https://www.cve.org/CVERecord?id=CVE-2025-39738 Référence CVE CVE-2025-39742 https://www.cve.org/CVERecord?id=CVE-2025-39742 Référence CVE CVE-2025-39743 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-39714 Référence CVE CVE-2025-39715 https://www.cve.org/CVERecord?id=CVE-2025-39715 Référence CVE CVE-2025-39716 https://www.cve.org/CVERecord?id=CVE-2025-39716 Référence CVE CVE-2025-39718 https://www.cve.org/CVERecord?id=CVE-2025-39718 Référence CVE CVE-2025-39719 https://www.cve.org/CVERecord?id=CVE-2025-39719 Référence CVE CVE-2025-39720 https://www.cve.org/CVERecord?id=CVE-2025-39720 Référence CVE CVE-2025-39721 https://www.cve.org/CVERecord?id=CVE-2025-39721 Référence CVE CVE-2025-39722 https://www.cve.org/CVERecord?id=CVE-2025-39722 Référence CVE CVE-2025-39723 https://www.cve.org/CVERecord?id=CVE-2025-39723 Référence CVE CVE-2025-39724 https://www.cve.org/CVERecord?id=CVE-2025-39724 Référence CVE CVE-2025-39736 https://www.cve.org/CVERecord?id=CVE-2025-39736 Référence CVE CVE-2025-39737 https://www.cve.org/CVERecord?id=CVE-2025-39737 Référence CVE CVE-2025-39738 https://www.cve.org/CVERecord?id=CVE-2025-39738 Référence CVE CVE-2025-39742 https://www.cve.org/CVERecord?id=CVE-2025-39742 Référence CVE CVE-2025-39743 https://www.cve.org/CVERecord?id=CVE-2025-39743 Référence CVE CVE-2025-39749 https://www.cve.org/CVERecord?id=CVE-2025-39749 Référence CVE CVE-2025-39751 https://www.cve.org/CVERecord?id=CVE-2025-39751 Référence CVE CVE-2025-39752 https://www.cve.org/CVERecord?id=

Official advisory
NCSC-NL · Dutch · NCSC-2026-0147Kwetsbaarheden verholpen in Siemens-producten

Multiple security vulnerabilities affecting Linux kernel subsystems, including AMD CPU data leakage, SEV-SNP guest memory integrity, and the VMSCAPE branch predictor flaw, were fixed across various SUSE Linux Enterprise and Micro kernel versions.

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.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
Fixed
< 3.13; 5.4.297 ≤ 5.4.*; 5.10.241 ≤ 5.10.*; 5.15.190 ≤ 5.15.*; 6.1.149 ≤ 6.1.*; 6.6.103 ≤ 6.6.*; 6.12.44 ≤ 6.12.*; 6.16.4 ≤ 6.16.*
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 5 Sept 2025 · Last source change 14 Jul 2026, 12:42 UTC · CWE not yet assigned

CVE recordCVE.org · 5.2
CVSS sourceNIST NVD
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2025-31503
Product sourceVendor CSAF · Siemens ProductCERT
Remediation sourceVendor CSAF · Siemens ProductCERT
CWE sourceUnavailable
NVD statusNVD modified after enrichment

Missing structured fields: CWE classification. Missing data is not evidence of low risk; review the primary advisory.

Material change intelligence

What changed after publication

View recent updates →

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

Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
ENISA EUVD · EUVD-2025-31503↗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-2025-39724 · cve.blacktree.nl