BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2026
CVE-2026-31452High confidence

ext4: convert inline data to extents when truncate exceeds inline size

Linux · Linux

7.8HighCVSS 3.1
Recommended action
Within 7 days

High technical severity; prioritise exposed affected systems while verifying vendor guidance.

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 11 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 11 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 11 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 11 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 11 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 11 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 11 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 11 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 11 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 11 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 11 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 11 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 11 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 11 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 11 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 11 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 11 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 11 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 11 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 11 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: ext4: convert inline data to extents when truncate exceeds inline size Add a check in ext4_setattr() to convert files from inline data storage to extent-based storage when truncate() grows the file size beyond the inline capacity. This prevents the filesystem from entering an inconsistent state where the inline data flag is set but the file size exceeds what can be stored inline. Without this fix, the following sequence causes a kernel BUG_ON(): 1. Mount filesystem with inode that has inline flag set and small size 2. truncate(file, 50MB) - grows size but inline flag remains set 3. sendfile() attempts to write data 4. ext4_write_inline_data() hits BUG_ON(write_size > inline_capacity) The crash occurs because ext4_write_inline_data() expects inline storage to accommodate the write, but the actual inline capacity (~60 bytes for i_block + ~96 bytes for xattrs) is far smaller than the file size and write request. The fix checks if the new size from setattr exceeds the inode's actual inline capacity (EXT4_I(inode)->i_inline_size) and converts the file to extent-based storage before proceeding with the size change. This addresses the root cause by ensuring the inline data flag and file size remain consistent during truncate operations.
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: ext4: convert inline data to extents when truncate exceeds inline size Add a check in ext4_setattr() to convert files from inline data storage to extent-based storage when truncate() grows the file size beyond the inline capacity. This prevents the filesystem from entering an inconsistent state where the inline data flag is set but the file size exceeds what can be stored inline. Without this fix, the following sequence causes a kernel BUG_ON(): 1. Mount filesystem with inode that has inline flag set and small size 2. truncate(file, 50MB) - grows size but inline flag remains set 3. sendfile() attempts to write data 4. ext4_write_inline_data() hits BUG_ON(write_size > inline_capacity) The crash occurs because ext4_write_inline_data() expects inline storage to accommodate the write, but the actual inline capacity (~60 bytes for i_block + ~96 bytes for xattrs) is far smaller than the file size and write request. The fix checks if the new size from setattr exceeds the inode's actual inline capacity (EXT4_I(inode)->i_inline_size) and converts the file to extent-based storage before proceeding with the size change. This addresses the root cause by ensuring the inline data flag and file size remain consistent during truncate operations.
Remediation
Limit access to the interactive shell of the additional GNU/Linux subssytem to trusted personnel only.
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Select the national-authority views to include. The exact source language is shown on each matched advisory. Your choice is remembered on this device and encoded in the shareable URL.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2026-24791

No EUVD known-exploited evidence

In the Linux kernel, the following vulnerability has been resolved: ext4: convert inline data to extents when truncate exceeds inline size Add a check in ext4_setattr() to convert files from inline data storage to extent-based storage when truncate() grows the file size beyond the inline capacity. This prevents the filesystem from entering an inconsistent state where the inline data flag is set but the file size exceeds what can be stored inline. Without this fix, the following sequence causes a kernel BUG_ON(): 1. Mount filesystem with inode that has inline flag set and small size 2. truncate(file, 50MB) - grows size but inline flag remains set 3. sendfile() attempts to write data 4. ext4_write_inline_data() hits BUG_ON(write_size > inline_capacity) The crash occurs because ext4_write_inline_data() expects inline storage to accommodate the write, but the actual inline capacity (~60 bytes for i_block + ~96 bytes for xattrs) is far smaller than the file size and write request. The fix checks if the new size from setattr exceeds the inode's actual inline capacity (EXT4_I(inode)->i_inline_size) and converts the file to extent-based storage before proceeding with the size change. This addresses the root cause by ensuring the inline data flag and file size remain consistent during truncate operations.

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 actionWithin 7 days

High technical severity; prioritise exposed affected systems while verifying vendor guidance.

Patch available
01

What, why and how

In the Linux kernel, the following vulnerability has been resolved: ext4: convert inline data to extents when truncate exceeds inline size Add a check in ext4_setattr() to convert files from inline data storage to extent-based storage when truncate() grows the file size beyond the inline capacity. This prevents the filesystem from entering an inconsistent state where the inline data flag is set but the file size exceeds what can be stored inline. Without this fix, the following sequence causes a kernel BUG_ON(): 1. Mount filesystem with inode that has inline flag set and small size 2. truncate(file, 50MB) - grows size but inline flag remains set 3. sendfile() attempts to write data 4. ext4_write_inline_data() hits BUG_ON(write_size > inline_capacity) The crash occurs because ext4_write_inline_data() expects inline storage to accommodate the write, but the actual inline capacity (~60 bytes for i_block + ~96 bytes for xattrs) is far smaller than the file size and write request. The fix checks if the new size from setattr exceeds the inode's actual inline capacity (EXT4_I(inode)->i_inline_size) and converts the file to extent-based storage before proceeding with the size change. This addresses the root cause by ensuring the inline data flag and file size remain consistent during truncate operations.

