CVE-2022-50648: Software Security Vulnerability Vulnerability

UNKNOWN

Advisory Identifier: GHSA-qjqh-pmxv-4qmf

Published 2025-12-09

Advisory Summary

CVE-2022-50648 is a security vulnerability vulnerability (General Security Weakness) affecting Software libraries in the Maven ecosystem. Remediation is available in the latest vendor maintenance releases.

CVE-2022-50648 at a Glance

CVE Identifier CVE-2022-50648

GHSA Identifier GHSA-qjqh-pmxv-4qmf

Severity N/A

CVSS v3.1 Base Score N/A

CWE Classification General Security Weakness

Affected Product Software

Package Ecosystem Maven

Published Date 2025-12-09

Last Updated 2025-12-09

How to Fix CVE-2022-50648

To remediate this vulnerability, upgrade all affected Software dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

mvn dependency:tree

How to Check if You Are Affected

To determine whether your Java application is affected by CVE-2022-50648, inspect your build dependencies using the Maven Dependency Plugin:

mvn dependency:tree

Analyze the terminal output to locate any version of Software in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than the patched release), your application is affected.

Note: The mvn dependency:tree command inspects the resolved dependency graph declared in your project's POM files; it does not perform automated security scanning or inspect runtime dynamic classpaths. Always verify runtime container classpaths and shaded JARs.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under General Security Weakness. In Software, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

In the Linux kernel, the following vulnerability has been resolved: ftrace: Fix recursive locking direct_mutex in ftrace_modify_direct_caller Naveen reported recursive locking of direct_mutex with sample ftrace-direct-modify.ko: [ 74.762406] WARNING: possible recursive locking detected [ 74.762887] 6.0.0-rc6+ #33 Not tainted [ 74.763216] -------------------------------------------- [ 74.763672] event-sample-fn/1084 is trying to acquire lock: [ 74.764152] ffffffff86c9d6b0 (direct_mutex){+.+.}-{3:3}, at: \ register_ftrace_function+0x1f/0x180 [ 74.764922] [ 74.764922] but task is already holding lock: [ 74.765421] ffffffff86c9d6b0 (direct_mutex){+.+.}-{3:3}, at: \ modify_ftrace_direct+0x34/0x1f0 [ 74.766142] [ 74.766142] other info that might help us debug this: [ 74.766701] Possible unsafe locking scenario: [ 74.766701] [ 74.767216] CPU0 [ 74.767437] ---- [ 74.767656] lock(direct_mutex); [ 74.767952] lock(direct_mutex); [ 74.768245] [ 74.768245] *** DEADLOCK *** [ 74.768245] [ 74.768750] May be due to missing lock nesting notation [ 74.768750] [ 74.769332] 1 lock held by event-sample-fn/1084: [ 74.769731] #0: ffffffff86c9d6b0 (direct_mutex){+.+.}-{3:3}, at: \ modify_ftrace_direct+0x34/0x1f0 [ 74.770496] [ 74.770496] stack backtrace: [ 74.770884] CPU: 4 PID: 1084 Comm: event-sample-fn Not tainted ... [ 74.771498] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), ... [ 74.772474] Call Trace: [ 74.772696] <TASK> [ 74.772896] dump_stack_lvl+0x44/0x5b [ 74.773223] __lock_acquire.cold.74+0xac/0x2b7 [ 74.773616] lock_acquire+0xd2/0x310 [ 74.773936] ? register_ftrace_function+0x1f/0x180 [ 74.774357] ? lock_is_held_type+0xd8/0x130 [ 74.774744] ? my_tramp2+0x11/0x11 [ftrace_direct_modify] [ 74.775213] __mutex_lock+0x99/0x1010 [ 74.775536] ? register_ftrace_function+0x1f/0x180 [ 74.775954] ? slab_free_freelist_hook.isra.43+0x115/0x160 [ 74.776424] ? ftrace_set_hash+0x195/0x220 [ 74.776779] ? register_ftrace_function+0x1f/0x180 [ 74.777194] ? kfree+0x3e1/0x440 [ 74.777482] ? my_tramp2+0x11/0x11 [ftrace_direct_modify] [ 74.777941] ? __schedule+0xb40/0xb40 [ 74.778258] ? register_ftrace_function+0x1f/0x180 [ 74.778672] ? my_tramp1+0xf/0xf [ftrace_direct_modify] [ 74.779128] register_ftrace_function+0x1f/0x180 [ 74.779527] ? ftrace_set_filter_ip+0x33/0x70 [ 74.779910] ? __schedule+0xb40/0xb40 [ 74.780231] ? my_tramp1+0xf/0xf [ftrace_direct_modify] [ 74.780678] ? my_tramp2+0x11/0x11 [ftrace_direct_modify] [ 74.781147] ftrace_modify_direct_caller+0x5b/0x90 [ 74.781563] ? 0xffffffffa0201000 [ 74.781859] ? my_tramp1+0xf/0xf [ftrace_direct_modify] [ 74.782309] modify_ftrace_direct+0x1b2/0x1f0 [ 74.782690] ? __schedule+0xb40/0xb40 [ 74.783014] ? simple_thread+0x2a/0xb0 [ftrace_direct_modify] [ 74.783508] ? __schedule+0xb40/0xb40 [ 74.783832] ? my_tramp2+0x11/0x11 [ftrace_direct_modify] [ 74.784294] simple_thread+0x76/0xb0 [ftrace_direct_modify] [ 74.784766] kthread+0xf5/0x120 [ 74.785052] ? kthread_complete_and_exit+0x20/0x20 [ 74.785464] ret_from_fork+0x22/0x30 [ 74.785781] </TASK> Fix this by using register_ftrace_function_nolock in ftrace_modify_direct_caller.

