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

net: bridge: fix soft lockup in br_multicast_query_expired()

Linux · Linux

5.5MediumCVSS 3.1
Recommended action
Scheduled

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

Patch available
Distribution package intelligence

Ubuntu vendor package status

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

20 package states
Repository candidate not checked

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

Ubuntu releaseSource packageVendor stateFixed versionEvidence
Ubuntu 24.04 LTSnoble · standard archivelinuxAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical record ↗Source updated 4 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 4 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 4 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 4 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 4 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 4 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 4 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 4 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 4 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 4 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 4 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 4 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 4 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 4 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 4 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 4 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 4 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 4 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 4 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 4 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.

3 current
SSA-019113 · CSAF 2.0 · revision 1 · interimSiemens ProductCERTSSA-019113: Vulnerabilities in the additional GNU/Linux subsystem of the SIMATIC S7-1500 CPU 1518(F)-4 PN/DP MFP V3.1.6
5 known affected

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

  • SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (6ES7518-4AX00-1AB0) >= V3.1.6
  • SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (6ES7518-4AX00-1AC0) >= V3.1.6
  • SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (6ES7518-4FX00-1AB0) >= V3.1.6
  • SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (6ES7518-4FX00-1AC0) >= V3.1.6
  • SIPLUS S7-1500 CPU 1518-4 PN/DP MFP (6AG1518-4AX00-4AC0) >= V3.1.6
