{
  "cveId": "CVE-2025-22069",
  "url": "https://patchblox.com/security/cve/CVE-2025-22069",
  "summary": "CVE-2025-22069 is fixed in linux on 1 platform by DEBIAN-CVE-2025-22069 (version 6.12.94-1), released April 16, 2025. It is not reported as exploited. Patch Radar priority: High.",
  "title": "linux: In the Linux kernel, the following vulnerability has been resolved:  riscv: fgraph: Fix stack layout to match __arch_...",
  "description": "In the Linux kernel, the following vulnerability has been resolved:  riscv: fgraph: Fix stack layout to match __arch_ftrace_regs argument of ftrace_return_to_handler  Naresh Kamboju reported a \u0022Bad frame pointer\u0022 kernel warning while running LTP trace ftrace_stress_test.sh in riscv. We can reproduce the same issue with the following command:  \u0060\u0060\u0060 $ cd /sys/kernel/debug/tracing $ echo \u0027f:myprobe do_nanosleep%return args1=$retval\u0027 \u003E dynamic_events $ echo 1 \u003E events/fprobes/enable $ echo 1 \u003E tracing_on $ sleep 1 \u0060\u0060\u0060  And we can get the following kernel warning:  [  127.692888] ------------[ cut here ]------------ [  127.693755] Bad frame pointer: expected ff2000000065be50, received ba34c141e9594000 [  127.693755]   from func do_nanosleep return to ffffffff800ccb16 [  127.698699] WARNING: CPU: 1 PID: 129 at kernel/trace/fgraph.c:755 ftrace_return_to_handler\u002B0x1b2/0x1be [  127.699894] Modules linked in: [  127.700908] CPU: 1 UID: 0 PID: 129 Comm: sleep Not tainted 6.14.0-rc3-g0ab191c74642 #32 [  127.701453] Hardware name: riscv-virtio,qemu (DT) [  127.701859] epc : ftrace_return_to_handler\u002B0x1b2/0x1be [  127.702032]  ra : ftrace_return_to_handler\u002B0x1b2/0x1be [  127.702151] epc : ffffffff8013b5e0 ra : ffffffff8013b5e0 sp : ff2000000065bd10 [  127.702221]  gp : ffffffff819c12f8 tp : ff60000080853100 t0 : 6e00000000000000 [  127.702284]  t1 : 0000000000000020 t2 : 6e7566206d6f7266 s0 : ff2000000065bd80 [  127.702346]  s1 : ff60000081262000 a0 : 000000000000007b a1 : ffffffff81894f20 [  127.702408]  a2 : 0000000000000010 a3 : fffffffffffffffe a4 : 0000000000000000 [  127.702470]  a5 : 0000000000000000 a6 : 0000000000000008 a7 : 0000000000000038 [  127.702530]  s2 : ba34c141e9594000 s3 : 0000000000000000 s4 : ff2000000065bdd0 [  127.702591]  s5 : 00007fff8adcf400 s6 : 000055556dc1d8c0 s7 : 0000000000000068 [  127.702651]  s8 : 00007fff8adf5d10 s9 : 000000000000006d s10: 0000000000000001 [  127.702710]  s11: 00005555737377c8 t3 : ffffffff819d899e t4 : ffffffff819d899e [  127.702769]  t5 : ffffffff819d89a0 t6 : ff2000000065bb18 [  127.702826] status: 0000000200000120 badaddr: 0000000000000000 cause: 0000000000000003 [  127.703292] [\u003Cffffffff8013b5e0\u003E] ftrace_return_to_handler\u002B0x1b2/0x1be [  127.703760] [\u003Cffffffff80017bce\u003E] return_to_handler\u002B0x16/0x26 [  127.704009] [\u003Cffffffff80017bb8\u003E] return_to_handler\u002B0x0/0x26 [  127.704057] [\u003Cffffffff800d3352\u003E] common_nsleep\u002B0x42/0x54 [  127.704117] [\u003Cffffffff800d44a2\u003E] __riscv_sys_clock_nanosleep\u002B0xba/0x10a [  127.704176] [\u003Cffffffff80901c56\u003E] do_trap_ecall_u\u002B0x188/0x218 [  127.704295] [\u003Cffffffff8090cc3e\u003E] handle_exception\u002B0x14a/0x156 [  127.705436] ---[ end trace 0000000000000000 ]---  The reason is that the stack layout for constructing argument for the ftrace_return_to_handler in the return_to_handler does not match the __arch_ftrace_regs structure of riscv, leading to unexpected results.",
  "published": "2025-04-16T15:16:01Z",
  "severity": "high",
  "cvss": 7.8,
  "cvssVector": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
  "epss": 0.00212,
  "epssPercentile": 0.11528,
  "priority": "High",
  "priorityTier": 3,
  "exploited": false,
  "vendorExploited": false,
  "disclosed": false,
  "fixes": [
    {
      "platform": "linux",
      "product": "linux",
      "release": "Debian 13.5 (trixie)",
      "fixedVersion": "6.12.94-1",
      "fix": "DEBIAN-CVE-2025-22069",
      "url": "https://patchblox.com/security/fix/linux/debian-cve-2025-22069",
      "released": "2025-04-16T15:16:01Z"
    }
  ],
  "noFixYet": [],
  "dataAsOf": "2026-11-08T13:06:02Z",
  "attribution": {
    "text": "Data: Patchblox Patch Radar",
    "url": "https://patchblox.com/security/patch-radar",
    "terms": "https://patchblox.com/security/patch-radar/use-the-data"
  }
}