What

In the Linux kernel, the following vulnerability has been resolved: ext4: convert inline data to extents when truncate exceeds inline size Add a check in ext4_setattr() to convert files from inline data storage to extent-based storage when truncate() grows the file size beyond the inline capacity. This prevents the filesystem from entering an inconsistent state where the inline data flag is set but the file size exceeds what can be stored inline. Without this fix, the following sequence causes a kernel BUG_ON(): 1. Mount filesystem with inode that has inline flag set and small size 2. truncate(file, 50MB) - grows size but inline flag remains set 3. sendfile() attempts to write data 4. ext4_write_inline_data() hits BUG_ON(write_size > inline_capacity) The crash occurs because ext4_write_inline_data() expects inline storage to accommodate the write, but the actual inline capacity (~60 bytes for i_block + ~96 bytes for xattrs) is far smaller than the file size and write request. The fix checks if the new size from setattr exceeds the inode's actual inline capacity (EXT4_I(inode)->i_inline_size) and converts the file to extent-based storage before proceeding with the size change. This addresses the root cause by ensuring the inline data flag and file size remain consistent during truncate operations.

Why

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

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may disrupt the affected service.

What

In the Linux kernel, the following vulnerability has been resolved: ext4: convert inline data to extents when truncate exceeds inline size Add a check in ext4_setattr() to convert files from inline data storage to extent-based storage when truncate() grows the file size beyond the inline capacity. This prevents the filesystem from entering an inconsistent state where the inline data flag is set but the file size exceeds what can be stored inline. Without this fix, the following sequence causes a kernel BUG_ON(): 1. Mount filesystem with inode that has inline flag set and small size 2. truncate(file, 50MB) - grows size but inline flag remains set 3. sendfile() attempts to write data 4. ext4_write_inline_data() hits BUG_ON(write_size > inline_capacity) The crash occurs because ext4_write_inline_data() expects inline storage to accommodate the write, but the actual inline capacity (~60 bytes for i_block + ~96 bytes for xattrs) is far smaller than the file size and write request. The fix checks if the new size from setattr exceeds the inode's actual inline capacity (EXT4_I(inode)->i_inline_size) and converts the file to extent-based storage before proceeding with the size change. This addresses the root cause by ensuring the inline data flag and file size remain consistent during truncate operations.

Why

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

How

An attacker operating through local access may attempt exploitation with low privileges. 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
local access → Out-of-bounds Write → disrupt the affected service
Attack surface
Local
Privileges required
Low: a basic authenticated account is required
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-787 ↗

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

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

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

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.CHighConfidentiality impact: A successful attack can cause a major loss.IHighIntegrity impact: A successful attack can cause a major loss.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.
Denial of serviceCWE-787
A

Official authority intelligence

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

ENISA EUVD · EUVD-2026-24791Official EUVD mapping

In the Linux kernel, the following vulnerability has been resolved: ext4: convert inline data to extents when truncate exceeds inline size Add a check in ext4_setattr() to convert files from inline data storage to extent-based storage when truncate() grows the file size beyond the inline capacity. This prevents the filesystem from entering an inconsistent state where the inline data flag is set but the file size exceeds what can be stored inline. Without this fix, the following sequence causes a kernel BUG_ON(): 1. Mount filesystem with inode that has inline flag set and small size 2. truncate(file, 50MB) - grows size but inline flag remains set 3. sendfile() attempts to write data 4. ext4_write_inline_data() hits BUG_ON(write_size > inline_capacity) The crash occurs because ext4_write_inline_data() expects inline storage to accommodate the write, but the actual inline capacity (~60 bytes for i_block + ~96 bytes for xattrs) is far smaller than the file size and write request. The fix checks if the new size from setattr exceeds the inode's actual inline capacity (EXT4_I(inode)->i_inline_size) and converts the file to extent-based storage before proceeding with the size change. This addresses the root cause by ensuring the inline data flag and file size remain consistent during truncate operations.

Official EUVD record ↗
BSI · German · WID-SEC-2026-1252Linux Kernel: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen, Sicherheitsmaßnahmen zu umgehen, Informationen offenzulegen, andere nicht näher spezifizierte Auswirkungen zu verursachen und möglicherweise Code auszuführen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20260429Security Bulletin 29 Apr 2026

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 29 Apr 2026, published on 29 April 2026. Open the linked bulletin for the product, severity and reference information published in that issue.

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

