<?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 13:16:35 +0000</lastBuildDate>
    <item>
      <title>CVE-2022-49149 — rxrpc: Fix call timer start racing with call destruction</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2022-49149</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;rxrpc: Fix call timer start racing with call destruction&lt;/p&gt;
&lt;p&gt;The rxrpc_call struct has a timer used to handle various timed events
relating to a call.  This timer can get started from the packet input
routines that are run in softirq mode with just the RCU read lock held.
Unfortunately, because only the RCU read lock is held - and neither ref or
other lock is taken - the call can start getting destroyed at the same time
a packet comes in addressed to that call.  This causes the timer - which
was already stopped - to get restarted.  Later, the timer dispatch code may
then oops if the timer got deallocated first.&lt;/p&gt;
&lt;p&gt;Fix this by trying to take a ref on the rxrpc_call struct and, if
successful, passing that ref along to the timer.  If the timer was already
running, the ref is discarded.&lt;/p&gt;
&lt;p&gt;The timer completion routine can then pass the ref along to the call&amp;#39;s work
item when it queues it.  If the timer or work item where already
queued/running, the extra ref is discarded.&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;rxrpc: Fix call timer start racing with call destruction&lt;/p&gt;
&lt;p&gt;The rxrpc_call struct has a timer used to handle various timed events
relating to a call.  This timer can get started from the packet input
routines that are run in softirq mode with just the RCU read lock held.
Unfortunately, because only the RCU read lock is held - and neither ref or
other lock is taken - the call can start getting destroyed at the same time
a packet comes in addressed to that call.  This causes the timer - which
was already stopped - to get restarted.  Later, the timer dispatch code may
then oops if the timer got deallocated first.&lt;/p&gt;
&lt;p&gt;Fix this by trying to take a ref on the rxrpc_call struct and, if
successful, passing that ref along to the timer.  If the timer was already
running, the ref is discarded.&lt;/p&gt;
&lt;p&gt;The timer completion routine can then pass the ref along to the call&amp;#39;s work
item when it queues it.  If the timer or work item where already
queued/running, the extra ref is discarded.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2022-49149</guid>
    </item>
    <item>
      <title>USN-8919-1 — linux, linux-aws, linux-azure, linux-azure-5.4, linux-fips, linux-gcp, linux-gcp-5.4, linux-gcp-fips, linux-hwe-5.4, li…</title>
      <link>https://cve.radiocsirt.org/vuln/usn-8919-1</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:18.04:LTS: linux-azure-5.4, Ubuntu:Pro:18.04:LTS: linux-gcp-5.4, Ubuntu:Pro:18.04:LTS: linux-hwe-5.4, Ubuntu:Pro:18.04:LTS: linux-oracle-5.4, Ubuntu:Pro:18.04:LTS: linux-raspi-5.4, Ubuntu:Pro:20.04:LTS: linux, Ubuntu:Pro:20.04:LTS: linux-aws, Ubuntu:Pro:20.04:LTS: linux-azure, Ubuntu:Pro:20.04:LTS: linux-gcp, Ubuntu:Pro:20.04:LTS: linux-iot and 6 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:
  - Ethernet bonding driver;
  - Network drivers;
  - F2FS file system;
  - Tracing infrastructure;
  - io_uring subsystem;
  - Networking core;
  - IUCV driver;
  - RxRPC session sockets;
(CVE-2022-49149, CVE-2022-49170, CVE-2022-49182, CVE-2022-49201,
CVE-2024-53187, CVE-2024-53210, CVE-2024-56763, CVE-2026-43456,
CVE-2026-52910)&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:18.04:LTS: linux-azure-5.4, Ubuntu:Pro:18.04:LTS: linux-gcp-5.4, Ubuntu:Pro:18.04:LTS: linux-hwe-5.4, Ubuntu:Pro:18.04:LTS: linux-oracle-5.4, Ubuntu:Pro:18.04:LTS: linux-raspi-5.4, Ubuntu:Pro:20.04:LTS: linux, Ubuntu:Pro:20.04:LTS: linux-aws, Ubuntu:Pro:20.04:LTS: linux-azure, Ubuntu:Pro:20.04:LTS: linux-gcp, Ubuntu:Pro:20.04:LTS: linux-iot and 6 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:
  - Ethernet bonding driver;
  - Network drivers;
  - F2FS file system;
  - Tracing infrastructure;
  - io_uring subsystem;
  - Networking core;
  - IUCV driver;
  - RxRPC session sockets;
(CVE-2022-49149, CVE-2022-49170, CVE-2022-49182, CVE-2022-49201,
CVE-2024-53187, CVE-2024-53210, CVE-2024-56763, CVE-2026-43456,
CVE-2026-52910)&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/usn-8919-1</guid>
    </item>
  </channel>
</rss>