References

NVD — CVE-2022-50648 NVD

https://nvd.nist.gov/vuln/detail/CVE-2022-50648

git.kernel.org/stable/c/2482eacb68... WEB

https://git.kernel.org/stable/c/2482eacb685b6500e158268befbe6c90de5f166a

git.kernel.org/stable/c/9d2ce78ddc... WEB

https://git.kernel.org/stable/c/9d2ce78ddcee159eb6a97449e9c68b6d60b9cec4

Frequently Asked Questions

What is CVE-2022-50648?

CVE-2022-50648 is a security vulnerability in Software classified as a security vulnerability vulnerability under General Security Weakness.

Which Software versions are affected?

Affected versions include releases prior to current release patches.

What version fixes CVE-2022-50648?

Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.

What CWE is associated with CVE-2022-50648?

CVE-2022-50648 is classified under General Security Weakness.

How can I check Maven dependencies for CVE-2022-50648?

Run the dependency tree command: 'mvn dependency:tree'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.

Machine-readable OSV JSON OSV v1.5 Schema

Normalized schema output

View Raw JSON

{
  "schema_version" : "1.4.0",
  "id" : "GHSA-qjqh-pmxv-4qmf",
  "modified" : "2025-12-09T03:31:09Z",
  "published" : "2025-12-09T03:31:09Z",
  "aliases" : [ "CVE-2022-50648" ],
  "details" : "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]  <TASK>\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]  </TASK>\n\nFix this by using register_ftrace_function_nolock in\nftrace_modify_direct_caller.",
  "severity" : [ ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2022-50648"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/2482eacb685b6500e158268befbe6c90de5f166a"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/9d2ce78ddcee159eb6a97449e9c68b6d60b9cec4"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : null,
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2025-12-09T01:16:47Z"
  }
}

Advisory Metadata

Source ID: GHSA-qjqh-pmxv-4qmf
Schema Version: 1.4.0
Published: 2025-12-09 03:31
Last Modified: 2025-12-09 03:31
Database Record File: advisories/unreviewed/2025/12/GHSA-qjqh-pmxv-4qmf/GHSA-qjqh-pmxv-4qmf.json