Vulnerability-Lookup

GHSA-QJQH-PMXV-4QMF

Vulnerability from github – Published: 2025-12-09 03:31 – Updated: 2025-12-09 03:31

Details

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] [ 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]

Fix this by using register_ftrace_function_nolock in ftrace_modify_direct_caller.

Show details on source website

JSON

To clipboard

{
  "affected": [],
  "aliases": [
    "CVE-2022-50648"
  ],
  "database_specific": {
    "cwe_ids": [],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2025-12-09T01:16:47Z",
    "severity": null
  },
  "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]  \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.",
  "id": "GHSA-qjqh-pmxv-4qmf",
  "modified": "2025-12-09T03:31:09Z",
  "published": "2025-12-09T03:31:09Z",
  "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"
    }
  ],
  "schema_version": "1.4.0",
  "severity": []
}

CVE-2022-50648 (GCVE-0-2022-50648)

Vulnerability from cvelistv5 – Published: 2025-12-09 00:00 – Updated: 2025-12-09 00:00

Title

ftrace: Fix recursive locking direct_mutex in ftrace_modify_direct_caller

Summary

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.

Severity ?

No CVSS data available.

Assigner

Linux

References

URL

Tags

	https://git.kernel.org/stable/c/2482eacb685b6500e…
	https://git.kernel.org/stable/c/9d2ce78ddcee159eb…

Impacted products

Vendor

Product

Version

Linux

Affected: 53cd885bc5c3ea283cc9c00ca6446c778f00bfba , < 2482eacb685b6500e158268befbe6c90de5f166a (git)
Affected: 53cd885bc5c3ea283cc9c00ca6446c778f00bfba , < 9d2ce78ddcee159eb6a97449e9c68b6d60b9cec4 (git)

Linux

Affected: 6.0
Unaffected: 0 , < 6.0 (semver)
Unaffected: 6.0.3 , ≤ 6.0.* (semver)
Unaffected: 6.1 , ≤ * (original_commit_for_fix)

Show details on NVD website

JSON

To clipboard

{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "kernel/trace/ftrace.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "2482eacb685b6500e158268befbe6c90de5f166a",
              "status": "affected",
              "version": "53cd885bc5c3ea283cc9c00ca6446c778f00bfba",
              "versionType": "git"
            },
            {
              "lessThan": "9d2ce78ddcee159eb6a97449e9c68b6d60b9cec4",
              "status": "affected",
              "version": "53cd885bc5c3ea283cc9c00ca6446c778f00bfba",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "kernel/trace/ftrace.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "6.0"
            },
            {
              "lessThan": "6.0",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.0.*",
              "status": "unaffected",
              "version": "6.0.3",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "6.1",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.0.3",
                  "versionStartIncluding": "6.0",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.1",
                  "versionStartIncluding": "6.0",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "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."
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2025-12-09T00:00:22.410Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/2482eacb685b6500e158268befbe6c90de5f166a"
        },
        {
          "url": "https://git.kernel.org/stable/c/9d2ce78ddcee159eb6a97449e9c68b6d60b9cec4"
        }
      ],
      "title": "ftrace: Fix recursive locking direct_mutex in ftrace_modify_direct_caller",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2022-50648",
    "datePublished": "2025-12-09T00:00:22.410Z",
    "dateReserved": "2025-12-08T23:57:43.371Z",
    "dateUpdated": "2025-12-09T00:00:22.410Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2"
}

Sightings

Author	Source	Type	Date

Nomenclature

Seen: The vulnerability was mentioned, discussed, or observed by the user.
Confirmed: The vulnerability has been validated from an analyst's perspective.
Published Proof of Concept: A public proof of concept is available for this vulnerability.
Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
Not confirmed: The user expressed doubt about the validity of the vulnerability.
Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.

Detection rules are retrieved from Rulezet.

Action not permitted

GHSA-QJQH-PMXV-4QMF

CVE-2022-50648 (GCVE-0-2022-50648)

Tags

Sightings

Nomenclature