<?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-07T04:34:04.349433+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-98481</id>
    <title>CVE-2026-98481 — nfc: port100: reject frames whose declared length exceeds the received data</title>
    <updated>2026-11-07T04:34:04.351011+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: port100: reject frames whose declared length exceeds the received data</p>
<p>port100_recv_response() passes the URB transfer buffer to
port100_rx_frame_is_valid(), which checksums le16_to_cpu(frame-&gt;datalen)
bytes of frame-&gt;data. datalen is a 16-bit field supplied by the device
and is never checked against the number of bytes actually received
(urb-&gt;actual_length), so a device reporting a datalen larger than the
received frame makes port100_data_checksum() read out of bounds past the
transfer buffer.</p>
<p>Reject a response whose declared frame size does not fit the received
length before validating it.</p>
<p>Found by 0sec (https://0sec.ai) using automated source analysis; the
missing bound is evident from source. Compile-tested.</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/cve-2026-98481"/>
  </entry>
</feed>