d?id=CVE-2026-31427 Référence CVE CVE-2026-31428 https://www.cve.org/CVERecord?id=CVE-2026-31428 Référence CVE CVE-2026-31431 https://www.cve.org/CVERecord?id=CVE-2026-31431 Référence CVE CVE-2026-31433 https://www.cve.org/CVERecord?id=CVE-2026-31433 Référence CVE CVE-2026-31444 https://www.cve.org/CVERecord?id=CVE-2026-31444 Référence CVE CVE-2026-31446 https://www.cve.org/CVERecord?id=CVE-2026-31446 Référence CVE CVE-2026-31447 https://www.cve.org/CVERecord?id=CVE-2026-31447 Référence CVE CVE-2026-31448 https://www.cve.org/CVERecord?id=CVE-2026-31448 Référence CVE CVE-2026-31450 https://www.cve.org/CVERecord?id=CVE-2026-31450 Référence CVE CVE-2026-31452 https://www.cve.org/CVERecord?id=CVE-2026-31452 Référence CVE CVE-2026-31454 https://www.cve.org/CVERecord?id=CVE-2026-31454 Référence CVE CVE-2026-31455 https://www.cve.org/CVERecord?id=CVE-2026-31455 Référence CVE CVE-2026-31464 https://www.cve.org/CVERecord?id=CVE-2026-31464 Référence CVE CVE-2026-31466 https://www.cve.org/CVERecord?id=CVE-2026-31466 Référence CVE CVE-2026-31467 https://www.cve.org/CVERecord?id=CVE-2026-31467 Référence CVE CVE-2026-31469 https://www.cve.org/CVERecord?id=CVE-2026-31469 Référence CVE CVE-2026-31473 https://www.cve.org/CVERecord?id=CVE-2026-31473 Référence CVE CVE-2026-31476 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-31439 Référence CVE CVE-2026-31440 https://www.cve.org/CVERecord?id=CVE-2026-31440 Référence CVE CVE-2026-31441 https://www.cve.org/CVERecord?id=CVE-2026-31441 Référence CVE CVE-2026-31446 https://www.cve.org/CVERecord?id=CVE-2026-31446 Référence CVE CVE-2026-31447 https://www.cve.org/CVERecord?id=CVE-2026-31447 Référence CVE CVE-2026-31448 https://www.cve.org/CVERecord?id=CVE-2026-31448 Référence CVE CVE-2026-31449 https://www.cve.org/CVERecord?id=CVE-2026-31449 Référence CVE CVE-2026-31450 https://www.cve.org/CVERecord?id=CVE-2026-31450 Référence CVE CVE-2026-31451 https://www.cve.org/CVERecord?id=CVE-2026-31451 Référence CVE CVE-2026-31452 https://www.cve.org/CVERecord?id=CVE-2026-31452 Référence CVE CVE-2026-31453 https://www.cve.org/CVERecord?id=CVE-2026-31453 Référence CVE CVE-2026-31454 https://www.cve.org/CVERecord?id=CVE-2026-31454 Référence CVE CVE-2026-31455 https://www.cve.org/CVERecord?id=CVE-2026-31455 Référence CVE CVE-2026-31458 https://www.cve.org/CVERecord?id=CVE-2026-31458 Référence CVE CVE-2026-31464 https://www.cve.org/CVERecord?id=CVE-2026-31464 Référence CVE CVE-2026-31466 https://www.cve.org/CVERecord?id=CVE-2026-31466 Référence CVE CVE-2026-31467 https://www.cve.org/CVERecord?id=CVE-2026-31467 Référence CVE CVE-2026-31469 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-2026-31423 Référence CVE CVE-2026-31424 https://www.cve.org/CVERecord?id=CVE-2026-31424 Référence CVE CVE-2026-31425 https://www.cve.org/CVERecord?id=CVE-2026-31425 Référence CVE CVE-2026-31427 https://www.cve.org/CVERecord?id=CVE-2026-31427 Référence CVE CVE-2026-31428 https://www.cve.org/CVERecord?id=CVE-2026-31428 Référence CVE CVE-2026-31433 https://www.cve.org/CVERecord?id=CVE-2026-31433 Référence CVE CVE-2026-31446 https://www.cve.org/CVERecord?id=CVE-2026-31446 Référence CVE CVE-2026-31447 https://www.cve.org/CVERecord?id=CVE-2026-31447 Référence CVE CVE-2026-31450 https://www.cve.org/CVERecord?id=CVE-2026-31450 Référence CVE CVE-2026-31452 https://www.cve.org/CVERecord?id=CVE-2026-31452 Référence CVE CVE-2026-31454 https://www.cve.org/CVERecord?id=CVE-2026-31454 Référence CVE CVE-2026-31455 https://www.cve.org/CVERecord?id=CVE-2026-31455 Référence CVE CVE-2026-31464 https://www.cve.org/CVERecord?id=CVE-2026-31464 Référence CVE CVE-2026-31466 https://www.cve.org/CVERecord?id=CVE-2026-31466 Référence CVE CVE-2026-31467 https://www.cve.org/CVERecord?id=CVE-2026-31467 Référence CVE CVE-2026-31469 https://www.cve.org/CVERecord?id=CVE-2026-31469 Référence CVE CVE-2026-31473 https://www.cve.org/CVERecord?id=CVE-2026-31473 Référence CVE CVE-2026-31476 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-23240 Référence CVE CVE-2026-23248 https://www.cve.org/CVERecord?id=CVE-2026-23248 Référence CVE CVE-2026-23393 https://www.cve.org/CVERecord?id=CVE-2026-23393 Référence CVE CVE-2026-23394 https://www.cve.org/CVERecord?id=CVE-2026-23394 Référence CVE CVE-2026-23451 https://www.cve.org/CVERecord?id=CVE-2026-23451 Référence CVE CVE-2026-31414 https://www.cve.org/CVERecord?id=CVE-2026-31414 Référence CVE CVE-2026-31429 https://www.cve.org/CVERecord?id=CVE-2026-31429 Référence CVE CVE-2026-31438 https://www.cve.org/CVERecord?id=CVE-2026-31438 Référence CVE CVE-2026-31450 https://www.cve.org/CVERecord?id=CVE-2026-31450 Référence CVE CVE-2026-31452 https://www.cve.org/CVERecord?id=CVE-2026-31452 Référence CVE CVE-2026-31466 https://www.cve.org/CVERecord?id=CVE-2026-31466 Référence CVE CVE-2026-31469 https://www.cve.org/CVERecord?id=CVE-2026-31469 Référence CVE CVE-2026-31479 https://www.cve.org/CVERecord?id=CVE-2026-31479 Référence CVE CVE-2026-31492 https://www.cve.org/CVERecord?id=CVE-2026-31492 Référence CVE CVE-2026-31495 https://www.cve.org/CVERecord?id=CVE-2026-31495 Référence CVE CVE-2026-31499 https://www.cve.org/CVERecord?id=CVE-2026-31499 Référence CVE CVE-2026-31502 https://www.cve.org/CVERecord?id=CVE-2026-31502 Référence CVE CVE-2026-31503 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-31440 Référence CVE CVE-2026-31441 https://www.cve.org/CVERecord?id=CVE-2026-31441 Référence CVE CVE-2026-31444 https://www.cve.org/CVERecord?id=CVE-2026-31444 Référence CVE CVE-2026-31446 https://www.cve.org/CVERecord?id=CVE-2026-31446 Référence CVE CVE-2026-31447 https://www.cve.org/CVERecord?id=CVE-2026-31447 Référence CVE CVE-2026-31448 https://www.cve.org/CVERecord?id=CVE-2026-31448 Référence CVE CVE-2026-31449 https://www.cve.org/CVERecord?id=CVE-2026-31449 Référence CVE CVE-2026-31450 https://www.cve.org/CVERecord?id=CVE-2026-31450 Référence CVE CVE-2026-31451 https://www.cve.org/CVERecord?id=CVE-2026-31451 Référence CVE CVE-2026-31452 https://www.cve.org/CVERecord?id=CVE-2026-31452 Référence CVE CVE-2026-31453 https://www.cve.org/CVERecord?id=CVE-2026-31453 Référence CVE CVE-2026-31454 https://www.cve.org/CVERecord?id=CVE-2026-31454 Référence CVE CVE-2026-31455 https://www.cve.org/CVERecord?id=CVE-2026-31455 Référence CVE CVE-2026-31458 https://www.cve.org/CVERecord?id=CVE-2026-31458 Référence CVE CVE-2026-31464 https://www.cve.org/CVERecord?id=CVE-2026-31464 Référence CVE CVE-2026-31466 https://www.cve.org/CVERecord?id=CVE-2026-31466 Référence CVE CVE-2026-31467 https://www.cve.org/CVERecord?id=CVE-2026-31467 Référence CVE CVE-2026-31469 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-31414 Référence CVE CVE-2026-31429 https://www.cve.org/CVERecord?id=CVE-2026-31429 Référence CVE CVE-2026-31430 https://www.cve.org/CVERecord?id=CVE-2026-31430 Référence CVE CVE-2026-31438 https://www.cve.org/CVERecord?id=CVE-2026-31438 Référence CVE CVE-2026-31439 https://www.cve.org/CVERecord?id=CVE-2026-31439 Référence CVE CVE-2026-31440 https://www.cve.org/CVERecord?id=CVE-2026-31440 Référence CVE CVE-2026-31441 https://www.cve.org/CVERecord?id=CVE-2026-31441 Référence CVE CVE-2026-31447 https://www.cve.org/CVERecord?id=CVE-2026-31447 Référence CVE CVE-2026-31450 https://www.cve.org/CVERecord?id=CVE-2026-31450 Référence CVE CVE-2026-31452 https://www.cve.org/CVERecord?id=CVE-2026-31452 Référence CVE CVE-2026-31466 https://www.cve.org/CVERecord?id=CVE-2026-31466 Référence CVE CVE-2026-31469 https://www.cve.org/CVERecord?id=CVE-2026-31469 Référence CVE CVE-2026-31474 https://www.cve.org/CVERecord?id=CVE-2026-31474 Référence CVE CVE-2026-31479 https://www.cve.org/CVERecord?id=CVE-2026-31479 Référence CVE CVE-2026-31485 https://www.cve.org/CVERecord?id=CVE-2026-31485 Référence CVE CVE-2026-31492 https://www.cve.org/CVERecord?id=CVE-2026-31492 Référence CVE CVE-2026-31495 https://www.cve.org/CVERecord?id=CVE-2026-31495 Référence CVE CVE-2026-31497 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-31440 Référence CVE CVE-2026-31441 https://www.cve.org/CVERecord?id=CVE-2026-31441 Référence CVE CVE-2026-31444 https://www.cve.org/CVERecord?id=CVE-2026-31444 Référence CVE CVE-2026-31446 https://www.cve.org/CVERecord?id=CVE-2026-31446 Référence CVE CVE-2026-31447 https://www.cve.org/CVERecord?id=CVE-2026-31447 Référence CVE CVE-2026-31448 https://www.cve.org/CVERecord?id=CVE-2026-31448 Référence CVE CVE-2026-31449 https://www.cve.org/CVERecord?id=CVE-2026-31449 Référence CVE CVE-2026-31450 https://www.cve.org/CVERecord?id=CVE-2026-31450 Référence CVE CVE-2026-31451 https://www.cve.org/CVERecord?id=CVE-2026-31451 Référence CVE CVE-2026-31452 https://www.cve.org/CVERecord?id=CVE-2026-31452 Référence CVE CVE-2026-31453 https://www.cve.org/CVERecord?id=CVE-2026-31453 Référence CVE CVE-2026-31454 https://www.cve.org/CVERecord?id=CVE-2026-31454 Référence CVE CVE-2026-31455 https://www.cve.org/CVERecord?id=CVE-2026-31455 Référence CVE CVE-2026-31458 https://www.cve.org/CVERecord?id=CVE-2026-31458 Référence CVE CVE-2026-31464 https://www.cve.org/CVERecord?id=CVE-2026-31464 Référence CVE CVE-2026-31466 https://www.cve.org/CVERecord?id=CVE-2026-31466 Référence CVE CVE-2026-31467 https://www.cve.org/CVERecord?id=CVE-2026-31467 Référence CVE CVE-2026-31469 https://www.cve.org/CVERecord?id=

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

