A vulnerability in the Linux kernel's ext4 filesystem code allows an out-of-bounds read due to an improper bounds check in the check_xattrs()… (CVE-2026-46094)
A vulnerability in the Linux kernel's ext4 filesystem code allows an out-of-bounds read due to an improper bounds check in the check_xattrs() function. The issue arises because the bounds check permits a pointer to be within sizeof(u32) bytes of the end of the valid region, leading to a 4-byte read beyond the valid memory area. This can cause a high-severity impact including potential denial of service due to memory corruption. The vulnerability affects version 3.0 of the Linux kernel ext4 code as specified. A fix involves adjusting the bounds check to ensure sufficient space for the 4-byte read. No patch link is provided in the data, and no known exploits are reported in the wild.
AI Analysis
Technical Summary
The vulnerability (CVE-2026-46094) in the Linux kernel ext4 filesystem is due to an incorrect bounds check in the check_xattrs() function. The original check (void *)next >= end allows the pointer 'next' to be positioned within sizeof(u32) bytes of the end boundary, which leads to an out-of-bounds read when IS_LAST_ENTRY() reads 4 bytes starting at 'next'. This can cause memory access beyond the valid xattr region. The fix changes the check to (void *)next + sizeof(u32) > end, ensuring the pointer does not approach the boundary too closely and preventing the out-of-bounds read. The vulnerability is classified under CWE-125 (Out-of-bounds Read).
Potential Impact
The vulnerability allows an out-of-bounds read of 4 bytes beyond the valid extended attribute region in the ext4 filesystem code. This can lead to denial of service (application or system crash) due to memory corruption. Confidentiality impact is rated high as per the CVSS vector, indicating potential exposure of sensitive information from memory. Integrity impact is none, and availability impact is high due to possible crashes.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. The vulnerability description indicates a fix by adjusting the bounds check in the Linux kernel ext4 code, but no explicit patch link or official fix advisory is provided. Users should monitor the Microsoft Security Response Center and Linux kernel advisories for an official patch and apply it once available. Until then, avoid untrusted input that could trigger extended attribute parsing in ext4 if possible.
A vulnerability in the Linux kernel's ext4 filesystem code allows an out-of-bounds read due to an improper bounds check in the check_xattrs()… (CVE-2026-46094)
Description
A vulnerability in the Linux kernel's ext4 filesystem code allows an out-of-bounds read due to an improper bounds check in the check_xattrs() function. The issue arises because the bounds check permits a pointer to be within sizeof(u32) bytes of the end of the valid region, leading to a 4-byte read beyond the valid memory area. This can cause a high-severity impact including potential denial of service due to memory corruption. The vulnerability affects version 3.0 of the Linux kernel ext4 code as specified. A fix involves adjusting the bounds check to ensure sufficient space for the 4-byte read. No patch link is provided in the data, and no known exploits are reported in the wild.
CVSS v3.1
Score 7.1high
Affected software
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability (CVE-2026-46094) in the Linux kernel ext4 filesystem is due to an incorrect bounds check in the check_xattrs() function. The original check (void *)next >= end allows the pointer 'next' to be positioned within sizeof(u32) bytes of the end boundary, which leads to an out-of-bounds read when IS_LAST_ENTRY() reads 4 bytes starting at 'next'. This can cause memory access beyond the valid xattr region. The fix changes the check to (void *)next + sizeof(u32) > end, ensuring the pointer does not approach the boundary too closely and preventing the out-of-bounds read. The vulnerability is classified under CWE-125 (Out-of-bounds Read).
Potential Impact
The vulnerability allows an out-of-bounds read of 4 bytes beyond the valid extended attribute region in the ext4 filesystem code. This can lead to denial of service (application or system crash) due to memory corruption. Confidentiality impact is rated high as per the CVSS vector, indicating potential exposure of sensitive information from memory. Integrity impact is none, and availability impact is high due to possible crashes.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. The vulnerability description indicates a fix by adjusting the bounds check in the Linux kernel ext4 code, but no explicit patch link or official fix advisory is provided. Users should monitor the Microsoft Security Response Center and Linux kernel advisories for an official patch and apply it once available. Until then, avoid untrusted input that could trigger extended attribute parsing in ext4 if possible.
Technical Details
- Gcve Source
- db.gcve.eu
- Csaf Category
- csaf_vex
- Csaf Version
- 2.0
- Publisher
- Microsoft Security Response Center
- Advisory Id
- msrc_CVE-2026-46094
- Cve Count
- 1
- Additional Cves
- []
- Cvss Version
- 3.1
Threat ID: 6a18ab75e29bf47b50288c6b
Added to database: 05/28/2026, 20:54:13 UTC
Last enriched: 06/26/2026, 23:38:08 UTC
Last updated: 07/31/2026, 19:22:59 UTC
Views: 47
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.