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-64146erofs: fix metabuf leak in inode xattr initialization

Description

In the Linux kernel, the following vulnerability has been resolved: erofs: fix metabuf leak in inode xattr initialization commit bb88e8da0025 ("erofs: use meta buffers for xattr operations") converted xattr operations to use on-stack erofs_buf instances. erofs_init_inode_xattrs() uses such a metabuf while reading the inline xattr header and shared xattr id array. Some error paths after erofs_read_metabuf() leave through out_unlock without dropping the metabuf, so the folio reference can leak. Consolidate the cleanup at out_unlock. erofs_put_metabuf() is a no-op if no folio has been acquired, and this keeps all paths after taking EROFS_I_BL_XATTR_BIT covered by a single cleanup site.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 4 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

CVSS scores of CVE-2026-64146, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.13% · top 97% 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: Medium 5.5.

Affected products

  • Linux · Linux

    • affected bb88e8da00253bea0e7f0f4cdfd7910572d7799f – < 89682dd09efb3825b0f162a72e342c52b69ea14a
    • affected bb88e8da00253bea0e7f0f4cdfd7910572d7799f – < 3812cfe6cb0a5988df4fedcdaf9aab677b9cca61
    • affected bb88e8da00253bea0e7f0f4cdfd7910572d7799f – < e4a552e0b6413c1af2e140b5bc14bb849b411b57
    • affected bb88e8da00253bea0e7f0f4cdfd7910572d7799f – < fcb23bb31508b62e8a1b32adf6217820e90e29b0
    • affected bb88e8da00253bea0e7f0f4cdfd7910572d7799f – < 492c73b21fefa36f3869cb2b188ffb7fe37b3a9b
    • affected bb88e8da00253bea0e7f0f4cdfd7910572d7799f – < 79b09c54c6563df9846ca3094bcfd72082c3e1d7
  • Linux · Linux

    • affected 5.17
    • unaffected < 5.17
    • unaffected 6.1.191 – ≤ 6.1.*
    • unaffected 6.6.160 – ≤ 6.6.*
    • unaffected 6.12.114 – ≤ 6.12.*
    • unaffected 6.18.57 – ≤ 6.18.*
    • unaffected 7.0.11 – ≤ 7.0.*
    • unaffected 7.1 – ≤ *

References

References6

Sources

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

Badge for a README or a ticket

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

Record last updated .