Answer in brief
CVE-2026-90321 records a High severity (CVSS 7.8) vulnerability in ocfs2: validate inline xattrs during inode block validation. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=cf1d6c763fbcb115263114302485ad17e7933d87 <3fd45b24879fa4885b66a582a6e47eda67f11310 || >=cf1d6c763fbcb115263114302485ad17e7933d87 <8914a3330b72378136c2c02d6328a826f6abdad7 | 3fd45b24879fa4885b66a582a6e47eda67f11310, 8914a3330b72378136c2c02d6328a826f6abdad7 |
| Linux/Linuxgeneric | 2.6.28 | Not reported |
| Linux/Linuxgeneric | >=cf1d6c763fbcb115263114302485ad17e7933d87 <7dec19f6bafe4e1503007141c9f5eb7eb10e5578 || >=cf1d6c763fbcb115263114302485ad17e7933d87 <8138d06e7a1d9a0b0481dc015c67b34e8bb60a58 || >=cf1d6c763fbcb115263114302485ad17e7933d87 <3fd45b24879fa4885b66a582a6e47eda67f11310 || >=cf1d6c763fbcb115263114302485ad17e7933d87 <8914a3330b72378136c2c02d6328a826f6abdad7 | 7dec19f6bafe4e1503007141c9f5eb7eb10e5578, 8138d06e7a1d9a0b0481dc015c67b34e8bb60a58, 3fd45b24879fa4885b66a582a6e47eda67f11310, 8914a3330b72378136c2c02d6328a826f6abdad7 |
Published upstream
Sep 17, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 21, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 17, 2026
In the Linux kernel, the following vulnerability has been resolved: ocfs2: validate inline xattrs during inode block validation Patch series "ocfs2: validate xattr entry bounds", v7. This series validates OCFS2 xattr entry name/value bounds when xattr metadata is read and validated, before getxattr() or listxattr() can walk out-of-range entry arrays or offsets from corrupted metadata. This patch (of 2): ocfs2_validate_inode_block() verifies a dinode before OCFS2 users walk metadata from it, but inline xattr metadata is still checked only in operation-specific consumers. The existing ibody lookup helper validates inline header placement and entry count, but inode block validation does not reject entry name/value bounds. Add a flat xattr entry validator and call it from inode block validation for inline xattrs. Keep the operation paths on their existing header/count lookup checks; the full entry bounds check now runs when the inode block is validated at read time. Reject corrupted inline xattr metadata before ocfs2_xattr_ibody_get() or listxattr() can walk past the inline storage. Validation reproduced this kernel report: BUG: KASAN: use-after-free in ocfs2_xattr_find_entry+0x5a/0x170 Read of size 2 at addr ffff8881242a2000 by task python3/529 Call Trace: dump_stack_lvl+0x66/0xa0 print_report+0xce/0x630 kasan_report+0xe0/0x110 ocfs2_xattr_find_entry+0x5a/0x170 ocfs2_xattr_get_nolock+0x20a/0x820 ocfs2_xattr_get+0x10c/0x1e0 __vfs_getxattr+0xe2/0x130 vfs_getxattr+0x185/0x1b0
Quoted source text, attributed separately from HOL analysis.