Skip to content
CVE Tracker
  • 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-2022-49914

btrfs: fix inode list leak during backref walking at resolve_indirect_refs()

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

Description

In the Linux kernel, the following vulnerability has been resolved: btrfs: fix inode list leak during backref walking at resolve_indirect_refs() During backref walking, at resolve_indirect_refs(), if we get an error we jump to the 'out' label and call ulist_free() on the 'parents' ulist, which frees all the elements in the ulist - however that does not free any inode lists that may be attached to elements, through the 'aux' field of a ulist node, so we end up leaking lists if we have any attached to the unodes. Fix this by calling free_leaf_list() instead of ulist_free() when we exit from resolve_indirect_refs(). The static function free_leaf_list() is moved up for this to be possible and it's slightly simplified by removing unnecessary code.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 13 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-2022-49914, 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.20% · top 90% 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.

Weakness

Affected products

  • Linux · Linux

    • affected 3301958b7c1dae8f0f5ded63aa881e0b71e78464 – < b1dc9019bb5f89abae85645de1a2dd4830c1f8e9
    • affected 3301958b7c1dae8f0f5ded63aa881e0b71e78464 – < cded2c89774b99b67c98147ae103ea878c92a206
    • affected 3301958b7c1dae8f0f5ded63aa881e0b71e78464 – < 2c0329406bb28109c07c6e23e5e3e0fa618a95d7
    • affected 3301958b7c1dae8f0f5ded63aa881e0b71e78464 – < a52e24c7fcc3c5ce3588a14e3663c00868d36623
    • affected 3301958b7c1dae8f0f5ded63aa881e0b71e78464 – < 6ba3479f9e96b9ad460c7e77abc26dd16e5dec4f
    • affected 3301958b7c1dae8f0f5ded63aa881e0b71e78464 – < 396515db923ad5cbeb179d6b88927870b4cbebb7
    • affected 3301958b7c1dae8f0f5ded63aa881e0b71e78464 – < 5614dc3a47e3310fbc77ea3b67eaadd1c6417bf1
  • Linux · Linux

    • affected 3.5
    • unaffected < 3.5
    • unaffected 4.14.299 – ≤ 4.14.*
    • unaffected 4.19.265 – ≤ 4.19.*
    • unaffected 5.4.224 – ≤ 5.4.*
    • unaffected 5.10.154 – ≤ 5.10.*
    • unaffected 5.15.78 – ≤ 5.15.*
    • unaffected 6.0.8 – ≤ 6.0.*
    • unaffected 6.1 – ≤ *

References (7)

Sources

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

Badge for a README or a ticket

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

Record last updated .