LiveActive security incident?Get immediate response
CVE Record

CVE-2022-49996: btrfs: fix possible memory leak in btrfs_get_dev_args_from_path()

In the Linux kernel, the following vulnerability has been resolved: btrfs: fix possible memory leak in btrfs_get_dev_args_from_path() In btrfs_get_dev_args_from_path(), btrfs_get_bdev_and_sb() can fail if the path is invalid. In this case, btrfs_get_dev_args_from_path() returns directly without freeing args->uuid and args->fsid allocated before, which causes memory leak. To fix these possible leaks, when btrfs_get_bdev_and_sb() fails, btrfs_put_dev_args_from_path() is called to clean up the memory.

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

Security readout for executives and security teams

Plain-English summary

This CVE is a Linux kernel Btrfs memory-leak bug. If an invalid path is processed, allocated UUID/FSID memory may not be freed. Sources do not show remote code execution, privilege escalation, or active exploitation. Business impact appears mainly availability or resource stability on affected Linux systems using Btrfs paths.

Executive priority

Treat this as a low-priority kernel maintenance issue unless Btrfs is heavily used on critical systems. Patch through normal Linux update cycles, with faster handling for systems showing memory pressure or allowing less-trusted users to exercise Btrfs-related operations.

Technical view

In btrfs_get_dev_args_from_path(), btrfs_get_bdev_and_sb() can fail for an invalid path. The error path returned before freeing args->uuid and args->fsid. The fix calls btrfs_put_dev_args_from_path() on failure to release allocations. CVSS and CWE are not provided in the bundle.

Likely exposure

Exposure is limited to Linux systems with affected kernel builds where Btrfs code paths are reachable. The provided version data is incomplete and includes kernel versions and commit identifiers, so organizations should map installed distro kernels to vendor advisories or the referenced upstream stable commits.

Exploitation context

The bundle does not cite active exploitation, CISA KEV listing, public exploit use, or weaponized details. The described trigger is an invalid path leading to a missed cleanup path, not a disclosed remote attack chain.

Researcher notes

Evidence supports a memory leak in a Btrfs error path and an upstream cleanup fix. The bundle lacks CVSS, CWE, exploitability analysis, and precise downstream package status. Avoid overstating impact beyond resource leakage without additional vendor analysis.

Mitigation direction

  • Update to a kernel package that includes the referenced upstream stable fixes.
  • Check Linux distribution advisories for backported fixes matching deployed kernel builds.
  • Prioritize systems using Btrfs or exposing Btrfs management operations to untrusted users.
  • Monitor kernel memory pressure until patched on relevant systems.
  • Do not rely on version strings alone; confirm vendor backport status.

Validation and detection

  • Inventory Linux hosts and record kernel package versions and Btrfs usage.
  • Compare deployed kernels with vendor advisories and the referenced stable commits.
  • Confirm patched builds include the btrfs_get_dev_args_from_path() cleanup fix.
  • Review logs and monitoring for unusual memory pressure on Btrfs hosts.
  • Document any systems deferred from patching and their compensating controls.
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-49996 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
LinuxLinux321a81835b4aed4f717f89921286f6544ffa8be9, faa775c41d655a4786e9d53cb075a77bb5a75f66, faa775c41d655a4786e9d53cb075a77bb5a75f66unaffected
LinuxLinux5.16, 0, 5.15.64, 5.19.6, 6.0affected
Weakness

CWE details

No CWE listed

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