<?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 04:29:45 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-31624 — HID: core: clamp report_size in s32ton() to avoid undefined shift</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-31624</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;HID: core: clamp report_size in s32ton() to avoid undefined shift&lt;/p&gt;
&lt;p&gt;s32ton() shifts by n-1 where n is the field&amp;#39;s report_size, a value that
comes directly from a HID device.  The HID parser bounds report_size
only to &amp;lt;= 256, so a broken HID device can supply a report descriptor
with a wide field that triggers shift exponents up to 256 on a 32-bit
type when an output report is built via hid_output_field() or
hid_set_field().&lt;/p&gt;
&lt;p&gt;Commit ec61b41918587 (&amp;#34;HID: core: fix shift-out-of-bounds in
hid_report_raw_event&amp;#34;) added the same n &amp;gt; 32 clamp to the function
snto32(), but s32ton() was never given the same fix as I guess syzbot
hadn&amp;#39;t figured out how to fuzz a device the same way.&lt;/p&gt;
&lt;p&gt;Fix this up by just clamping the max value of n, just like snto32()
does.&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;HID: core: clamp report_size in s32ton() to avoid undefined shift&lt;/p&gt;
&lt;p&gt;s32ton() shifts by n-1 where n is the field&amp;#39;s report_size, a value that
comes directly from a HID device.  The HID parser bounds report_size
only to &amp;lt;= 256, so a broken HID device can supply a report descriptor
with a wide field that triggers shift exponents up to 256 on a 32-bit
type when an output report is built via hid_output_field() or
hid_set_field().&lt;/p&gt;
&lt;p&gt;Commit ec61b41918587 (&amp;#34;HID: core: fix shift-out-of-bounds in
hid_report_raw_event&amp;#34;) added the same n &amp;gt; 32 clamp to the function
snto32(), but s32ton() was never given the same fix as I guess syzbot
hadn&amp;#39;t figured out how to fuzz a device the same way.&lt;/p&gt;
&lt;p&gt;Fix this up by just clamping the max value of n, just like snto32()
does.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-31624</guid>
    </item>
  </channel>
</rss>
