<?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>Mon, 02 Nov 2026 09:45:46 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-98575 — nfc: pn533: fix OOB read in pn533_acr122_is_rx_frame_valid()</title>
      <link>https://db.gcve.eu/vuln/cve-2026-98575</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;nfc: pn533: fix OOB read in pn533_acr122_is_rx_frame_valid()&lt;/p&gt;
&lt;p&gt;frame-&amp;gt;ccid.datalen is read directly from the USB response frame
and used, unchecked, as an index into frame-&amp;gt;data[]. A malicious or
malfunctioning device can set this field to an arbitrary value,
causing the driver to read far outside the received buffer.&lt;/p&gt;
&lt;p&gt;Bound ccid.datalen against the maximum possible ACR122 frame size
before using it. This replaces the existing datalen == 0 check,
since datalen &amp;lt; 2 already covers that case and additionally
rejects datalen == 1, which would still underflow the
&amp;#34;datalen - 2&amp;#34; offset used below.&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;nfc: pn533: fix OOB read in pn533_acr122_is_rx_frame_valid()&lt;/p&gt;
&lt;p&gt;frame-&amp;gt;ccid.datalen is read directly from the USB response frame
and used, unchecked, as an index into frame-&amp;gt;data[]. A malicious or
malfunctioning device can set this field to an arbitrary value,
causing the driver to read far outside the received buffer.&lt;/p&gt;
&lt;p&gt;Bound ccid.datalen against the maximum possible ACR122 frame size
before using it. This replaces the existing datalen == 0 check,
since datalen &amp;lt; 2 already covers that case and additionally
rejects datalen == 1, which would still underflow the
&amp;#34;datalen - 2&amp;#34; offset used below.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-98575</guid>
    </item>
  </channel>
</rss>
