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

bpf: Forget ranges when refining tnum after JSET

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 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-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 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: bpf: Forget ranges when refining tnum after JSET Syzbot reported a kernel warning due to a range invariant violation on the following BPF program. 0: call bpf_get_netns_cookie 1: if r0 == 0 goto 2: if r0 & Oxffffffff goto The issue is on the path where we fall through both jumps. That path is unreachable at runtime: after insn 1, we know r0 != 0, but with the sign extension on the jset, we would only fallthrough insn 2 if r0 == 0. Unfortunately, is_branch_taken() isn't currently able to figure this out, so the verifier walks all branches. The verifier then refines the register bounds using the second condition and we end up with inconsistent bounds on this unreachable path: 1: if r0 == 0 goto r0: u64=[0x1, 0xffffffffffffffff] var_off=(0, 0xffffffffffffffff) 2: if r0 & 0xffffffff goto r0 before reg_bounds_sync: u64=[0x1, 0xffffffffffffffff] var_off=(0, 0) r0 after reg_bounds_sync: u64=[0x1, 0] var_off=(0, 0) Improving the range refinement for JSET to cover all cases is tricky. We also don't expect many users to rely on JSET given LLVM doesn't generate those instructions. So instead of improving the range refinement for JSETs, Eduard suggested we forget the ranges whenever we're narrowing tnums after a JSET. This patch implements that approach.
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: bpf: Forget ranges when refining tnum after JSET Syzbot reported a kernel warning due to a range invariant violation on the following BPF program. 0: call bpf_get_netns_cookie 1: if r0 == 0 goto 2: if r0 & Oxffffffff goto The issue is on the path where we fall through both jumps. That path is unreachable at runtime: after insn 1, we know r0 != 0, but with the sign extension on the jset, we would only fallthrough insn 2 if r0 == 0. Unfortunately, is_branch_taken() isn't currently able to figure this out, so the verifier walks all branches. The verifier then refines the register bounds using the second condition and we end up with inconsistent bounds on this unreachable path: 1: if r0 == 0 goto r0: u64=[0x1, 0xffffffffffffffff] var_off=(0, 0xffffffffffffffff) 2: if r0 & 0xffffffff goto r0 before reg_bounds_sync: u64=[0x1, 0xffffffffffffffff] var_off=(0, 0) r0 after reg_bounds_sync: u64=[0x1, 0] var_off=(0, 0) Improving the range refinement for JSET to cover all cases is tricky. We also don't expect many users to rely on JSET given LLVM doesn't generate those instructions. So instead of improving the range refinement for JSETs, Eduard suggested we forget the ranges whenever we're narrowing tnums after a JSET. This patch implements that approach.
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-2025-28963

No EUVD known-exploited evidence

In the Linux kernel, the following vulnerability has been resolved: bpf: Forget ranges when refining tnum after JSET Syzbot reported a kernel warning due to a range invariant violation on the following BPF program. 0: call bpf_get_netns_cookie 1: if r0 == 0 goto <exit> 2: if r0 & Oxffffffff goto <exit> The issue is on the path where we fall through both jumps. That path is unreachable at runtime: after insn 1, we know r0 != 0, but with the sign extension on the jset, we would only fallthrough insn 2 if r0 == 0. Unfortunately, is_branch_taken() isn't currently able to figure this out, so the verifier walks all branches. The verifier then refines the register bounds using the second condition and we end up with inconsistent bounds on this unreachable path: 1: if r0 == 0 goto <exit> r0: u64=[0x1, 0xffffffffffffffff] var_off=(0, 0xffffffffffffffff) 2: if r0 & 0xffffffff goto <exit> r0 before reg_bounds_sync: u64=[0x1, 0xffffffffffffffff] var_off=(0, 0) r0 after reg_bounds_sync: u64=[0x1, 0] var_off=(0, 0) Improving the range refinement for JSET to cover all cases is tricky. We also don't expect many users to rely on JSET given LLVM doesn't generate those instructions. So instead of improving the range refinement for JSETs, Eduard suggested we forget the ranges whenever we're narrowing tnums after a JSET. This patch implements that approach.

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

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

Patch available
01

What, why and how

