LiveActive security incident?Get immediate response
CVE Record

CVE-2022-49914: btrfs: fix inode list leak during backref walking at resolve_indirect_refs()

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2022-49914 is a Linux kernel Btrfs bug where certain error handling during back-reference walking can leak kernel memory structures. The sources describe a resource leak, not direct data theft or code execution. Business urgency depends on whether affected Linux kernels and Btrfs are used.

Executive priority

Treat this as a targeted Linux storage reliability issue until more evidence appears. Prioritize patching systems that use Btrfs for production workloads, but do not treat it as proven active exploitation based on the provided sources.

Technical view

In Btrfs resolve_indirect_refs(), an error path freed the parent ulist with ulist_free() but did not free inode lists stored through ulist node aux fields. The fix switches that exit path to free_leaf_list(), moving and simplifying that helper as needed.

Likely exposure

Exposure is likely limited to Linux systems using affected kernel versions with Btrfs. The source lists Linux kernel versions including 3.5, 4.14.299, 4.19.265, 5.4.224, 5.10.154, 5.15.78, 6.0.8, and 6.1 as affected, but distribution-specific status is not provided.

Exploitation context

The bundle does not report active exploitation, and KEV is false. The public description indicates a memory leak on an error path during Btrfs backref walking. No source in the bundle describes exploitability, attacker prerequisites, or observed abuse.

Researcher notes

Evidence is narrow: the CVE record identifies a Btrfs memory leak and points to stable kernel commits. There is no CVSS, CWE, exploit detail, or vendor distribution matrix in the bundle. Validate exposure by kernel lineage and Btrfs usage rather than CVE title alone.

Mitigation direction

  • Identify systems running Linux kernels with Btrfs enabled or mounted.
  • Check vendor kernel advisories for fixed packages matching the referenced stable commits.
  • Prioritize kernel updates where Btrfs is used on production storage.
  • If no vendor package is available, follow distribution guidance for backported fixes.
  • Monitor systems for memory pressure until patched.

Validation and detection

  • Inventory kernel versions across Linux hosts and appliances.
  • Confirm whether Btrfs filesystems are present or mounted.
  • Map installed kernel packages to vendor advisories or stable commits.
  • Verify patched hosts no longer run affected kernel builds.
  • Review monitoring for unexplained memory growth on Btrfs systems.
Prepared
Confidence
medium
Sources
9

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2022-49914 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
0ADP providers
8Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux3301958b7c1dae8f0f5ded63aa881e0b71e78464, 3301958b7c1dae8f0f5ded63aa881e0b71e78464, 3301958b7c1dae8f0f5ded63aa881e0b71e78464, 3301958b7c1dae8f0f5ded63aa881e0b71e78464, 3301958b7c1dae8f0f5ded63aa881e0b71e78464, 3301958b7c1dae8f0f5ded63aa881e0b71e78464, 3301958b7c1dae8f0f5ded63aa881e0b71e78464unaffected
LinuxLinux3.5, 0, 4.14.299, 4.19.265, 5.4.224, 5.10.154, 5.15.78, 6.0.8, 6.1affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.