LiveActive security incident?Get immediate response
CVE Record

CVE-2022-50766: btrfs: set generation before calling btrfs_clean_tree_block in btrfs_init_new_buffer

In the Linux kernel, the following vulnerability has been resolved: btrfs: set generation before calling btrfs_clean_tree_block in btrfs_init_new_buffer syzbot is reporting uninit-value in btrfs_clean_tree_block() [1], for commit bc877d285ca3dba2 ("btrfs: Deduplicate extent_buffer init code") missed that btrfs_set_header_generation() in btrfs_init_new_buffer() must not be moved to after clean_tree_block() because clean_tree_block() is calling btrfs_header_generation() since commit 55c69072d6bd5be1 ("Btrfs: Fix extent_buffer usage when nodesize != leafsize"). Since memzero_extent_buffer() will reset "struct btrfs_header" part, we can't move btrfs_set_header_generation() to before memzero_extent_buffer(). Just re-add btrfs_set_header_generation() before btrfs_clean_tree_block().

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-50766 is a Linux kernel Btrfs bug involving use of an uninitialized value during tree block initialization. The public record says it has been resolved upstream, but provides no CVSS score, CWE, or stated security impact. Business urgency depends on whether affected Linux kernels use Btrfs.

Executive priority

Treat as a patch-management item, with higher priority for Btrfs-dependent systems. Because impact and exploitability are not described publicly, this is not enough evidence for emergency action absent vendor guidance or additional exposure.

Technical view

The issue is in btrfs_init_new_buffer(). A prior deduplication change moved btrfs_set_header_generation() after btrfs_clean_tree_block(), but btrfs_clean_tree_block() reads the header generation. The fix re-adds setting the generation before btrfs_clean_tree_block(), while keeping it after memzero_extent_buffer().

Likely exposure

Potential exposure is Linux systems running affected kernel versions or commits with Btrfs available or in use. The source lists affected kernel entries including 4.19, 5.15.75, 5.19.17, 6.0.3, and 6.1, but distro backports may change real exposure.

Exploitation context

No active exploitation is reported in the provided sources, and the CVE is not marked KEV. The issue was reported by syzbot as an uninitialized-value finding. Public sources do not define attacker prerequisites, exploitability, or practical impact.

Researcher notes

The record is sparse: no CVSS, CWE, impact statement, or exploitability assessment. Analysis should focus on commit lineage, stable backports, and whether Btrfs code paths are reachable in local deployments. Avoid assuming remote exposure from the available evidence.

Mitigation direction

  • Check Linux vendor or distribution advisories for fixed kernel packages.
  • Prioritize updates on systems using Btrfs filesystems.
  • Apply kernel updates containing the referenced stable fixes.
  • If immediate patching is not possible, review vendor guidance for interim controls.

Validation and detection

  • Inventory Linux kernel versions across affected assets.
  • Identify hosts using or enabling Btrfs.
  • Compare installed kernels against vendor-fixed builds or referenced stable commits.
  • Verify patched systems have rebooted into the updated kernel.
  • Monitor vendor advisories for corrected affected-version ranges.
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-50766 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
0Timeline events
0ADP providers
5Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxbc877d285ca3dba24c52406946a4a69847cc7422, bc877d285ca3dba24c52406946a4a69847cc7422, bc877d285ca3dba24c52406946a4a69847cc7422, bc877d285ca3dba24c52406946a4a69847cc7422unaffected
LinuxLinux4.19, 0, 5.15.75, 5.19.17, 6.0.3, 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.