In the Linux kernel, the following vulnerability has been resolved: bpf: Forget ranges when refining tnum after JSET Syzbot reported a kernel warning due to a range invariant violation on the following BPF program. 0: call bpf_get_netns_cookie 1: if r0 == 0 goto <exit> 2: if r0 & Oxffffffff goto <exit> The issue is on the path where we fall through both jumps. That path is unreachable at runtime: after insn 1, we know r0 != 0, but with the sign extension on the jset, we would only fallthrough insn 2 if r0 == 0. Unfortunately, is_branch_taken() isn't currently able to figure this out, so the verifier walks all branches. The verifier then refines the register bounds using the second condition and we end up with inconsistent bounds on this unreachable path: 1: if r0 == 0 goto <exit> r0: u64=[0x1, 0xffffffffffffffff] var_off=(0, 0xffffffffffffffff) 2: if r0 & 0xffffffff goto <exit> r0 before reg_bounds_sync: u64=[0x1, 0xffffffffffffffff] var_off=(0, 0) r0 after reg_bounds_sync: u64=[0x1, 0] var_off=(0, 0) Improving the range refinement for JSET to cover all cases is tricky. We also don't expect many users to rely on JSET given LLVM doesn't generate those instructions. So instead of improving the range refinement for JSETs, Eduard suggested we forget the ranges whenever we're narrowing tnums after a JSET. This patch implements that approach.

What

In the Linux kernel, the following vulnerability has been resolved: bpf: Forget ranges when refining tnum after JSET Syzbot reported a kernel warning due to a range invariant violation on the following BPF program. 0: call bpf_get_netns_cookie 1: if r0 == 0 goto <exit> 2: if r0 & Oxffffffff goto <exit> The issue is on the path where we fall through both jumps. That path is unreachable at runtime: after insn 1, we know r0 != 0, but with the sign extension on the jset, we would only fallthrough insn 2 if r0 == 0. Unfortunately, is_branch_taken() isn't currently able to figure this out, so the verifier walks all branches. The verifier then refines the register bounds using the second condition and we end up with inconsistent bounds on this unreachable path: 1: if r0 == 0 goto <exit> r0: u64=[0x1, 0xffffffffffffffff] var_off=(0, 0xffffffffffffffff) 2: if r0 & 0xffffffff goto <exit> r0 before reg_bounds_sync: u64=[0x1, 0xffffffffffffffff] var_off=(0, 0) r0 after reg_bounds_sync: u64=[0x1, 0] var_off=(0, 0) Improving the range refinement for JSET to cover all cases is tricky. We also don't expect many users to rely on JSET given LLVM doesn't generate those instructions. So instead of improving the range refinement for JSETs, Eduard suggested we forget the ranges whenever we're narrowing tnums after a JSET. This patch implements that approach.

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: bpf: Forget ranges when refining tnum after JSET Syzbot reported a kernel warning due to a range invariant violation on the following BPF program. 0: call bpf_get_netns_cookie 1: if r0 == 0 goto <exit> 2: if r0 & Oxffffffff goto <exit> The issue is on the path where we fall through both jumps. That path is unreachable at runtime: after insn 1, we know r0 != 0, but with the sign extension on the jset, we would only fallthrough insn 2 if r0 == 0. Unfortunately, is_branch_taken() isn't currently able to figure this out, so the verifier walks all branches. The verifier then refines the register bounds using the second condition and we end up with inconsistent bounds on this unreachable path: 1: if r0 == 0 goto <exit> r0: u64=[0x1, 0xffffffffffffffff] var_off=(0, 0xffffffffffffffff) 2: if r0 & 0xffffffff goto <exit> r0 before reg_bounds_sync: u64=[0x1, 0xffffffffffffffff] var_off=(0, 0) r0 after reg_bounds_sync: u64=[0x1, 0] var_off=(0, 0) Improving the range refinement for JSET to cover all cases is tricky. We also don't expect many users to rely on JSET given LLVM doesn't generate those instructions. So instead of improving the range refinement for JSETs, Eduard suggested we forget the ranges whenever we're narrowing tnums after a JSET. This patch implements that approach.

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.

ENISA EUVD · EUVD-2025-28963Official EUVD mapping

