<?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:49:54 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-89459 — s390/percpu: Fix MVIY_PERCPU() with older binutils</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-89459</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/percpu: Fix MVIY_PERCPU() with older binutils&lt;/p&gt;
&lt;p&gt;Commit a737737cdb9c (&amp;#34;s390/percpu: Infrastructure for more efficient
this_cpu operations&amp;#34;) introduced MVIY_PERCPU(), which stringifies
arguments that are already C string literals. This generates an
assembler macro invocation with whitespace-separated quoted arguments:&lt;/p&gt;
&lt;p&gt;GEN_MVIY &amp;#34;459712&amp;#34; &amp;#34;%r3&amp;#34;&lt;/p&gt;
&lt;p&gt;GNU as versions prior to binutils 2.39 drop the separating whitespace
between quoted macro arguments during input scrubbing. They
consequently parse the invocation as a single argument and emit
repeated warnings:&lt;/p&gt;
&lt;p&gt;Warning: missing closing `&amp;#34;&amp;#39;&lt;/p&gt;
&lt;p&gt;The .ifc in GEN_MVIY never matches and GNU as exits successfully
without emitting the mviy instruction. As a result, the interrupted
per-CPU sequence is not marked in lowcore and the exception return
path cannot repair the per-CPU address register after migration.&lt;/p&gt;
&lt;p&gt;All MVIY_PERCPU() callers pass C string literals. Use them directly
and separate the assembler macro arguments with an explicit comma. The
resulting invocation is:&lt;/p&gt;
&lt;p&gt;GEN_MVIY 459712, %r3&lt;/p&gt;
&lt;p&gt;This form is unambiguous for GNU as and LLVM&amp;#39;s integrated assembler.
This behavior was fixed in GNU as from binutils 2.39, but Linux
supports binutils 2.30.&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/percpu: Fix MVIY_PERCPU() with older binutils&lt;/p&gt;
&lt;p&gt;Commit a737737cdb9c (&amp;#34;s390/percpu: Infrastructure for more efficient
this_cpu operations&amp;#34;) introduced MVIY_PERCPU(), which stringifies
arguments that are already C string literals. This generates an
assembler macro invocation with whitespace-separated quoted arguments:&lt;/p&gt;
&lt;p&gt;GEN_MVIY &amp;#34;459712&amp;#34; &amp;#34;%r3&amp;#34;&lt;/p&gt;
&lt;p&gt;GNU as versions prior to binutils 2.39 drop the separating whitespace
between quoted macro arguments during input scrubbing. They
consequently parse the invocation as a single argument and emit
repeated warnings:&lt;/p&gt;
&lt;p&gt;Warning: missing closing `&amp;#34;&amp;#39;&lt;/p&gt;
&lt;p&gt;The .ifc in GEN_MVIY never matches and GNU as exits successfully
without emitting the mviy instruction. As a result, the interrupted
per-CPU sequence is not marked in lowcore and the exception return
path cannot repair the per-CPU address register after migration.&lt;/p&gt;
&lt;p&gt;All MVIY_PERCPU() callers pass C string literals. Use them directly
and separate the assembler macro arguments with an explicit comma. The
resulting invocation is:&lt;/p&gt;
&lt;p&gt;GEN_MVIY 459712, %r3&lt;/p&gt;
&lt;p&gt;This form is unambiguous for GNU as and LLVM&amp;#39;s integrated assembler.
This behavior was fixed in GNU as from binutils 2.39, but Linux
supports binutils 2.30.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2026-89459</guid>
    </item>
  </channel>
</rss>
