<?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>Fri, 16 Oct 2026 23:02:08 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-43226 — net/rds: No shortcut out of RDS_CONN_ERROR</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-43226</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;net/rds: No shortcut out of RDS_CONN_ERROR&lt;/p&gt;
&lt;p&gt;RDS connections carry a state &amp;#34;rds_conn_path::cp_state&amp;#34;
and transitions from one state to another and are conditional
upon an expected state: &amp;#34;rds_conn_path_transition.&amp;#34;&lt;/p&gt;
&lt;p&gt;There is one exception to this conditionality, which is
&amp;#34;RDS_CONN_ERROR&amp;#34; that can be enforced by &amp;#34;rds_conn_path_drop&amp;#34;
regardless of what state the condition is currently in.&lt;/p&gt;
&lt;p&gt;But as soon as a connection enters state &amp;#34;RDS_CONN_ERROR&amp;#34;,
the connection handling code expects it to go through the
shutdown-path.&lt;/p&gt;
&lt;p&gt;The RDS/TCP multipath changes added a shortcut out of
&amp;#34;RDS_CONN_ERROR&amp;#34; straight back to &amp;#34;RDS_CONN_CONNECTING&amp;#34;
via &amp;#34;rds_tcp_accept_one_path&amp;#34; (e.g. after &amp;#34;rds_tcp_state_change&amp;#34;).&lt;/p&gt;
&lt;p&gt;A subsequent &amp;#34;rds_tcp_reset_callbacks&amp;#34; can then transition
the state to &amp;#34;RDS_CONN_RESETTING&amp;#34; with a shutdown-worker queued.&lt;/p&gt;
&lt;p&gt;That&amp;#39;ll trip up &amp;#34;rds_conn_init_shutdown&amp;#34;, which was
never adjusted to handle &amp;#34;RDS_CONN_RESETTING&amp;#34; and subsequently
drops the connection with the dreaded &amp;#34;DR_INV_CONN_STATE&amp;#34;,
which leaves &amp;#34;RDS_SHUTDOWN_WORK_QUEUED&amp;#34; on forever.&lt;/p&gt;
&lt;p&gt;So we do two things here:&lt;/p&gt;
&lt;p&gt;a) Don&amp;#39;t shortcut &amp;#34;RDS_CONN_ERROR&amp;#34;, but take the longer
   path through the shutdown code.&lt;/p&gt;
&lt;p&gt;b) Add &amp;#34;RDS_CONN_RESETTING&amp;#34; to the expected states in
  &amp;#34;rds_conn_init_shutdown&amp;#34; so that we won&amp;#39;t error out
  and get stuck, if we ever hit weird state transitions
  like this again.&amp;#34;&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;net/rds: No shortcut out of RDS_CONN_ERROR&lt;/p&gt;
&lt;p&gt;RDS connections carry a state &amp;#34;rds_conn_path::cp_state&amp;#34;
and transitions from one state to another and are conditional
upon an expected state: &amp;#34;rds_conn_path_transition.&amp;#34;&lt;/p&gt;
&lt;p&gt;There is one exception to this conditionality, which is
&amp;#34;RDS_CONN_ERROR&amp;#34; that can be enforced by &amp;#34;rds_conn_path_drop&amp;#34;
regardless of what state the condition is currently in.&lt;/p&gt;
&lt;p&gt;But as soon as a connection enters state &amp;#34;RDS_CONN_ERROR&amp;#34;,
the connection handling code expects it to go through the
shutdown-path.&lt;/p&gt;
&lt;p&gt;The RDS/TCP multipath changes added a shortcut out of
&amp;#34;RDS_CONN_ERROR&amp;#34; straight back to &amp;#34;RDS_CONN_CONNECTING&amp;#34;
via &amp;#34;rds_tcp_accept_one_path&amp;#34; (e.g. after &amp;#34;rds_tcp_state_change&amp;#34;).&lt;/p&gt;
&lt;p&gt;A subsequent &amp;#34;rds_tcp_reset_callbacks&amp;#34; can then transition
the state to &amp;#34;RDS_CONN_RESETTING&amp;#34; with a shutdown-worker queued.&lt;/p&gt;
&lt;p&gt;That&amp;#39;ll trip up &amp;#34;rds_conn_init_shutdown&amp;#34;, which was
never adjusted to handle &amp;#34;RDS_CONN_RESETTING&amp;#34; and subsequently
drops the connection with the dreaded &amp;#34;DR_INV_CONN_STATE&amp;#34;,
which leaves &amp;#34;RDS_SHUTDOWN_WORK_QUEUED&amp;#34; on forever.&lt;/p&gt;
&lt;p&gt;So we do two things here:&lt;/p&gt;
&lt;p&gt;a) Don&amp;#39;t shortcut &amp;#34;RDS_CONN_ERROR&amp;#34;, but take the longer
   path through the shutdown code.&lt;/p&gt;
