<?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, 06 Oct 2026 15:14:17 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-80918 — HID: core: fix number/pointer type confusion on long items</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-80918</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: fix number/pointer type confusion on long items&lt;/p&gt;
&lt;p&gt;When fetch_item() is called by hid_scan_report() on an item with
HID_ITEM_TAG_LONG, it stores a pointer to the item data in
item-&amp;gt;data.longdata instead of storing a value directly in
item-&amp;gt;data.{u8/u16/u32}.&lt;/p&gt;
&lt;p&gt;When item_udata() or item_sdata() encounters such an item, it incorrectly
assumes that the item is in short format, and therefore returns the lower
part of a kernel pointer reinterpreted as a number.&lt;/p&gt;
&lt;p&gt;When a HID device is connected whose descriptor contains a
HID_GLOBAL_ITEM_TAG_REPORT_SIZE encoded in long format with size=4, this
causes the lower half of a kernel pointer to be printed into dmesg as a
number, like this:&lt;/p&gt;
&lt;p&gt;hid (null): invalid report_size 107953555&lt;/p&gt;
&lt;p&gt;To fix it, let item_udata() and item_sdata() verify that the item is in
short format.&lt;/p&gt;
&lt;p&gt;Note that this bug only affects hid_scan_report(), while the main parsing
pass hid_parse_collections() will always bail out when encountering a long
item.&lt;/p&gt;
&lt;p&gt;Sidenote: There are currently no users of data.longdata; maybe we should
just remove any parsing of long-format descriptors as a follow-up.&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: fix number/pointer type confusion on long items&lt;/p&gt;
&lt;p&gt;When fetch_item() is called by hid_scan_report() on an item with
HID_ITEM_TAG_LONG, it stores a pointer to the item data in
item-&amp;gt;data.longdata instead of storing a value directly in
item-&amp;gt;data.{u8/u16/u32}.&lt;/p&gt;
&lt;p&gt;When item_udata() or item_sdata() encounters such an item, it incorrectly
assumes that the item is in short format, and therefore returns the lower
part of a kernel pointer reinterpreted as a number.&lt;/p&gt;
&lt;p&gt;When a HID device is connected whose descriptor contains a
HID_GLOBAL_ITEM_TAG_REPORT_SIZE encoded in long format with size=4, this
causes the lower half of a kernel pointer to be printed into dmesg as a
number, like this:&lt;/p&gt;
&lt;p&gt;hid (null): invalid report_size 107953555&lt;/p&gt;
&lt;p&gt;To fix it, let item_udata() and item_sdata() verify that the item is in
short format.&lt;/p&gt;
&lt;p&gt;Note that this bug only affects hid_scan_report(), while the main parsing
pass hid_parse_collections() will always bail out when encountering a long
item.&lt;/p&gt;
&lt;p&gt;Sidenote: There are currently no users of data.longdata; maybe we should
just remove any parsing of long-format descriptors as a follow-up.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-80918</guid>
    </item>
  </channel>
</rss>
