<?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-03T08:14:42.836391+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-98754</id>
    <title>CVE-2026-98754 — tty: vcc: hold port lock when clearing tty pointer in vcc_cleanup</title>
    <updated>2026-11-03T08:14:42.868837+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>tty: vcc: hold port lock when clearing tty pointer in vcc_cleanup</p>
<p>vcc_cleanup() sets port-&gt;tty to NULL without holding port-&gt;lock, racing
with vcc_event() LDC callbacks that read port-&gt;tty under port-&gt;lock and
then use tty-&gt;port. This can cause a use-after-free when the callback
dereferences tty-&gt;port after cleanup has already destroyed and freed it.</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/cve-2026-98754"/>
  </entry>
</feed>