In the Linux kernel, the following vulnerability has been resolved: bpf: Forget ranges when refining tnum after JSET Syzbot reported a kernel warning due to a range invariant violation on the following BPF program. 0: call bpf_get_netns_cookie 1: if r0 == 0 goto <exit> 2: if r0 & Oxffffffff goto <exit> The issue is on the path where we fall through both jumps. That path is unreachable at runtime: after insn 1, we know r0 != 0, but with the sign extension on the jset, we would only fallthrough insn 2 if r0 == 0. Unfortunately, is_branch_taken() isn't currently able to figure this out, so the verifier walks all branches. The verifier then refines the register bounds using the second condition and we end up with inconsistent bounds on this unreachable path: 1: if r0 == 0 goto <exit> r0: u64=[0x1, 0xffffffffffffffff] var_off=(0, 0xffffffffffffffff) 2: if r0 & 0xffffffff goto <exit> r0 before reg_bounds_sync: u64=[0x1, 0xffffffffffffffff] var_off=(0, 0) r0 after reg_bounds_sync: u64=[0x1, 0] var_off=(0, 0) Improving the range refinement for JSET to cover all cases is tricky. We also don't expect many users to rely on JSET given LLVM doesn't generate those instructions. So instead of improving the range refinement for JSETs, Eduard suggested we forget the ranges whenever we're narrowing tnums after a JSET. This patch implements that approach.

