Linux Kernel up to 6.12.79/6.18.20/6.19.10 ext4 ext4_ext_correct_indexes out-of-bounds

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.6$0-$5k0.00

Summaryinfo

A vulnerability was found in Linux Kernel up to 6.12.79/6.18.20/6.19.10. It has been classified as critical. Affected by this issue is the function ext4_ext_correct_indexes of the component ext4. This manipulation causes out-of-bounds. The identification of this vulnerability is CVE-2026-31449. There is no exploit available. Upgrading the affected component is recommended.

Detailsinfo

A vulnerability was found in Linux Kernel up to 6.12.79/6.18.20/6.19.10. It has been declared as problematic. Affected by this vulnerability is the function ext4_ext_correct_indexes of the component ext4. The manipulation with an unknown input leads to a out-of-bounds vulnerability. The CWE definition for the vulnerability is CWE-125. The product reads data past the end, or before the beginning, of the intended buffer. As an impact it is known to affect confidentiality. The summary by CVE is:

In the Linux kernel, the following vulnerability has been resolved: ext4: validate p_idx bounds in ext4_ext_correct_indexes ext4_ext_correct_indexes() walks up the extent tree correcting index entries when the first extent in a leaf is modified. Before accessing path[k].p_idx->ei_block, there is no validation that p_idx falls within the valid range of index entries for that level. If the on-disk extent header contains a corrupted or crafted eh_entries value, p_idx can point past the end of the allocated buffer, causing a slab-out-of-bounds read. Fix this by validating path[k].p_idx against EXT_LAST_INDEX() at both access sites: before the while loop and inside it. Return -EFSCORRUPTED if the index pointer is out of range, consistent with how other bounds violations are handled in the ext4 extent tree code.

The advisory is shared at git.kernel.org. This vulnerability is known as CVE-2026-31449 since 03/09/2026. Technical details are known, but no exploit is available.

The vulnerability scanner Nessus provides a plugin with the ID 316948 (Amazon Linux 2023 : bpftool6.18, kernel6.18, kernel6.18-devel (ALAS2023-2026-1746)), which helps to determine the existence of the flaw in a target environment.

Upgrading to version 6.12.80, 6.18.21 or 6.19.11 eliminates this vulnerability. Applying the patch 407c944f217c17d4343148011acafebc604d55e1/93f2e975ed658ce09db4d4c2877ca2c06540df83/01bf1e0b997d82c0e353b51ed74ef99698043c33/2acb5c12ebd860f30e4faf67e6cc8c44ddfe5fe8 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.

The vulnerability is also documented in the databases at Tenable (316948) and CERT Bund (WID-SEC-2026-1252). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Affected

  • Google Container-Optimized OS
  • Debian Linux
  • Red Hat Enterprise Linux
  • Ubuntu Linux
  • SUSE Linux
  • Oracle Linux
  • SUSE openSUSE
  • RESF Rocky Linux
  • Open Source Linux Kernel

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 5.6
VulDB Meta Temp Score: 5.6

VulDB Base Score: 3.5
VulDB Temp Score: 3.4
VulDB Vector: 🔒
VulDB Reliability: 🔍

CNA Base Score: 7.8
CNA Vector (Linux): 🔒

CVSSv2info

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

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

Exploitinginfo

Class: Out-of-bounds
CWE: CWE-125 / CWE-119
CAPEC: 🔒
ATT&CK: 🔒

Physical: Partially
Local: Yes
Remote: Partially

Availability: 🔒
Status: Not defined

EPSS Score: 🔒
EPSS Percentile: 🔒

Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 316948
Nessus Name: Amazon Linux 2023 : bpftool6.18, kernel6.18, kernel6.18-devel (ALAS2023-2026-1746)

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔒

Upgrade: Kernel 6.12.80/6.18.21/6.19.11
Patch: 407c944f217c17d4343148011acafebc604d55e1/93f2e975ed658ce09db4d4c2877ca2c06540df83/01bf1e0b997d82c0e353b51ed74ef99698043c33/2acb5c12ebd860f30e4faf67e6cc8c44ddfe5fe8

Timelineinfo

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

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2026-31449 (🔒)
GCVE (CVE): GCVE-0-2026-31449
GCVE (VulDB): GCVE-100-358909
CERT Bund: WID-SEC-2026-1252 - Linux Kernel: Mehrere Schwachstellen

Entryinfo

Created: 04/22/2026 17:16
Updated: 06/04/2026 22:01
Changes: 04/22/2026 17:16 (59), 04/24/2026 02:52 (7), 05/17/2026 23:25 (11), 05/27/2026 19:54 (2), 06/04/2026 22:01 (1)
Complete: 🔍
Cache ID: 216::103

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you want to use VulDB in your project?

Use the official API to access entries easily!