<?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://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-09-29T11:28:25.135029+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" 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://vulnerability.circl.lu/vuln/cve-2026-80799</id>
    <title>CVE-2026-80799 — nfc: llcp: fix OOB read and u8 offset wrap in TLV parsers</title>
    <updated>2026-09-29T11:28:25.308667+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: llcp: fix OOB read and u8 offset wrap in TLV parsers</p>
<p>nfc_llcp_parse_gb_tlv() and nfc_llcp_parse_connection_tlv() contain
three related bugs in their TLV parsing loops:</p>
<p>1. 'offset' is declared u8 but tlv_array_len is u16. When TLV data
   advances offset past 255 it silently wraps to zero, causing
   infinite loops or double-processing of buffer data.</p>
<p>2. Before reading tlv[0] (type) and tlv[1] (length) there is no
   check that offset+2 &lt;= tlv_array_len. A truncated TLV causes
   an OOB read of one byte past the buffer end.</p>
<p>3. After reading the length field, the value bytes are accessed
   without checking offset+2+length &lt;= tlv_array_len. A crafted
   length=0xFF on a short buffer causes up to 255 bytes of OOB
   read past the buffer end.</p>
<p>Both functions are reachable without authentication via
nfc_llcp_set_remote_gb() which feeds remote LLCP general bytes
directly into nfc_llcp_parse_gb_tlv() with no additional
validation.</p>
<p>Fix all three issues by widening offset from u8 to u16 and adding
bounds checks for both the TLV header and value field before each
access.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2026-80799"/>
  </entry>
</feed>