Official EUVD record
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-1093Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2025-37786 Référence CVE CVE-2025-38006 https://www.cve.org/CVERecord?id=CVE-2025-38006 Référence CVE CVE-2025-38105 https://www.cve.org/CVERecord?id=CVE-2025-38105 Référence CVE CVE-2025-38192 https://www.cve.org/CVERecord?id=CVE-2025-38192 Référence CVE CVE-2025-38250 https://www.cve.org/CVERecord?id=CVE-2025-38250 Référence CVE CVE-2025-38562 https://www.cve.org/CVERecord?id=CVE-2025-38562 Référence CVE CVE-2025-38626 https://www.cve.org/CVERecord?id=CVE-2025-38626 Référence CVE CVE-2025-38659 https://www.cve.org/CVERecord?id=CVE-2025-38659 Référence CVE CVE-2025-38710 https://www.cve.org/CVERecord?id=CVE-2025-38710 Référence CVE CVE-2025-39748 https://www.cve.org/CVERecord?id=CVE-2025-39748 Référence CVE CVE-2025-39764 https://www.cve.org/CVERecord?id=CVE-2025-39764 Référence CVE CVE-2025-40005 https://www.cve.org/CVERecord?id=CVE-2025-40005 Référence CVE CVE-2025-40016 https://www.cve.org/CVERecord?id=CVE-2025-40016 Référence CVE CVE-2025-40103 https://www.cve.org/CVERecord?id=CVE-2025-40103 Référence CVE CVE-2025-40323 https://www.cve.org/CVERecord?id=CVE-2025-40323 Référence CVE CVE-2025-54505 https://www.cve.org/CVERecord?id=CVE-2025-54505 Référence CVE CVE-2025-54518 https://www.cve.org/CVERecord?id=CVE-2025-54518 Référence CVE CVE-2025-68206 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-37786 Référence CVE CVE-2025-38006 https://www.cve.org/CVERecord?id=CVE-2025-38006 Référence CVE CVE-2025-38105 https://www.cve.org/CVERecord?id=CVE-2025-38105 Référence CVE CVE-2025-38192 https://www.cve.org/CVERecord?id=CVE-2025-38192 Référence CVE CVE-2025-38250 https://www.cve.org/CVERecord?id=CVE-2025-38250 Référence CVE CVE-2025-38562 https://www.cve.org/CVERecord?id=CVE-2025-38562 Référence CVE CVE-2025-38626 https://www.cve.org/CVERecord?id=CVE-2025-38626 Référence CVE CVE-2025-38659 https://www.cve.org/CVERecord?id=CVE-2025-38659 Référence CVE CVE-2025-38710 https://www.cve.org/CVERecord?id=CVE-2025-38710 Référence CVE CVE-2025-39748 https://www.cve.org/CVERecord?id=CVE-2025-39748 Référence CVE CVE-2025-39764 https://www.cve.org/CVERecord?id=CVE-2025-39764 Référence CVE CVE-2025-40005 https://www.cve.org/CVERecord?id=CVE-2025-40005 Référence CVE CVE-2025-40016 https://www.cve.org/CVERecord?id=CVE-2025-40016 Référence CVE CVE-2025-40103 https://www.cve.org/CVERecord?id=CVE-2025-40103 Référence CVE CVE-2025-40323 https://www.cve.org/CVERecord?id=CVE-2025-40323 Référence CVE CVE-2025-54505 https://www.cve.org/CVERecord?id=CVE-2025-54505 Référence CVE CVE-2025-54518 https://www.cve.org/CVERecord?id=CVE-2025-54518 Référence CVE CVE-2025-68206 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-38105 Référence CVE CVE-2025-38192 https://www.cve.org/CVERecord?id=CVE-2025-38192 Référence CVE CVE-2025-38201 https://www.cve.org/CVERecord?id=CVE-2025-38201 Référence CVE CVE-2025-38250 https://www.cve.org/CVERecord?id=CVE-2025-38250 Référence CVE CVE-2025-38426 https://www.cve.org/CVERecord?id=CVE-2025-38426 Référence CVE CVE-2025-38562 https://www.cve.org/CVERecord?id=CVE-2025-38562 Référence CVE CVE-2025-38626 https://www.cve.org/CVERecord?id=CVE-2025-38626 Référence CVE CVE-2025-38659 https://www.cve.org/CVERecord?id=CVE-2025-38659 Référence CVE CVE-2025-38710 https://www.cve.org/CVERecord?id=CVE-2025-38710 Référence CVE CVE-2025-39748 https://www.cve.org/CVERecord?id=CVE-2025-39748 Référence CVE CVE-2025-39764 https://www.cve.org/CVERecord?id=CVE-2025-39764 Référence CVE CVE-2025-40005 https://www.cve.org/CVERecord?id=CVE-2025-40005 Référence CVE CVE-2025-40016 https://www.cve.org/CVERecord?id=CVE-2025-40016 Référence CVE CVE-2025-40082 https://www.cve.org/CVERecord?id=CVE-2025-40082 Référence CVE CVE-2025-40103 https://www.cve.org/CVERecord?id=CVE-2025-40103 Référence CVE CVE-2025-40135 https://www.cve.org/CVERecord?id=CVE-2025-40135 Référence CVE CVE-2025-40150 https://www.cve.org/CVERecord?id=CVE-2025-40150 Référence CVE CVE-2025-40323 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-38006 Référence CVE CVE-2025-38105 https://www.cve.org/CVERecord?id=CVE-2025-38105 Référence CVE CVE-2025-38192 https://www.cve.org/CVERecord?id=CVE-2025-38192 Référence CVE CVE-2025-38250 https://www.cve.org/CVERecord?id=CVE-2025-38250 Référence CVE CVE-2025-38426 https://www.cve.org/CVERecord?id=CVE-2025-38426 Référence CVE CVE-2025-38562 https://www.cve.org/CVERecord?id=CVE-2025-38562 Référence CVE CVE-2025-38626 https://www.cve.org/CVERecord?id=CVE-2025-38626 Référence CVE CVE-2025-38659 https://www.cve.org/CVERecord?id=CVE-2025-38659 Référence CVE CVE-2025-38710 https://www.cve.org/CVERecord?id=CVE-2025-38710 Référence CVE CVE-2025-39748 https://www.cve.org/CVERecord?id=CVE-2025-39748 Référence CVE CVE-2025-39764 https://www.cve.org/CVERecord?id=CVE-2025-39764 Référence CVE CVE-2025-40005 https://www.cve.org/CVERecord?id=CVE-2025-40005 Référence CVE CVE-2025-40016 https://www.cve.org/CVERecord?id=CVE-2025-40016 Référence CVE CVE-2025-40103 https://www.cve.org/CVERecord?id=CVE-2025-40103 Référence CVE CVE-2025-40135 https://www.cve.org/CVERecord?id=CVE-2025-40135 Référence CVE CVE-2025-40150 https://www.cve.org/CVERecord?id=CVE-2025-40150 Référence CVE CVE-2025-40323 https://www.cve.org/CVERecord?id=CVE-2025-40323 Référence CVE CVE-2025-54505 https://www.cve.org/CVERecord?id=

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

25-21959, CVE-2025-21999, CVE-2025-22005, CVE-2025-22015, CVE-2025-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

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

