<?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://127.0.0.1:10001</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>Sat, 21 Nov 2026 08:56:44 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-68372</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2026-68372</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/bell-cve-2026-68372</guid>
    </item>
    <item>
      <title>certfr-2026-avi-1069 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian LTS. Elles permettent à un attaquant de p…</title>
      <link>https://127.0.0.1:10001/vuln/certfr-2026-avi-1069</link>
      <description>certfr-2026-avi-1069</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2026-avi-1069</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-68372</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2026-68372</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; 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 155 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: usb: core: port: Deattach Type-C connector on component unbind connector_unbind() is the mirror of connector_bind(), but it is missing the symmetric call to typec_deattach() that connector_bind() makes via:     if (port_dev-&amp;gt;child)         typec_attach(port_dev-&amp;gt;connector, &amp;amp;port_dev-&amp;gt;child-&amp;gt;dev); When a Thunderbolt dock is unplugged, two teardown paths race: 1. The component framework calls connector_unbind() first, which sets    port_dev-&amp;gt;connector = NULL without calling typec_deattach().  This    leaves port-&amp;gt;usb2_dev/port-&amp;gt;usb3_dev in struct typec_port pointing at    the USB device that is about to be freed. 2. usb_disconnect() then calls typec_deattach(port_dev-&amp;gt;connector, ...),    but port_dev-&amp;gt;connector is already NULL, so the call is a no-op and    port-&amp;gt;usb2_dev is never cleared. 3. Concurrently, UCSI detects a PD partner-disconnect event and calls    typec_unregister_partner(), which reads port-&amp;gt;usb2_dev (now a dangling    pointer to freed memory) and passes it to typec_partner_unlink_device()    -&amp;gt; sysfs_remove_link() -&amp;gt; dev_name() on the freed device, corrupting    the typec/UCSI partner state. This corruption leaves the Thunderbolt tunnel in an inconsistent state on the next dock hot-plug.  On affected hardware the dock&amp;#39;s I225/igc NIC fails to enumerate: AER fires a slot reset while the igc driver is still initialising (&amp;#34;PCIe link lost&amp;#34;), and the subsequent igc_reset attempt hits igc_rd32 on an a…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; 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 155 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: usb: core: port: Deattach Type-C connector on component unbind connector_unbind() is the mirror of connector_bind(), but it is missing the symmetric call to typec_deattach() that connector_bind() makes via:     if (port_dev-&amp;gt;child)         typec_attach(port_dev-&amp;gt;connector, &amp;amp;port_dev-&amp;gt;child-&amp;gt;dev); When a Thunderbolt dock is unplugged, two teardown paths race: 1. The component framework calls connector_unbind() first, which sets    port_dev-&amp;gt;connector = NULL without calling typec_deattach().  This    leaves port-&amp;gt;usb2_dev/port-&amp;gt;usb3_dev in struct typec_port pointing at    the USB device that is about to be freed. 2. usb_disconnect() then calls typec_deattach(port_dev-&amp;gt;connector, ...),    but port_dev-&amp;gt;connector is already NULL, so the call is a no-op and    port-&amp;gt;usb2_dev is never cleared. 3. Concurrently, UCSI detects a PD partner-disconnect event and calls    typec_unregister_partner(), which reads port-&amp;gt;usb2_dev (now a dangling    pointer to freed memory) and passes it to typec_partner_unlink_device()    -&amp;gt; sysfs_remove_link() -&amp;gt; dev_name() on the freed device, corrupting    the typec/UCSI partner state. This corruption leaves the Thunderbolt tunnel in an inconsistent state on the next dock hot-plug.  On affected hardware the dock&amp;#39;s I225/igc NIC fails to enumerate: AER fires a slot reset while the igc driver is still initialising (&amp;#34;PCIe link lost&amp;#34;), and the subsequent igc_reset attempt hits igc_rd32 on an a…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2026-68372</guid>
    </item>
  </channel>
</rss>
