LiveActive security incident?Get immediate response
CVE Record

CVE-2026-46094: ext4: fix bounds check in check_xattrs() to prevent out-of-bounds access

In the Linux kernel, the following vulnerability has been resolved: ext4: fix bounds check in check_xattrs() to prevent out-of-bounds access The bounds check for the next xattr entry in check_xattrs() uses (void *)next >= end, which allows next to point within sizeof(u32) bytes of end. On the next loop iteration, IS_LAST_ENTRY() reads 4 bytes via *(__u32 *)(entry), which can overrun the valid xattr region. For example, if next lands at end - 1, the check passes since next < end, but IS_LAST_ENTRY() reads 4 bytes starting at end - 1, accessing 3 bytes beyond the valid region. Fix this by changing the check to (void *)next + sizeof(u32) > end, ensuring there is always enough space for the IS_LAST_ENTRY() read on the subsequent iteration.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This Linux kernel ext4 issue is a boundary-checking flaw in extended attribute parsing. Under certain xattr layouts, the kernel can read beyond the valid xattr region. The public record does not provide CVSS, confirmed impact, or exploitation evidence, so urgency depends on where affected kernels are deployed.

Executive priority

Set this as a monitored kernel maintenance item until vendor severity is available. Patch through normal kernel update channels, with higher priority for systems that process ext4 filesystems or cannot tolerate kernel memory-safety faults.

Technical view

In ext4 check_xattrs(), the prior bounds check allowed the next xattr entry pointer to be within four bytes of the end. A later IS_LAST_ENTRY() read could access bytes beyond the valid xattr area. The fix changes the check to require enough remaining space for the four-byte read.

Likely exposure

Exposure is limited to systems running affected Linux kernel versions or commits identified in the CVE record, particularly where ext4 extended attributes are parsed. The bundle lists Linux as affected, but does not map this cleanly to distribution package versions.

Exploitation context

No active exploitation is supported by the provided sources. The CVE is not marked KEV, and the public bundle does not describe exploit prerequisites, attacker position, or a working exploit. Treat exploitability as unconfirmed from this evidence.

Researcher notes

The source bundle supports an out-of-bounds read in ext4 xattr validation, but not impact beyond that. No CWE, CVSS, exploit status, or distribution-specific fixed versions are supplied. Analysis should stay tied to vendor kernel advisories and the referenced stable commits.

Mitigation direction

  • Check your Linux distribution advisories for CVE-2026-46094 coverage.
  • Apply kernel updates that include the referenced ext4 bounds-check fix.
  • Prioritize systems using affected Linux kernel branches listed in the CVE record.
  • Track vendor backports because distro package versions may differ from upstream kernel versions.

Validation and detection

  • Inventory Linux kernel versions across servers, endpoints, containers hosts, and appliances.
  • Compare kernel builds against vendor advisories for CVE-2026-46094.
  • Confirm whether fixes reference the linked upstream stable commits.
  • Document ext4 usage where kernel updates cannot be applied immediately.
Prepared
Confidence
medium
Sources
7

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2026-46094 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
0ADP providers
6Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux3478c83cf26bbffd026ae6a56bcb1fe544f0834e, 3478c83cf26bbffd026ae6a56bcb1fe544f0834e, 3478c83cf26bbffd026ae6a56bcb1fe544f0834e, 3478c83cf26bbffd026ae6a56bcb1fe544f0834e, 3478c83cf26bbffd026ae6a56bcb1fe544f0834eunaffected
LinuxLinux6.3, 0, 6.6.140, 6.12.86, 6.18.27, 7.0.4, 7.1affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.