nux de Debian LTS. Certaines d'entre elles permettent à un attaquant de provoquer une élévation de privilèges, une atteinte à la confidentialité des données et un déni de service. Solutions Se référer au bulletin de sécurité de l'éditeur pour l'obtention des correctifs (cf. section Documentation). Documentation Bulletin de sécurité Debian LTS msg00051 du 29 mai 2026 https://lists.debian.org/debian-lts-announce/2026/05/msg00051.html Bulletin de sécurité Debian LTS msg00052 du 29 mai 2026 https://lists.debian.org/debian-lts-announce/2026/05/msg00052.html Référence CVE CVE-2024-56584 https://www.cve.org/CVERecord?id=CVE-2024-56584 Référence CVE CVE-2025-39748 https://www.cve.org/CVERecord?id=CVE-2025-39748 Référence CVE CVE-2025-39764 https://www.cve.org/CVERecord?id=CVE-2025-39764 Référence CVE CVE-2025-40219 https://www.cve.org/CVERecord?id=CVE-2025-40219 Référence CVE CVE-2025-40261 https://www.cve.org/CVERecord?id=CVE-2025-40261 Référence CVE CVE-2025-68206 https://www.cve.org/CVERecord?id=CVE-2025-68206 Référence CVE CVE-2025-71274 https://www.cve.org/CVERecord?id=CVE-2025-71274 Référence CVE CVE-2025-71292 https://www.cve.org/CVERecord?id=CVE-2025-71292 Référence CVE CVE-2025-71304 https://www.cve.org/CVERecord?id=CVE-2025-71304 Référence CVE CVE-2026-23100 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-38192 Référence CVE CVE-2025-38250 https://www.cve.org/CVERecord?id=CVE-2025-38250 Référence CVE CVE-2025-38303 https://www.cve.org/CVERecord?id=CVE-2025-38303 Référence CVE CVE-2025-38426 https://www.cve.org/CVERecord?id=CVE-2025-38426 Référence CVE CVE-2025-38436 https://www.cve.org/CVERecord?id=CVE-2025-38436 Référence CVE CVE-2025-38626 https://www.cve.org/CVERecord?id=CVE-2025-38626 Référence CVE CVE-2025-38627 https://www.cve.org/CVERecord?id=CVE-2025-38627 Référence CVE CVE-2025-38659 https://www.cve.org/CVERecord?id=CVE-2025-38659 Référence CVE CVE-2025-38704 https://www.cve.org/CVERecord?id=CVE-2025-38704 Référence CVE CVE-2025-39748 https://www.cve.org/CVERecord?id=CVE-2025-39748 Référence CVE CVE-2025-39764 https://www.cve.org/CVERecord?id=CVE-2025-39764 Référence CVE CVE-2025-39863 https://www.cve.org/CVERecord?id=CVE-2025-39863 Référence CVE CVE-2025-40005 https://www.cve.org/CVERecord?id=CVE-2025-40005 Référence CVE CVE-2025-40016 https://www.cve.org/CVERecord?id=CVE-2025-40016 Référence CVE CVE-2025-40135 https://www.cve.org/CVERecord?id=CVE-2025-40135 Référence CVE CVE-2025-40147 https://www.cve.org/CVERecord?id=CVE-2025-40147 Référence CVE CVE-2025-40150 https://www.cve.org/CVERecord?id=CVE-2025-40150 Référence CVE CVE-2025-40219 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-2025-38105 Référence CVE CVE-2025-38162 https://www.cve.org/CVERecord?id=CVE-2025-38162 Référence CVE CVE-2025-38192 https://www.cve.org/CVERecord?id=CVE-2025-38192 Référence CVE CVE-2025-38250 https://www.cve.org/CVERecord?id=CVE-2025-38250 Référence CVE CVE-2025-38303 https://www.cve.org/CVERecord?id=CVE-2025-38303 Référence CVE CVE-2025-38436 https://www.cve.org/CVERecord?id=CVE-2025-38436 Référence CVE CVE-2025-38626 https://www.cve.org/CVERecord?id=CVE-2025-38626 Référence CVE CVE-2025-38659 https://www.cve.org/CVERecord?id=CVE-2025-38659 Référence CVE CVE-2025-38704 https://www.cve.org/CVERecord?id=CVE-2025-38704 Référence CVE CVE-2025-39748 https://www.cve.org/CVERecord?id=CVE-2025-39748 Référence CVE CVE-2025-39764 https://www.cve.org/CVERecord?id=CVE-2025-39764 Référence CVE CVE-2025-39863 https://www.cve.org/CVERecord?id=CVE-2025-39863 Référence CVE CVE-2025-40005 https://www.cve.org/CVERecord?id=CVE-2025-40005 Référence CVE CVE-2025-40016 https://www.cve.org/CVERecord?id=CVE-2025-40016 Référence CVE CVE-2025-40135 https://www.cve.org/CVERecord?id=CVE-2025-40135 Référence CVE CVE-2025-40219 https://www.cve.org/CVERecord?id=CVE-2025-40219 Référence CVE CVE-2025-40242 https://www.cve.org/CVERecord?id=CVE-2025-40242 Référence CVE CVE-2025-40261 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-38243 Référence CVE CVE-2025-38321 https://www.cve.org/CVERecord?id=CVE-2025-38321 Référence CVE CVE-2025-38322 https://www.cve.org/CVERecord?id=CVE-2025-38322 Référence CVE CVE-2025-38375 https://www.cve.org/CVERecord?id=CVE-2025-38375 Référence CVE CVE-2025-38379 https://www.cve.org/CVERecord?id=CVE-2025-38379 Référence CVE CVE-2025-38488 https://www.cve.org/CVERecord?id=CVE-2025-38488 Référence CVE CVE-2025-38539 https://www.cve.org/CVERecord?id=CVE-2025-38539 Référence CVE CVE-2025-38728 https://www.cve.org/CVERecord?id=CVE-2025-38728 Référence CVE CVE-2025-39689 https://www.cve.org/CVERecord?id=CVE-2025-39689 Référence CVE CVE-2025-39748 https://www.cve.org/CVERecord?id=CVE-2025-39748 Référence CVE CVE-2025-39813 https://www.cve.org/CVERecord?id=CVE-2025-39813 Référence CVE CVE-2025-39817 https://www.cve.org/CVERecord?id=CVE-2025-39817 Référence CVE CVE-2025-39829 https://www.cve.org/CVERecord?id=CVE-2025-39829 Référence CVE CVE-2025-39880 https://www.cve.org/CVERecord?id=CVE-2025-39880 Référence CVE CVE-2025-39890 https://www.cve.org/CVERecord?id=CVE-2025-39890 Référence CVE CVE-2025-39913 https://www.cve.org/CVERecord?id=CVE-2025-39913 Référence CVE CVE-2025-39964 https://www.cve.org/CVERecord?id=CVE-2025-39964 Référence CVE CVE-2025-39977 https://www.cve.org/CVERecord?id=

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

