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-2024-39276ext4: fix mb_cache_entry's e_refcnt leak in ext4_xattr_block_cache_find()

Description

In the Linux kernel, the following vulnerability has been resolved: ext4: fix mb_cache_entry's e_refcnt leak in ext4_xattr_block_cache_find() Syzbot reports a warning as follows: ============================================ WARNING: CPU: 0 PID: 5075 at fs/mbcache.c:419 mb_cache_destroy+0x224/0x290 Modules linked in: CPU: 0 PID: 5075 Comm: syz-executor199 Not tainted 6.9.0-rc6-gb947cc5bf6d7 RIP: 0010:mb_cache_destroy+0x224/0x290 fs/mbcache.c:419 Call Trace: <TASK> ext4_put_super+0x6d4/0xcd0 fs/ext4/super.c:1375 generic_shutdown_super+0x136/0x2d0 fs/super.c:641 kill_block_super+0x44/0x90 fs/super.c:1675 ext4_kill_sb+0x68/0xa0 fs/ext4/super.c:7327 [...] ============================================ This is because when finding an entry in ext4_xattr_block_cache_find(), if ext4_sb_bread() returns -ENOMEM, the ce's e_refcnt, which has already grown in the __entry_find(), won't be put away, and eventually trigger the above issue in mb_cache_destroy() due to reference count leakage. So call mb_cache_entry_put() on the -ENOMEM error branch as a quick fix.

Timeline

  1. ID reserved

    By Linux

  2. · 1 day later

    Published

  3. · 23 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-2024-39276, by who scored it
Scored byCVSSScoreVector
CISA-ADPADP (enrichment)3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
NVDNVD · Analyzed3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
EPSS (exploitation in 30 days)
0.23% · top 86% of all CVEs (15 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 b878c8a7f08f0c225b6a46ba1ac867e9c5d17807 – < 9ad75e78747b5a50dc5a52f0f8e92e920a653f16
    • affected fb265c9cb49e2074ddcdd4de99728aefdd3b3592 – < 896a7e7d0d555ad8b2b46af0c2fa7de7467f9483
    • affected fb265c9cb49e2074ddcdd4de99728aefdd3b3592 – < 76dc776153a47372719d664e0fc50d6355791abb
    • affected fb265c9cb49e2074ddcdd4de99728aefdd3b3592 – < 681ff9a09accd8a4379f8bd30b7a1641ee19bb3e
    • affected fb265c9cb49e2074ddcdd4de99728aefdd3b3592 – < e941b712e758f615d311946bf98216e79145ccd9
    • affected fb265c9cb49e2074ddcdd4de99728aefdd3b3592 – < a95df6f04f2c37291adf26a74205cde0314d4577
    • affected fb265c9cb49e2074ddcdd4de99728aefdd3b3592 – < b37c0edef4e66fb21a2fbc211471195a383e5ab8
    • affected fb265c9cb49e2074ddcdd4de99728aefdd3b3592 – < 0c0b4a49d3e7f49690a6827a41faeffad5df7e21
    • affected 9da1f6d06b7a6d068e68fcfd7cbbf6b586d888e1
    • affected 81313ed2c705d958744882a269bf4a5e3ddec95e
    • affected 4.19.14 – < 4.19.316
    • affected 4.14.92 – < 4.15
    • affected 4.20.1 – < 4.21
  • Linux · Linux

    • affected 5.0
    • unaffected < 5.0
    • unaffected 4.19.316 – ≤ 4.19.*
    • unaffected 5.4.278 – ≤ 5.4.*
    • unaffected 5.10.219 – ≤ 5.10.*
    • unaffected 5.15.161 – ≤ 5.15.*
    • unaffected 6.1.94 – ≤ 6.1.*
    • unaffected 6.6.34 – ≤ 6.6.*
    • unaffected 6.9.5 – ≤ 6.9.*
    • unaffected 6.10 – ≤ *

References

References8

Sources

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

Badge for a README or a ticket

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

Record last updated .