<?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-30T16:15:59.717581+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-100079</id>
    <title>CVE-2026-100079 — usb: typec: ucsi: unregister debugfs entries on teardown</title>
    <updated>2026-09-30T16:16:00.784097+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>usb: typec: ucsi: unregister debugfs entries on teardown</p>
<p>ucsi_register() creates per-instance debugfs entries, but
ucsi_unregister() keeps them around until ucsi_destroy().</p>
<p>Drivers like ucsi_glink that unregister/register the same UCSI
instance across remoteproc restart then try to create an already
existing debugfs directory and log:</p>
<p>debugfs: 'pmic_glink.ucsi.0' already exists in 'ucsi'</p>
<p>Unregister debugfs entries as part of ucsi_unregister(), and
clear ucsi-&gt;debugfs after freeing it so repeated unregister
paths remain safe.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2026-100079"/>
  </entry>
</feed>
