CVE-2026-80805

xfs: validate attr entry pointer before field access

N/A
Published: September 4, 2026 at 03:13 PM UTC
Updated: October 19, 2026 at 09:17 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: xfs: validate attr entry pointer before field access xfs_attr3_leaf_verify_entry() accesses lentry/rentry fields (namelen, valuelen) before checking if the entry pointer itself is within bounds. If nameidx is crafted to point near the end of the buffer, these field accesses can read out-of-bounds before the bounds check at name_end > buf_end is performed. Add explicit bounds checks for entry pointers before accessing their fields. Use offsetof() to check that the start of the flexible array member (nameval/name) is within bounds, which ensures all preceding fields are safe to access.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

5.5c84760659dcf237902d4cc997cd5f55cb3b2807f
Vendor states this is fixed in 03a12253dd2a036545bdb0110a4e0b8dc70f8e7c (fixed)
Vendor states this is fixed in 0f82586741e39926542f621bafa424e237a04fa4 (fixed)
Vendor states this is fixed in 134d82a2b5e3eba3ebf58753a1387b22f26ca1de (fixed)
Vendor states this is fixed in 184c1a80421a5b5ddcd262e47980ce2e67fee211 (fixed)
Vendor states this is fixed in 98a42bb9d60d42898c3494de351a1bf508348cde (fixed)
Vendor states this is fixed in 9f92e749fc08b7ff3d9da190c4d1b2273745b282 (fixed)
Vendor states this is fixed in b7eea80be25f3334f131d52982b3131aba77b97d (fixed)
Vendor states this is fixed in c35da2bac6f7cb9a9be73f188b4fcc324615c327 (fixed)
Vendor states this is fixed in e99120b5944a16d0bc27e52b33de78bcdaaabf5c (fixed)
Vendor states this is fixed in 5.10.267 (unaffected)
Vendor states this is fixed in 5.15.218 (unaffected)
Vendor states this is fixed in 5.5 (unaffected)
Vendor states this is fixed in 6.1.185 (unaffected)
Vendor states this is fixed in 6.12.106 (unaffected)
Vendor states this is fixed in 6.18.47 (unaffected)
Vendor states this is fixed in 6.6.154 (unaffected)
Vendor states this is fixed in 7.1.11 (unaffected)
Vendor states this is fixed in 7.2.1 (unaffected)
Vendor states this is fixed in 7.3 (unaffected)
Vendor states this is fixed in 7.3-rc1 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card