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

ext4: validate p_idx bounds in ext4_ext_correct_indexes

Linux · Linux

Official source article: Siemens SSA-019113 ↗. Check the applicable product and release in the original source.

7.8HighCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 25 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityHighOperational priority:High, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • EPSS is 0.20% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict local access and enforce least privilege on affected hosts.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs Linux Linux and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: Within 30 daysRemediation target: Within 180 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 25 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

24 package states
Package result overrides the generic status

BlackTree has verified remediation for at least one product or source, but the relevant distribution still reports no fixed package for 20 affected package states shown here. Treat those rows as affected with no fix until that distribution publishes a fixed version.

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.

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.12.85-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.176-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.19.11-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.19.11-1Debian Security Tracker ↗Source updated 5 Oct 2026
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 Ubuntu Security ↗Source updated 5 Oct 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 Ubuntu Security ↗Source updated 5 Oct 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 Ubuntu Security ↗Source updated 5 Oct 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 Ubuntu Security ↗Source updated 5 Oct 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 Ubuntu Security ↗Source updated 5 Oct 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 Ubuntu Security ↗Source updated 5 Oct 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 Ubuntu Security ↗Source updated 5 Oct 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 Ubuntu Security ↗Source updated 5 Oct 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 Ubuntu Security ↗Source updated 5 Oct 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 Ubuntu Security ↗Source updated 5 Oct 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 Ubuntu Security ↗Source updated 5 Oct 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 Ubuntu Security ↗Source updated 5 Oct 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 Ubuntu Security ↗Source updated 5 Oct 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 Ubuntu Security ↗Source updated 5 Oct 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 Ubuntu Security ↗Source updated 5 Oct 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 Ubuntu Security ↗Source updated 5 Oct 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 Ubuntu Security ↗Source updated 5 Oct 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 Ubuntu Security ↗Source updated 5 Oct 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 Ubuntu Security ↗Source updated 5 Oct 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 Ubuntu Security ↗Source updated 5 Oct 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.

1 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: 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.
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.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

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-24786

No EUVD known-exploited evidence

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.

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
7.8 · CVSS 3.1
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 25 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

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.

What

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.

Why

The product reads data past the end, or before the beginning, of the intended buffer.

How

An attacker operating through local access may attempt exploitation without authentication after a user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

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.

Why

The product reads data past the end, or before the beginning, of the intended buffer.

How

An attacker operating through local access may attempt exploitation without authentication after a user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

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 Read → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Local
Privileges required
None: unauthenticated exploitation is possible
User interaction
Required interaction required
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-125 ↗

CWE-125: Out-of-bounds Read. The product reads 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:N/UI:R/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.PRNonePrivileges required: The attacker does not need an account or existing privileges.UIRequiredUser interaction: Another user must perform an action for exploitation to succeed.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.
UnauthenticatedCWE-125
A

Official authority intelligence

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

ENISA EUVD · EUVD-2026-24786Official EUVD mapping

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.

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-1066Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?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-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-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=

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

d?id=CVE-2026-31436 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-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=

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

d?id=CVE-2026-31436 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-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=

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

d?id=CVE-2026-23255 Référence CVE CVE-2026-23310 https://www.cve.org/CVERecord?id=CVE-2026-23310 Référence CVE CVE-2026-23389 https://www.cve.org/CVERecord?id=CVE-2026-23389 Référence CVE CVE-2026-23399 https://www.cve.org/CVERecord?id=CVE-2026-23399 Référence CVE CVE-2026-23442 https://www.cve.org/CVERecord?id=CVE-2026-23442 Référence CVE CVE-2026-23444 https://www.cve.org/CVERecord?id=CVE-2026-23444 Référence CVE CVE-2026-23468 https://www.cve.org/CVERecord?id=CVE-2026-23468 Référence CVE CVE-2026-31407 https://www.cve.org/CVERecord?id=CVE-2026-31407 Référence CVE CVE-2026-31419 https://www.cve.org/CVERecord?id=CVE-2026-31419 Référence CVE CVE-2026-31449 https://www.cve.org/CVERecord?id=CVE-2026-31449 Référence CVE CVE-2026-31488 https://www.cve.org/CVERecord?id=CVE-2026-31488 Référence CVE CVE-2026-31489 https://www.cve.org/CVERecord?id=CVE-2026-31489 Référence CVE CVE-2026-31500 https://www.cve.org/CVERecord?id=CVE-2026-31500 Référence CVE CVE-2026-31532 https://www.cve.org/CVERecord?id=CVE-2026-31532 Référence CVE CVE-2026-31576 https://www.cve.org/CVERecord?id=CVE-2026-31576 Référence CVE CVE-2026-31577 https://www.cve.org/CVERecord?id=CVE-2026-31577 Référence CVE CVE-2026-31578 https://www.cve.org/CVERecord?id=CVE-2026-31578 Référence CVE CVE-2026-31580 https://www.cve.org/CVERecord?id=

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

