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-46840btrfs: clean up our handling of refs == 0 in snapshot delete

Description

In the Linux kernel, the following vulnerability has been resolved: btrfs: clean up our handling of refs == 0 in snapshot delete In reada we BUG_ON(refs == 0), which could be unkind since we aren't holding a lock on the extent leaf and thus could get a transient incorrect answer. In walk_down_proc we also BUG_ON(refs == 0), which could happen if we have extent tree corruption. Change that to return -EUCLEAN. In do_walk_down() we catch this case and handle it correctly, however we return -EIO, which -EUCLEAN is a more appropriate error code. Finally in walk_up_proc we have the same BUG_ON(refs == 0), so convert that to proper error handling. Also adjust the error message so we can actually do something with the information.

Timeline

  1. ID reserved

    By Linux

  2. · 16 days later

    Published

  3. · 20 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-46840, 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.26% · top 82% 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 2c47e605a91dde6b0514f689645e7ab336c8592a – < c847b28a799733b04574060ab9d00f215970627d
    • affected 2c47e605a91dde6b0514f689645e7ab336c8592a – < 71291aa7246645ef622621934d2067400380645e
    • affected 2c47e605a91dde6b0514f689645e7ab336c8592a – < c60676b81fab456b672796830f6d8057058f029c
    • affected 2c47e605a91dde6b0514f689645e7ab336c8592a – < 728d4d045b628e006b48a448f3326a7194c88d32
    • affected 2c47e605a91dde6b0514f689645e7ab336c8592a – < 9cc887ac24b7a0598f4042ae9af6b9a33072f75b
    • affected 2c47e605a91dde6b0514f689645e7ab336c8592a – < 7d1df13bf078ffebfedd361d714ff6cee1ff01b9
    • affected 2c47e605a91dde6b0514f689645e7ab336c8592a – < 03804641ec2d0da4fa088ad21c88e703d151ce16
    • affected 2c47e605a91dde6b0514f689645e7ab336c8592a – < b8ccef048354074a548f108e51d0557d6adfd3a3
  • Linux · Linux

    • affected 2.6.31
    • unaffected < 2.6.31
    • unaffected 4.19.322 – ≤ 4.19.*
    • unaffected 5.4.284 – ≤ 5.4.*
    • unaffected 5.10.226 – ≤ 5.10.*
    • unaffected 5.15.167 – ≤ 5.15.*
    • unaffected 6.1.110 – ≤ 6.1.*
    • unaffected 6.6.51 – ≤ 6.6.*
    • unaffected 6.10.10 – ≤ 6.10.*
    • unaffected 6.11 – ≤ *

References

References10

Sources

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

Badge for a README or a ticket

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

Record last updated .