{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2022-50766 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2022-50766 is a vulnerability in Linux, published on 24 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-50766 and fix it if it is affected.\n\nWhat it is: CVE-2022-50766 is a vulnerability in Linux, published on 24 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2022-50766 in the wild and no public exploit code.\n\nAffected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2022-50766/ (Markdown: https://insights.sbomify.com/CVE-2022-50766/index.md)","id":"CVE-2022-50766","markdown":"https://insights.sbomify.com/CVE-2022-50766/index.md","name":"CVE-2022-50766","record":{"aliases":["DEBIAN-CVE-2022-50766","GHSA-65xq-q38h-gcrc","ROOT-OS-DEBIAN-11-CVE-2022-50766","UBUNTU-CVE-2022-50766"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel","requires_auth":"none","summary":"A local attacker can read uninitialized kernel memory via a race condition in the Btrfs filesystem, potentially exposing sensitive data.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nbtrfs: set generation before calling btrfs_clean_tree_block in btrfs_init_new_buffer\n\nsyzbot is reporting uninit-value in btrfs_clean_tree_block() [1], for\ncommit bc877d285ca3dba2 (\"btrfs: Deduplicate extent_buffer init code\")\nmissed that btrfs_set_header_generation() in btrfs_init_new_buffer() must\nnot be moved to after clean_tree_block() because clean_tree_block() is\ncalling btrfs_header_generation() since commit 55c69072d6bd5be1 (\"Btrfs:\nFix extent_buffer usage when nodesize != leafsize\").\n\nSince memzero_extent_buffer() will reset \"struct btrfs_header\" part, we\ncan't move btrfs_set_header_generation() to before memzero_extent_buffer().\nJust re-add btrfs_set_header_generation() before btrfs_clean_tree_block().","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"btrfs: set generation before calling btrfs_clean_tree_block in btrfs_init_new_buffer","id":"CVE-2022-50766","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2022"},"n_packages":0,"n_references":4,"next":{"headline":"fbdev: smscufx: Fix several use-after-free bugs","id":"CVE-2022-50767"},"packages":[],"prev":{"headline":"RISC-V: kexec: Fix memory leak of elf header buffer","id":"CVE-2022-50765"},"products":["Linux"],"published":"2025-12-24","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-05-11","vendors":["Linux"]},"summary":"A local attacker can read uninitialized kernel memory via a race condition in the Btrfs filesystem, potentially exposing sensitive data.","url":"https://insights.sbomify.com/CVE-2022-50766/"}