<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Mon, 05 Oct 2026 10:11:47 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-22069 — riscv: fgraph: Fix stack layout to match __arch_ftrace_regs argument of ftrace_return_to_handler</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2025-22069</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;riscv: fgraph: Fix stack layout to match __arch_ftrace_regs argument of ftrace_return_to_handler&lt;/p&gt;
&lt;p&gt;Naresh Kamboju reported a &amp;#34;Bad frame pointer&amp;#34; kernel warning while
running LTP trace ftrace_stress_test.sh in riscv. We can reproduce the
same issue with the following command:&lt;/p&gt;
&lt;p&gt;```
$ cd /sys/kernel/debug/tracing
$ echo &amp;#39;f:myprobe do_nanosleep%return args1=$retval&amp;#39; &amp;gt; dynamic_events
$ echo 1 &amp;gt; events/fprobes/enable
$ echo 1 &amp;gt; tracing_on
$ sleep 1
```&lt;/p&gt;
&lt;p&gt;And we can get the following kernel warning:&lt;/p&gt;
&lt;p&gt;[  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+0x1b2/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+0x1b2/0x1be
[  127.702032]  ra : ftrace_return_to_handler+0x1b2/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…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;riscv: fgraph: Fix stack layout to match __arch_ftrace_regs argument of ftrace_return_to_handler&lt;/p&gt;
&lt;p&gt;Naresh Kamboju reported a &amp;#34;Bad frame pointer&amp;#34; kernel warning while
running LTP trace ftrace_stress_test.sh in riscv. We can reproduce the
same issue with the following command:&lt;/p&gt;
&lt;p&gt;```
$ cd /sys/kernel/debug/tracing
$ echo &amp;#39;f:myprobe do_nanosleep%return args1=$retval&amp;#39; &amp;gt; dynamic_events
$ echo 1 &amp;gt; events/fprobes/enable
$ echo 1 &amp;gt; tracing_on
$ sleep 1
```&lt;/p&gt;
&lt;p&gt;And we can get the following kernel warning:&lt;/p&gt;
&lt;p&gt;[  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+0x1b2/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+0x1b2/0x1be
[  127.702032]  ra : ftrace_return_to_handler+0x1b2/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…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2025-22069</guid>
    </item>
  </channel>
</rss>
