Skip to content
TrackCVE
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API documentationPage
  • MCP serverPage
  • Data sourcesPage
  • ChangelogPage
  • AboutPage
  • How it's builtPage
Back

CVE-2023-53672

btrfs: output extra debug info if we failed to find an inline backref

Medium5.5EPSS 0.15%
Published
Updated
Reserved
Assigned by
Linux

Description

In the Linux kernel, the following vulnerability has been resolved: btrfs: output extra debug info if we failed to find an inline backref [BUG] Syzbot reported several warning triggered inside lookup_inline_extent_backref(). [CAUSE] As usual, the reproducer doesn't reliably trigger locally here, but at least we know the WARN_ON() is triggered when an inline backref can not be found, and it can only be triggered when @insert is true. (I.e. inserting a new inline backref, which means the backref should already exist) [ENHANCEMENT] After the WARN_ON(), dump all the parameters and the extent tree leaf to help debug.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 7 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-2023-53672, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.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.15% · top 96% of all CVEs (7 Nov 2026)
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 492104c866cb1b62a11393adccb477f5cd2c7768 – < 376b41524b71e494514720bd6114325b0a2ed19c
    • affected 492104c866cb1b62a11393adccb477f5cd2c7768 – < 400e08a16604b534fdd82c5a288fa150d04f5f79
    • affected 492104c866cb1b62a11393adccb477f5cd2c7768 – < 7afbfde45d665953b4d5a42a721e15bf0315d89b
    • affected 492104c866cb1b62a11393adccb477f5cd2c7768 – < b7c3cf2f6c42e6688b1c37215a0b1663f982f915
    • affected 492104c866cb1b62a11393adccb477f5cd2c7768 – < 6994f806c6d1ae8b59344d3700358547f3b3fe1d
    • affected 492104c866cb1b62a11393adccb477f5cd2c7768 – < 28062cd6eda04035d8f6ded2001292ac8b496149
    • affected 492104c866cb1b62a11393adccb477f5cd2c7768 – < e70ba449b04b40584bdabb383d10455397cbf177
    • affected 492104c866cb1b62a11393adccb477f5cd2c7768 – < 7f72f50547b7af4ddf985b07fc56600a4deba281
  • Linux · Linux

    • affected 3.9
    • unaffected < 3.9
    • unaffected 4.14.326 – ≤ 4.14.*
    • unaffected 4.19.295 – ≤ 4.19.*
    • unaffected 5.4.257 – ≤ 5.4.*
    • unaffected 5.10.197 – ≤ 5.10.*
    • unaffected 5.15.133 – ≤ 5.15.*
    • unaffected 6.1.55 – ≤ 6.1.*
    • unaffected 6.5.5 – ≤ 6.5.*
    • unaffected 6.6 – ≤ *

References (8)

Sources

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

Badge for a README or a ticket

CVE-2023-53672 badge
[![CVE-2023-53672](https://trackcve.app/badge/CVE-2023-53672.svg)](https://trackcve.app/cve/CVE-2023-53672)

Record last updated .