Summary
In the Linux kernel, the following vulnerability has been resolved: net: bridge: fix soft lockup in br_multicast_query_expired() When set multicast_query_interval to a large value, the local variable 'time' in br_multicast_send_query() may overflow. If the time is smaller than jiffies, the timer will expire immediately, and then call mod_timer() again, which creates a loop and may trigger the following soft lockup issue. watchdog: BUG: soft lockup - CPU#1 stuck for 221s! [rb_consumer:66] CPU: 1 UID: 0 PID: 66 Comm: rb_consumer Not tainted 6.16.0+ #259 PREEMPT(none) Call Trace: __netdev_alloc_skb+0x2e/0x3a0 br_ip6_multicast_alloc_query+0x212/0x1b70 __br_multicast_send_query+0x376/0xac0 br_multicast_send_query+0x299/0x510 br_multicast_query_expired.constprop.0+0x16d/0x1b0 call_timer_fn+0x3b/0x2a0 __run_timers+0x619/0x950 run_timer_softirq+0x11c/0x220 handle_softirqs+0x18e/0x560 __irq_exit_rcu+0x158/0x1a0 sysvec_apic_timer_interrupt+0x76/0x90 This issue can be reproduced with: ip link add br0 type bridge echo 1 > /sys/class/net/br0/bridge/multicast_querier echo 0xffffffffffffffff > /sys/class/net/br0/bridge/multicast_query_interval ip link set dev br0 up The multicast_startup_query_interval can also cause this issue. Similar to the commit 99b40610956a ("net: bridge: mcast: add and enforce query interval minimum"), add check for the query interval maximum to fix this issue.
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: net: bridge: fix soft lockup in br_multicast_query_expired() When set multicast_query_interval to a large value, the local variable 'time' in br_multicast_send_query() may overflow. If the time is smaller than jiffies, the timer will expire immediately, and then call mod_timer() again, which creates a loop and may trigger the following soft lockup issue. watchdog: BUG: soft lockup - CPU#1 stuck for 221s! [rb_consumer:66] CPU: 1 UID: 0 PID: 66 Comm: rb_consumer Not tainted 6.16.0+ #259 PREEMPT(none) Call Trace: __netdev_alloc_skb+0x2e/0x3a0 br_ip6_multicast_alloc_query+0x212/0x1b70 __br_multicast_send_query+0x376/0xac0 br_multicast_send_query+0x299/0x510 br_multicast_query_expired.constprop.0+0x16d/0x1b0 call_timer_fn+0x3b/0x2a0 __run_timers+0x619/0x950 run_timer_softirq+0x11c/0x220 handle_softirqs+0x18e/0x560 __irq_exit_rcu+0x158/0x1a0 sysvec_apic_timer_interrupt+0x76/0x90 This issue can be reproduced with: ip link add br0 type bridge echo 1 > /sys/class/net/br0/bridge/multicast_querier echo 0xffffffffffffffff > /sys/class/net/br0/bridge/multicast_query_interval ip link set dev br0 up The multicast_startup_query_interval can also cause this issue. Similar to the commit 99b40610956a ("net: bridge: mcast: add and enforce query interval minimum"), add check for the query interval maximum to fix this issue.
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: net: bridge: fix soft lockup in br_multicast_query_expired() When set multicast_query_interval to a large value, the local variable 'time' in br_multicast_send_query() may overflow. If the time is smaller than jiffies, the timer will expire immediately, and then call mod_timer() again, which creates a loop and may trigger the following soft lockup issue. watchdog: BUG: soft lockup - CPU#1 stuck for 221s! [rb_consumer:66] CPU: 1 UID: 0 PID: 66 Comm: rb_consumer Not tainted 6.16.0+ #259 PREEMPT(none) Call Trace: __netdev_alloc_skb+0x2e/0x3a0 br_ip6_multicast_alloc_query+0x212/0x1b70 __br_multicast_send_query+0x376/0xac0 br_multicast_send_query+0x299/0x510 br_multicast_query_expired.constprop.0+0x16d/0x1b0 call_timer_fn+0x3b/0x2a0 __run_timers+0x619/0x950 run_timer_softirq+0x11c/0x220 handle_softirqs+0x18e/0x560 __irq_exit_rcu+0x158/0x1a0 sysvec_apic_timer_interrupt+0x76/0x90 This issue can be reproduced with: ip link add br0 type bridge echo 1 > /sys/class/net/br0/bridge/multicast_querier echo 0xffffffffffffffff > /sys/class/net/br0/bridge/multicast_query_interval ip link set dev br0 up The multicast_startup_query_interval can also cause this issue. Similar to the commit 99b40610956a ("net: bridge: mcast: add and enforce query interval minimum"), add check for the query interval maximum to fix this issue.
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-28939

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: net: bridge: fix soft lockup in br_multicast_query_expired() When set multicast_query_interval to a large value, the local variable 'time' in br_multicast_send_query() may overflow. If the time is smaller than jiffies, the timer will expire immediately, and then call mod_timer() again, which creates a loop and may trigger the following soft lockup issue. watchdog: BUG: soft lockup - CPU#1 stuck for 221s! [rb_consumer:66] CPU: 1 UID: 0 PID: 66 Comm: rb_consumer Not tainted 6.16.0+ #259 PREEMPT(none) Call Trace: <IRQ> __netdev_alloc_skb+0x2e/0x3a0 br_ip6_multicast_alloc_query+0x212/0x1b70 __br_multicast_send_query+0x376/0xac0 br_multicast_send_query+0x299/0x510 br_multicast_query_expired.constprop.0+0x16d/0x1b0 call_timer_fn+0x3b/0x2a0 __run_timers+0x619/0x950 run_timer_softirq+0x11c/0x220 handle_softirqs+0x18e/0x560 __irq_exit_rcu+0x158/0x1a0 sysvec_apic_timer_interrupt+0x76/0x90 </IRQ> This issue can be reproduced with: ip link add br0 type bridge echo 1 > /sys/class/net/br0/bridge/multicast_querier echo 0xffffffffffffffff > /sys/class/net/br0/bridge/multicast_query_interval ip link set dev br0 up The multicast_startup_query_interval can also cause this issue. Similar to the commit 99b40610956a ("net: bridge: mcast: add and enforce query interval minimum"), add check for the query interval maximum to fix this issue.

What

In the Linux kernel, the following vulnerability has been resolved: net: bridge: fix soft lockup in br_multicast_query_expired() When set multicast_query_interval to a large value, the local variable 'time' in br_multicast_send_query() may overflow. If the time is smaller than jiffies, the timer will expire immediately, and then call mod_timer() again, which creates a loop and may trigger the following soft lockup issue. watchdog: BUG: soft lockup - CPU#1 stuck for 221s! [rb_consumer:66] CPU: 1 UID: 0 PID: 66 Comm: rb_consumer Not tainted 6.16.0+ #259 PREEMPT(none) Call Trace: <IRQ> __netdev_alloc_skb+0x2e/0x3a0 br_ip6_multicast_alloc_query+0x212/0x1b70 __br_multicast_send_query+0x376/0xac0 br_multicast_send_query+0x299/0x510 br_multicast_query_expired.constprop.0+0x16d/0x1b0 call_timer_fn+0x3b/0x2a0 __run_timers+0x619/0x950 run_timer_softirq+0x11c/0x220 handle_softirqs+0x18e/0x560 __irq_exit_rcu+0x158/0x1a0 sysvec_apic_timer_interrupt+0x76/0x90 </IRQ> This issue can be reproduced with: ip link add br0 type bridge echo 1 > /sys/class/net/br0/bridge/multicast_querier echo 0xffffffffffffffff > /sys/class/net/br0/bridge/multicast_query_interval ip link set dev br0 up The multicast_startup_query_interval can also cause this issue. Similar to the commit 99b40610956a ("net: bridge: mcast: add and enforce query interval minimum"), add check for the query interval maximum to fix this issue.

