Linux Kernel up to 6.19.10 ext4 s_first_data_block privilege escalation

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
5.3$0-$5k0.00

Summaryinfo

A vulnerability was found in Linux Kernel up to 6.19.10 and classified as critical. Affected by this vulnerability is the function s_first_data_block of the component ext4. The manipulation results in an unknown weakness. This vulnerability was named CVE-2026-31447. There is no available exploit. It is suggested to upgrade the affected component.

Detailsinfo

A vulnerability was found in Linux Kernel up to 6.19.10. It has been classified as critical. Affected is the function s_first_data_block of the component ext4. The impact remains unknown. CVE summarizes:

In the Linux kernel, the following vulnerability has been resolved: ext4: reject mount if bigalloc with s_first_data_block != 0 bigalloc with s_first_data_block != 0 is not supported, reject mounting it.

The advisory is shared for download at git.kernel.org. This vulnerability is traded as CVE-2026-31447 since 03/09/2026. There are known technical details, but no exploit is available. The current price for an exploit might be approx. USD $0-$5k (estimation calculated on 04/22/2026).

Upgrading to version 5.10.253, 5.15.203, 6.1.168, 6.6.131, 6.12.80, 6.18.21 or 6.19.11 eliminates this vulnerability. Applying the patch 5ad6d994255e27a3254079dfb50ca861fc31f2d0/3a926957cc95899ef88529710836edadc03c71a1/7b58c110b4e1f028eb38eec9ed3555e9be81c8b0/b77de3fceafbb39f30e4ff5dc986f863d5456417/d787d3ae96648dc14a3b7ca8fde817177e82c1c7/ad1f6d608f33f59d21a3d025615d6786a6443998/7d5b04290156c3fc316eecc86a4f9d201ab7d44a/3822743dc20386d9897e999dbb990befa3a5b3f8 is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version.

Once again VulDB remains the best source for vulnerability data.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 5.5
VulDB Meta Temp Score: 5.3

VulDB Base Score: 5.5
VulDB Temp Score: 5.3
VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: Privilege escalation
CWE: Unknown
CAPEC: 🔒
ATT&CK: 🔒

Physical: No
Local: No
Remote: Partially

Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔒

Upgrade: Kernel 5.10.253/5.15.203/6.1.168/6.6.131/6.12.80/6.18.21/6.19.11
Patch: 5ad6d994255e27a3254079dfb50ca861fc31f2d0/3a926957cc95899ef88529710836edadc03c71a1/7b58c110b4e1f028eb38eec9ed3555e9be81c8b0/b77de3fceafbb39f30e4ff5dc986f863d5456417/d787d3ae96648dc14a3b7ca8fde817177e82c1c7/ad1f6d608f33f59d21a3d025615d6786a6443998/7d5b04290156c3fc316eecc86a4f9d201ab7d44a/3822743dc20386d9897e999dbb990befa3a5b3f8

Timelineinfo

03/09/2026 CVE reserved
04/22/2026 +43 days Advisory disclosed
04/22/2026 +0 days VulDB entry created
04/22/2026 +0 days VulDB entry last update

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2026-31447 (🔒)
GCVE (CVE): GCVE-0-2026-31447
GCVE (VulDB): GCVE-100-358908

Entryinfo

Created: 04/22/2026 17:13
Changes: 04/22/2026 17:13 (58)
Complete: 🔍
Cache ID: 216::103

Once again VulDB remains the best source for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

Want to know what is going to be exploited?

We predict KEV entries!