LiveActive security incident?Get immediate response
CVE Record

CVE-2022-49469: btrfs: fix anon_dev leak in create_subvol()

In the Linux kernel, the following vulnerability has been resolved: btrfs: fix anon_dev leak in create_subvol() When btrfs_qgroup_inherit(), btrfs_alloc_tree_block, or btrfs_insert_root() fail in create_subvol(), we return without freeing anon_dev. Reorganize the error handling in create_subvol() to fix this.

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

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel Btrfs resource-leak flaw. Failed subvolume creation can leave an anonymous device reference allocated. The sources do not show remote code execution, privilege escalation, public exploitation, or a CVSS score.

Executive priority

Treat as routine kernel hygiene unless your environment heavily uses Btrfs subvolume automation. Prioritize through standard Linux patch cycles, with faster action for shared hosts or systems where untrusted users can manage Btrfs subvolumes.

Technical view

In create_subvol(), failures from btrfs_qgroup_inherit(), btrfs_alloc_tree_block(), or btrfs_insert_root() could return without freeing anon_dev. Upstream stable commits reorganize error handling to release the resource on these failure paths.

Likely exposure

Exposure is most likely on Linux systems using Btrfs with vulnerable kernel builds and workflows that create subvolumes. Exact distro exposure needs vendor package confirmation because backports may change version-based conclusions.

Exploitation context

The provided bundle marks CISA KEV as false and cites no active exploitation. The issue appears to require reaching Btrfs subvolume creation failure paths; the sources do not describe public exploitability or impact beyond the leak.

Researcher notes

Evidence is limited to the CVE record and upstream stable commits. No CVSS, CWE, exploit status, or detailed attack preconditions are provided. Focus analysis on error-path cleanup, Btrfs subvolume permissions, and distro backport status.

Mitigation direction

  • Apply vendor kernel updates that include the referenced stable Btrfs fixes.
  • Check distribution advisories because backported kernel packages may not match upstream version numbers.
  • Limit Btrfs subvolume creation to trusted administrators until updated.
  • Monitor affected systems for unusual Btrfs failures or resource exhaustion symptoms.

Validation and detection

  • Inventory systems using Btrfs and compare kernel packages against vendor CVE guidance.
  • Confirm whether the referenced upstream stable commits are present or backported.
  • Review whether untrusted users or automation can trigger Btrfs subvolume creation.
  • Track remediation through normal kernel patch compliance reporting.
Prepared
Confidence
medium
Sources
5

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-49469 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
4Source 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
LinuxLinux2dfb1e43f57dd3aeaa66f7cf05d068db2d4c8788, 2dfb1e43f57dd3aeaa66f7cf05d068db2d4c8788, 2dfb1e43f57dd3aeaa66f7cf05d068db2d4c8788, 917d608fe375041eb7f29befa6a6d7fd3cf32ddeunaffected
LinuxLinux5.9, 0, 5.17.14, 5.18.3, 5.19affected
Weakness

CWE details

No CWE listed

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