<?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-21T13:52:42.530577+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-68378</id>
    <title>BELL-CVE-2026-68378</title>
    <updated>2026-11-21T13:52:42.546079+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p><strong>Affected:</strong> Alpaquita:stream: linux-lts</p>
      </div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/bell-cve-2026-68378"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/certfr-2026-avi-1286</id>
    <title>certfr-2026-avi-1286 — De multiples vulnérabilités ont été découvertes dans le noyau Linux d'Ubuntu. Certaines d'entre elles permettent à un a…</title>
    <updated>2026-11-21T13:52:42.546162+00:00</updated>
    <content>certfr-2026-avi-1286</content>
    <link href="https://127.0.0.1:10001/vuln/certfr-2026-avi-1286"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/ubuntu-cve-2026-68378</id>
    <title>UBUNTU-CVE-2026-68378</title>
    <updated>2026-11-21T13:52:42.546183+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 120 more</p>
<p>In the Linux kernel, the following vulnerability has been resolved: dpll: fix NULL pointer dereference in dpll_msg_add_pin_ref_sync() When a dpll_pin is shared across multiple dpll_device instances and those devices are being unregistered (e.g. during driver module removal), a NULL pointer dereference can occur in dpll_msg_add_pin_ref_sync(). This happens under the following conditions:  - A pin is registered with two or more dpll devices (dpll_A, dpll_B)  - The pin has ref_sync pairs with other pins  - During unregistration of dpll_A's pins, a ref_sync partner pin is    unregistered first, removing it from dpll_A-&gt;pin_refs  - But since the partner pin is still registered with dpll_B, its    dpll_refs is not empty, so dpll_pin_ref_sync_pair_del() does NOT    run and the partner stays in the pin's ref_sync_pins xarray  - When the pin itself is then unregistered from dpll_A, the delete    notification calls dpll_msg_add_pin_ref_sync() which finds the    partner in ref_sync_pins, passes dpll_pin_available() (partner is    still registered with dpll_B), but dpll_pin_on_dpll_priv(dpll_A,    partner) returns NULL because partner was already removed from    dpll_A-&gt;pin_refs  - The NULL priv pointer is passed to the driver's ref_sync_get    callback, which dereferences it  BUG: kernel NULL pointer dereference, address: 0000000000000034  Oops: Oops: 0000 [#1] SMP NOPTI  RIP: 0010:zl3073x_dpll_input_pin_ref_sync_get+0x73/0x80 [zl3073x]  Call Trace:   dpll_msg_add_pin_ref_sync+0xb8/0x2…</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/ubuntu-cve-2026-68378"/>
  </entry>
</feed>
