CVE-2026-31452: ext4: convert inline data to extents when truncate exceeds inline size

Published Apr 22, 2026
·
Updated

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

Affected Software

15 affected componentsFixes available
Linux Linux kernel
Microsoft azl3 kernel 6.6.130.1-3
Linux Linux kernel>=3.8<5.10.253
Linux Linux kernel>=5.11<5.15.203
Linux Linux kernel>=5.16<6.1.168
Linux Linux kernel>=6.2<6.6.131
Linux Linux kernel>=6.7<6.12.80
Linux Linux kernel>=6.13<6.18.21
Linux Linux kernel>=6.19<6.19.11
Linux Linux kernel=7.0-rc1
Linux Linux kernel=7.0-rc2
Linux Linux kernel=7.0-rc3
Linux Linux kernel=7.0-rc4
Linux Linux kernel=7.0-rc5
debian/linux
6.1.176-16.1.190-16.12.107-16.12.115-27.2.12-17.2.15-1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade debian/linux to a version that resolves this vulnerability.

    Fixed in 6.1.176-1Fixed in 6.1.190-1Fixed in 6.12.107-1Fixed in 6.12.113-1Fixed in 7.2.12-1Fixed in 7.2.13-1

Event History

Apr 22, 2026
CVE Published
via MITRE·01:53 PM
Data Sourced
via MITRE·01:53 PM
Description
Data Sourced
via NVD·02:16 PM
RemedyDescriptionSeverityWeaknessAffected Software
Apr 23, 2026
Data Sourced
via Microsoft·08:04 AM
DescriptionSeverityWeaknessAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Peer vulnerabilities

Found alongside the following vulnerabilities.

Frequently Asked Questions

1

What level of access is required to trigger the issue?

The vulnerability has local attack vector and requires low privileges. Triggering it involves operating on an ext4 filesystem containing an inode marked for inline data storage.

2

What conditions are needed for the crash to occur?

A file with the inline-data flag and a small initial size must be grown with truncate() beyond its actual inline capacity. A subsequent sendfile() write can then reach ext4_write_inline_data() with a write size larger than the inline capacity and trigger a kernel BUG_ON().

3

How would an affected system behave?

The ext4 inode can enter an inconsistent state in which its inline-data flag remains set even though its file size exceeds inline storage capacity. The observable consequence described is a kernel crash through BUG_ON() during a later write attempt.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203