{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2022-50715 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2022-50715 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-50715 and fix it if it is affected.\n\nWhat it is: CVE-2022-50715 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-50715 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-50715/ (Markdown: https://insights.sbomify.com/CVE-2022-50715/index.md)","id":"CVE-2022-50715","markdown":"https://insights.sbomify.com/CVE-2022-50715/index.md","name":"CVE-2022-50715","record":{"aliases":["DEBIAN-CVE-2022-50715","GHSA-rrpf-vhv2-qw86","UBUNTU-CVE-2022-50715"],"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":"high_privilege","summary":"A local attacker with high privileges can cause a kernel crash during system shutdown by triggering a null pointer dereference in the RAID1 subsystem.","user_interaction":"not_required","vuln_class":"null_dereference"},"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\nmd/raid1: stop mdx_raid1 thread when raid1 array run failed\n\nfail run raid1 array when we assemble array with the inactive disk only,\nbut the mdx_raid1 thread were not stop, Even if the associated resources\nhave been released. it will caused a NULL dereference when we do poweroff.\n\nThis causes the following Oops:\n    [  287.587787] BUG: kernel NULL pointer dereference, address: 0000000000000070\n    [  287.594762] #PF: supervisor read access in kernel mode\n    [  287.599912] #PF: error_code(0x0000) - not-present page\n    [  287.605061] PGD 0 P4D 0\n    [  287.607612] Oops: 0000 [#1] SMP NOPTI\n    [  287.611287] CPU: 3 PID: 5265 Comm: md0_raid1 Tainted: G     U            5.10.146 #0\n    [  287.619029] Hardware name: xxxxxxx/To be filled by O.E.M, BIOS 5.19 06/16/2022\n    [  287.626775] RIP: 0010:md_check_recovery+0x57/0x500 [md_mod]\n    [  287.632357] Code: fe 01 00 00 48 83 bb 10 03 00 00 00 74 08 48 89 ......\n    [  287.651118] RSP: 0018:ffffc90000433d78 EFLAGS: 00010202\n    [  287.656347] RAX: 0000000000000000 RBX: ffff888105986800 RCX: 0000000000000000\n    [  287.663491] RDX: ffffc90000433bb0 RSI: 00000000ffffefff RDI: ffff888105986800\n    [  287.670634] RBP: ffffc90000433da0 R08: 0000000000000000 R09: c0000000ffffefff\n    [  287.677771] R10: 0000000000000001 R11: ffffc90000433ba8 R12: ffff888105986800\n    [  287.684907] R13: 0000000000000000 R14: fffffffffffffe00 R15: ffff888100b6b500\n    [  287.692052] FS:  0000000000000000(0000) GS:ffff888277f80000(0000) knlGS:0000000000000000\n    [  287.700149] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n    [  287.705897] CR2: 0000000000000070 CR3: 000000000320a000 CR4: 0000000000350ee0\n    [  287.713033] Call Trace:\n    [  287.715498]  raid1d+0x6c/0xbbb [raid1]\n    [  287.719256]  ? __schedule+0x1ff/0x760\n    [  287.722930]  ? schedule+0x3b/0xb0\n    [  287.726260]  ? schedule_timeout+0x1ed/0x290\n    [  287.730456]  ? __switch_to+0x11f/0x400\n    [  287.734219]  md_thread+0xe9/0x140 [md_mod]\n    [  287.738328]  ? md_thread+0xe9/0x140 [md_mod]\n    [  287.742601]  ? wait_woken+0x80/0x80\n    [  287.746097]  ? md_register_thread+0xe0/0xe0 [md_mod]\n    [  287.751064]  kthread+0x11a/0x140\n    [  287.754300]  ? kthread_park+0x90/0x90\n    [  287.757974]  ret_from_fork+0x1f/0x30\n\nIn fact, when raid1 array run fail, we need to do\nmd_unregister_thread() before raid1_free().","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":"md/raid1: stop mdx_raid1 thread when raid1 array run failed","id":"CVE-2022-50715","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2022"},"n_packages":0,"n_references":9,"next":{"headline":"wifi: ar5523: Fix use-after-free on ar5523_cmd() timed out","id":"CVE-2022-50716"},"packages":[],"prev":{"headline":"wifi: mt76: mt7921e: fix rmmod crash in driver reload test","id":"CVE-2022-50714"},"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-23","vendors":["Linux"]},"summary":"A local attacker with high privileges can cause a kernel crash during system shutdown by triggering a null pointer dereference in the RAID1 subsystem.","url":"https://insights.sbomify.com/CVE-2022-50715/"}