CVE-2022-49833: btrfs: zoned: clone zoned device info when cloning a device
In the Linux kernel, the following vulnerability has been resolved:
btrfs: zoned: clone zoned device info when cloning a device
When cloning a btrfs_device, we're not cloning the associated
btrfs_zoned_device_info structure of the device in case of a zoned
filesystem.
Later on this leads to a NULL pointer dereference when accessing the
device's zone_info for instance when setting a zone as active.
This was uncovered by fstests' testcase btrfs/161.
Security readout for executives and security teams
Plain-English summary
This is a Linux kernel btrfs zoned-filesystem bug that can crash kernel code through a NULL pointer dereference. The public record does not provide a CVSS score, remote attack claim, or active exploitation evidence. Business urgency depends mainly on whether systems use btrfs on zoned block devices.
Executive priority
Treat as targeted operational risk, not an emergency based on current evidence. Prioritize patching where btrfs zoned storage is used, especially on production storage systems where kernel crashes could affect availability.
Technical view
When a btrfs device is cloned, the associated btrfs_zoned_device_info is not cloned for zoned filesystems. Later zone operations, such as marking a zone active, may access a missing zone_info pointer and trigger a NULL pointer dereference. The issue was found by fstests testcase btrfs/161.
Likely exposure
Exposure appears limited to Linux systems using btrfs zoned filesystem functionality. Standard Linux hosts not using btrfs zoned mode are less likely to be exposed. Exact distribution package impact cannot be determined from the bundle alone.
Exploitation context
The source bundle reports no CISA KEV listing and provides no evidence of exploitation in the wild. The described impact is kernel NULL pointer dereference during specific btrfs zoned-device handling, suggesting reliability or denial-of-service concern rather than confirmed remote compromise.
Researcher notes
The public description is concise and lacks CVSS, CWE, exploitability detail, and distribution-specific affected package ranges. Analysis should stay tied to btrfs zoned code paths and the two upstream stable commits referenced by the CVE record.
Mitigation direction
Check Linux distribution advisories for CVE-2022-49833 package status.
Apply a kernel containing the referenced stable btrfs fixes.
Prioritize systems using btrfs with zoned block devices.
Reduce reliance on affected btrfs zoned deployments until patched.
Track vendor guidance if exact package mapping is unclear.
Validation and detection
Inventory hosts using btrfs filesystems and zoned block devices.
Compare running kernel versions against vendor CVE advisories.
Confirm patched kernels include the referenced upstream stable commits.
Review crash logs for btrfs zoned NULL pointer dereference symptoms.
Run relevant btrfs regression tests in staging after patching.
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-49833 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
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
3Source links
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
CVE publishedCVE Program
The CVE record was published.
May 1, 2025, 14:09 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.