Why

The product does not properly acquire or release a lock on a resource, leading to unexpected resource state changes and behaviors.

How

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

What

In the Linux kernel, the following vulnerability has been resolved: net: bridge: fix soft lockup in br_multicast_query_expired() When set multicast_query_interval to a large value, the local variable 'time' in br_multicast_send_query() may overflow. If the time is smaller than jiffies, the timer will expire immediately, and then call mod_timer() again, which creates a loop and may trigger the following soft lockup issue. watchdog: BUG: soft lockup - CPU#1 stuck for 221s! [rb_consumer:66] CPU: 1 UID: 0 PID: 66 Comm: rb_consumer Not tainted 6.16.0+ #259 PREEMPT(none) Call Trace: <IRQ> __netdev_alloc_skb+0x2e/0x3a0 br_ip6_multicast_alloc_query+0x212/0x1b70 __br_multicast_send_query+0x376/0xac0 br_multicast_send_query+0x299/0x510 br_multicast_query_expired.constprop.0+0x16d/0x1b0 call_timer_fn+0x3b/0x2a0 __run_timers+0x619/0x950 run_timer_softirq+0x11c/0x220 handle_softirqs+0x18e/0x560 __irq_exit_rcu+0x158/0x1a0 sysvec_apic_timer_interrupt+0x76/0x90 </IRQ> This issue can be reproduced with: ip link add br0 type bridge echo 1 > /sys/class/net/br0/bridge/multicast_querier echo 0xffffffffffffffff > /sys/class/net/br0/bridge/multicast_query_interval ip link set dev br0 up The multicast_startup_query_interval can also cause this issue. Similar to the commit 99b40610956a ("net: bridge: mcast: add and enforce query interval minimum"), add check for the query interval maximum to fix this issue.

Why

The product does not properly acquire or release a lock on a resource, leading to unexpected resource state changes and behaviors.

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 → Improper Locking → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Local
Privileges required
Low: a basic authenticated account is required
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-667 ↗

CWE-667: Improper Locking. The product does not properly acquire or release a lock on a resource, leading to unexpected resource state changes and behaviors.

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

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

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

Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um Sicherheitsmechanismen zu umgehen, sowie einen Denial of Service Angriff oder andere nicht spezifizierte Angriffe durchzuführen.

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

25-22055, CVE-2025-22056, CVE-2025-22060, CVE-2025-22083, CVE-2025-22090, CVE-2025-22095, CVE-2025-22107, CVE-2025-22111, CVE-2025-22121, CVE-2025-23136, CVE-2025-23143, CVE-2025-37785, CVE-2025-37909, CVE-2025-37917, CVE-2025-37945, CVE-2025-37959, CVE-2025-37964, CVE-2025-37972, CVE-2025-37980, CVE-2025-38125, CVE-2025-38162, CVE-2025-38192, CVE-2025-38201, CVE-2025-38232, CVE-2025-38322, CVE-2025-38591, CVE-2025-38614, CVE-2025-38681, CVE-2025-38704, CVE-2025-38721, CVE-2025-38725, CVE-2025-38727, CVE-2025-38732, CVE-2025-38736, CVE-2025-39681, CVE-2025-39691, CVE-2025-39721, CVE-2025-39748, CVE-2025-39756, CVE-2025-39764, CVE-2025-39770, CVE-2025-39773, CVE-2025-39782, CVE-2025-39795, CVE-2025-39826, CVE-2025-39827, CVE-2025-39845, CVE-2025-39866, CVE-2025-39871, CVE-2025-39931, CVE-2025-39953, CVE-2025-39955, CVE-2025-39964, CVE-2025-39977, CVE-2025-39978, CVE-2025-39980, CVE-2025-40022, CVE-2025-40070, CVE-2025-40078, CVE-2025-40080, CVE-2025-40105, CVE-2025-40135, CVE-2025-40149, CVE-2025-40219, CVE-2025-40261, CVE-2025-40300, CVE-2025-61984, CVE-2025-61985, CVE-2025-68206, CVE-2025-68261, CVE-2025-68264, CVE-2025-68265, CVE-2025-68266, CVE-2025-68291, CVE-2025-68337, CVE-2025-68349, CVE-2025-68363, CVE-2025-68371, CVE-2025-68724, CVE-2025-68725, CVE-2025-68742, CVE-2025-68764, CVE-2025

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