26-23414, CVE-2026-23422, CVE-2026-23434, CVE-2026-23438, CVE-2026-23439, CVE-2026-23446, CVE-2026-23449, CVE-2026-23450, CVE-2026-23452, CVE-2026-23454, CVE-2026-23455, CVE-2026-23456, CVE-2026-23457, CVE-2026-23458, CVE-2026-23463, CVE-2026-23474, CVE-2026-23475, CVE-2026-27135, CVE-2026-31389, CVE-2026-31391, CVE-2026-31396, CVE-2026-31402, CVE-2026-31403, CVE-2026-31411, CVE-2026-31414, CVE-2026-31415, CVE-2026-31416, CVE-2026-31417, CVE-2026-31418, CVE-2026-31421, CVE-2026-31422, CVE-2026-31423, CVE-2026-31424, CVE-2026-31427, CVE-2026-31428, CVE-2026-31431, CVE-2026-31441, CVE-2026-31446, CVE-2026-31447, CVE-2026-31448, CVE-2026-31450, CVE-2026-31452, CVE-2026-31466, CVE-2026-31469, CVE-2026-31485, CVE-2026-31494, CVE-2026-31495, CVE-2026-31496, CVE-2026-31503, CVE-2026-31504, CVE-2026-31507, CVE-2026-31508, CVE-2026-31515, CVE-2026-31518, CVE-2026-31521, CVE-2026-31533, CVE-2026-31546, CVE-2026-31555, CVE-2026-31563, CVE-2026-31565, CVE-2026-31628, CVE-2026-31634, CVE-2026-31649, CVE-2026-31651, CVE-2026-31658, CVE-2026-31664, CVE-2026-31665, CVE-2026-31669, CVE-2026-31670, CVE-2026-31671, CVE-2026-31674, CVE-2026-31680, CVE-2026-31682, CVE-2026-31737, CVE-2026-31752, CVE-2026-31761, CVE-2026-31768, CVE-2026-40355, CVE-2026-41989, CVE-2026-43011, CVE-2026-43024, CVE-2026-43025, CVE-2026

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

