<?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://127.0.0.1:10001/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-11-21T16:56:21.526251+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://127.0.0.1:10001" 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://127.0.0.1:10001/vuln/bell-cve-2026-89628</id>
    <title>BELL-CVE-2026-89628</title>
    <updated>2026-11-21T16:56:21.535374+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p><strong>Affected:</strong> Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts</p>
      </div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/bell-cve-2026-89628"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/certfr-2026-avi-1253</id>
    <title>certfr-2026-avi-1253 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian. Certaines d'entre elles permettent à un…</title>
    <updated>2026-11-21T16:56:21.535407+00:00</updated>
    <content>certfr-2026-avi-1253</content>
    <link href="https://127.0.0.1:10001/vuln/certfr-2026-avi-1253"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/ubuntu-cve-2026-89628</id>
    <title>UBUNTU-CVE-2026-89628</title>
    <updated>2026-11-21T16:56:21.535418+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, 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 and 248 more</p>
<p>In the Linux kernel, the following vulnerability has been resolved: HID: picolcd: clamp eeprom debugfs read to bytes actually received picolcd_debug_eeprom_read() trusts resp-&gt;raw_data[2] -- a length byte supplied by the device in its REPORT_EE_DATA reply -- clamped only to the caller's read() count: 	ret = resp-&gt;raw_data[2]; 	if (ret &gt; s) 		ret = s; 	if (copy_to_user(u, resp-&gt;raw_data+3, ret)) It never checks resp-&gt;raw_size, the number of bytes picolcd_raw_event() actually copied into the 64-byte raw_data[] of the kmalloc'd struct picolcd_pending. A device (or a spoofed picoLCD) returning a length byte of 0xff, read with a count &gt;= 255, makes copy_to_user() read past raw_data[] into adjacent slab memory and return it to userspace through the debugfs "eeprom" file: 	BUG: KASAN: slab-out-of-bounds in _copy_to_user 	Read of size 255 ... picolcd_debug_eeprom_read+0x214/0x2f0 [hid_picolcd] The debug-dump path in the same file already validates the device length byte against the received size before trusting it; this read does not. The file is created S_IRUSR (root-only) and a crafted device is needed, so it is neither unprivileged- nor remotely-triggerable. Clamp the copy length to resp-&gt;raw_size - 3 (the payload actually received, minus the 3-byte header), floored at 0 for short replies.</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/ubuntu-cve-2026-89628"/>
  </entry>
</feed>