d?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=CVE-2025-39756 Référence CVE CVE-2025-39757 https://www.cve.org/CVERecord?id=CVE-2025-39757 Référence CVE CVE-2025-39759 https://www.cve.org/CVERecord?id=CVE-2025-39759 Référence CVE CVE-2025-39760 https://www.cve.org/CVERecord?id=CVE-2025-39760 Référence CVE CVE-2025-39766 https://www.cve.org/CVERecord?id=CVE-2025-39766 Référence CVE CVE-2025-39770 https://www.cve.org/CVERecord?id=CVE-2025-39770 Référence CVE CVE-2025-39772 https://www.cve.org/CVERecord?id=CVE-2025-39772 Référence CVE CVE-2025-39773 https://www.cve.org/CVERecord?id=CVE-2025-39773 Référence CVE CVE-2025-39776 https://www.cve.org/CVERecord?id=CVE-2025-39776 Référence CVE CVE-2025-39782 https://www.cve.org/CVERecord?id=CVE-2025-39782 Référence CVE CVE-2025-39783 https://www.cve.org/CVERecord?id=CVE-2025-39783 Référence CVE CVE-2025-39787 https://www.cve.org/CVERecord?id=CVE-2025-39787 Référence CVE CVE-2025-39788 https://www.cve.org/CVERecord?id=CVE-2025-39788 Référence CVE CVE-2025-39790 https://www.cve.org/CVERecord?id=CVE-2025-39790 Référence CVE CVE-2025-39794 https://www.cve.org/CVERecord?id=CVE-2025-39794 Référence CVE CVE-2025-39795 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-39757 Référence CVE CVE-2025-39758 https://www.cve.org/CVERecord?id=CVE-2025-39758 Référence CVE CVE-2025-39759 https://www.cve.org/CVERecord?id=CVE-2025-39759 Référence CVE CVE-2025-39760 https://www.cve.org/CVERecord?id=CVE-2025-39760 Référence CVE CVE-2025-39761 https://www.cve.org/CVERecord?id=CVE-2025-39761 Référence CVE CVE-2025-39763 https://www.cve.org/CVERecord?id=CVE-2025-39763 Référence CVE CVE-2025-39766 https://www.cve.org/CVERecord?id=CVE-2025-39766 Référence CVE CVE-2025-39770 https://www.cve.org/CVERecord?id=CVE-2025-39770 Référence CVE CVE-2025-39772 https://www.cve.org/CVERecord?id=CVE-2025-39772 Référence CVE CVE-2025-39773 https://www.cve.org/CVERecord?id=CVE-2025-39773 Référence CVE CVE-2025-39776 https://www.cve.org/CVERecord?id=CVE-2025-39776 Référence CVE CVE-2025-39779 https://www.cve.org/CVERecord?id=CVE-2025-39779 Référence CVE CVE-2025-39781 https://www.cve.org/CVERecord?id=CVE-2025-39781 Référence CVE CVE-2025-39782 https://www.cve.org/CVERecord?id=CVE-2025-39782 Référence CVE CVE-2025-39783 https://www.cve.org/CVERecord?id=CVE-2025-39783 Référence CVE CVE-2025-39787 https://www.cve.org/CVERecord?id=CVE-2025-39787 Référence CVE CVE-2025-39788 https://www.cve.org/CVERecord?id=CVE-2025-39788 Référence CVE CVE-2025-39790 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-39757 Référence CVE CVE-2025-39758 https://www.cve.org/CVERecord?id=CVE-2025-39758 Référence CVE CVE-2025-39759 https://www.cve.org/CVERecord?id=CVE-2025-39759 Référence CVE CVE-2025-39760 https://www.cve.org/CVERecord?id=CVE-2025-39760 Référence CVE CVE-2025-39761 https://www.cve.org/CVERecord?id=CVE-2025-39761 Référence CVE CVE-2025-39763 https://www.cve.org/CVERecord?id=CVE-2025-39763 Référence CVE CVE-2025-39766 https://www.cve.org/CVERecord?id=CVE-2025-39766 Référence CVE CVE-2025-39770 https://www.cve.org/CVERecord?id=CVE-2025-39770 Référence CVE CVE-2025-39772 https://www.cve.org/CVERecord?id=CVE-2025-39772 Référence CVE CVE-2025-39773 https://www.cve.org/CVERecord?id=CVE-2025-39773 Référence CVE CVE-2025-39776 https://www.cve.org/CVERecord?id=CVE-2025-39776 Référence CVE CVE-2025-39779 https://www.cve.org/CVERecord?id=CVE-2025-39779 Référence CVE CVE-2025-39781 https://www.cve.org/CVERecord?id=CVE-2025-39781 Référence CVE CVE-2025-39782 https://www.cve.org/CVERecord?id=CVE-2025-39782 Référence CVE CVE-2025-39783 https://www.cve.org/CVERecord?id=CVE-2025-39783 Référence CVE CVE-2025-39787 https://www.cve.org/CVERecord?id=CVE-2025-39787 Référence CVE CVE-2025-39788 https://www.cve.org/CVERecord?id=CVE-2025-39788 Référence CVE CVE-2025-39790 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-39757 Référence CVE CVE-2025-39758 https://www.cve.org/CVERecord?id=CVE-2025-39758 Référence CVE CVE-2025-39759 https://www.cve.org/CVERecord?id=CVE-2025-39759 Référence CVE CVE-2025-39760 https://www.cve.org/CVERecord?id=CVE-2025-39760 Référence CVE CVE-2025-39761 https://www.cve.org/CVERecord?id=CVE-2025-39761 Référence CVE CVE-2025-39763 https://www.cve.org/CVERecord?id=CVE-2025-39763 Référence CVE CVE-2025-39766 https://www.cve.org/CVERecord?id=CVE-2025-39766 Référence CVE CVE-2025-39770 https://www.cve.org/CVERecord?id=CVE-2025-39770 Référence CVE CVE-2025-39772 https://www.cve.org/CVERecord?id=CVE-2025-39772 Référence CVE CVE-2025-39773 https://www.cve.org/CVERecord?id=CVE-2025-39773 Référence CVE CVE-2025-39776 https://www.cve.org/CVERecord?id=CVE-2025-39776 Référence CVE CVE-2025-39779 https://www.cve.org/CVERecord?id=CVE-2025-39779 Référence CVE CVE-2025-39781 https://www.cve.org/CVERecord?id=CVE-2025-39781 Référence CVE CVE-2025-39782 https://www.cve.org/CVERecord?id=CVE-2025-39782 Référence CVE CVE-2025-39783 https://www.cve.org/CVERecord?id=CVE-2025-39783 Référence CVE CVE-2025-39787 https://www.cve.org/CVERecord?id=CVE-2025-39787 Référence CVE CVE-2025-39788 https://www.cve.org/CVERecord?id=CVE-2025-39788 Référence CVE CVE-2025-39790 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-39757 Référence CVE CVE-2025-39758 https://www.cve.org/CVERecord?id=CVE-2025-39758 Référence CVE CVE-2025-39759 https://www.cve.org/CVERecord?id=CVE-2025-39759 Référence CVE CVE-2025-39760 https://www.cve.org/CVERecord?id=CVE-2025-39760 Référence CVE CVE-2025-39761 https://www.cve.org/CVERecord?id=CVE-2025-39761 Référence CVE CVE-2025-39763 https://www.cve.org/CVERecord?id=CVE-2025-39763 Référence CVE CVE-2025-39766 https://www.cve.org/CVERecord?id=CVE-2025-39766 Référence CVE CVE-2025-39770 https://www.cve.org/CVERecord?id=CVE-2025-39770 Référence CVE CVE-2025-39772 https://www.cve.org/CVERecord?id=CVE-2025-39772 Référence CVE CVE-2025-39773 https://www.cve.org/CVERecord?id=CVE-2025-39773 Référence CVE CVE-2025-39776 https://www.cve.org/CVERecord?id=CVE-2025-39776 Référence CVE CVE-2025-39779 https://www.cve.org/CVERecord?id=CVE-2025-39779 Référence CVE CVE-2025-39781 https://www.cve.org/CVERecord?id=CVE-2025-39781 Référence CVE CVE-2025-39782 https://www.cve.org/CVERecord?id=CVE-2025-39782 Référence CVE CVE-2025-39783 https://www.cve.org/CVERecord?id=CVE-2025-39783 Référence CVE CVE-2025-39787 https://www.cve.org/CVERecord?id=CVE-2025-39787 Référence CVE CVE-2025-39788 https://www.cve.org/CVERecord?id=CVE-2025-39788 Référence CVE CVE-2025-39790 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-39757 Référence CVE CVE-2025-39758 https://www.cve.org/CVERecord?id=CVE-2025-39758 Référence CVE CVE-2025-39759 https://www.cve.org/CVERecord?id=CVE-2025-39759 Référence CVE CVE-2025-39760 https://www.cve.org/CVERecord?id=CVE-2025-39760 Référence CVE CVE-2025-39761 https://www.cve.org/CVERecord?id=CVE-2025-39761 Référence CVE CVE-2025-39763 https://www.cve.org/CVERecord?id=CVE-2025-39763 Référence CVE CVE-2025-39766 https://www.cve.org/CVERecord?id=CVE-2025-39766 Référence CVE CVE-2025-39770 https://www.cve.org/CVERecord?id=CVE-2025-39770 Référence CVE CVE-2025-39772 https://www.cve.org/CVERecord?id=CVE-2025-39772 Référence CVE CVE-2025-39773 https://www.cve.org/CVERecord?id=CVE-2025-39773 Référence CVE CVE-2025-39776 https://www.cve.org/CVERecord?id=CVE-2025-39776 Référence CVE CVE-2025-39779 https://www.cve.org/CVERecord?id=CVE-2025-39779 Référence CVE CVE-2025-39781 https://www.cve.org/CVERecord?id=CVE-2025-39781 Référence CVE CVE-2025-39782 https://www.cve.org/CVERecord?id=CVE-2025-39782 Référence CVE CVE-2025-39783 https://www.cve.org/CVERecord?id=CVE-2025-39783 Référence CVE CVE-2025-39787 https://www.cve.org/CVERecord?id=CVE-2025-39787 Référence CVE CVE-2025-39788 https://www.cve.org/CVERecord?id=CVE-2025-39788 Référence CVE CVE-2025-39790 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-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=CVE-2025-39756 Référence CVE CVE-2025-39757 https://www.cve.org/CVERecord?id=CVE-2025-39757 Référence CVE CVE-2025-39760 https://www.cve.org/CVERecord?id=CVE-2025-39760 Référence CVE CVE-2025-39766 https://www.cve.org/CVERecord?id=CVE-2025-39766 Référence CVE CVE-2025-39772 https://www.cve.org/CVERecord?id=CVE-2025-39772 Référence CVE CVE-2025-39773 https://www.cve.org/CVERecord?id=CVE-2025-39773 Référence CVE CVE-2025-39776 https://www.cve.org/CVERecord?id=CVE-2025-39776 Référence CVE CVE-2025-39782 https://www.cve.org/CVERecord?id=CVE-2025-39782 Référence CVE CVE-2025-39783 https://www.cve.org/CVERecord?id=CVE-2025-39783 Référence CVE CVE-2025-39787 https://www.cve.org/CVERecord?id=CVE-2025-39787 Référence CVE CVE-2025-39788 https://www.cve.org/CVERecord?id=CVE-2025-39788 Référence CVE CVE-2025-39790 https://www.cve.org/CVERecord?id=CVE-2025-39790 Référence CVE CVE-2025-39794 https://www.cve.org/CVERecord?id=CVE-2025-39794 Référence CVE CVE-2025-39795 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-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=CVE-2025-39756 Référence CVE CVE-2025-39757 https://www.cve.org/CVERecord?id=CVE-2025-39757 Référence CVE CVE-2025-39760 https://www.cve.org/CVERecord?id=CVE-2025-39760 Référence CVE CVE-2025-39766 https://www.cve.org/CVERecord?id=CVE-2025-39766 Référence CVE CVE-2025-39772 https://www.cve.org/CVERecord?id=CVE-2025-39772 Référence CVE CVE-2025-39773 https://www.cve.org/CVERecord?id=CVE-2025-39773 Référence CVE CVE-2025-39776 https://www.cve.org/CVERecord?id=CVE-2025-39776 Référence CVE CVE-2025-39782 https://www.cve.org/CVERecord?id=CVE-2025-39782 Référence CVE CVE-2025-39783 https://www.cve.org/CVERecord?id=CVE-2025-39783 Référence CVE CVE-2025-39787 https://www.cve.org/CVERecord?id=CVE-2025-39787 Référence CVE CVE-2025-39788 https://www.cve.org/CVERecord?id=CVE-2025-39788 Référence CVE CVE-2025-39790 https://www.cve.org/CVERecord?id=CVE-2025-39790 Référence CVE CVE-2025-39794 https://www.cve.org/CVERecord?id=CVE-2025-39794 Référence CVE CVE-2025-39795 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-39759 Référence CVE CVE-2025-39760 https://www.cve.org/CVERecord?id=CVE-2025-39760 Référence CVE CVE-2025-39761 https://www.cve.org/CVERecord?id=CVE-2025-39761 Référence CVE CVE-2025-39763 https://www.cve.org/CVERecord?id=CVE-2025-39763 Référence CVE CVE-2025-39764 https://www.cve.org/CVERecord?id=CVE-2025-39764 Référence CVE CVE-2025-39765 https://www.cve.org/CVERecord?id=CVE-2025-39765 Référence CVE CVE-2025-39766 https://www.cve.org/CVERecord?id=CVE-2025-39766 Référence CVE CVE-2025-39770 https://www.cve.org/CVERecord?id=CVE-2025-39770 Référence CVE CVE-2025-39772 https://www.cve.org/CVERecord?id=CVE-2025-39772 Référence CVE CVE-2025-39773 https://www.cve.org/CVERecord?id=CVE-2025-39773 Référence CVE CVE-2025-39775 https://www.cve.org/CVERecord?id=CVE-2025-39775 Référence CVE CVE-2025-39779 https://www.cve.org/CVERecord?id=CVE-2025-39779 Référence CVE CVE-2025-39782 https://www.cve.org/CVERecord?id=CVE-2025-39782 Référence CVE CVE-2025-39783 https://www.cve.org/CVERecord?id=CVE-2025-39783 Référence CVE CVE-2025-39787 https://www.cve.org/CVERecord?id=CVE-2025-39787 Référence CVE CVE-2025-39788 https://www.cve.org/CVERecord?id=CVE-2025-39788 Référence CVE CVE-2025-39790 https://www.cve.org/CVERecord?id=CVE-2025-39790 Référence CVE CVE-2025-39791 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-39758 Référence CVE CVE-2025-39759 https://www.cve.org/CVERecord?id=CVE-2025-39759 Référence CVE CVE-2025-39760 https://www.cve.org/CVERecord?id=CVE-2025-39760 Référence CVE CVE-2025-39761 https://www.cve.org/CVERecord?id=CVE-2025-39761 Référence CVE CVE-2025-39763 https://www.cve.org/CVERecord?id=CVE-2025-39763 Référence CVE CVE-2025-39764 https://www.cve.org/CVERecord?id=CVE-2025-39764 Référence CVE CVE-2025-39766 https://www.cve.org/CVERecord?id=CVE-2025-39766 Référence CVE CVE-2025-39770 https://www.cve.org/CVERecord?id=CVE-2025-39770 Référence CVE CVE-2025-39772 https://www.cve.org/CVERecord?id=CVE-2025-39772 Référence CVE CVE-2025-39773 https://www.cve.org/CVERecord?id=CVE-2025-39773 Référence CVE CVE-2025-39782 https://www.cve.org/CVERecord?id=CVE-2025-39782 Référence CVE CVE-2025-39783 https://www.cve.org/CVERecord?id=CVE-2025-39783 Référence CVE CVE-2025-39787 https://www.cve.org/CVERecord?id=CVE-2025-39787 Référence CVE CVE-2025-39790 https://www.cve.org/CVERecord?id=CVE-2025-39790 Référence CVE CVE-2025-39797 https://www.cve.org/CVERecord?id=CVE-2025-39797 Référence CVE CVE-2025-39798 https://www.cve.org/CVERecord?id=CVE-2025-39798 Référence CVE CVE-2025-39800 https://www.cve.org/CVERecord?id=CVE-2025-39800 Référence CVE CVE-2025-39801 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-39758 Référence CVE CVE-2025-39759 https://www.cve.org/CVERecord?id=CVE-2025-39759 Référence CVE CVE-2025-39760 https://www.cve.org/CVERecord?id=CVE-2025-39760 Référence CVE CVE-2025-39761 https://www.cve.org/CVERecord?id=CVE-2025-39761 Référence CVE CVE-2025-39763 https://www.cve.org/CVERecord?id=CVE-2025-39763 Référence CVE CVE-2025-39764 https://www.cve.org/CVERecord?id=CVE-2025-39764 Référence CVE CVE-2025-39766 https://www.cve.org/CVERecord?id=CVE-2025-39766 Référence CVE CVE-2025-39770 https://www.cve.org/CVERecord?id=CVE-2025-39770 Référence CVE CVE-2025-39772 https://www.cve.org/CVERecord?id=CVE-2025-39772 Référence CVE CVE-2025-39773 https://www.cve.org/CVERecord?id=CVE-2025-39773 Référence CVE CVE-2025-39782 https://www.cve.org/CVERecord?id=CVE-2025-39782 Référence CVE CVE-2025-39783 https://www.cve.org/CVERecord?id=CVE-2025-39783 Référence CVE CVE-2025-39787 https://www.cve.org/CVERecord?id=CVE-2025-39787 Référence CVE CVE-2025-39790 https://www.cve.org/CVERecord?id=CVE-2025-39790 Référence CVE CVE-2025-39797 https://www.cve.org/CVERecord?id=CVE-2025-39797 Référence CVE CVE-2025-39798 https://www.cve.org/CVERecord?id=CVE-2025-39798 Référence CVE CVE-2025-39800 https://www.cve.org/CVERecord?id=CVE-2025-39800 Référence CVE CVE-2025-39801 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-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=CVE-2025-39756 Référence CVE CVE-2025-39757 https://www.cve.org/CVERecord?id=CVE-2025-39757 Référence CVE CVE-2025-39759 https://www.cve.org/CVERecord?id=CVE-2025-39759 Référence CVE CVE-2025-39760 https://www.cve.org/CVERecord?id=CVE-2025-39760 Référence CVE CVE-2025-39766 https://www.cve.org/CVERecord?id=CVE-2025-39766 Référence CVE CVE-2025-39770 https://www.cve.org/CVERecord?id=CVE-2025-39770 Référence CVE CVE-2025-39772 https://www.cve.org/CVERecord?id=CVE-2025-39772 Référence CVE CVE-2025-39773 https://www.cve.org/CVERecord?id=CVE-2025-39773 Référence CVE CVE-2025-39776 https://www.cve.org/CVERecord?id=CVE-2025-39776 Référence CVE CVE-2025-39782 https://www.cve.org/CVERecord?id=CVE-2025-39782 Référence CVE CVE-2025-39783 https://www.cve.org/CVERecord?id=CVE-2025-39783 Référence CVE CVE-2025-39787 https://www.cve.org/CVERecord?id=CVE-2025-39787 Référence CVE CVE-2025-39788 https://www.cve.org/CVERecord?id=CVE-2025-39788 Référence CVE CVE-2025-39790 https://www.cve.org/CVERecord?id=CVE-2025-39790 Référence CVE CVE-2025-39794 https://www.cve.org/CVERecord?id=CVE-2025-39794 Référence CVE CVE-2025-39795 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-39756 Référence CVE CVE-2025-39757 https://www.cve.org/CVERecord?id=CVE-2025-39757 Référence CVE CVE-2025-39759 https://www.cve.org/CVERecord?id=CVE-2025-39759 Référence CVE CVE-2025-39760 https://www.cve.org/CVERecord?id=CVE-2025-39760 Référence CVE CVE-2025-39765 https://www.cve.org/CVERecord?id=CVE-2025-39765 Référence CVE CVE-2025-39766 https://www.cve.org/CVERecord?id=CVE-2025-39766 Référence CVE CVE-2025-39767 https://www.cve.org/CVERecord?id=CVE-2025-39767 Référence CVE CVE-2025-39770 https://www.cve.org/CVERecord?id=CVE-2025-39770 Référence CVE CVE-2025-39772 https://www.cve.org/CVERecord?id=CVE-2025-39772 Référence CVE CVE-2025-39773 https://www.cve.org/CVERecord?id=CVE-2025-39773 Référence CVE CVE-2025-39776 https://www.cve.org/CVERecord?id=CVE-2025-39776 Référence CVE CVE-2025-39779 https://www.cve.org/CVERecord?id=CVE-2025-39779 Référence CVE CVE-2025-39780 https://www.cve.org/CVERecord?id=CVE-2025-39780 Référence CVE CVE-2025-39781 https://www.cve.org/CVERecord?id=CVE-2025-39781 Référence CVE CVE-2025-39782 https://www.cve.org/CVERecord?id=CVE-2025-39782 Référence CVE CVE-2025-39783 https://www.cve.org/CVERecord?id=CVE-2025-39783 Référence CVE CVE-2025-39787 https://www.cve.org/CVERecord?id=CVE-2025-39787 Référence CVE CVE-2025-39788 https://www.cve.org/CVERecord?id=

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

Multiple security vulnerabilities affecting the Linux kernel, including timer overflow, CPU cache initialization flaws, AMD processor data leakage, and the VMSCAPE branch predictor isolation flaw, were addressed 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.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.34; 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.*; 6.17 ≤ *
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 11 Sept 2025 · Last source change 14 Jul 2026, 12:42 UTC · CWE-667 · Improper Locking

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

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

Material change intelligence

What changed after publication

View recent updates →

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

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