d?id=CVE-2026-23444 Référence CVE CVE-2026-23451 https://www.cve.org/CVERecord?id=CVE-2026-23451 Référence CVE CVE-2026-31396 https://www.cve.org/CVERecord?id=CVE-2026-31396 Référence CVE CVE-2026-31402 https://www.cve.org/CVERecord?id=CVE-2026-31402 Référence CVE CVE-2026-31414 https://www.cve.org/CVERecord?id=CVE-2026-31414 Référence CVE CVE-2026-31429 https://www.cve.org/CVERecord?id=CVE-2026-31429 Référence CVE CVE-2026-31446 https://www.cve.org/CVERecord?id=CVE-2026-31446 Référence CVE CVE-2026-31448 https://www.cve.org/CVERecord?id=CVE-2026-31448 Référence CVE CVE-2026-31450 https://www.cve.org/CVERecord?id=CVE-2026-31450 Référence CVE CVE-2026-31452 https://www.cve.org/CVERecord?id=CVE-2026-31452 Référence CVE CVE-2026-31453 https://www.cve.org/CVERecord?id=CVE-2026-31453 Référence CVE CVE-2026-31454 https://www.cve.org/CVERecord?id=CVE-2026-31454 Référence CVE CVE-2026-31455 https://www.cve.org/CVERecord?id=CVE-2026-31455 Référence CVE CVE-2026-31462 https://www.cve.org/CVERecord?id=CVE-2026-31462 Référence CVE CVE-2026-31464 https://www.cve.org/CVERecord?id=CVE-2026-31464 Référence CVE CVE-2026-31466 https://www.cve.org/CVERecord?id=CVE-2026-31466 Référence CVE CVE-2026-31469 https://www.cve.org/CVERecord?id=CVE-2026-31469 Référence CVE CVE-2026-31473 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-23438 Référence CVE CVE-2026-23444 https://www.cve.org/CVERecord?id=CVE-2026-23444 Référence CVE CVE-2026-31396 https://www.cve.org/CVERecord?id=CVE-2026-31396 Référence CVE CVE-2026-31402 https://www.cve.org/CVERecord?id=CVE-2026-31402 Référence CVE CVE-2026-31405 https://www.cve.org/CVERecord?id=CVE-2026-31405 Référence CVE CVE-2026-31414 https://www.cve.org/CVERecord?id=CVE-2026-31414 Référence CVE CVE-2026-31429 https://www.cve.org/CVERecord?id=CVE-2026-31429 Référence CVE CVE-2026-31446 https://www.cve.org/CVERecord?id=CVE-2026-31446 Référence CVE CVE-2026-31448 https://www.cve.org/CVERecord?id=CVE-2026-31448 Référence CVE CVE-2026-31452 https://www.cve.org/CVERecord?id=CVE-2026-31452 Référence CVE CVE-2026-31453 https://www.cve.org/CVERecord?id=CVE-2026-31453 Référence CVE CVE-2026-31454 https://www.cve.org/CVERecord?id=CVE-2026-31454 Référence CVE CVE-2026-31455 https://www.cve.org/CVERecord?id=CVE-2026-31455 Référence CVE CVE-2026-31464 https://www.cve.org/CVERecord?id=CVE-2026-31464 Référence CVE CVE-2026-31469 https://www.cve.org/CVERecord?id=CVE-2026-31469 Référence CVE CVE-2026-31473 https://www.cve.org/CVERecord?id=CVE-2026-31473 Référence CVE CVE-2026-31480 https://www.cve.org/CVERecord?id=CVE-2026-31480 Référence CVE CVE-2026-31492 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-23448 Référence CVE CVE-2026-31396 https://www.cve.org/CVERecord?id=CVE-2026-31396 Référence CVE CVE-2026-31401 https://www.cve.org/CVERecord?id=CVE-2026-31401 Référence CVE CVE-2026-31405 https://www.cve.org/CVERecord?id=CVE-2026-31405 Référence CVE CVE-2026-31415 https://www.cve.org/CVERecord?id=CVE-2026-31415 Référence CVE CVE-2026-31421 https://www.cve.org/CVERecord?id=CVE-2026-31421 Référence CVE CVE-2026-31446 https://www.cve.org/CVERecord?id=CVE-2026-31446 Référence CVE CVE-2026-31447 https://www.cve.org/CVERecord?id=CVE-2026-31447 Référence CVE CVE-2026-31448 https://www.cve.org/CVERecord?id=CVE-2026-31448 Référence CVE CVE-2026-31452 https://www.cve.org/CVERecord?id=CVE-2026-31452 Référence CVE CVE-2026-31454 https://www.cve.org/CVERecord?id=CVE-2026-31454 Référence CVE CVE-2026-31455 https://www.cve.org/CVERecord?id=CVE-2026-31455 Référence CVE CVE-2026-31464 https://www.cve.org/CVERecord?id=CVE-2026-31464 Référence CVE CVE-2026-31469 https://www.cve.org/CVERecord?id=CVE-2026-31469 Référence CVE CVE-2026-31473 https://www.cve.org/CVERecord?id=CVE-2026-31473 Référence CVE CVE-2026-31480 https://www.cve.org/CVERecord?id=CVE-2026-31480 Référence CVE CVE-2026-31483 https://www.cve.org/CVERecord?id=CVE-2026-31483 Référence CVE CVE-2026-31493 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-31421 Référence CVE CVE-2026-31422 https://www.cve.org/CVERecord?id=CVE-2026-31422 Référence CVE CVE-2026-31423 https://www.cve.org/CVERecord?id=CVE-2026-31423 Référence CVE CVE-2026-31424 https://www.cve.org/CVERecord?id=CVE-2026-31424 Référence CVE CVE-2026-31425 https://www.cve.org/CVERecord?id=CVE-2026-31425 Référence CVE CVE-2026-31427 https://www.cve.org/CVERecord?id=CVE-2026-31427 Référence CVE CVE-2026-31428 https://www.cve.org/CVERecord?id=CVE-2026-31428 Référence CVE CVE-2026-31447 https://www.cve.org/CVERecord?id=CVE-2026-31447 Référence CVE CVE-2026-31450 https://www.cve.org/CVERecord?id=CVE-2026-31450 Référence CVE CVE-2026-31452 https://www.cve.org/CVERecord?id=CVE-2026-31452 Référence CVE CVE-2026-31454 https://www.cve.org/CVERecord?id=CVE-2026-31454 Référence CVE CVE-2026-31455 https://www.cve.org/CVERecord?id=CVE-2026-31455 Référence CVE CVE-2026-31466 https://www.cve.org/CVERecord?id=CVE-2026-31466 Référence CVE CVE-2026-31469 https://www.cve.org/CVERecord?id=CVE-2026-31469 Référence CVE CVE-2026-31473 https://www.cve.org/CVERecord?id=CVE-2026-31473 Référence CVE CVE-2026-31485 https://www.cve.org/CVERecord?id=CVE-2026-31485 Référence CVE CVE-2026-31494 https://www.cve.org/CVERecord?id=CVE-2026-31494 Référence CVE CVE-2026-31495 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-31428 Référence CVE CVE-2026-31431 https://www.cve.org/CVERecord?id=CVE-2026-31431 Référence CVE CVE-2026-31433 https://www.cve.org/CVERecord?id=CVE-2026-31433 Référence CVE CVE-2026-31434 https://www.cve.org/CVERecord?id=CVE-2026-31434 Référence CVE CVE-2026-31441 https://www.cve.org/CVERecord?id=CVE-2026-31441 Référence CVE CVE-2026-31446 https://www.cve.org/CVERecord?id=CVE-2026-31446 Référence CVE CVE-2026-31447 https://www.cve.org/CVERecord?id=CVE-2026-31447 Référence CVE CVE-2026-31448 https://www.cve.org/CVERecord?id=CVE-2026-31448 Référence CVE CVE-2026-31450 https://www.cve.org/CVERecord?id=CVE-2026-31450 Référence CVE CVE-2026-31452 https://www.cve.org/CVERecord?id=CVE-2026-31452 Référence CVE CVE-2026-31453 https://www.cve.org/CVERecord?id=CVE-2026-31453 Référence CVE CVE-2026-31454 https://www.cve.org/CVERecord?id=CVE-2026-31454 Référence CVE CVE-2026-31455 https://www.cve.org/CVERecord?id=CVE-2026-31455 Référence CVE CVE-2026-31464 https://www.cve.org/CVERecord?id=CVE-2026-31464 Référence CVE CVE-2026-31466 https://www.cve.org/CVERecord?id=CVE-2026-31466 Référence CVE CVE-2026-31467 https://www.cve.org/CVERecord?id=CVE-2026-31467 Référence CVE CVE-2026-31469 https://www.cve.org/CVERecord?id=CVE-2026-31469 Référence CVE CVE-2026-31473 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-2026-31439 Référence CVE CVE-2026-31440 https://www.cve.org/CVERecord?id=CVE-2026-31440 Référence CVE CVE-2026-31441 https://www.cve.org/CVERecord?id=CVE-2026-31441 Référence CVE CVE-2026-31446 https://www.cve.org/CVERecord?id=CVE-2026-31446 Référence CVE CVE-2026-31447 https://www.cve.org/CVERecord?id=CVE-2026-31447 Référence CVE CVE-2026-31448 https://www.cve.org/CVERecord?id=CVE-2026-31448 Référence CVE CVE-2026-31449 https://www.cve.org/CVERecord?id=CVE-2026-31449 Référence CVE CVE-2026-31450 https://www.cve.org/CVERecord?id=CVE-2026-31450 Référence CVE CVE-2026-31451 https://www.cve.org/CVERecord?id=CVE-2026-31451 Référence CVE CVE-2026-31452 https://www.cve.org/CVERecord?id=CVE-2026-31452 Référence CVE CVE-2026-31453 https://www.cve.org/CVERecord?id=CVE-2026-31453 Référence CVE CVE-2026-31454 https://www.cve.org/CVERecord?id=CVE-2026-31454 Référence CVE CVE-2026-31455 https://www.cve.org/CVERecord?id=CVE-2026-31455 Référence CVE CVE-2026-31458 https://www.cve.org/CVERecord?id=CVE-2026-31458 Référence CVE CVE-2026-31462 https://www.cve.org/CVERecord?id=CVE-2026-31462 Référence CVE CVE-2026-31464 https://www.cve.org/CVERecord?id=CVE-2026-31464 Référence CVE CVE-2026-31466 https://www.cve.org/CVERecord?id=CVE-2026-31466 Référence CVE CVE-2026-31467 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0519Multiples vulnérabilités dans Microsoft Azure Linux

