LiveActive security incident?Get immediate response
CVE Record

CVE-2022-50300: btrfs: fix extent map use-after-free when handling missing device in read_one_chunk

In the Linux kernel, the following vulnerability has been resolved: btrfs: fix extent map use-after-free when handling missing device in read_one_chunk Store the error code before freeing the extent_map. Though it's reference counted structure, in that function it's the first and last allocation so this would lead to a potential use-after-free. The error can happen eg. when chunk is stored on a missing device and the degraded mount option is missing. Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=216721

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-50300 is a Linux kernel btrfs flaw where error handling can reference freed memory. The documented trigger involves a btrfs chunk on a missing device when the degraded mount option is absent. Public sources do not provide CVSS, exploit evidence, or business impact details.

Executive priority

Treat as a targeted Linux storage stability risk rather than an internet-facing emergency. Prioritize patch verification for btrfs systems, storage appliances, and servers where degraded disk conditions could disrupt availability.

Technical view

The bug is a potential use-after-free in btrfs read_one_chunk. The fix stores the error code before freeing an extent_map. The CVE source lists Linux kernel versions including 4.15, 5.15.87, 6.0.18, 6.1.4, and 6.2 as affected and references stable kernel commits.

Likely exposure

Exposure is most likely on Linux systems using btrfs, especially multi-device or degraded storage scenarios. Systems not using btrfs are less likely to encounter the documented path, but the source does not provide complete distribution-level affected package mapping.

Exploitation context

The source bundle does not report active exploitation, and CISA KEV status is false. The described condition is operationally specific: a missing btrfs device and no degraded mount option. No public exploitability assessment is provided.

Researcher notes

Evidence is limited to the CVE record and kernel stable commits. The vulnerable path is in btrfs read_one_chunk error handling around extent_map lifetime. No CWE, CVSS vector, exploit status, or distribution package matrix is present in the bundle.

Mitigation direction

  • Check Linux vendor advisories for fixed kernel packages containing the referenced stable commits.
  • Prioritize updates on hosts using btrfs or degraded storage configurations.
  • Avoid unsupported kernel builds where stable fixes may not be backported.
  • Review btrfs operational procedures for missing-device recovery and degraded mounts.

Validation and detection

  • Inventory Linux hosts and identify which use btrfs filesystems.
  • Compare kernel versions and vendor package changelogs against the referenced stable fixes.
  • Review storage incident logs for btrfs missing-device or mount failure events.
  • Confirm affected distributions have published backports before closing remediation.
Prepared
Confidence
medium
Sources
6

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-50300 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
5Source 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
LinuxLinuxadfb69af7d8cb6a3958f75aad1ef4bc96891d116, adfb69af7d8cb6a3958f75aad1ef4bc96891d116, adfb69af7d8cb6a3958f75aad1ef4bc96891d116, adfb69af7d8cb6a3958f75aad1ef4bc96891d116unaffected
LinuxLinux4.15, 0, 5.15.87, 6.0.18, 6.1.4, 6.2affected
Weakness

CWE details

No CWE listed

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