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-52962ceph: fix a buffer leak in __ceph_setxattr()

Description

In the Linux kernel, the following vulnerability has been resolved: ceph: fix a buffer leak in __ceph_setxattr() The old_blob in __ceph_setxattr() can store ci->i_xattrs.prealloc_blob value during the retry. However, it is never called the ceph_buffer_put() for the old_blob object. This patch fixes the issue of the buffer leak.

Timeline

  1. ID reserved

    By Linux

  2. · 15 days later

    Published

  3. · 5 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-52962, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.14% · top 97% of all CVEs (18 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: High 7.8.

Affected products

  • Linux · Linux

    • affected 86968ef21596515958d5f0a40233d02be78ecec0 – < 521e5aba857fd267624892c8dd6295f22ce0267e
    • affected 86968ef21596515958d5f0a40233d02be78ecec0 – < d0cb994605c84a159c1d00d72cdc8583c321ef95
    • affected 86968ef21596515958d5f0a40233d02be78ecec0 – < ecf94823c5c6a20790bb76ed2816822b0beb0c22
    • affected 86968ef21596515958d5f0a40233d02be78ecec0 – < 4bfdcefdaa6092a06cacd59389c7756b36e6de8c
    • affected 86968ef21596515958d5f0a40233d02be78ecec0 – < 7d3e8d2d648d5f0df29b4710246680f47695fe94
    • affected 86968ef21596515958d5f0a40233d02be78ecec0 – < 3fa13ceefbc5f36131110342743994cb3de80637
    • affected 86968ef21596515958d5f0a40233d02be78ecec0 – < bc7abce4460e490dcb579eec770f175b150b685f
    • affected 86968ef21596515958d5f0a40233d02be78ecec0 – < 5d3cc36b4e77a27ce7b686b7c59c7072bcb3fa8e
    • affected 1d86cb8d3204337e1853b84d69ea0f30dc0ba973
    • affected 9cec64d3f6d91da590cc4069172254067b43d0b2
    • affected de30fc2ca852365ed635f62d7d818bffc15e55c9
    • affected dfb8712c7acce0689aed6c400a22b35f4d2861fe
    • affected f41cd559f1f3412db8e0acdede05ecf990ebfd8a
    • affected 4.4.192 – < 4.5
    • affected 4.9.192 – < 4.10
    • affected 4.14.143 – < 4.15
    • affected 4.19.72 – < 4.20
    • affected 5.2.14 – < 5.3
  • Linux · Linux

    • affected 5.3
    • unaffected < 5.3
    • unaffected 5.10.258 – ≤ 5.10.*
    • unaffected 5.15.209 – ≤ 5.15.*
    • unaffected 6.1.175 – ≤ 6.1.*
    • unaffected 6.6.141 – ≤ 6.6.*
    • unaffected 6.12.91 – ≤ 6.12.*
    • unaffected 6.18.33 – ≤ 6.18.*
    • unaffected 7.0.10 – ≤ 7.0.*
    • unaffected 7.1 – ≤ *

References

References8

Sources

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

Badge for a README or a ticket

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

Record last updated .