{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2022-50864 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2022-50864 is a vulnerability in Linux, published on 30 Dec 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2022-50864 and fix it if it is affected.\n\nWhat it is: CVE-2022-50864 is a vulnerability in Linux, published on 30 Dec 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2022-50864 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-50864/ (Markdown: https://insights.sbomify.com/CVE-2022-50864/index.md)","id":"CVE-2022-50864","markdown":"https://insights.sbomify.com/CVE-2022-50864/index.md","name":"CVE-2022-50864","record":{"aliases":["DEBIAN-CVE-2022-50864","GHSA-gfhq-qmg6-x4ch","UBUNTU-CVE-2022-50864"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel","requires_auth":"none","summary":"A local attacker can cause a kernel panic via a crafted nilfs2 filesystem image due to an integer overflow in block size handling.","user_interaction":"required","vuln_class":"integer_overflow"},"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\nnilfs2: fix shift-out-of-bounds due to too large exponent of block size\n\nIf field s_log_block_size of superblock data is corrupted and too large,\ninit_nilfs() and load_nilfs() still can trigger a shift-out-of-bounds\nwarning followed by a kernel panic (if panic_on_warn is set):\n\n shift exponent 38973 is too large for 32-bit type 'int'\n Call Trace:\n  \u003cTASK\u003e\n  dump_stack_lvl+0xcd/0x134\n  ubsan_epilogue+0xb/0x50\n  __ubsan_handle_shift_out_of_bounds.cold.12+0x17b/0x1f5\n  init_nilfs.cold.11+0x18/0x1d [nilfs2]\n  nilfs_mount+0x9b5/0x12b0 [nilfs2]\n  ...\n\nThis fixes the issue by adding and using a new helper function for getting\nblock size with sanity check.","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":"nilfs2: fix shift-out-of-bounds due to too large exponent of block size","id":"CVE-2022-50864","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"integer_overflow","year":"2022"},"n_packages":0,"n_references":5,"next":{"headline":"tcp: fix a signed-integer-overflow bug in tcp_add_backlog()","id":"CVE-2022-50865"},"packages":[],"prev":{"headline":"wifi: rtw89: free unused skb to prevent memory leak","id":"CVE-2022-50863"},"products":["Linux"],"published":"2025-12-30","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 cause a kernel panic via a crafted nilfs2 filesystem image due to an integer overflow in block size handling.","url":"https://insights.sbomify.com/CVE-2022-50864/"}