<?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 05:11:00 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-42271 — net/iucv: fix use after free in iucv_sock_close()</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2024-42271</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/iucv: fix use after free in iucv_sock_close()&lt;/p&gt;
&lt;p&gt;iucv_sever_path() is called from process context and from bh context.
iucv-&amp;gt;path is used as indicator whether somebody else is taking care of
severing the path (or it is already removed / never existed).
This needs to be done with atomic compare and swap, otherwise there is a
small window where iucv_sock_close() will try to work with a path that has
already been severed and freed by iucv_callback_connrej() called by
iucv_tasklet_fn().&lt;/p&gt;
&lt;p&gt;Example:
[452744.123844] Call Trace:
[452744.123845] ([&amp;lt;0000001e87f03880&amp;gt;] 0x1e87f03880)
[452744.123966]  [&amp;lt;00000000d593001e&amp;gt;] iucv_path_sever+0x96/0x138
[452744.124330]  [&amp;lt;000003ff801ddbca&amp;gt;] iucv_sever_path+0xc2/0xd0 [af_iucv]
[452744.124336]  [&amp;lt;000003ff801e01b6&amp;gt;] iucv_sock_close+0xa6/0x310 [af_iucv]
[452744.124341]  [&amp;lt;000003ff801e08cc&amp;gt;] iucv_sock_release+0x3c/0xd0 [af_iucv]
[452744.124345]  [&amp;lt;00000000d574794e&amp;gt;] __sock_release+0x5e/0xe8
[452744.124815]  [&amp;lt;00000000d5747a0c&amp;gt;] sock_close+0x34/0x48
[452744.124820]  [&amp;lt;00000000d5421642&amp;gt;] __fput+0xba/0x268
[452744.124826]  [&amp;lt;00000000d51b382c&amp;gt;] task_work_run+0xbc/0xf0
[452744.124832]  [&amp;lt;00000000d5145710&amp;gt;] do_notify_resume+0x88/0x90
[452744.124841]  [&amp;lt;00000000d5978096&amp;gt;] system_call+0xe2/0x2c8
[452744.125319] Last Breaking-Event-Address:
[452744.125321]  [&amp;lt;00000000d5930018&amp;gt;] iucv_path_sever+0x90/0x138
[452744.125324]
[452744.125325] Kernel panic - not syncing: Fatal exception in inter…&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/iucv: fix use after free in iucv_sock_close()&lt;/p&gt;
&lt;p&gt;iucv_sever_path() is called from process context and from bh context.
iucv-&amp;gt;path is used as indicator whether somebody else is taking care of
severing the path (or it is already removed / never existed).
This needs to be done with atomic compare and swap, otherwise there is a
small window where iucv_sock_close() will try to work with a path that has
already been severed and freed by iucv_callback_connrej() called by
iucv_tasklet_fn().&lt;/p&gt;
&lt;p&gt;Example:
[452744.123844] Call Trace:
[452744.123845] ([&amp;lt;0000001e87f03880&amp;gt;] 0x1e87f03880)
[452744.123966]  [&amp;lt;00000000d593001e&amp;gt;] iucv_path_sever+0x96/0x138
[452744.124330]  [&amp;lt;000003ff801ddbca&amp;gt;] iucv_sever_path+0xc2/0xd0 [af_iucv]
[452744.124336]  [&amp;lt;000003ff801e01b6&amp;gt;] iucv_sock_close+0xa6/0x310 [af_iucv]
[452744.124341]  [&amp;lt;000003ff801e08cc&amp;gt;] iucv_sock_release+0x3c/0xd0 [af_iucv]
[452744.124345]  [&amp;lt;00000000d574794e&amp;gt;] __sock_release+0x5e/0xe8
[452744.124815]  [&amp;lt;00000000d5747a0c&amp;gt;] sock_close+0x34/0x48
[452744.124820]  [&amp;lt;00000000d5421642&amp;gt;] __fput+0xba/0x268
[452744.124826]  [&amp;lt;00000000d51b382c&amp;gt;] task_work_run+0xbc/0xf0
[452744.124832]  [&amp;lt;00000000d5145710&amp;gt;] do_notify_resume+0x88/0x90
[452744.124841]  [&amp;lt;00000000d5978096&amp;gt;] system_call+0xe2/0x2c8
[452744.125319] Last Breaking-Event-Address:
[452744.125321]  [&amp;lt;00000000d5930018&amp;gt;] iucv_path_sever+0x90/0x138
[452744.125324]
[452744.125325] Kernel panic - not syncing: Fatal exception in inter…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2024-42271</guid>
    </item>
    <item>
      <title>USN-7069-1 — linux, linux-aws, linux-aws-hwe, linux-azure-4.15, linux-gcp, linux-gcp-4.15, linux-hwe, linux-kvm, linux-oracle vulner…</title>
      <link>https://cve.radiocsirt.org/vuln/usn-7069-1</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe, Ubuntu:Pro:16.04:LTS: linux-oracle, Ubuntu:Pro:18.04:LTS: linux, Ubuntu:Pro:18.04:LTS: linux-aws, Ubuntu:Pro:18.04:LTS: linux-azure-4.15, Ubuntu:Pro:18.04:LTS: linux-gcp-4.15, Ubuntu:Pro:18.04:LTS: linux-kvm, Ubuntu:Pro:18.04:LTS: linux-oracle&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:
  - x86 architecture;
  - Cryptographic API;
  - CPU frequency scaling framework;
  - HW tracing;
  - ISDN/mISDN subsystem;
  - Media drivers;
  - Network drivers;
  - NVME drivers;
  - S/390 drivers;
  - SCSI drivers;
  - USB subsystem;
  - VFIO drivers;
  - Watchdog drivers;
  - JFS file system;
  - IRQ subsystem;
  - Core kernel;
  - Memory management;
  - Amateur Radio drivers;
  - IPv4 networking;
  - IPv6 networking;
  - IUCV driver;
  - Network traffic control;
  - TIPC protocol;
  - XFRM subsystem;
  - Integrity Measurement Architecture(IMA) framework;
  - SoC Audio for Freescale CPUs drivers;
  - USB sound devices;
