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

ext4: refresh inline data size before write operations

Linux · Linux

…UnscoredAssess manually
Recommended action
Needs assessment

No CVSS base score is available from the CNA, CISA ADP or NIST. Absence of a score is not evidence of low risk; review the vendor advisory, affected exposure and exploit evidence.

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 10 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 10 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 10 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 10 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 10 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 10 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 10 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 10 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 10 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 10 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 10 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 10 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 10 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 10 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 10 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 10 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 10 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 10 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 10 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 10 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.

1 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: ext4: refresh inline data size before write operations The cached ei->i_inline_size can become stale between the initial size check and when ext4_update_inline_data()/ext4_create_inline_data() use it. Although ext4_get_max_inline_size() reads the correct value at the time of the check, concurrent xattr operations can modify i_inline_size before ext4_write_lock_xattr() is acquired. This causes ext4_update_inline_data() and ext4_create_inline_data() to work with stale capacity values, leading to a BUG_ON() crash in ext4_write_inline_data(): kernel BUG at fs/ext4/inline.c:1331! BUG_ON(pos + len > EXT4_I(inode)->i_inline_size); The race window: 1. ext4_get_max_inline_size() reads i_inline_size = 60 (correct) 2. Size check passes for 50-byte write 3. [Another thread adds xattr, i_inline_size changes to 40] 4. ext4_write_lock_xattr() acquires lock 5. ext4_update_inline_data() uses stale i_inline_size = 60 6. Attempts to write 50 bytes but only 40 bytes actually available 7. BUG_ON() triggers Fix this by recalculating i_inline_size via ext4_find_inline_data_nolock() immediately after acquiring xattr_sem. This ensures ext4_update_inline_data() and ext4_create_inline_data() work with current values that are protected from concurrent modifications. This is similar to commit a54c4613dac1 ("ext4: fix race writing to an inline_data file while its xattrs are changing") which fixed i_inline_off staleness. This patch addresses the related i_inline_size staleness issue.
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-203738

No EUVD known-exploited evidence

In the Linux kernel, the following vulnerability has been resolved: ext4: refresh inline data size before write operations The cached ei->i_inline_size can become stale between the initial size check and when ext4_update_inline_data()/ext4_create_inline_data() use it. Although ext4_get_max_inline_size() reads the correct value at the time of the check, concurrent xattr operations can modify i_inline_size before ext4_write_lock_xattr() is acquired. This causes ext4_update_inline_data() and ext4_create_inline_data() to work with stale capacity values, leading to a BUG_ON() crash in ext4_write_inline_data(): kernel BUG at fs/ext4/inline.c:1331! BUG_ON(pos + len > EXT4_I(inode)->i_inline_size); The race window: 1. ext4_get_max_inline_size() reads i_inline_size = 60 (correct) 2. Size check passes for 50-byte write 3. [Another thread adds xattr, i_inline_size changes to 40] 4. ext4_write_lock_xattr() acquires lock 5. ext4_update_inline_data() uses stale i_inline_size = 60 6. Attempts to write 50 bytes but only 40 bytes actually available 7. BUG_ON() triggers Fix this by recalculating i_inline_size via ext4_find_inline_data_nolock() immediately after acquiring xattr_sem. This ensures ext4_update_inline_data() and ext4_create_inline_data() work with current values that are protected from concurrent modifications. This is similar to commit a54c4613dac1 ("ext4: fix race writing to an inline_data file while its xattrs are changing") which fixed i_inline_off staleness. This patch addresses the related i_inline_size staleness issue.

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 actionNeeds assessment

No CVSS base score is available from the CNA, CISA ADP or NIST. Absence of a score is not evidence of low risk; review the vendor advisory, affected exposure and exploit evidence.

Patch available
01

What, why and how

In the Linux kernel, the following vulnerability has been resolved: ext4: refresh inline data size before write operations The cached ei->i_inline_size can become stale between the initial size check and when ext4_update_inline_data()/ext4_create_inline_data() use it. Although ext4_get_max_inline_size() reads the correct value at the time of the check, concurrent xattr operations can modify i_inline_size before ext4_write_lock_xattr() is acquired. This causes ext4_update_inline_data() and ext4_create_inline_data() to work with stale capacity values, leading to a BUG_ON() crash in ext4_write_inline_data(): kernel BUG at fs/ext4/inline.c:1331! BUG_ON(pos + len > EXT4_I(inode)->i_inline_size); The race window: 1. ext4_get_max_inline_size() reads i_inline_size = 60 (correct) 2. Size check passes for 50-byte write 3. [Another thread adds xattr, i_inline_size changes to 40] 4. ext4_write_lock_xattr() acquires lock 5. ext4_update_inline_data() uses stale i_inline_size = 60 6. Attempts to write 50 bytes but only 40 bytes actually available 7. BUG_ON() triggers Fix this by recalculating i_inline_size via ext4_find_inline_data_nolock() immediately after acquiring xattr_sem. This ensures ext4_update_inline_data() and ext4_create_inline_data() work with current values that are protected from concurrent modifications. This is similar to commit a54c4613dac1 ("ext4: fix race writing to an inline_data file while its xattrs are changing") which fixed i_inline_off staleness. This patch addresses the related i_inline_size staleness issue.

What

