<?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://cve.radiocsirt.org</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, 17 Oct 2026 05:31:34 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-68372 — usb: core: port: Deattach Type-C connector on component unbind</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-68372</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: core: port: Deattach Type-C connector on component unbind&lt;/p&gt;
&lt;p&gt;connector_unbind() is the mirror of connector_bind(), but it is missing
the symmetric call to typec_deattach() that connector_bind() makes via:&lt;/p&gt;
&lt;p&gt;if (port_dev-&amp;gt;child)
        typec_attach(port_dev-&amp;gt;connector, &amp;amp;port_dev-&amp;gt;child-&amp;gt;dev);&lt;/p&gt;
&lt;p&gt;When a Thunderbolt dock is unplugged, two teardown paths race:&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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…&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: core: port: Deattach Type-C connector on component unbind&lt;/p&gt;
&lt;p&gt;connector_unbind() is the mirror of connector_bind(), but it is missing
the symmetric call to typec_deattach() that connector_bind() makes via:&lt;/p&gt;
&lt;p&gt;if (port_dev-&amp;gt;child)
        typec_attach(port_dev-&amp;gt;connector, &amp;amp;port_dev-&amp;gt;child-&amp;gt;dev);&lt;/p&gt;
&lt;p&gt;When a Thunderbolt dock is unplugged, two teardown paths race:&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2026-68372</guid>
    </item>
    <item>
      <title>USN-8727-1 — linux-oem-7.0 vulnerabilities</title>
      <link>https://cve.radiocsirt.org/vuln/usn-8727-1</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:26.04:LTS: linux-oem-7.0&lt;/p&gt;
&lt;p&gt;It was discovered that some Arm processors could complete a broadcast
translation lookaside buffer (TLB) invalidation before memory writes made
through the invalidated translation were globally observed. A local
attacker could possibly use this to write to memory after permission to do
so had been revoked, bypassing memory protections or escalating privileges.
(CVE-2025-10263)&lt;/p&gt;
&lt;p&gt;Several security issues were discovered in the Linux kernel.
An attacker could possibly use these to compromise the system.
This update corrects flaws in the following subsystems:
  - ARM64 architecture;
  - User-space API (UAPI);
  - Kernel build system;
  - ARM32 architecture;
  - RISC-V architecture;
  - S390 architecture;
  - x86 architecture;
  - Block layer subsystem;
  - Cryptographic API;
  - Compute Acceleration Framework;
  - Intel NPU Driver;
  - ACPI drivers;
  - Android drivers;
  - Drivers core;
  - Compressed RAM block device driver;
  - Bluetooth drivers;
  - Character device driver;
  - Hardware random number generator core;
  - CPU frequency scaling framework;
  - Hardware crypto device drivers;
  - Buffer Sharing and Synchronization framework;
  - Intel Stratix 10 firmware drivers;
  - FPGA Framework;
  - GPIO subsystem;
  - GPU drivers;
  - HID subsystem;
  - CoreSight HW tracing drivers;
  - I2C subsystem;
  - IIO subsystem;
  - IIO ADC drivers;
  - InfiniBand drivers;
  - Input Device core drivers;
  - Input Device (Mouse) drivers;
  - IOMMU subsystem;
  - IRQ chip drivers;
  - M…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:26.04:LTS: linux-oem-7.0&lt;/p&gt;
&lt;p&gt;It was discovered that some Arm processors could complete a broadcast
translation lookaside buffer (TLB) invalidation before memory writes made
through the invalidated translation were globally observed. A local
attacker could possibly use this to write to memory after permission to do
so had been revoked, bypassing memory protections or escalating privileges.
(CVE-2025-10263)&lt;/p&gt;
&lt;p&gt;Several security issues were discovered in the Linux kernel.
An attacker could possibly use these to compromise the system.
This update corrects flaws in the following subsystems:
  - ARM64 architecture;
  - User-space API (UAPI);
  - Kernel build system;
  - ARM32 architecture;
  - RISC-V architecture;
  - S390 architecture;
  - x86 architecture;
  - Block layer subsystem;
  - Cryptographic API;
  - Compute Acceleration Framework;
  - Intel NPU Driver;
  - ACPI drivers;
  - Android drivers;
  - Drivers core;
  - Compressed RAM block device driver;
  - Bluetooth drivers;
  - Character device driver;
  - Hardware random number generator core;
  - CPU frequency scaling framework;
  - Hardware crypto device drivers;
  - Buffer Sharing and Synchronization framework;
  - Intel Stratix 10 firmware drivers;
  - FPGA Framework;
  - GPIO subsystem;
  - GPU drivers;
  - HID subsystem;
  - CoreSight HW tracing drivers;
  - I2C subsystem;
  - IIO subsystem;
  - IIO ADC drivers;
  - InfiniBand drivers;
  - Input Device core drivers;
  - Input Device (Mouse) drivers;
  - IOMMU subsystem;
  - IRQ chip drivers;
  - M…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/usn-8727-1</guid>
    </item>
  </channel>
</rss>
