<?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-10-09T22:30:59.315228+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-88373</id>
    <title>CVE-2026-88373</title>
    <updated>2026-10-09T22:30:59.317691+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>libde265 commit 4d45a6b contains a NULL pointer dereference vulnerability in the NAL parsing path. When de265_push_NAL() is called with a zero-length NAL unit, the resulting NAL_unit may retain a NULL backing buffer, which is subsequently passed as the destination argument to memcpy() in NAL_unit::set_data(). Although the copy length is zero, this violates the nonnull requirement of memcpy() and results in undefined behavior, causing process termination in UBSan-instrumented builds and denial of service.</p>
      </div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2026-88373"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/usn-8909-1</id>
    <title>USN-8909-1 — libde265 vulnerability</title>
    <updated>2026-10-09T22:30:59.317768+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Ubuntu:Pro:16.04:LTS: libde265, Ubuntu:Pro:18.04:LTS: libde265, Ubuntu:Pro:20.04:LTS: libde265, Ubuntu:Pro:22.04:LTS: libde265, Ubuntu:24.04:LTS: libde265, Ubuntu:Pro:26.04:LTS: libde265</p>
<p>It was discovered that libde265 did not properly validate certain crafted
H.265 bitstreams, leading to a NULL pointer dereference. An attacker could
possibly use this issue to cause libde265 to crash, resulting in a denial
of service.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/usn-8909-1"/>
  </entry>
</feed>
