CVE-2026-31447: ext4: reject mount if bigalloc with s_first_data_block != 0
Published Apr 22, 2026
·Updated
ext4: reject mount if bigalloc with sfirstdatablock != 0
Affected Software
14 affected componentsFixes available
Linux Linux kernel (ext4)
Microsoft azl3 kernel 6.6.130.1-3
Linux Linux kernel>=3.2<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
Event History
Apr 22, 2026
CVE Published
via MITRE·01:53 PM
Data Sourced
via MITRE·01:53 PM
DescriptionSeverity
Data Sourced
via NVD·02:16 PM
RemedyDescriptionSeverityAffected Software
Apr 23, 2026
Data Sourced
via Microsoft·08:08 AM
DescriptionSeverityWeakness
Data Sourced
via Microsoft·08:08 AM
Affected Software
Updated
via Microsoft·08:08 AM
DescriptionSeverity
Frequently Asked Questions
1
What is the severity of CVE-2026-31447?
The severity of CVE-2026-31447 is rated as high with a score of 7.8.
2
What does CVE-2026-31447 affect?
CVE-2026-31447 affects the ext4 filesystem in the Linux kernel.
3
How do I fix CVE-2026-31447?
To fix CVE-2026-31447, you should apply the available patch provided by the Linux kernel updates.
4
What is the risk level associated with CVE-2026-31447?
CVE-2026-31447 carries a risk level of 68, indicating it is a significant vulnerability.
5
What happens if CVE-2026-31447 is exploited?
Exploiting CVE-2026-31447 could lead to issues where bigalloc cannot correctly mount if s_first_data_block is not set to 0.