<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://vulnerability.circl.lu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Tue, 29 Sep 2026 01:05:02 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-36893 — usb: typec: tcpm: Check for port partner validity before consuming it</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2024-36893</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;usb: typec: tcpm: Check for port partner validity before consuming it&lt;/p&gt;
&lt;p&gt;typec_register_partner() does not guarantee partner registration
to always succeed. In the event of failure, port-&amp;gt;partner is set
to the error value or NULL. Given that port-&amp;gt;partner validity is
not checked, this results in the following crash:&lt;/p&gt;
&lt;p&gt;Unable to handle kernel NULL pointer dereference at virtual address xx
 pc : run_state_machine+0x1bc8/0x1c08
 lr : run_state_machine+0x1b90/0x1c08
..
 Call trace:
   run_state_machine+0x1bc8/0x1c08
   tcpm_state_machine_work+0x94/0xe4
   kthread_worker_fn+0x118/0x328
   kthread+0x1d0/0x23c
   ret_from_fork+0x10/0x20&lt;/p&gt;
&lt;p&gt;To prevent the crash, check for port-&amp;gt;partner validity before
derefencing it in all the call sites.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;usb: typec: tcpm: Check for port partner validity before consuming it&lt;/p&gt;
&lt;p&gt;typec_register_partner() does not guarantee partner registration
to always succeed. In the event of failure, port-&amp;gt;partner is set
to the error value or NULL. Given that port-&amp;gt;partner validity is
not checked, this results in the following crash:&lt;/p&gt;
&lt;p&gt;Unable to handle kernel NULL pointer dereference at virtual address xx
 pc : run_state_machine+0x1bc8/0x1c08
 lr : run_state_machine+0x1b90/0x1c08
..
 Call trace:
   run_state_machine+0x1bc8/0x1c08
   tcpm_state_machine_work+0x94/0xe4
   kthread_worker_fn+0x118/0x328
   kthread+0x1d0/0x23c
   ret_from_fork+0x10/0x20&lt;/p&gt;
&lt;p&gt;To prevent the crash, check for port-&amp;gt;partner validity before
derefencing it in all the call sites.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2024-36893</guid>
    </item>
  </channel>
</rss>
