<?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://vulnerability.circl.lu</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>Tue, 29 Sep 2026 03:44:05 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-90195 — riscv, bpf: Fix missing sign-ext for signed 1-byte and 2-byte kfunc args</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-90195</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, bpf: Fix missing sign-ext for signed 1-byte and 2-byte kfunc args&lt;/p&gt;
&lt;p&gt;On RV64, the ABI requires sign-extension for signed 1-byte and 2-byte kfunc
args. However, the RV64 JIT currently does not perform sign-extension for
such kfunc args.&lt;/p&gt;
&lt;p&gt;Before commit 7ce090afbf72 (&amp;#34;bpf: Infer zext_dst based on static register
liveness analysis&amp;#34;), state pruning could potentially omit zero-extension
of 32-bit subregisters, which inadvertently masked the above issue by making
the args appear as if they had been properly sign-extended. After that
commit, the problem is exposed, causing the kfunc_call/kfunc_call_test4
selftest to fail.&lt;/p&gt;
&lt;p&gt;Fix this by extending the existing sign-extension logic to handle signed
1-byte and 2-byte kfunc args as well.&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, bpf: Fix missing sign-ext for signed 1-byte and 2-byte kfunc args&lt;/p&gt;
&lt;p&gt;On RV64, the ABI requires sign-extension for signed 1-byte and 2-byte kfunc
args. However, the RV64 JIT currently does not perform sign-extension for
such kfunc args.&lt;/p&gt;
&lt;p&gt;Before commit 7ce090afbf72 (&amp;#34;bpf: Infer zext_dst based on static register
liveness analysis&amp;#34;), state pruning could potentially omit zero-extension
of 32-bit subregisters, which inadvertently masked the above issue by making
the args appear as if they had been properly sign-extended. After that
commit, the problem is exposed, causing the kfunc_call/kfunc_call_test4
selftest to fail.&lt;/p&gt;
&lt;p&gt;Fix this by extending the existing sign-extension logic to handle signed
1-byte and 2-byte kfunc args as well.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-90195</guid>
    </item>
  </channel>
</rss>
