CVE-2026-46094
What it is
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.
At a glance
- Exploitability
- Can be exploited locally on the machine with a low-privilege account. High risk of data exposure, service disruption.
- Exploit odds
- 0.1% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.1% in the next 30 days (EPSS).
- Severity: 7.1 HIGH (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.1% · EPSS, next 30 days
- Weakness
- CWE-125 · Out-of-bounds read
- Record status
- Analyzed
Affected
- Linux Kernel < 6.6.140
- Linux Kernel < 6.12.86
- Linux Kernel < 6.18.27
- Linux Kernel < 7.0.4
Attack profile CVSS 3.1 · 7.1
- Attack vector
- Local
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- High
Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2026-46094.md and follow it. Check whether this project is affected by CVE-2026-46094. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://git.kernel.org/stable/c/520986722dbf869c122252123fc161c7302eab7d
- https://git.kernel.org/stable/c/537e065977022aa22f2c2503e8accaf16622e0fd
- https://git.kernel.org/stable/c/5a5314d2387633a272a04d1bd8727f99058e4e68
- https://git.kernel.org/stable/c/ab6da97bc310db35d4e4ef5354bc3ff626b0698c
- https://git.kernel.org/stable/c/eceafc31ea7b42c984ece10d79d505c0bb6615d5
References
- https://git.kernel.org/stable/c/520986722dbf869c122252123fc161c7302eab7d
- https://git.kernel.org/stable/c/537e065977022aa22f2c2503e8accaf16622e0fd
- https://git.kernel.org/stable/c/5a5314d2387633a272a04d1bd8727f99058e4e68
- https://git.kernel.org/stable/c/ab6da97bc310db35d4e4ef5354bc3ff626b0698c
- https://git.kernel.org/stable/c/eceafc31ea7b42c984ece10d79d505c0bb6615d5