CVE-2025-40358
Description
In the Linux kernel, the following vulnerability has been resolved:
riscv: stacktrace: Disable KASAN checks for non-current tasks
Unwinding the stack of a task other than current, KASAN would report "BUG: KASAN: out-of-bounds in walk_stackframe+0x41c/0x460"
There is a same issue on x86 and has been resolved by the commit 84936118bdf3 ("x86/unwind: Disable KASAN checks for non-current tasks") The solution could be applied to RISC-V too.
This patch also can solve the issue: https://seclists.org/oss-sec/2025/q4/23
[pjw@kernel.org: clean up checkpatch issues]
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
In the Linux kernel, a KASAN out-of-bounds error occurs when unwinding the stack of a non-current task's stack on RISC-V, fixed by disabling KASAN checks for such tasks.
Vulnerability
In the Linux kernel, when unwinding the stack of a task other than the current one on RISC-V, KASAN (Kernel Address Sanitizer) incorrectly reports a "BUG: KASAN: out-of-bounds in walk_stackframe+0x41c/0x460". This is a false positive caused by KASAN checking memory accesses that are actually valid for non-current tasks. The same issue was previously resolved on x86 by commit 84936118bdf3 ("x86/unwind: Disable KASAN checks for non-current tasks").
Exploitation
This vulnerability is triggered during stack unwinding operations for tasks that are not currently running. An attacker would need to be able to trigger such an unwinding, which typically requires local access or the ability to influence kernel stack tracing. No special privileges are required beyond those needed to initiate stack unwinding for another task.
Impact
The impact is a kernel panic or system crash due to the KASAN false positive, leading to a denial of service. The out-of-bounds report is spurious and does not represent an actual memory safety violation, but it can disrupt system operation.
Mitigation
The fix disables KASAN checks for non-current tasks during stack unwinding on RISC-V, mirroring the x86 solution applied to x86. The patch has been applied to the Linux kernel stable tree [1][2]. Users should update to a kernel version containing this fix.
AI Insight generated on May 19, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.
Affected products
2Patches
5ef4d626ac59af34ba22989da27379fcc15a12c8d2b53866f060ea84a484eVulnerability mechanics
Generated on May 9, 2026. Inputs: CWE entries + fix-commit diffs from this CVE's patches. Citations validated against bundle.
References
5- git.kernel.org/stable/c/060ea84a484e852b52b938f234bf9b5503a6c910nvd
- git.kernel.org/stable/c/27379fcc15a10d3e3780fe79ba3fc7ed1ccd78e2nvd
- git.kernel.org/stable/c/2c8d2b53866fb229b438296526ef0fa5a990e5e5nvd
- git.kernel.org/stable/c/ef4d626ac59a56f8ec5cc09c1fef26f2923eec6fnvd
- git.kernel.org/stable/c/f34ba22989da61186f30a40b6a82e0b3337b96fcnvd
News mentions
0No linked articles in our index yet.