In the Linux kernel, the following vulnerability has been resolved: ext4: refresh inline data size before write operations The cached ei->i_inline_size can become stale between the initial size check and when ext4_update_inline_data()/ext4_create_inline_data() use it. Although ext4_get_max_inline_size() reads the correct value at the time of the check, concurrent xattr operations can modify i_inline_size before ext4_write_lock_xattr() is acquired. This causes ext4_update_inline_data() and ext4_create_inline_data() to work with stale capacity values, leading to a BUG_ON() crash in ext4_write_inline_data(): kernel BUG at fs/ext4/inline.c:1331! BUG_ON(pos + len > EXT4_I(inode)->i_inline_size); The race window: 1. ext4_get_max_inline_size() reads i_inline_size = 60 (correct) 2. Size check passes for 50-byte write 3. [Another thread adds xattr, i_inline_size changes to 40] 4. ext4_write_lock_xattr() acquires lock 5. ext4_update_inline_data() uses stale i_inline_size = 60 6. Attempts to write 50 bytes but only 40 bytes actually available 7. BUG_ON() triggers Fix this by recalculating i_inline_size via ext4_find_inline_data_nolock() immediately after acquiring xattr_sem. This ensures ext4_update_inline_data() and ext4_create_inline_data() work with current values that are protected from concurrent modifications. This is similar to commit a54c4613dac1 ("ext4: fix race writing to an inline_data file while its xattrs are changing") which fixed i_inline_off staleness. This patch addresses the related i_inline_size staleness issue.

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 the affected interface may attempt exploitation when the stated preconditions are met. If successful, the issue may disrupt the affected service.

What

In the Linux kernel, the following vulnerability has been resolved: ext4: refresh inline data size before write operations The cached ei->i_inline_size can become stale between the initial size check and when ext4_update_inline_data()/ext4_create_inline_data() use it. Although ext4_get_max_inline_size() reads the correct value at the time of the check, concurrent xattr operations can modify i_inline_size before ext4_write_lock_xattr() is acquired. This causes ext4_update_inline_data() and ext4_create_inline_data() to work with stale capacity values, leading to a BUG_ON() crash in ext4_write_inline_data(): kernel BUG at fs/ext4/inline.c:1331! BUG_ON(pos + len > EXT4_I(inode)->i_inline_size); The race window: 1. ext4_get_max_inline_size() reads i_inline_size = 60 (correct) 2. Size check passes for 50-byte write 3. [Another thread adds xattr, i_inline_size changes to 40] 4. ext4_write_lock_xattr() acquires lock 5. ext4_update_inline_data() uses stale i_inline_size = 60 6. Attempts to write 50 bytes but only 40 bytes actually available 7. BUG_ON() triggers Fix this by recalculating i_inline_size via ext4_find_inline_data_nolock() immediately after acquiring xattr_sem. This ensures ext4_update_inline_data() and ext4_create_inline_data() work with current values that are protected from concurrent modifications. This is similar to commit a54c4613dac1 ("ext4: fix race writing to an inline_data file while its xattrs are changing") which fixed i_inline_off staleness. This patch addresses the related i_inline_size staleness issue.

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 the affected interface may attempt exploitation when the stated preconditions are met. If successful, the issue may disrupt the affected service.

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
the affected interface → vulnerable operation → disrupt the affected service
Attack surface
Unspecified
Privileges required
Not stated in the selected CVSS metric
User interaction
Not stated in the selected CVSS metric
Attack complexity
Not stated in the selected CVSS metric
Security boundary
Not stated in the selected CVSS metric
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.
Not available from the selected scoring authority.
Post-exploitation / living off the land
No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
Denial of service
A

Official authority intelligence

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

ENISA EUVD · EUVD-2025-203738Official EUVD mapping

In the Linux kernel, the following vulnerability has been resolved: ext4: refresh inline data size before write operations The cached ei->i_inline_size can become stale between the initial size check and when ext4_update_inline_data()/ext4_create_inline_data() use it. Although ext4_get_max_inline_size() reads the correct value at the time of the check, concurrent xattr operations can modify i_inline_size before ext4_write_lock_xattr() is acquired. This causes ext4_update_inline_data() and ext4_create_inline_data() to work with stale capacity values, leading to a BUG_ON() crash in ext4_write_inline_data(): kernel BUG at fs/ext4/inline.c:1331! BUG_ON(pos + len > EXT4_I(inode)->i_inline_size); The race window: 1. ext4_get_max_inline_size() reads i_inline_size = 60 (correct) 2. Size check passes for 50-byte write 3. [Another thread adds xattr, i_inline_size changes to 40] 4. ext4_write_lock_xattr() acquires lock 5. ext4_update_inline_data() uses stale i_inline_size = 60 6. Attempts to write 50 bytes but only 40 bytes actually available 7. BUG_ON() triggers Fix this by recalculating i_inline_size via ext4_find_inline_data_nolock() immediately after acquiring xattr_sem. This ensures ext4_update_inline_data() and ext4_create_inline_data() work with current values that are protected from concurrent modifications. This is similar to commit a54c4613dac1 ("ext4: fix race writing to an inline_data file while its xattrs are changing") which fixed i_inline_off staleness. This patch addresses the related i_inline_size staleness issue.

Official EUVD record
BSI · German · WID-SEC-W-2025-2868Linux Kernel: Mehrere Schwachstellen

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

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

25-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-68773, CVE-2025-68776, CVE-2025-68782, CVE-2025-68787, CVE-2025-68788, CVE-2025-68798, CVE-2025-68803, CVE-2025-68814, CVE-2025-68816, CVE-2025-68818, CVE-2025-68820, CVE-2025-71064, CVE-2025-71075, CVE-2025-71079, CVE-2025-71085, CVE-2025-71086, CVE-2025-71088, CVE-2025-71095, CVE-2025-71097, CVE-2025-71098, CVE-2025-71104, CVE-2025-71112, CVE-2025-71113, CVE-2025-71114, CVE-2025-71120, CVE-2025-71123, CVE-2025-71131, CVE-2025-71161, CVE-2025-71162, CVE-2025

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