Date de la dernière version 30 avril 2026 Source(s) Bulletin de sécurité Microsoft CVE-2026-27820 du 18 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31439 du 23 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31441 du 23 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31444 du 23 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31446 du 23 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31447 du 23 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31448 du 23 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31450 du 23 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31451 du 23 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31452 du 23 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31453 du 23 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31454 du 23 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31455 du 23 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31458 du 23 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31467 du 23 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31469 du 23 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31473 du 23 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31474 du 23 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31476 du 23 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31483 du 23 avril 2026 Bu

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2026-014402LinuxのLinux Kernelにおける境界外書き込みに関する脆弱性

Linuxカーネルにおいて、以下の脆弱性が修正されました。ext4ファイルシステムで、truncate操作によりファイルサイズがインラインデータの容量を超えた場合に、インラインデータからextentベースのストレージへ変換する処理をext4_setattr()に追加しました。これにより、インラインデータフラグが設定されたままファイルサイズがインラインで格納可能な容量を超える不整合な状態になることを防ぎます。修正前は、以下の手順でカーネルがBUG_ON()を発生させてクラッシュしていました。1. インラインフラグがセットされていて小さいサイズのinodeを持つファイルシステムをマウントする。2. truncate(file, 50MB)でサイズを拡張するがインラインフラグは解除されなかった。3. sendfile()がデータ書き込みを試みる。4. ext4_write_inline_data()はwrite_sizeがinline_capacityを超えたためBUG_ON()を引き起こしていました。クラッシュは、ext4_write_inline_data()がインラインストレージ内への書き込みを前提としている一方で、実際のインライン容量（i_blockで約60バイト、xattrsで約96バイト）よりもファイルサイズと書き込み要求が大幅に大きいために発生していました。修正では、setattrによる新しいファイルサイズがinodeの実際のインライン容量（EXT4_I(inode)-i_inline_size）を超えた場合に、サイズ変更前にファイルをextentベースのストレージに変換し不整合を防止します。これにより、truncate操作中にインラインデータフラグとファイルサイズの整合性が維持され、根本的な問題が解決されました。

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
Fixed
Linux: < 3.8, 5.10.253 ≤ 5.10.*, 5.15.203 ≤ 5.15.*, 6.1.168 ≤ 6.1.*, 6.6.131 ≤ 6.6.*, 6.12.80 ≤ 6.12.*, 6.18.21 ≤ 6.18.*, 6.19.11 ≤ 6.19.*, 7.0 ≤ *
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 22 Apr 2026 · Last source change 14 Jul 2026, 12:47 UTC · CWE-787 · Out-of-bounds Write

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

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

