https://db.gcve.eu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Mon, 02 Nov 2026 01:29:32 +0000 https://db.gcve.eu/vuln/certfr-2026-avi-1375 certfr-2026-avi-1375 https://db.gcve.eu/vuln/certfr-2026-avi-1375 https://db.gcve.eu/vuln/fkie_cve-2026-98575 <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 &#34;datalen - 2&#34; offset used below.</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 &#34;datalen - 2&#34; offset used below.</p> https://db.gcve.eu/vuln/fkie_cve-2026-98575 https://db.gcve.eu/vuln/ghsa-68mj-7vm5-9gjg <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 &#34;datalen - 2&#34; offset used below.</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 &#34;datalen - 2&#34; offset used below.</p> https://db.gcve.eu/vuln/ghsa-68mj-7vm5-9gjg https://db.gcve.eu/vuln/msrc_cve-2026-98575 msrc_CVE-2026-98575 https://db.gcve.eu/vuln/msrc_cve-2026-98575 https://db.gcve.eu/vuln/ubuntu-cve-2026-98575 <p><strong>Affected:</strong> Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe, Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:Pro:16.04:LTS: linux-oracle, Ubuntu:Pro:18.04:LTS: linux, Ubuntu:Pro:18.04:LTS: linux-aws, Ubuntu:18.04:LTS: linux-aws-5.0 and 239 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: nfc: pn533: fix OOB read in pn533_acr122_is_rx_frame_valid() 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. 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 &#34;datalen - 2&#34; offset used below.</p> <p><strong>Affected:</strong> Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe, Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:Pro:16.04:LTS: linux-oracle, Ubuntu:Pro:18.04:LTS: linux, Ubuntu:Pro:18.04:LTS: linux-aws, Ubuntu:18.04:LTS: linux-aws-5.0 and 239 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: nfc: pn533: fix OOB read in pn533_acr122_is_rx_frame_valid() 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. 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 &#34;datalen - 2&#34; offset used below.</p> https://db.gcve.eu/vuln/ubuntu-cve-2026-98575