/suse-su-20260928-1 Référence CVE CVE-2023-53794 https://www.cve.org/CVERecord?id=CVE-2023-53794 Référence CVE CVE-2023-53817 https://www.cve.org/CVERecord?id=CVE-2023-53817 Référence CVE CVE-2023-53827 https://www.cve.org/CVERecord?id=CVE-2023-53827 Référence CVE CVE-2025-21738 https://www.cve.org/CVERecord?id=CVE-2025-21738 Référence CVE CVE-2025-37861 https://www.cve.org/CVERecord?id=CVE-2025-37861 Référence CVE CVE-2025-38129 https://www.cve.org/CVERecord?id=CVE-2025-38129 Référence CVE CVE-2025-38224 https://www.cve.org/CVERecord?id=CVE-2025-38224 Référence CVE CVE-2025-38375 https://www.cve.org/CVERecord?id=CVE-2025-38375 Référence CVE CVE-2025-39748 https://www.cve.org/CVERecord?id=CVE-2025-39748 Référence CVE CVE-2025-39964 https://www.cve.org/CVERecord?id=CVE-2025-39964 Référence CVE CVE-2025-40099 https://www.cve.org/CVERecord?id=CVE-2025-40099 Référence CVE CVE-2025-40103 https://www.cve.org/CVERecord?id=CVE-2025-40103 Référence CVE CVE-2025-68283 https://www.cve.org/CVERecord?id=CVE-2025-68283 Référence CVE CVE-2025-68285 https://www.cve.org/CVERecord?id=CVE-2025-68285 Référence CVE CVE-2025-68295 https://www.cve.org/CVERecord?id=CVE-2025-68295 Référence CVE CVE-2025-68374 https://www.cve.org/CVERecord?id=CVE-2025-68374 Référence CVE CVE-2025-68736 https://www.cve.org/CVERecord?id=

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