&lt;p&gt;b) Add &amp;#34;RDS_CONN_RESETTING&amp;#34; to the expected states in
  &amp;#34;rds_conn_init_shutdown&amp;#34; so that we won&amp;#39;t error out
  and get stuck, if we ever hit weird state transitions
  like this again.&amp;#34;&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2026-43226</guid>
    </item>
    <item>
      <title>USN-8492-1 — linux, linux-aws, linux-aws-fips, linux-gcp, linux-gcp-fips, linux-ibm, linux-nvidia, linux-nvidia-6.8, linux-oracle, l…</title>
      <link>https://cve.radiocsirt.org/vuln/usn-8492-1</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:22.04:LTS: linux-nvidia-6.8, Ubuntu:Pro:Realtime:22.04:LTS: linux-realtime-6.8, Ubuntu:24.04:LTS: linux, Ubuntu:24.04:LTS: linux-aws, Ubuntu:24.04:LTS: linux-gcp, Ubuntu:24.04:LTS: linux-ibm, Ubuntu:24.04:LTS: linux-nvidia, Ubuntu:24.04:LTS: linux-oracle, Ubuntu:Pro:Realtime:24.04:LTS: linux-realtime, Ubuntu:Pro:FIPS-updates:24.04:LTS: linux-aws-fips and 1 more&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;
  - MIPS architecture;
  - PowerPC architecture;
  - x86 architecture;
  - Block layer subsystem;
  - Cryptographic API;
  - ACPI drivers;
  - ATM drivers;
  - RNBD block device driver;
  - Ublk userspace block driver;
  - Bus devices;
  - Character device driver;
  - TPM device driver;
  - Clock framework and drivers;
  - Clocksource drivers;
  - CPU idle management framework;
  - Hardware crypto device drivers;
  - DMA engine subsystem;
  - EFI core;
  - GPIO subsystem;
  - GPU drivers;
  - HID subsystem;
  - Hardware monitoring drivers;
  - IIO subsystem;
  - InfiniBand drivers;
  - IOMMU subsystem;
  - Multiple devices driver;
  - Media drivers;
  - Multifunction device drivers;
  - Broadcom VK accelerator driver;
  - MOST (Media Oriented Systems Transport) drivers;
  - MTD block device drivers;
  - Ethernet bonding driver;
  - Network drivers;
  - Mellanox network drivers;
  - STMicroelectronics network drivers;
  - NTB driver;
  - NVME drivers;
  - PCI subsystem;
  - Performance monitor drivers;
  - Pin controllers subsystem;
  - x86 platform drivers;
  - Power supply drivers;
  - RapidIO drivers;
  - RAS (Reliability, Availability, Serviceability) subsystem;
  - Remote Processor subsystem;
  - RPMSG subsystem;
  - S/390 drivers;
  - SCSI subsystem;
  - MediaTek SoC dr…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:22.04:LTS: linux-nvidia-6.8, Ubuntu:Pro:Realtime:22.04:LTS: linux-realtime-6.8, Ubuntu:24.04:LTS: linux, Ubuntu:24.04:LTS: linux-aws, Ubuntu:24.04:LTS: linux-gcp, Ubuntu:24.04:LTS: linux-ibm, Ubuntu:24.04:LTS: linux-nvidia, Ubuntu:24.04:LTS: linux-oracle, Ubuntu:Pro:Realtime:24.04:LTS: linux-realtime, Ubuntu:Pro:FIPS-updates:24.04:LTS: linux-aws-fips and 1 more&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;
  - MIPS architecture;
  - PowerPC architecture;
  - x86 architecture;
  - Block layer subsystem;
  - Cryptographic API;
  - ACPI drivers;
  - ATM drivers;
  - RNBD block device driver;
  - Ublk userspace block driver;
  - Bus devices;
  - Character device driver;
  - TPM device driver;
  - Clock framework and drivers;
  - Clocksource drivers;
  - CPU idle management framework;
  - Hardware crypto device drivers;
  - DMA engine subsystem;
  - EFI core;
  - GPIO subsystem;
  - GPU drivers;
  - HID subsystem;
  - Hardware monitoring drivers;
  - IIO subsystem;
  - InfiniBand drivers;
  - IOMMU subsystem;
  - Multiple devices driver;
  - Media drivers;
  - Multifunction device drivers;
  - Broadcom VK accelerator driver;
  - MOST (Media Oriented Systems Transport) drivers;
  - MTD block device drivers;
  - Ethernet bonding driver;
  - Network drivers;
  - Mellanox network drivers;
  - STMicroelectronics network drivers;
  - NTB driver;
  - NVME drivers;
  - PCI subsystem;
  - Performance monitor drivers;
  - Pin controllers subsystem;
  - x86 platform drivers;
  - Power supply drivers;
  - RapidIO drivers;
  - RAS (Reliability, Availability, Serviceability) subsystem;
  - Remote Processor subsystem;
  - RPMSG subsystem;
  - S/390 drivers;
  - SCSI subsystem;
  - MediaTek SoC dr…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/usn-8492-1</guid>
    </item>
  </channel>
</rss>