Material change intelligence

What changed after publication

View recent updates ↗
  1. Affected versionsThe structured affected or fixed version information changed.
    Before
    67cf5b09a46f72e048501b84996f2f77bc42e947 < 110d7ef602659ce4d7947c5480f7ca2779696aaf; 67cf5b09a46f72e048501b84996f2f77bc42e947 < f53a5d9f32924bc2a810d2df243b7714da58b636; 67cf5b09a46f72e048501b84996f2f77bc42e947 < c047332be7195833a5c5126816c2502df8269fe4; 67cf5b09a46f72e048501b84996f2f77bc42e947 < 699bac4d4c951974d55b045c983d1de777215949; 67cf5b09a46f72e048501b84996f2f77bc42e947 < 7920dcc571cef3d8aa9ee109c136125d61d41669; 67cf5b09a46f72e048501b84996f2f77bc42e947 < 93cb2d103e5c707de0f7ad58a39b7f0fddc27aa6; 67cf5b09a46f72e048501b84996f2f77bc42e947 < 07c1a31af18290054da3d18221b8bf58983c5d3a; 67cf5b09a46f72e048501b84996f2f77bc42e947 < ed9356a30e59c7cc3198e7fc46cfedf3767b9b17 · Fixed: < 3.8; 5.10.253 ≤ 5.10.*; 5.15.203 ≤ 5.15.*; 6.1.168 ≤ 6.1.*; 6.6.131 ≤ 6.6.*; 6.12.80 ≤ 6.12.*; 6.18.21 ≤ 6.18.*; 6.19.11 ≤ 6.19.*
    After
    Linux: 67cf5b09a46f72e048501b84996f2f77bc42e947 < 110d7ef602659ce4d7947c5480f7ca2779696aaf, 67cf5b09a46f72e048501b84996f2f77bc42e947 < f53a5d9f32924bc2a810d2df243b7714da58b636, 67cf5b09a46f72e048501b84996f2f77bc42e947 < c047332be7195833a5c5126816c2502df8269fe4, 67cf5b09a46f72e048501b84996f2f77bc42e947 < 699bac4d4c951974d55b045c983d1de777215949, 67cf5b09a46f72e048501b84996f2f77bc42e947 < 7920dcc571cef3d8aa9ee109c136125d61d41669, 67cf5b09a46f72e048501b84996f2f77bc42e947 < 93cb2d103e5c707de0f7ad58a39b7f0fddc27aa6, 67cf5b09a46f72e048501b84996f2f77bc42e947 < 07c1a31af18290054da3d18221b8bf58983c5d3a, 67cf5b09a46f72e048501b84996f2f77bc42e947 < ed9356a30e59c7cc3198e7fc46cfedf3767b9b17, 3.8 · Fixed: Linux: < 3.8, 5.10.253 ≤ 5.10.*, 5.15.203 ≤ 5.15.*, 6.1.168 ≤ 6.1.*, 6.6.131 ≤ 6.6.*, 6.12.80 ≤ 6.12.*, 6.18.21 ≤ 6.18.*, 6.19.11 ≤ 6.19.*, 7.0 ≤ *
    CNA ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
ENISA EUVD · EUVD-2026-24791↗Vendor CSAF · Siemens ProductCERT↗CVE authority or vendor reference↗Patch or update reference↗Patch or update reference↗Patch or update reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2026-31452 · cve.blacktree.nl