<?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>Wed, 30 Sep 2026 12:31:12 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-68751 — s390/fpu: Fix false-positive kmsan report in fpu_vstl()</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2025-68751</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;s390/fpu: Fix false-positive kmsan report in fpu_vstl()&lt;/p&gt;
&lt;p&gt;A false-positive kmsan report is detected when running ping command.&lt;/p&gt;
&lt;p&gt;An inline assembly instruction &amp;#39;vstl&amp;#39; can write varied amount of bytes
depending on value of &amp;#39;index&amp;#39; argument. If &amp;#39;index&amp;#39; &amp;gt; 0, &amp;#39;vstl&amp;#39; writes
at least 2 bytes.&lt;/p&gt;
&lt;p&gt;clang generates kmsan write helper call depending on inline assembly
constraints. Constraints are evaluated compile-time, but value of
&amp;#39;index&amp;#39; argument is known only at runtime.&lt;/p&gt;
&lt;p&gt;clang currently generates call to __msan_instrument_asm_store with 1 byte
as size. Manually call kmsan function to indicate correct amount of bytes
written and fix false-positive report.&lt;/p&gt;
&lt;p&gt;This change fixes following kmsan reports:&lt;/p&gt;
&lt;p&gt;[   36.563119] =====================================================
[   36.563594] BUG: KMSAN: uninit-value in virtqueue_add+0x35c6/0x7c70
[   36.563852]  virtqueue_add+0x35c6/0x7c70
[   36.564016]  virtqueue_add_outbuf+0xa0/0xb0
[   36.564266]  start_xmit+0x288c/0x4a20
[   36.564460]  dev_hard_start_xmit+0x302/0x900
[   36.564649]  sch_direct_xmit+0x340/0xea0
[   36.564894]  __dev_queue_xmit+0x2e94/0x59b0
[   36.565058]  neigh_resolve_output+0x936/0xb40
[   36.565278]  __neigh_update+0x2f66/0x3a60
[   36.565499]  neigh_update+0x52/0x60
[   36.565683]  arp_process+0x1588/0x2de0
[   36.565916]  NF_HOOK+0x1da/0x240
[   36.566087]  arp_rcv+0x3e4/0x6e0
[   36.566306]  __netif_receive_skb_list_core+0x1374/0x15a0
[   36.566527]…&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;s390/fpu: Fix false-positive kmsan report in fpu_vstl()&lt;/p&gt;
&lt;p&gt;A false-positive kmsan report is detected when running ping command.&lt;/p&gt;
&lt;p&gt;An inline assembly instruction &amp;#39;vstl&amp;#39; can write varied amount of bytes
depending on value of &amp;#39;index&amp;#39; argument. If &amp;#39;index&amp;#39; &amp;gt; 0, &amp;#39;vstl&amp;#39; writes
at least 2 bytes.&lt;/p&gt;
&lt;p&gt;clang generates kmsan write helper call depending on inline assembly
constraints. Constraints are evaluated compile-time, but value of
&amp;#39;index&amp;#39; argument is known only at runtime.&lt;/p&gt;
&lt;p&gt;clang currently generates call to __msan_instrument_asm_store with 1 byte
as size. Manually call kmsan function to indicate correct amount of bytes
written and fix false-positive report.&lt;/p&gt;
&lt;p&gt;This change fixes following kmsan reports:&lt;/p&gt;
&lt;p&gt;[   36.563119] =====================================================
[   36.563594] BUG: KMSAN: uninit-value in virtqueue_add+0x35c6/0x7c70
[   36.563852]  virtqueue_add+0x35c6/0x7c70
[   36.564016]  virtqueue_add_outbuf+0xa0/0xb0
[   36.564266]  start_xmit+0x288c/0x4a20
[   36.564460]  dev_hard_start_xmit+0x302/0x900
[   36.564649]  sch_direct_xmit+0x340/0xea0
[   36.564894]  __dev_queue_xmit+0x2e94/0x59b0
[   36.565058]  neigh_resolve_output+0x936/0xb40
[   36.565278]  __neigh_update+0x2f66/0x3a60
[   36.565499]  neigh_update+0x52/0x60
[   36.565683]  arp_process+0x1588/0x2de0
[   36.565916]  NF_HOOK+0x1da/0x240
[   36.566087]  arp_rcv+0x3e4/0x6e0
[   36.566306]  __netif_receive_skb_list_core+0x1374/0x15a0
[   36.566527]…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2025-68751</guid>
    </item>
  </channel>
</rss>
