[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025121629-CVE-2025-68173-788c@gregkh>
Date: Tue, 16 Dec 2025 14:43:34 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2025-68173: ftrace: Fix softlockup in ftrace_module_enable
From: Greg Kroah-Hartman <gregkh@...nel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
ftrace: Fix softlockup in ftrace_module_enable
A soft lockup was observed when loading amdgpu module.
If a module has a lot of tracable functions, multiple calls
to kallsyms_lookup can spend too much time in RCU critical
section and with disabled preemption, causing kernel panic.
This is the same issue that was fixed in
commit d0b24b4e91fc ("ftrace: Prevent RCU stall on PREEMPT_VOLUNTARY
kernels") and commit 42ea22e754ba ("ftrace: Add cond_resched() to
ftrace_graph_set_hash()").
Fix it the same way by adding cond_resched() in ftrace_module_enable.
The Linux kernel CVE team has assigned CVE-2025-68173 to this issue.
Affected and fixed versions
===========================
Fixed in 6.1.159 with commit a1dd0abd741a8111260676da729825d6c1461a71
Fixed in 6.6.117 with commit e81e6d6d99b16dae11adbeda5c996317942a940c
Fixed in 6.12.58 with commit 40c8ee40e48a2c82c762539952ed8fc0571db5bf
Fixed in 6.17.8 with commit 7e3c96010ade29bb340a5bdce8675f50c7f59001
Fixed in 6.18 with commit 4099b98203d6b33d990586542fa5beee408032a3
Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.
Unaffected versions might change over time as fixes are backported to
older supported kernel versions. The official CVE entry at
https://cve.org/CVERecord/?id=CVE-2025-68173
will be updated if fixes are backported, please check that for the most
up to date information about this issue.
Affected files
==============
The file(s) affected by this issue are:
kernel/trace/ftrace.c
Mitigation
==========
The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes. Individual
changes are never tested alone, but rather are part of a larger kernel
release. Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all. If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
https://git.kernel.org/stable/c/a1dd0abd741a8111260676da729825d6c1461a71
https://git.kernel.org/stable/c/e81e6d6d99b16dae11adbeda5c996317942a940c
https://git.kernel.org/stable/c/40c8ee40e48a2c82c762539952ed8fc0571db5bf
https://git.kernel.org/stable/c/7e3c96010ade29bb340a5bdce8675f50c7f59001
https://git.kernel.org/stable/c/4099b98203d6b33d990586542fa5beee408032a3
Powered by blists - more mailing lists