<?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://db.gcve.eu</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, 10 Nov 2026 01:01:19 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-99186 — x86/insn-eval: Fix shadowed segment index in get_seg_reg_override_idx()</title>
      <link>https://db.gcve.eu/vuln/cve-2026-99186</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;x86/insn-eval: Fix shadowed segment index in get_seg_reg_override_idx()&lt;/p&gt;
&lt;p&gt;Commit 45e1dccc0653 (&amp;#34;x86/insn: Simplify for_each_insn_prefix()&amp;#34;) made
for_each_insn_prefix() declare its own loop counter named idx.
get_seg_reg_override_idx() keeps its result in a local of the same name,
so the assignments in the loop body now write the loop counter:&lt;/p&gt;
&lt;p&gt;- the function always returns INAT_SEG_REG_DEFAULT, so FS and GS
   overrides are ignored;&lt;/p&gt;
&lt;p&gt;- a CS override sets the counter to INAT_SEG_REG_CS (2), the increment
   makes it 3, and prefixes.bytes[3] holds the last prefix, 0x2e again,
   so the loop never terminates.&lt;/p&gt;
&lt;p&gt;The UMIP emulation reaches this from the #GP handler for user space: an
SGDT, SIDT or SMSW with a memory operand and a CS prefix leaves the task
spinning in the kernel, never returning to user space, with a SIGKILL
that is never delivered.  Any user can thus tie up CPUs until reboot.
With an FS or GS prefix, the emulated result is written to the wrong
address.&lt;/p&gt;
&lt;p&gt;Rename the internal macro iterator variable.&lt;/p&gt;
&lt;p&gt;[ Lukas&amp;#39; original patch renamed the use site, I changed it to rename the
  iterator in the macro instead, but left Lukas&amp;#39; commit message and
  authorship   - Linus ]&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;x86/insn-eval: Fix shadowed segment index in get_seg_reg_override_idx()&lt;/p&gt;
&lt;p&gt;Commit 45e1dccc0653 (&amp;#34;x86/insn: Simplify for_each_insn_prefix()&amp;#34;) made
for_each_insn_prefix() declare its own loop counter named idx.
get_seg_reg_override_idx() keeps its result in a local of the same name,
so the assignments in the loop body now write the loop counter:&lt;/p&gt;
&lt;p&gt;- the function always returns INAT_SEG_REG_DEFAULT, so FS and GS
   overrides are ignored;&lt;/p&gt;
&lt;p&gt;- a CS override sets the counter to INAT_SEG_REG_CS (2), the increment
   makes it 3, and prefixes.bytes[3] holds the last prefix, 0x2e again,
   so the loop never terminates.&lt;/p&gt;
&lt;p&gt;The UMIP emulation reaches this from the #GP handler for user space: an
SGDT, SIDT or SMSW with a memory operand and a CS prefix leaves the task
spinning in the kernel, never returning to user space, with a SIGKILL
that is never delivered.  Any user can thus tie up CPUs until reboot.
With an FS or GS prefix, the emulated result is written to the wrong
address.&lt;/p&gt;
&lt;p&gt;Rename the internal macro iterator variable.&lt;/p&gt;
&lt;p&gt;[ Lukas&amp;#39; original patch renamed the use site, I changed it to rename the
  iterator in the macro instead, but left Lukas&amp;#39; commit message and
  authorship   - Linus ]&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-99186</guid>
    </item>
  </channel>
</rss>
