<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://db.gcve.eu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-11-02T09:45:48.592230+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@gcve.eu</email>
  </author>
  <link href="https://db.gcve.eu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://db.gcve.eu/vuln/cve-2026-98575</id>
    <title>CVE-2026-98575 — nfc: pn533: fix OOB read in pn533_acr122_is_rx_frame_valid()</title>
    <updated>2026-11-02T09:45:48.594219+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Linux</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>nfc: pn533: fix OOB read in pn533_acr122_is_rx_frame_valid()</p>
<p>frame-&gt;ccid.datalen is read directly from the USB response frame
and used, unchecked, as an index into frame-&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.</p>
<p>Bound ccid.datalen against the maximum possible ACR122 frame size
before using it. This replaces the existing datalen == 0 check,
since datalen &lt; 2 already covers that case and additionally
rejects datalen == 1, which would still underflow the
"datalen - 2" offset used below.</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/cve-2026-98575"/>
  </entry>
</feed>