d?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-39720 https://www.cve.org/CVERecord?id=CVE-2025-39720 Référence CVE CVE-2025-39726 https://www.cve.org/CVERecord?id=CVE-2025-39726 Référence CVE CVE-2025-39732 https://www.cve.org/CVERecord?id=CVE-2025-39732 Référence CVE CVE-2025-39744 https://www.cve.org/CVERecord?id=CVE-2025-39744 Référence CVE CVE-2025-39745 https://www.cve.org/CVERecord?id=CVE-2025-39745 Référence CVE CVE-2025-39746 https://www.cve.org/CVERecord?id=CVE-2025-39746 Référence CVE CVE-2025-39747 https://www.cve.org/CVERecord?id=CVE-2025-39747 Référence CVE CVE-2025-39748 https://www.cve.org/CVERecord?id=CVE-2025-39748 Référence CVE CVE-2025-39750 https://www.cve.org/CVERecord?id=CVE-2025-39750 Référence CVE CVE-2025-39753 https://www.cve.org/CVERecord?id=CVE-2025-39753 Référence CVE CVE-2025-39754 https://www.cve.org/CVERecord?id=CVE-2025-39754 Référence CVE CVE-2025-39759 https://www.cve.org/CVERecord?id=CVE-2025-39759 Référence CVE CVE-2025-39761 https://www.cve.org/CVERecord?id=CVE-2025-39761 Référence CVE CVE-2025-39762 https://www.cve.org/CVERecord?id=CVE-2025-39762 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=

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

d?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-39720 https://www.cve.org/CVERecord?id=CVE-2025-39720 Référence CVE CVE-2025-39726 https://www.cve.org/CVERecord?id=CVE-2025-39726 Référence CVE CVE-2025-39732 https://www.cve.org/CVERecord?id=CVE-2025-39732 Référence CVE CVE-2025-39744 https://www.cve.org/CVERecord?id=CVE-2025-39744 Référence CVE CVE-2025-39745 https://www.cve.org/CVERecord?id=CVE-2025-39745 Référence CVE CVE-2025-39746 https://www.cve.org/CVERecord?id=CVE-2025-39746 Référence CVE CVE-2025-39747 https://www.cve.org/CVERecord?id=CVE-2025-39747 Référence CVE CVE-2025-39748 https://www.cve.org/CVERecord?id=CVE-2025-39748 Référence CVE CVE-2025-39750 https://www.cve.org/CVERecord?id=CVE-2025-39750 Référence CVE CVE-2025-39753 https://www.cve.org/CVERecord?id=CVE-2025-39753 Référence CVE CVE-2025-39754 https://www.cve.org/CVERecord?id=CVE-2025-39754 Référence CVE CVE-2025-39759 https://www.cve.org/CVERecord?id=CVE-2025-39759 Référence CVE CVE-2025-39761 https://www.cve.org/CVERecord?id=CVE-2025-39761 Référence CVE CVE-2025-39762 https://www.cve.org/CVERecord?id=CVE-2025-39762 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=

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

