{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2022-50674 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2022-50674 is a vulnerability in Linux, published on 9 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-50674 and fix it if it is affected.\n\nWhat it is: CVE-2022-50674 is a vulnerability in Linux, published on 9 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-50674 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-50674/ (Markdown: https://insights.sbomify.com/CVE-2022-50674/index.md)","id":"CVE-2022-50674","markdown":"https://insights.sbomify.com/CVE-2022-50674/index.md","name":"CVE-2022-50674","record":{"aliases":["DEBIAN-CVE-2022-50674","GHSA-5mq2-5w2q-8jxg","UBUNTU-CVE-2022-50674"],"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":"low_privilege","summary":"A local attacker can trigger a kernel crash via a NULL pointer dereference in the RISC-V vdso implementation during vfork operations.","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\nriscv: vdso: fix NULL deference in vdso_join_timens() when vfork\n\nTesting tools/testing/selftests/timens/vfork_exec.c got below\nkernel log:\n\n[    6.838454] Unable to handle kernel access to user memory without uaccess routines at virtual address 0000000000000020\n[    6.842255] Oops [#1]\n[    6.842871] Modules linked in:\n[    6.844249] CPU: 1 PID: 64 Comm: vfork_exec Not tainted 6.0.0-rc3-rt15+ #8\n[    6.845861] Hardware name: riscv-virtio,qemu (DT)\n[    6.848009] epc : vdso_join_timens+0xd2/0x110\n[    6.850097]  ra : vdso_join_timens+0xd2/0x110\n[    6.851164] epc : ffffffff8000635c ra : ffffffff8000635c sp : ff6000000181fbf0\n[    6.852562]  gp : ffffffff80cff648 tp : ff60000000fdb700 t0 : 3030303030303030\n[    6.853852]  t1 : 0000000000000030 t2 : 3030303030303030 s0 : ff6000000181fc40\n[    6.854984]  s1 : ff60000001e6c000 a0 : 0000000000000010 a1 : ffffffff8005654c\n[    6.856221]  a2 : 00000000ffffefff a3 : 0000000000000000 a4 : 0000000000000000\n[    6.858114]  a5 : 0000000000000000 a6 : 0000000000000008 a7 : 0000000000000038\n[    6.859484]  s2 : ff60000001e6c068 s3 : ff6000000108abb0 s4 : 0000000000000000\n[    6.860751]  s5 : 0000000000001000 s6 : ffffffff8089dc40 s7 : ffffffff8089dc38\n[    6.862029]  s8 : ffffffff8089dc30 s9 : ff60000000fdbe38 s10: 000000000000005e\n[    6.863304]  s11: ffffffff80cc3510 t3 : ffffffff80d1112f t4 : ffffffff80d1112f\n[    6.864565]  t5 : ffffffff80d11130 t6 : ff6000000181fa00\n[    6.865561] status: 0000000000000120 badaddr: 0000000000000020 cause: 000000000000000d\n[    6.868046] [\u003cffffffff8008dc94\u003e] timens_commit+0x38/0x11a\n[    6.869089] [\u003cffffffff8008dde8\u003e] timens_on_fork+0x72/0xb4\n[    6.870055] [\u003cffffffff80190096\u003e] begin_new_exec+0x3c6/0x9f0\n[    6.871231] [\u003cffffffff801d826c\u003e] load_elf_binary+0x628/0x1214\n[    6.872304] [\u003cffffffff8018ee7a\u003e] bprm_execve+0x1f2/0x4e4\n[    6.873243] [\u003cffffffff8018f90c\u003e] do_execveat_common+0x16e/0x1ee\n[    6.874258] [\u003cffffffff8018f9c8\u003e] sys_execve+0x3c/0x48\n[    6.875162] [\u003cffffffff80003556\u003e] ret_from_syscall+0x0/0x2\n[    6.877484] ---[ end trace 0000000000000000 ]---\n\nThis is because the mm-\u003econtext.vdso_info is NULL in vfork case. From\nanother side, mm-\u003econtext.vdso_info either points to vdso info\nfor RV64 or vdso info for compat, there's no need to bloat riscv's\nmm_context_t, we can handle the difference when setup the additional\npage for vdso.","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":"riscv: vdso: fix NULL deference in vdso_join_timens() when vfork","id":"CVE-2022-50674","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2022"},"n_packages":0,"n_references":3,"next":{"headline":"arm64: mte: Avoid setting PG_mte_tagged if no tags cleared or restored","id":"CVE-2022-50675"},"packages":[],"prev":{"headline":"ext4: fix use-after-free in ext4_orphan_cleanup","id":"CVE-2022-50673"},"products":["Linux"],"published":"2025-12-09","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 trigger a kernel crash via a NULL pointer dereference in the RISC-V vdso implementation during vfork operations.","url":"https://insights.sbomify.com/CVE-2022-50674/"}