(CVE-2024-36971, CVE-2024-42271, CVE-2024-38630, CVE-2024-38602,
CVE-2024-42223, CVE-2024-44940, CVE-2023-52528, CVE-2024-41097,
CVE-2024-27051, CVE-2024-42157, CVE-2024-46673, CVE-2024-39494,
CVE-2024-42089, CVE-2024-41073, CVE-2024-26810, CVE-2024-26960,
CVE-2024-38611, CVE-2024-31076, CVE-2024-26754, CVE-2023-52510,
CVE-2024-40941, CVE-2024-45016, CVE-2024-38627, CVE-2024-38621,
CVE-2024-39487, CVE-2024-27436, CVE-2024-40901, CVE-2024-26812,
CVE-2024-42244, CVE-2024-42229, CVE-2024-43858, CVE-2024-42280,
CVE-2024-26641, CVE-2024-42284, CVE-2024-26602)&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe, Ubuntu:Pro:16.04:LTS: linux-oracle, Ubuntu:Pro:18.04:LTS: linux, Ubuntu:Pro:18.04:LTS: linux-aws, Ubuntu:Pro:18.04:LTS: linux-azure-4.15, Ubuntu:Pro:18.04:LTS: linux-gcp-4.15, Ubuntu:Pro:18.04:LTS: linux-kvm, Ubuntu:Pro:18.04:LTS: linux-oracle&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:
  - x86 architecture;
  - Cryptographic API;
  - CPU frequency scaling framework;
  - HW tracing;
  - ISDN/mISDN subsystem;
  - Media drivers;
  - Network drivers;
  - NVME drivers;
  - S/390 drivers;
  - SCSI drivers;
  - USB subsystem;
  - VFIO drivers;
  - Watchdog drivers;
  - JFS file system;
  - IRQ subsystem;
  - Core kernel;
  - Memory management;
  - Amateur Radio drivers;
  - IPv4 networking;
  - IPv6 networking;
  - IUCV driver;
  - Network traffic control;
  - TIPC protocol;
  - XFRM subsystem;
  - Integrity Measurement Architecture(IMA) framework;
  - SoC Audio for Freescale CPUs drivers;
  - USB sound devices;
(CVE-2024-36971, CVE-2024-42271, CVE-2024-38630, CVE-2024-38602,
CVE-2024-42223, CVE-2024-44940, CVE-2023-52528, CVE-2024-41097,
CVE-2024-27051, CVE-2024-42157, CVE-2024-46673, CVE-2024-39494,
CVE-2024-42089, CVE-2024-41073, CVE-2024-26810, CVE-2024-26960,
CVE-2024-38611, CVE-2024-31076, CVE-2024-26754, CVE-2023-52510,
CVE-2024-40941, CVE-2024-45016, CVE-2024-38627, CVE-2024-38621,
CVE-2024-39487, CVE-2024-27436, CVE-2024-40901, CVE-2024-26812,
CVE-2024-42244, CVE-2024-42229, CVE-2024-43858, CVE-2024-42280,
CVE-2024-26641, CVE-2024-42284, CVE-2024-26602)&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/usn-7069-1</guid>
    </item>
  </channel>
</rss>
