<?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 02:33:00 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-37862 — HID: pidff: Fix null pointer dereference in pidff_find_fields</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2025-37862</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: pidff: Fix null pointer dereference in pidff_find_fields&lt;/p&gt;
&lt;p&gt;This function triggered a null pointer dereference if used to search for
a report that isn&amp;#39;t implemented on the device. This happened both for
optional and required reports alike.&lt;/p&gt;
&lt;p&gt;The same logic was applied to pidff_find_special_field and although
pidff_init_fields should return an error earlier if one of the required
reports is missing, future modifications could change this logic and
resurface this possible null pointer dereference again.&lt;/p&gt;
&lt;p&gt;LKML bug report:
https://lore.kernel.org/all/CAL-gK7f5=R0nrrQdPtaZZr1fd-cdAMbDMuZ_NLA8vM0SX+nGSw@mail.gmail.com&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: pidff: Fix null pointer dereference in pidff_find_fields&lt;/p&gt;
&lt;p&gt;This function triggered a null pointer dereference if used to search for
a report that isn&amp;#39;t implemented on the device. This happened both for
optional and required reports alike.&lt;/p&gt;
&lt;p&gt;The same logic was applied to pidff_find_special_field and although
pidff_init_fields should return an error earlier if one of the required
reports is missing, future modifications could change this logic and
resurface this possible null pointer dereference again.&lt;/p&gt;
&lt;p&gt;LKML bug report:
https://lore.kernel.org/all/CAL-gK7f5=R0nrrQdPtaZZr1fd-cdAMbDMuZ_NLA8vM0SX+nGSw@mail.gmail.com&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2025-37862</guid>
    </item>
  </channel>
</rss>