d?id=CVE-2025-68206 Référence CVE CVE-2025-68254 https://www.cve.org/CVERecord?id=CVE-2025-68254 Référence CVE CVE-2025-68255 https://www.cve.org/CVERecord?id=CVE-2025-68255 Référence CVE CVE-2025-68256 https://www.cve.org/CVERecord?id=CVE-2025-68256 Référence CVE CVE-2025-68257 https://www.cve.org/CVERecord?id=CVE-2025-68257 Référence CVE CVE-2025-68258 https://www.cve.org/CVERecord?id=CVE-2025-68258 Référence CVE CVE-2025-68259 https://www.cve.org/CVERecord?id=CVE-2025-68259 Référence CVE CVE-2025-68261 https://www.cve.org/CVERecord?id=CVE-2025-68261 Référence CVE CVE-2025-68263 https://www.cve.org/CVERecord?id=CVE-2025-68263 Référence CVE CVE-2025-68264 https://www.cve.org/CVERecord?id=CVE-2025-68264 Référence CVE CVE-2025-68265 https://www.cve.org/CVERecord?id=CVE-2025-68265 Référence CVE CVE-2025-68266 https://www.cve.org/CVERecord?id=CVE-2025-68266 Référence CVE CVE-2025-68291 https://www.cve.org/CVERecord?id=CVE-2025-68291 Référence CVE CVE-2025-68325 https://www.cve.org/CVERecord?id=CVE-2025-68325 Référence CVE CVE-2025-68332 https://www.cve.org/CVERecord?id=CVE-2025-68332 Référence CVE CVE-2025-68335 https://www.cve.org/CVERecord?id=CVE-2025-68335 Référence CVE CVE-2025-68336 https://www.cve.org/CVERecord?id=CVE-2025-68336 Référence CVE CVE-2025-68337 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-68249 Référence CVE CVE-2025-68254 https://www.cve.org/CVERecord?id=CVE-2025-68254 Référence CVE CVE-2025-68255 https://www.cve.org/CVERecord?id=CVE-2025-68255 Référence CVE CVE-2025-68256 https://www.cve.org/CVERecord?id=CVE-2025-68256 Référence CVE CVE-2025-68257 https://www.cve.org/CVERecord?id=CVE-2025-68257 Référence CVE CVE-2025-68258 https://www.cve.org/CVERecord?id=CVE-2025-68258 Référence CVE CVE-2025-68259 https://www.cve.org/CVERecord?id=CVE-2025-68259 Référence CVE CVE-2025-68261 https://www.cve.org/CVERecord?id=CVE-2025-68261 Référence CVE CVE-2025-68263 https://www.cve.org/CVERecord?id=CVE-2025-68263 Référence CVE CVE-2025-68264 https://www.cve.org/CVERecord?id=CVE-2025-68264 Référence CVE CVE-2025-68265 https://www.cve.org/CVERecord?id=CVE-2025-68265 Référence CVE CVE-2025-68266 https://www.cve.org/CVERecord?id=CVE-2025-68266 Référence CVE CVE-2025-68282 https://www.cve.org/CVERecord?id=CVE-2025-68282 Référence CVE CVE-2025-68283 https://www.cve.org/CVERecord?id=CVE-2025-68283 Référence CVE CVE-2025-68284 https://www.cve.org/CVERecord?id=CVE-2025-68284 Référence CVE CVE-2025-68285 https://www.cve.org/CVERecord?id=CVE-2025-68285 Référence CVE CVE-2025-68286 https://www.cve.org/CVERecord?id=CVE-2025-68286 Référence CVE CVE-2025-68287 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-68249 Référence CVE CVE-2025-68254 https://www.cve.org/CVERecord?id=CVE-2025-68254 Référence CVE CVE-2025-68255 https://www.cve.org/CVERecord?id=CVE-2025-68255 Référence CVE CVE-2025-68256 https://www.cve.org/CVERecord?id=CVE-2025-68256 Référence CVE CVE-2025-68257 https://www.cve.org/CVERecord?id=CVE-2025-68257 Référence CVE CVE-2025-68258 https://www.cve.org/CVERecord?id=CVE-2025-68258 Référence CVE CVE-2025-68259 https://www.cve.org/CVERecord?id=CVE-2025-68259 Référence CVE CVE-2025-68261 https://www.cve.org/CVERecord?id=CVE-2025-68261 Référence CVE CVE-2025-68263 https://www.cve.org/CVERecord?id=CVE-2025-68263 Référence CVE CVE-2025-68264 https://www.cve.org/CVERecord?id=CVE-2025-68264 Référence CVE CVE-2025-68265 https://www.cve.org/CVERecord?id=CVE-2025-68265 Référence CVE CVE-2025-68266 https://www.cve.org/CVERecord?id=CVE-2025-68266 Référence CVE CVE-2025-68282 https://www.cve.org/CVERecord?id=CVE-2025-68282 Référence CVE CVE-2025-68284 https://www.cve.org/CVERecord?id=CVE-2025-68284 Référence CVE CVE-2025-68285 https://www.cve.org/CVERecord?id=CVE-2025-68285 Référence CVE CVE-2025-68286 https://www.cve.org/CVERecord?id=CVE-2025-68286 Référence CVE CVE-2025-68287 https://www.cve.org/CVERecord?id=CVE-2025-68287 Référence CVE CVE-2025-68288 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-68206 Référence CVE CVE-2025-68254 https://www.cve.org/CVERecord?id=CVE-2025-68254 Référence CVE CVE-2025-68255 https://www.cve.org/CVERecord?id=CVE-2025-68255 Référence CVE CVE-2025-68256 https://www.cve.org/CVERecord?id=CVE-2025-68256 Référence CVE CVE-2025-68257 https://www.cve.org/CVERecord?id=CVE-2025-68257 Référence CVE CVE-2025-68258 https://www.cve.org/CVERecord?id=CVE-2025-68258 Référence CVE CVE-2025-68259 https://www.cve.org/CVERecord?id=CVE-2025-68259 Référence CVE CVE-2025-68261 https://www.cve.org/CVERecord?id=CVE-2025-68261 Référence CVE CVE-2025-68263 https://www.cve.org/CVERecord?id=CVE-2025-68263 Référence CVE CVE-2025-68264 https://www.cve.org/CVERecord?id=CVE-2025-68264 Référence CVE CVE-2025-68265 https://www.cve.org/CVERecord?id=CVE-2025-68265 Référence CVE CVE-2025-68266 https://www.cve.org/CVERecord?id=CVE-2025-68266 Référence CVE CVE-2025-68291 https://www.cve.org/CVERecord?id=CVE-2025-68291 Référence CVE CVE-2025-68325 https://www.cve.org/CVERecord?id=CVE-2025-68325 Référence CVE CVE-2025-68332 https://www.cve.org/CVERecord?id=CVE-2025-68332 Référence CVE CVE-2025-68335 https://www.cve.org/CVERecord?id=CVE-2025-68335 Référence CVE CVE-2025-68336 https://www.cve.org/CVERecord?id=CVE-2025-68336 Référence CVE CVE-2025-68337 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-68211 Référence CVE CVE-2025-68254 https://www.cve.org/CVERecord?id=CVE-2025-68254 Référence CVE CVE-2025-68255 https://www.cve.org/CVERecord?id=CVE-2025-68255 Référence CVE CVE-2025-68256 https://www.cve.org/CVERecord?id=CVE-2025-68256 Référence CVE CVE-2025-68257 https://www.cve.org/CVERecord?id=CVE-2025-68257 Référence CVE CVE-2025-68258 https://www.cve.org/CVERecord?id=CVE-2025-68258 Référence CVE CVE-2025-68259 https://www.cve.org/CVERecord?id=CVE-2025-68259 Référence CVE CVE-2025-68261 https://www.cve.org/CVERecord?id=CVE-2025-68261 Référence CVE CVE-2025-68263 https://www.cve.org/CVERecord?id=CVE-2025-68263 Référence CVE CVE-2025-68264 https://www.cve.org/CVERecord?id=CVE-2025-68264 Référence CVE CVE-2025-68265 https://www.cve.org/CVERecord?id=CVE-2025-68265 Référence CVE CVE-2025-68266 https://www.cve.org/CVERecord?id=CVE-2025-68266 Référence CVE CVE-2025-68291 https://www.cve.org/CVERecord?id=CVE-2025-68291 Référence CVE CVE-2025-68325 https://www.cve.org/CVERecord?id=CVE-2025-68325 Référence CVE CVE-2025-68332 https://www.cve.org/CVERecord?id=CVE-2025-68332 Référence CVE CVE-2025-68335 https://www.cve.org/CVERecord?id=CVE-2025-68335 Référence CVE CVE-2025-68336 https://www.cve.org/CVERecord?id=CVE-2025-68336 Référence CVE CVE-2025-68337 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-68249 Référence CVE CVE-2025-68254 https://www.cve.org/CVERecord?id=CVE-2025-68254 Référence CVE CVE-2025-68255 https://www.cve.org/CVERecord?id=CVE-2025-68255 Référence CVE CVE-2025-68256 https://www.cve.org/CVERecord?id=CVE-2025-68256 Référence CVE CVE-2025-68257 https://www.cve.org/CVERecord?id=CVE-2025-68257 Référence CVE CVE-2025-68258 https://www.cve.org/CVERecord?id=CVE-2025-68258 Référence CVE CVE-2025-68259 https://www.cve.org/CVERecord?id=CVE-2025-68259 Référence CVE CVE-2025-68261 https://www.cve.org/CVERecord?id=CVE-2025-68261 Référence CVE CVE-2025-68263 https://www.cve.org/CVERecord?id=CVE-2025-68263 Référence CVE CVE-2025-68264 https://www.cve.org/CVERecord?id=CVE-2025-68264 Référence CVE CVE-2025-68265 https://www.cve.org/CVERecord?id=CVE-2025-68265 Référence CVE CVE-2025-68266 https://www.cve.org/CVERecord?id=CVE-2025-68266 Référence CVE CVE-2025-68282 https://www.cve.org/CVERecord?id=CVE-2025-68282 Référence CVE CVE-2025-68284 https://www.cve.org/CVERecord?id=CVE-2025-68284 Référence CVE CVE-2025-68285 https://www.cve.org/CVERecord?id=CVE-2025-68285 Référence CVE CVE-2025-68286 https://www.cve.org/CVERecord?id=CVE-2025-68286 Référence CVE CVE-2025-68287 https://www.cve.org/CVERecord?id=CVE-2025-68287 Référence CVE CVE-2025-68288 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-68254 Référence CVE CVE-2025-68255 https://www.cve.org/CVERecord?id=CVE-2025-68255 Référence CVE CVE-2025-68256 https://www.cve.org/CVERecord?id=CVE-2025-68256 Référence CVE CVE-2025-68257 https://www.cve.org/CVERecord?id=CVE-2025-68257 Référence CVE CVE-2025-68258 https://www.cve.org/CVERecord?id=CVE-2025-68258 Référence CVE CVE-2025-68259 https://www.cve.org/CVERecord?id=CVE-2025-68259 Référence CVE CVE-2025-68261 https://www.cve.org/CVERecord?id=CVE-2025-68261 Référence CVE CVE-2025-68262 https://www.cve.org/CVERecord?id=CVE-2025-68262 Référence CVE CVE-2025-68263 https://www.cve.org/CVERecord?id=CVE-2025-68263 Référence CVE CVE-2025-68264 https://www.cve.org/CVERecord?id=CVE-2025-68264 Référence CVE CVE-2025-68265 https://www.cve.org/CVERecord?id=CVE-2025-68265 Référence CVE CVE-2025-68266 https://www.cve.org/CVERecord?id=CVE-2025-68266 Référence CVE CVE-2025-68281 https://www.cve.org/CVERecord?id=CVE-2025-68281 Référence CVE CVE-2025-68282 https://www.cve.org/CVERecord?id=CVE-2025-68282 Référence CVE CVE-2025-68283 https://www.cve.org/CVERecord?id=CVE-2025-68283 Référence CVE CVE-2025-68284 https://www.cve.org/CVERecord?id=CVE-2025-68284 Référence CVE CVE-2025-68285 https://www.cve.org/CVERecord?id=CVE-2025-68285 Référence CVE CVE-2025-68286 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-68254 Référence CVE CVE-2025-68255 https://www.cve.org/CVERecord?id=CVE-2025-68255 Référence CVE CVE-2025-68256 https://www.cve.org/CVERecord?id=CVE-2025-68256 Référence CVE CVE-2025-68257 https://www.cve.org/CVERecord?id=CVE-2025-68257 Référence CVE CVE-2025-68258 https://www.cve.org/CVERecord?id=CVE-2025-68258 Référence CVE CVE-2025-68259 https://www.cve.org/CVERecord?id=CVE-2025-68259 Référence CVE CVE-2025-68261 https://www.cve.org/CVERecord?id=CVE-2025-68261 Référence CVE CVE-2025-68262 https://www.cve.org/CVERecord?id=CVE-2025-68262 Référence CVE CVE-2025-68263 https://www.cve.org/CVERecord?id=CVE-2025-68263 Référence CVE CVE-2025-68264 https://www.cve.org/CVERecord?id=CVE-2025-68264 Référence CVE CVE-2025-68265 https://www.cve.org/CVERecord?id=CVE-2025-68265 Référence CVE CVE-2025-68266 https://www.cve.org/CVERecord?id=CVE-2025-68266 Référence CVE CVE-2025-68281 https://www.cve.org/CVERecord?id=CVE-2025-68281 Référence CVE CVE-2025-68282 https://www.cve.org/CVERecord?id=CVE-2025-68282 Référence CVE CVE-2025-68283 https://www.cve.org/CVERecord?id=CVE-2025-68283 Référence CVE CVE-2025-68284 https://www.cve.org/CVERecord?id=CVE-2025-68284 Référence CVE CVE-2025-68285 https://www.cve.org/CVERecord?id=CVE-2025-68285 Référence CVE CVE-2025-68286 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-68254 Référence CVE CVE-2025-68255 https://www.cve.org/CVERecord?id=CVE-2025-68255 Référence CVE CVE-2025-68256 https://www.cve.org/CVERecord?id=CVE-2025-68256 Référence CVE CVE-2025-68257 https://www.cve.org/CVERecord?id=CVE-2025-68257 Référence CVE CVE-2025-68258 https://www.cve.org/CVERecord?id=CVE-2025-68258 Référence CVE CVE-2025-68259 https://www.cve.org/CVERecord?id=CVE-2025-68259 Référence CVE CVE-2025-68261 https://www.cve.org/CVERecord?id=CVE-2025-68261 Référence CVE CVE-2025-68262 https://www.cve.org/CVERecord?id=CVE-2025-68262 Référence CVE CVE-2025-68263 https://www.cve.org/CVERecord?id=CVE-2025-68263 Référence CVE CVE-2025-68264 https://www.cve.org/CVERecord?id=CVE-2025-68264 Référence CVE CVE-2025-68265 https://www.cve.org/CVERecord?id=CVE-2025-68265 Référence CVE CVE-2025-68266 https://www.cve.org/CVERecord?id=CVE-2025-68266 Référence CVE CVE-2025-68281 https://www.cve.org/CVERecord?id=CVE-2025-68281 Référence CVE CVE-2025-68282 https://www.cve.org/CVERecord?id=CVE-2025-68282 Référence CVE CVE-2025-68283 https://www.cve.org/CVERecord?id=CVE-2025-68283 Référence CVE CVE-2025-68284 https://www.cve.org/CVERecord?id=CVE-2025-68284 Référence CVE CVE-2025-68285 https://www.cve.org/CVERecord?id=CVE-2025-68285 Référence CVE CVE-2025-68286 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-68249 Référence CVE CVE-2025-68252 https://www.cve.org/CVERecord?id=CVE-2025-68252 Référence CVE CVE-2025-68254 https://www.cve.org/CVERecord?id=CVE-2025-68254 Référence CVE CVE-2025-68255 https://www.cve.org/CVERecord?id=CVE-2025-68255 Référence CVE CVE-2025-68256 https://www.cve.org/CVERecord?id=CVE-2025-68256 Référence CVE CVE-2025-68257 https://www.cve.org/CVERecord?id=CVE-2025-68257 Référence CVE CVE-2025-68258 https://www.cve.org/CVERecord?id=CVE-2025-68258 Référence CVE CVE-2025-68259 https://www.cve.org/CVERecord?id=CVE-2025-68259 Référence CVE CVE-2025-68261 https://www.cve.org/CVERecord?id=CVE-2025-68261 Référence CVE CVE-2025-68264 https://www.cve.org/CVERecord?id=CVE-2025-68264 Référence CVE CVE-2025-68283 https://www.cve.org/CVERecord?id=CVE-2025-68283 Référence CVE CVE-2025-68284 https://www.cve.org/CVERecord?id=CVE-2025-68284 Référence CVE CVE-2025-68285 https://www.cve.org/CVERecord?id=CVE-2025-68285 Référence CVE CVE-2025-68286 https://www.cve.org/CVERecord?id=CVE-2025-68286 Référence CVE CVE-2025-68287 https://www.cve.org/CVERecord?id=CVE-2025-68287 Référence CVE CVE-2025-68289 https://www.cve.org/CVERecord?id=CVE-2025-68289 Référence CVE CVE-2025-68290 https://www.cve.org/CVERecord?id=CVE-2025-68290 Référence CVE CVE-2025-68295 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-68254 Référence CVE CVE-2025-68255 https://www.cve.org/CVERecord?id=CVE-2025-68255 Référence CVE CVE-2025-68256 https://www.cve.org/CVERecord?id=CVE-2025-68256 Référence CVE CVE-2025-68257 https://www.cve.org/CVERecord?id=CVE-2025-68257 Référence CVE CVE-2025-68258 https://www.cve.org/CVERecord?id=CVE-2025-68258 Référence CVE CVE-2025-68259 https://www.cve.org/CVERecord?id=CVE-2025-68259 Référence CVE CVE-2025-68261 https://www.cve.org/CVERecord?id=CVE-2025-68261 Référence CVE CVE-2025-68262 https://www.cve.org/CVERecord?id=CVE-2025-68262 Référence CVE CVE-2025-68263 https://www.cve.org/CVERecord?id=CVE-2025-68263 Référence CVE CVE-2025-68264 https://www.cve.org/CVERecord?id=CVE-2025-68264 Référence CVE CVE-2025-68265 https://www.cve.org/CVERecord?id=CVE-2025-68265 Référence CVE CVE-2025-68266 https://www.cve.org/CVERecord?id=CVE-2025-68266 Référence CVE CVE-2025-68281 https://www.cve.org/CVERecord?id=CVE-2025-68281 Référence CVE CVE-2025-68282 https://www.cve.org/CVERecord?id=CVE-2025-68282 Référence CVE CVE-2025-68283 https://www.cve.org/CVERecord?id=CVE-2025-68283 Référence CVE CVE-2025-68284 https://www.cve.org/CVERecord?id=CVE-2025-68284 Référence CVE CVE-2025-68285 https://www.cve.org/CVERecord?id=CVE-2025-68285 Référence CVE CVE-2025-68286 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-68245 Référence CVE CVE-2025-68246 https://www.cve.org/CVERecord?id=CVE-2025-68246 Référence CVE CVE-2025-68254 https://www.cve.org/CVERecord?id=CVE-2025-68254 Référence CVE CVE-2025-68255 https://www.cve.org/CVERecord?id=CVE-2025-68255 Référence CVE CVE-2025-68256 https://www.cve.org/CVERecord?id=CVE-2025-68256 Référence CVE CVE-2025-68257 https://www.cve.org/CVERecord?id=CVE-2025-68257 Référence CVE CVE-2025-68258 https://www.cve.org/CVERecord?id=CVE-2025-68258 Référence CVE CVE-2025-68261 https://www.cve.org/CVERecord?id=CVE-2025-68261 Référence CVE CVE-2025-68263 https://www.cve.org/CVERecord?id=CVE-2025-68263 Référence CVE CVE-2025-68264 https://www.cve.org/CVERecord?id=CVE-2025-68264 Référence CVE CVE-2025-68265 https://www.cve.org/CVERecord?id=CVE-2025-68265 Référence CVE CVE-2025-68266 https://www.cve.org/CVERecord?id=CVE-2025-68266 Référence CVE CVE-2025-68281 https://www.cve.org/CVERecord?id=CVE-2025-68281 Référence CVE CVE-2025-68282 https://www.cve.org/CVERecord?id=CVE-2025-68282 Référence CVE CVE-2025-68283 https://www.cve.org/CVERecord?id=CVE-2025-68283 Référence CVE CVE-2025-68284 https://www.cve.org/CVERecord?id=CVE-2025-68284 Référence CVE CVE-2025-68285 https://www.cve.org/CVERecord?id=CVE-2025-68285 Référence CVE CVE-2025-68286 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-68245 Référence CVE CVE-2025-68246 https://www.cve.org/CVERecord?id=CVE-2025-68246 Référence CVE CVE-2025-68254 https://www.cve.org/CVERecord?id=CVE-2025-68254 Référence CVE CVE-2025-68255 https://www.cve.org/CVERecord?id=CVE-2025-68255 Référence CVE CVE-2025-68256 https://www.cve.org/CVERecord?id=CVE-2025-68256 Référence CVE CVE-2025-68257 https://www.cve.org/CVERecord?id=CVE-2025-68257 Référence CVE CVE-2025-68258 https://www.cve.org/CVERecord?id=CVE-2025-68258 Référence CVE CVE-2025-68261 https://www.cve.org/CVERecord?id=CVE-2025-68261 Référence CVE CVE-2025-68263 https://www.cve.org/CVERecord?id=CVE-2025-68263 Référence CVE CVE-2025-68264 https://www.cve.org/CVERecord?id=CVE-2025-68264 Référence CVE CVE-2025-68265 https://www.cve.org/CVERecord?id=CVE-2025-68265 Référence CVE CVE-2025-68266 https://www.cve.org/CVERecord?id=CVE-2025-68266 Référence CVE CVE-2025-68281 https://www.cve.org/CVERecord?id=CVE-2025-68281 Référence CVE CVE-2025-68282 https://www.cve.org/CVERecord?id=CVE-2025-68282 Référence CVE CVE-2025-68283 https://www.cve.org/CVERecord?id=CVE-2025-68283 Référence CVE CVE-2025-68284 https://www.cve.org/CVERecord?id=CVE-2025-68284 Référence CVE CVE-2025-68285 https://www.cve.org/CVERecord?id=CVE-2025-68285 Référence CVE CVE-2025-68286 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-68249 Référence CVE CVE-2025-68252 https://www.cve.org/CVERecord?id=CVE-2025-68252 Référence CVE CVE-2025-68254 https://www.cve.org/CVERecord?id=CVE-2025-68254 Référence CVE CVE-2025-68255 https://www.cve.org/CVERecord?id=CVE-2025-68255 Référence CVE CVE-2025-68256 https://www.cve.org/CVERecord?id=CVE-2025-68256 Référence CVE CVE-2025-68257 https://www.cve.org/CVERecord?id=CVE-2025-68257 Référence CVE CVE-2025-68258 https://www.cve.org/CVERecord?id=CVE-2025-68258 Référence CVE CVE-2025-68259 https://www.cve.org/CVERecord?id=CVE-2025-68259 Référence CVE CVE-2025-68261 https://www.cve.org/CVERecord?id=CVE-2025-68261 Référence CVE CVE-2025-68264 https://www.cve.org/CVERecord?id=CVE-2025-68264 Référence CVE CVE-2025-68284 https://www.cve.org/CVERecord?id=CVE-2025-68284 Référence CVE CVE-2025-68285 https://www.cve.org/CVERecord?id=CVE-2025-68285 Référence CVE CVE-2025-68286 https://www.cve.org/CVERecord?id=CVE-2025-68286 Référence CVE CVE-2025-68287 https://www.cve.org/CVERecord?id=CVE-2025-68287 Référence CVE CVE-2025-68289 https://www.cve.org/CVERecord?id=CVE-2025-68289 Référence CVE CVE-2025-68290 https://www.cve.org/CVERecord?id=CVE-2025-68290 Référence CVE CVE-2025-68296 https://www.cve.org/CVERecord?id=CVE-2025-68296 Référence CVE CVE-2025-68297 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-68249 Référence CVE CVE-2025-68252 https://www.cve.org/CVERecord?id=CVE-2025-68252 Référence CVE CVE-2025-68254 https://www.cve.org/CVERecord?id=CVE-2025-68254 Référence CVE CVE-2025-68255 https://www.cve.org/CVERecord?id=CVE-2025-68255 Référence CVE CVE-2025-68256 https://www.cve.org/CVERecord?id=CVE-2025-68256 Référence CVE CVE-2025-68257 https://www.cve.org/CVERecord?id=CVE-2025-68257 Référence CVE CVE-2025-68258 https://www.cve.org/CVERecord?id=CVE-2025-68258 Référence CVE CVE-2025-68259 https://www.cve.org/CVERecord?id=CVE-2025-68259 Référence CVE CVE-2025-68261 https://www.cve.org/CVERecord?id=CVE-2025-68261 Référence CVE CVE-2025-68264 https://www.cve.org/CVERecord?id=CVE-2025-68264 Référence CVE CVE-2025-68284 https://www.cve.org/CVERecord?id=CVE-2025-68284 Référence CVE CVE-2025-68285 https://www.cve.org/CVERecord?id=CVE-2025-68285 Référence CVE CVE-2025-68286 https://www.cve.org/CVERecord?id=CVE-2025-68286 Référence CVE CVE-2025-68287 https://www.cve.org/CVERecord?id=CVE-2025-68287 Référence CVE CVE-2025-68289 https://www.cve.org/CVERecord?id=CVE-2025-68289 Référence CVE CVE-2025-68290 https://www.cve.org/CVERecord?id=CVE-2025-68290 Référence CVE CVE-2025-68296 https://www.cve.org/CVERecord?id=CVE-2025-68296 Référence CVE CVE-2025-68297 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-68192 Référence CVE CVE-2025-68200 https://www.cve.org/CVERecord?id=CVE-2025-68200 Référence CVE CVE-2025-68215 https://www.cve.org/CVERecord?id=CVE-2025-68215 Référence CVE CVE-2025-68227 https://www.cve.org/CVERecord?id=CVE-2025-68227 Référence CVE CVE-2025-68241 https://www.cve.org/CVERecord?id=CVE-2025-68241 Référence CVE CVE-2025-68245 https://www.cve.org/CVERecord?id=CVE-2025-68245 Référence CVE CVE-2025-68254 https://www.cve.org/CVERecord?id=CVE-2025-68254 Référence CVE CVE-2025-68256 https://www.cve.org/CVERecord?id=CVE-2025-68256 Référence CVE CVE-2025-68261 https://www.cve.org/CVERecord?id=CVE-2025-68261 Référence CVE CVE-2025-68264 https://www.cve.org/CVERecord?id=CVE-2025-68264 Référence CVE CVE-2025-68284 https://www.cve.org/CVERecord?id=CVE-2025-68284 Référence CVE CVE-2025-68285 https://www.cve.org/CVERecord?id=CVE-2025-68285 Référence CVE CVE-2025-68286 https://www.cve.org/CVERecord?id=CVE-2025-68286 Référence CVE CVE-2025-68296 https://www.cve.org/CVERecord?id=CVE-2025-68296 Référence CVE CVE-2025-68297 https://www.cve.org/CVERecord?id=CVE-2025-68297 Référence CVE CVE-2025-68301 https://www.cve.org/CVERecord?id=CVE-2025-68301 Référence CVE CVE-2025-68303 https://www.cve.org/CVERecord?id=CVE-2025-68303 Référence CVE CVE-2025-68305 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-68223 Référence CVE CVE-2025-68254 https://www.cve.org/CVERecord?id=CVE-2025-68254 Référence CVE CVE-2025-68255 https://www.cve.org/CVERecord?id=CVE-2025-68255 Référence CVE CVE-2025-68256 https://www.cve.org/CVERecord?id=CVE-2025-68256 Référence CVE CVE-2025-68257 https://www.cve.org/CVERecord?id=CVE-2025-68257 Référence CVE CVE-2025-68258 https://www.cve.org/CVERecord?id=CVE-2025-68258 Référence CVE CVE-2025-68259 https://www.cve.org/CVERecord?id=CVE-2025-68259 Référence CVE CVE-2025-68261 https://www.cve.org/CVERecord?id=CVE-2025-68261 Référence CVE CVE-2025-68263 https://www.cve.org/CVERecord?id=CVE-2025-68263 Référence CVE CVE-2025-68264 https://www.cve.org/CVERecord?id=CVE-2025-68264 Référence CVE CVE-2025-68266 https://www.cve.org/CVERecord?id=CVE-2025-68266 Référence CVE CVE-2025-68282 https://www.cve.org/CVERecord?id=CVE-2025-68282 Référence CVE CVE-2025-68291 https://www.cve.org/CVERecord?id=CVE-2025-68291 Référence CVE CVE-2025-68325 https://www.cve.org/CVERecord?id=CVE-2025-68325 Référence CVE CVE-2025-68332 https://www.cve.org/CVERecord?id=CVE-2025-68332 Référence CVE CVE-2025-68335 https://www.cve.org/CVERecord?id=CVE-2025-68335 Référence CVE CVE-2025-68336 https://www.cve.org/CVERecord?id=CVE-2025-68336 Référence CVE CVE-2025-68337 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-68223 Référence CVE CVE-2025-68254 https://www.cve.org/CVERecord?id=CVE-2025-68254 Référence CVE CVE-2025-68255 https://www.cve.org/CVERecord?id=CVE-2025-68255 Référence CVE CVE-2025-68256 https://www.cve.org/CVERecord?id=CVE-2025-68256 Référence CVE CVE-2025-68257 https://www.cve.org/CVERecord?id=CVE-2025-68257 Référence CVE CVE-2025-68258 https://www.cve.org/CVERecord?id=CVE-2025-68258 Référence CVE CVE-2025-68259 https://www.cve.org/CVERecord?id=CVE-2025-68259 Référence CVE CVE-2025-68261 https://www.cve.org/CVERecord?id=CVE-2025-68261 Référence CVE CVE-2025-68263 https://www.cve.org/CVERecord?id=CVE-2025-68263 Référence CVE CVE-2025-68264 https://www.cve.org/CVERecord?id=CVE-2025-68264 Référence CVE CVE-2025-68266 https://www.cve.org/CVERecord?id=CVE-2025-68266 Référence CVE CVE-2025-68291 https://www.cve.org/CVERecord?id=CVE-2025-68291 Référence CVE CVE-2025-68325 https://www.cve.org/CVERecord?id=CVE-2025-68325 Référence CVE CVE-2025-68332 https://www.cve.org/CVERecord?id=CVE-2025-68332 Référence CVE CVE-2025-68333 https://www.cve.org/CVERecord?id=CVE-2025-68333 Référence CVE CVE-2025-68335 https://www.cve.org/CVERecord?id=CVE-2025-68335 Référence CVE CVE-2025-68336 https://www.cve.org/CVERecord?id=CVE-2025-68336 Référence CVE CVE-2025-68337 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-68244 Référence CVE CVE-2025-68249 https://www.cve.org/CVERecord?id=CVE-2025-68249 Référence CVE CVE-2025-68252 https://www.cve.org/CVERecord?id=CVE-2025-68252 Référence CVE CVE-2025-68254 https://www.cve.org/CVERecord?id=CVE-2025-68254 Référence CVE CVE-2025-68255 https://www.cve.org/CVERecord?id=CVE-2025-68255 Référence CVE CVE-2025-68256 https://www.cve.org/CVERecord?id=CVE-2025-68256 Référence CVE CVE-2025-68257 https://www.cve.org/CVERecord?id=CVE-2025-68257 Référence CVE CVE-2025-68258 https://www.cve.org/CVERecord?id=CVE-2025-68258 Référence CVE CVE-2025-68259 https://www.cve.org/CVERecord?id=CVE-2025-68259 Référence CVE CVE-2025-68264 https://www.cve.org/CVERecord?id=CVE-2025-68264 Référence CVE CVE-2025-68283 https://www.cve.org/CVERecord?id=CVE-2025-68283 Référence CVE CVE-2025-68284 https://www.cve.org/CVERecord?id=CVE-2025-68284 Référence CVE CVE-2025-68285 https://www.cve.org/CVERecord?id=CVE-2025-68285 Référence CVE CVE-2025-68286 https://www.cve.org/CVERecord?id=CVE-2025-68286 Référence CVE CVE-2025-68287 https://www.cve.org/CVERecord?id=CVE-2025-68287 Référence CVE CVE-2025-68289 https://www.cve.org/CVERecord?id=CVE-2025-68289 Référence CVE CVE-2025-68290 https://www.cve.org/CVERecord?id=CVE-2025-68290 Référence CVE CVE-2025-68293 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2025-68238 Référence CVE CVE-2025-68239 https://www.cve.org/CVERecord?id=CVE-2025-68239 Référence CVE CVE-2025-68244 https://www.cve.org/CVERecord?id=CVE-2025-68244 Référence CVE CVE-2025-68249 https://www.cve.org/CVERecord?id=CVE-2025-68249 Référence CVE CVE-2025-68252 https://www.cve.org/CVERecord?id=CVE-2025-68252 Référence CVE CVE-2025-68255 https://www.cve.org/CVERecord?id=CVE-2025-68255 Référence CVE CVE-2025-68257 https://www.cve.org/CVERecord?id=CVE-2025-68257 Référence CVE CVE-2025-68258 https://www.cve.org/CVERecord?id=CVE-2025-68258 Référence CVE CVE-2025-68259 https://www.cve.org/CVERecord?id=CVE-2025-68259 Référence CVE CVE-2025-68264 https://www.cve.org/CVERecord?id=CVE-2025-68264 Référence CVE CVE-2025-68286 https://www.cve.org/CVERecord?id=CVE-2025-68286 Référence CVE CVE-2025-68287 https://www.cve.org/CVERecord?id=CVE-2025-68287 Référence CVE CVE-2025-68289 https://www.cve.org/CVERecord?id=CVE-2025-68289 Référence CVE CVE-2025-68290 https://www.cve.org/CVERecord?id=CVE-2025-68290 Référence CVE CVE-2025-68298 https://www.cve.org/CVERecord?id=CVE-2025-68298 Référence CVE CVE-2025-68302 https://www.cve.org/CVERecord?id=CVE-2025-68302 Référence CVE CVE-2025-68303 https://www.cve.org/CVERecord?id=CVE-2025-68303 Référence CVE CVE-2025-68305 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
< 3.8; 5.10.248 ≤ 5.10.*; 5.15.198 ≤ 5.15.*; 6.1.160 ≤ 6.1.*; 6.6.120 ≤ 6.6.*; 6.12.62 ≤ 6.12.*; 6.17.12 ≤ 6.17.*; 6.18.1 ≤ 6.18.*
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 16 Dec 2025 · Last source change 8 Sept 2026, 08:43 UTC · CWE not yet assigned

CVE recordCVE.org · 5.2
CVSS sourceUnavailable
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-203738
Product sourceVendor CSAF · Siemens ProductCERT
Remediation sourceVendor CSAF · Siemens ProductCERT
CWE sourceUnavailable
NVD statusNVD not scheduled

Missing structured fields: CVSS base score, 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-203738↗Vendor CSAF · Siemens ProductCERT↗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-68264 · cve.blacktree.nl