d?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-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=CVE-2025-39744 Référence CVE CVE-2025-39746 https://www.cve.org/CVERecord?id=CVE-2025-39746 Référence CVE CVE-2025-39747 https://www.cve.org/CVERecord?id=CVE-2025-39747 Référence CVE CVE-2025-39748 https://www.cve.org/CVERecord?id=CVE-2025-39748 Référence CVE CVE-2025-39749 https://www.cve.org/CVERecord?id=CVE-2025-39749 Référence CVE CVE-2025-39750 https://www.cve.org/CVERecord?id=CVE-2025-39750 Référence CVE CVE-2025-39752 https://www.cve.org/CVERecord?id=CVE-2025-39752 Référence CVE CVE-2025-39753 https://www.cve.org/CVERecord?id=CVE-2025-39753 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-39758 https://www.cve.org/CVERecord?id=CVE-2025-39758 Référence CVE CVE-2025-39759 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-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-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=CVE-2025-39744 Référence CVE CVE-2025-39746 https://www.cve.org/CVERecord?id=CVE-2025-39746 Référence CVE CVE-2025-39747 https://www.cve.org/CVERecord?id=CVE-2025-39747 Référence CVE CVE-2025-39748 https://www.cve.org/CVERecord?id=CVE-2025-39748 Référence CVE CVE-2025-39749 https://www.cve.org/CVERecord?id=CVE-2025-39749 Référence CVE CVE-2025-39750 https://www.cve.org/CVERecord?id=CVE-2025-39750 Référence CVE CVE-2025-39752 https://www.cve.org/CVERecord?id=CVE-2025-39752 Référence CVE CVE-2025-39753 https://www.cve.org/CVERecord?id=CVE-2025-39753 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-39758 https://www.cve.org/CVERecord?id=CVE-2025-39758 Référence CVE CVE-2025-39759 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-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-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=CVE-2025-39744 Référence CVE CVE-2025-39746 https://www.cve.org/CVERecord?id=CVE-2025-39746 Référence CVE CVE-2025-39747 https://www.cve.org/CVERecord?id=CVE-2025-39747 Référence CVE CVE-2025-39748 https://www.cve.org/CVERecord?id=CVE-2025-39748 Référence CVE CVE-2025-39749 https://www.cve.org/CVERecord?id=CVE-2025-39749 Référence CVE CVE-2025-39750 https://www.cve.org/CVERecord?id=CVE-2025-39750 Référence CVE CVE-2025-39752 https://www.cve.org/CVERecord?id=CVE-2025-39752 Référence CVE CVE-2025-39753 https://www.cve.org/CVERecord?id=CVE-2025-39753 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-39758 https://www.cve.org/CVERecord?id=CVE-2025-39758 Référence CVE CVE-2025-39759 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-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-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=CVE-2025-39744 Référence CVE CVE-2025-39746 https://www.cve.org/CVERecord?id=CVE-2025-39746 Référence CVE CVE-2025-39747 https://www.cve.org/CVERecord?id=CVE-2025-39747 Référence CVE CVE-2025-39748 https://www.cve.org/CVERecord?id=CVE-2025-39748 Référence CVE CVE-2025-39749 https://www.cve.org/CVERecord?id=CVE-2025-39749 Référence CVE CVE-2025-39750 https://www.cve.org/CVERecord?id=CVE-2025-39750 Référence CVE CVE-2025-39752 https://www.cve.org/CVERecord?id=CVE-2025-39752 Référence CVE CVE-2025-39753 https://www.cve.org/CVERecord?id=CVE-2025-39753 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-39758 https://www.cve.org/CVERecord?id=CVE-2025-39758 Référence CVE CVE-2025-39759 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-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-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=CVE-2025-39744 Référence CVE CVE-2025-39746 https://www.cve.org/CVERecord?id=CVE-2025-39746 Référence CVE CVE-2025-39747 https://www.cve.org/CVERecord?id=CVE-2025-39747 Référence CVE CVE-2025-39748 https://www.cve.org/CVERecord?id=CVE-2025-39748 Référence CVE CVE-2025-39749 https://www.cve.org/CVERecord?id=CVE-2025-39749 Référence CVE CVE-2025-39750 https://www.cve.org/CVERecord?id=CVE-2025-39750 Référence CVE CVE-2025-39752 https://www.cve.org/CVERecord?id=CVE-2025-39752 Référence CVE CVE-2025-39753 https://www.cve.org/CVERecord?id=CVE-2025-39753 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-39758 https://www.cve.org/CVERecord?id=CVE-2025-39758 Référence CVE CVE-2025-39759 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-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=CVE-2025-39744 Référence CVE CVE-2025-39746 https://www.cve.org/CVERecord?id=CVE-2025-39746 Référence CVE CVE-2025-39747 https://www.cve.org/CVERecord?id=CVE-2025-39747 Référence CVE CVE-2025-39748 https://www.cve.org/CVERecord?id=CVE-2025-39748 Référence CVE CVE-2025-39749 https://www.cve.org/CVERecord?id=CVE-2025-39749 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=CVE-2025-39751 Référence CVE CVE-2025-39754 https://www.cve.org/CVERecord?id=CVE-2025-39754 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-39758 https://www.cve.org/CVERecord?id=CVE-2025-39758 Référence CVE CVE-2025-39759 https://www.cve.org/CVERecord?id=

Official advisory
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Patch available
Affected
SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (6ES7518-4AX00-1AB0) >= V3.1.6; SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (6ES7518-4AX00-1AC0) >= V3.1.6; SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (6ES7518-4FX00-1AB0) >= V3.1.6; SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (6ES7518-4FX00-1AC0) >= V3.1.6; SIPLUS S7-1500 CPU 1518-4 PN/DP MFP (6AG1518-4AX00-4AC0) >= V3.1.6
Fixed
< 5.0; 5.10.253 ≤ 5.10.*; 5.15.203 ≤ 5.15.*; 6.1.167 ≤ 6.1.*; 6.6.130 ≤ 6.6.*; 6.12.43 ≤ 6.12.*; 6.15.11 ≤ 6.15.*; 6.16.2 ≤ 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 11 Sept 2025 · Last source change 8 Sept 2026, 08: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-28963
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-28963↗Vendor CSAF · Siemens ProductCERT↗Patch or update reference↗Patch or update reference↗Patch or update reference↗Patch or update reference↗CVE authority or vendor reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2025-39748 · cve.blacktree.nl