d?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-31426 https://www.cve.org/CVERecord?id=CVE-2026-31426 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-31435 https://www.cve.org/CVERecord?id=CVE-2026-31435 Référence CVE CVE-2026-31436 https://www.cve.org/CVERecord?id=CVE-2026-31436 Référence CVE CVE-2026-31449 https://www.cve.org/CVERecord?id=CVE-2026-31449 Référence CVE CVE-2026-31453 https://www.cve.org/CVERecord?id=CVE-2026-31453 Référence CVE CVE-2026-31456 https://www.cve.org/CVERecord?id=CVE-2026-31456 Référence CVE CVE-2026-31470 https://www.cve.org/CVERecord?id=CVE-2026-31470 Référence CVE CVE-2026-31488 https://www.cve.org/CVERecord?id=CVE-2026-31488 Référence CVE CVE-2026-31494 https://www.cve.org/CVERecord?id=CVE-2026-31494 Référence CVE CVE-2026-31496 https://www.cve.org/CVERecord?id=CVE-2026-31496 Référence CVE CVE-2026-31503 https://www.cve.org/CVERecord?id=CVE-2026-31503 Référence CVE CVE-2026-31504 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-31434 Référence CVE CVE-2026-31436 https://www.cve.org/CVERecord?id=CVE-2026-31436 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-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=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2026-014843LinuxのLinux Kernelにおける境界外読み取りに関する脆弱性

Linuxカーネルにおいて、ext4_ext_correct_indexes関数内でp_idxの境界を検証しなかった問題によりスラブの境界外読み取りが発生する脆弱性が修正されました。オンディスクのエクステントヘッダーが破損または不正なeh_entries値を含む場合、p_idxが割り当てられたバッファの末尾を越えてアクセスできる可能性がありました。この問題は、whileループの前後でpath[k].p_idxをEXT_LAST_INDEX()に対して検証し、不正な場合は-EFSCORRUPTEDを返すことで修正されました。

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.
Fix availability varies by product
Affected
Fixed
Linux: < 2.6.19, 5.10.259 ≤ 5.10.*, 5.15.210 ≤ 5.15.*, 6.1.175 ≤ 6.1.*, 6.6.140 ≤ 6.6.*, 6.12.80 ≤ 6.12.*, 6.18.21 ≤ 6.18.*, 6.19.11 ≤ 6.19.*, 7.0 ≤ *
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
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 8 Sept 2026, 08:47 UTC · CWE-125 · Out-of-bounds Read

CVE recordCVE.org · 5.2
CVSS sourceCNA
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-24786
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
    a86c61812637c7dd0c57e29880cffd477b62f2e7 < 39d6e2b67651614bac0dc6592fa9836321910067; a86c61812637c7dd0c57e29880cffd477b62f2e7 < c5839b34704c9c2f47f079451bdbb22de0da1ed1; a86c61812637c7dd0c57e29880cffd477b62f2e7 < 10242e640b36b91ad03d25f3dc77854bbdff8358; a86c61812637c7dd0c57e29880cffd477b62f2e7 < 4d08401aa13f1531216f1a7ae281ca4806e90a5c; a86c61812637c7dd0c57e29880cffd477b62f2e7 < 407c944f217c17d4343148011acafebc604d55e1; a86c61812637c7dd0c57e29880cffd477b62f2e7 < 93f2e975ed658ce09db4d4c2877ca2c06540df83; a86c61812637c7dd0c57e29880cffd477b62f2e7 < 01bf1e0b997d82c0e353b51ed74ef99698043c33; a86c61812637c7dd0c57e29880cffd477b62f2e7 < 2acb5c12ebd860f30e4faf67e6cc8c44ddfe5fe8 · Fixed: < 2.6.19; 5.10.259 ≤ 5.10.*; 5.15.210 ≤ 5.15.*; 6.1.175 ≤ 6.1.*; 6.6.140 ≤ 6.6.*; 6.12.80 ≤ 6.12.*; 6.18.21 ≤ 6.18.*; 6.19.11 ≤ 6.19.*
    After
    Linux: a86c61812637c7dd0c57e29880cffd477b62f2e7 < 39d6e2b67651614bac0dc6592fa9836321910067, a86c61812637c7dd0c57e29880cffd477b62f2e7 < c5839b34704c9c2f47f079451bdbb22de0da1ed1, a86c61812637c7dd0c57e29880cffd477b62f2e7 < 10242e640b36b91ad03d25f3dc77854bbdff8358, a86c61812637c7dd0c57e29880cffd477b62f2e7 < 4d08401aa13f1531216f1a7ae281ca4806e90a5c, a86c61812637c7dd0c57e29880cffd477b62f2e7 < 407c944f217c17d4343148011acafebc604d55e1, a86c61812637c7dd0c57e29880cffd477b62f2e7 < 93f2e975ed658ce09db4d4c2877ca2c06540df83, a86c61812637c7dd0c57e29880cffd477b62f2e7 < 01bf1e0b997d82c0e353b51ed74ef99698043c33, a86c61812637c7dd0c57e29880cffd477b62f2e7 < 2acb5c12ebd860f30e4faf67e6cc8c44ddfe5fe8, 2.6.19 · Fixed: Linux: < 2.6.19, 5.10.259 ≤ 5.10.*, 5.15.210 ≤ 5.15.*, 6.1.175 ≤ 6.1.*, 6.6.140 ≤ 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
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-31449 · cve.blacktree.nl