Skip to page content

AEGLIX MIND

Connected intelligence.Security research, connected

AEGLIX vulnerability intelligence

CVE-2026-43067

CRITICAL · CVSS 9.8 · Modified

Published: 2026-05-05 · Updated: 2026-11-11 · Source: NVD

Stored catalog record

Source record retrieved 2026-11-12T01:13:55.390727+00:00. Scheduled imports handle updates; this page does not assert that the provider was queried just now.

Continue your research

Connect this record to stored reporting, reviewed campaign mentions and source-domain investigation. These are research leads, not inferred attack relationships.

Open CVE research in Investigate · Find Arsenal listings referencing this CVE

Vulnerability overview

In the Linux kernel, the following vulnerability has been resolved: ext4: handle wraparound when searching for blocks for indirect mapped blocks Commit 4865c768b563 ("ext4: always allocate blocks only from groups inode can use") restricts what blocks will be allocated for indirect block based files to block numbers that fit within 32-bit block numbers. However, when using a review bot running on the latest Gemini LLM to check this commit when backporting into an LTS based kernel, it raised this concern: If ac->ac_g_ex.fe_group is >= ngroups (for instance, if the goal group was populated via stream allocation from s_mb_last_groups), then start will be >= ngroups. Does this allow allocating blocks beyond the 32-bit limit for indirect block mapped files? The commit message mentions that ext4_mb_scan_groups_linear() takes care to not select unsupported groups. However, its loop uses group = *start, and the very first iteration will call ext4_mb_scan_group() with this unsupported group because next_linear_group() is only called at the end of the iteration. After reviewing the code paths involved and considering the LLM review, I determined that this can happen when there is a file system where some files/directories are extent-mapped and others are indirect-block mapped. To address this, add a safety clamp in ext4_mb_scan_groups().

Patch review priority

Critical technical severity

  • CVSS is at least 9.0; exploitation is not established by severity alone.

FIRST EPSS: 0.50% · percentile 43.8 · score date 2026-11-18.

EPSS estimates probability of exploitation in the next 30 days. It does not measure your exposure or prove exploitation. The elevated threshold is 10%; CISA KEV takes precedence. About FIRST EPSS ↗

Severity and scoring

CVSS score
9.8 · CRITICAL
CVSS version
3.1
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Weaknesses
CWE-822, NVD-CWE-noinfo

CVSS measures technical severity; it does not establish whether this vulnerability is being exploited in your environment.

Known exploitation and remediation

Not listed in the CISA catalog retrieved for this record. This does not establish that exploitation has not occurred.

Verify affected versions and patch availability in the vendor advisory before making changes.

Affected products and versions

  • cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*

    From (inclusive): 5.15.203

    Before (exclusive): 5.16

  • cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*

    From (inclusive): 6.6.130

    Before (exclusive): 6.6.134

  • cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*

    From (inclusive): 6.12.77

    Before (exclusive): 6.12.80

  • cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*

    From (inclusive): 6.18.14

    Before (exclusive): 6.18.21

  • cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*

    From (inclusive): 6.19.4

    Before (exclusive): 6.19.11

  • cpe:2.3:o:linux:linux_kernel:6.1.167:*:*:*:*:*:*:*

These are NVD CPE applicability entries. Some products depend on configuration conditions; consult the official record to confirm applicability.

Advisories and references

Explore official sources

Read the official NVD record ↗

Explore the CISA catalog ↗

Back to CVE intelligence