{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2022-50648 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2022-50648 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-50648 and fix it if it is affected.\n\nWhat it is: CVE-2022-50648 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-50648 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-50648/ (Markdown: https://insights.sbomify.com/CVE-2022-50648/index.md)","id":"CVE-2022-50648","markdown":"https://insights.sbomify.com/CVE-2022-50648/index.md","name":"CVE-2022-50648","record":{"aliases":["DEBIAN-CVE-2022-50648","GHSA-qjqh-pmxv-4qmf","UBUNTU-CVE-2022-50648"],"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 recursive locking bug in the Linux kernel ftrace subsystem can cause a deadlock, leading to a local denial of service.","user_interaction":"not_required","vuln_class":"race_condition"},"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\nftrace: Fix recursive locking direct_mutex in ftrace_modify_direct_caller\n\nNaveen reported recursive locking of direct_mutex with sample\nftrace-direct-modify.ko:\n\n[   74.762406] WARNING: possible recursive locking detected\n[   74.762887] 6.0.0-rc6+ #33 Not tainted\n[   74.763216] --------------------------------------------\n[   74.763672] event-sample-fn/1084 is trying to acquire lock:\n[   74.764152] ffffffff86c9d6b0 (direct_mutex){+.+.}-{3:3}, at: \\\n    register_ftrace_function+0x1f/0x180\n[   74.764922]\n[   74.764922] but task is already holding lock:\n[   74.765421] ffffffff86c9d6b0 (direct_mutex){+.+.}-{3:3}, at: \\\n    modify_ftrace_direct+0x34/0x1f0\n[   74.766142]\n[   74.766142] other info that might help us debug this:\n[   74.766701]  Possible unsafe locking scenario:\n[   74.766701]\n[   74.767216]        CPU0\n[   74.767437]        ----\n[   74.767656]   lock(direct_mutex);\n[   74.767952]   lock(direct_mutex);\n[   74.768245]\n[   74.768245]  *** DEADLOCK ***\n[   74.768245]\n[   74.768750]  May be due to missing lock nesting notation\n[   74.768750]\n[   74.769332] 1 lock held by event-sample-fn/1084:\n[   74.769731]  #0: ffffffff86c9d6b0 (direct_mutex){+.+.}-{3:3}, at: \\\n    modify_ftrace_direct+0x34/0x1f0\n[   74.770496]\n[   74.770496] stack backtrace:\n[   74.770884] CPU: 4 PID: 1084 Comm: event-sample-fn Not tainted ...\n[   74.771498] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), ...\n[   74.772474] Call Trace:\n[   74.772696]  \u003cTASK\u003e\n[   74.772896]  dump_stack_lvl+0x44/0x5b\n[   74.773223]  __lock_acquire.cold.74+0xac/0x2b7\n[   74.773616]  lock_acquire+0xd2/0x310\n[   74.773936]  ? register_ftrace_function+0x1f/0x180\n[   74.774357]  ? lock_is_held_type+0xd8/0x130\n[   74.774744]  ? my_tramp2+0x11/0x11 [ftrace_direct_modify]\n[   74.775213]  __mutex_lock+0x99/0x1010\n[   74.775536]  ? register_ftrace_function+0x1f/0x180\n[   74.775954]  ? slab_free_freelist_hook.isra.43+0x115/0x160\n[   74.776424]  ? ftrace_set_hash+0x195/0x220\n[   74.776779]  ? register_ftrace_function+0x1f/0x180\n[   74.777194]  ? kfree+0x3e1/0x440\n[   74.777482]  ? my_tramp2+0x11/0x11 [ftrace_direct_modify]\n[   74.777941]  ? __schedule+0xb40/0xb40\n[   74.778258]  ? register_ftrace_function+0x1f/0x180\n[   74.778672]  ? my_tramp1+0xf/0xf [ftrace_direct_modify]\n[   74.779128]  register_ftrace_function+0x1f/0x180\n[   74.779527]  ? ftrace_set_filter_ip+0x33/0x70\n[   74.779910]  ? __schedule+0xb40/0xb40\n[   74.780231]  ? my_tramp1+0xf/0xf [ftrace_direct_modify]\n[   74.780678]  ? my_tramp2+0x11/0x11 [ftrace_direct_modify]\n[   74.781147]  ftrace_modify_direct_caller+0x5b/0x90\n[   74.781563]  ? 0xffffffffa0201000\n[   74.781859]  ? my_tramp1+0xf/0xf [ftrace_direct_modify]\n[   74.782309]  modify_ftrace_direct+0x1b2/0x1f0\n[   74.782690]  ? __schedule+0xb40/0xb40\n[   74.783014]  ? simple_thread+0x2a/0xb0 [ftrace_direct_modify]\n[   74.783508]  ? __schedule+0xb40/0xb40\n[   74.783832]  ? my_tramp2+0x11/0x11 [ftrace_direct_modify]\n[   74.784294]  simple_thread+0x76/0xb0 [ftrace_direct_modify]\n[   74.784766]  kthread+0xf5/0x120\n[   74.785052]  ? kthread_complete_and_exit+0x20/0x20\n[   74.785464]  ret_from_fork+0x22/0x30\n[   74.785781]  \u003c/TASK\u003e\n\nFix this by using register_ftrace_function_nolock in\nftrace_modify_direct_caller.","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":"ftrace: Fix recursive locking direct_mutex in ftrace_modify_direct_caller","id":"CVE-2022-50648","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"race_condition","year":"2022"},"n_packages":0,"n_references":2,"next":{"headline":"power: supply: adp5061: fix out-of-bounds read in adp5061_get_chg_type()","id":"CVE-2022-50649"},"packages":[],"prev":{"headline":"RISC-V: Make port I/O string accessors actually work","id":"CVE-2022-50647"},"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 recursive locking bug in the Linux kernel ftrace subsystem can cause a deadlock, leading to a local denial of service.","url":"https://insights.sbomify.com/CVE-2022-50648/"}