Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-80805xfs: validate attr entry pointer before field access

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.

Timeline

  1. ID reserved

    By Linux

  2. · 9 days later

    Published

  3. · 2 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.19% · top 91% of all CVEs (16 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected c84760659dcf237902d4cc997cd5f55cb3b2807f – < 0f82586741e39926542f621bafa424e237a04fa4
    • affected c84760659dcf237902d4cc997cd5f55cb3b2807f – < 134d82a2b5e3eba3ebf58753a1387b22f26ca1de
    • affected c84760659dcf237902d4cc997cd5f55cb3b2807f – < 03a12253dd2a036545bdb0110a4e0b8dc70f8e7c
    • affected c84760659dcf237902d4cc997cd5f55cb3b2807f – < e99120b5944a16d0bc27e52b33de78bcdaaabf5c
    • affected c84760659dcf237902d4cc997cd5f55cb3b2807f – < 98a42bb9d60d42898c3494de351a1bf508348cde
    • affected c84760659dcf237902d4cc997cd5f55cb3b2807f – < 184c1a80421a5b5ddcd262e47980ce2e67fee211
    • affected c84760659dcf237902d4cc997cd5f55cb3b2807f – < 9f92e749fc08b7ff3d9da190c4d1b2273745b282
    • affected c84760659dcf237902d4cc997cd5f55cb3b2807f – < c35da2bac6f7cb9a9be73f188b4fcc324615c327
    • affected c84760659dcf237902d4cc997cd5f55cb3b2807f – < b7eea80be25f3334f131d52982b3131aba77b97d
  • Linux · Linux

    • affected 5.5
    • unaffected < 5.5
    • unaffected 5.10.267 – ≤ 5.10.*
    • unaffected 5.15.218 – ≤ 5.15.*
    • unaffected 6.1.185 – ≤ 6.1.*
    • unaffected 6.6.154 – ≤ 6.6.*
    • unaffected 6.12.106 – ≤ 6.12.*
    • unaffected 6.18.47 – ≤ 6.18.*
    • unaffected 7.1.11 – ≤ 7.1.*
    • unaffected 7.2.1 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References9

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-80805 badge
[![CVE-2026-80805](https://cveledger.app/badge/CVE-2026-80805.svg)](https://cveledger.app/cve/CVE-2026-80805)

Record last updated .