Threats Tagged 'cve-2026-46094'
View all threats tagged with 'cve-2026-46094'. Filter and sort to focus on specific types of threats.
Stop chasing alerts. Route them.
Start free, then upgrade once to turn Radar into an automated delivery engine for your security stack.
Custom feeds / Automations: email, Slack, webhooks, SIEM/MISP / API access (baseline limits)
API access activates after upgrading in Console -> Billing.
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.
Filter Threats
Narrow down the results by type, severity, or affected countries
Threats Tagged 'cve-2026-46094'
Click on any threat for detailed analysis and mitigation recommendations
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. Join the discussion | GCVE Database | 05/27/2026, 15:33:23 UTC Added: 05/28/2026, 20:54:13 UTC |
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. Join the discussion | GCVE Database | 05/27/2026, 14:17:00 UTC Added: 07/17/2026, 10:21:02 UTC |
Showing 1 to 2 of 2 results