<?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>Thu, 15 Oct 2026 12:26:56 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-43853 — cgroup/cpuset: Prevent UAF in proc_cpuset_show()</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2024-43853</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;cgroup/cpuset: Prevent UAF in proc_cpuset_show()&lt;/p&gt;
&lt;p&gt;An UAF can happen when /proc/cpuset is read as reported in [1].&lt;/p&gt;
&lt;p&gt;This can be reproduced by the following methods:
1.add an mdelay(1000) before acquiring the cgroup_lock In the
 cgroup_path_ns function.
2.$cat /proc/&amp;lt;pid&amp;gt;/cpuset   repeatly.
3.$mount -t cgroup -o cpuset cpuset /sys/fs/cgroup/cpuset/
$umount /sys/fs/cgroup/cpuset/   repeatly.&lt;/p&gt;
&lt;p&gt;The race that cause this bug can be shown as below:&lt;/p&gt;
&lt;p&gt;(umount)		|	(cat /proc/&amp;lt;pid&amp;gt;/cpuset)
css_release		|	proc_cpuset_show
css_release_work_fn	|	css = task_get_css(tsk, cpuset_cgrp_id);
css_free_rwork_fn	|	cgroup_path_ns(css-&amp;gt;cgroup, ...);
cgroup_destroy_root	|	mutex_lock(&amp;amp;cgroup_mutex);
rebind_subsystems	|
cgroup_free_root 	|
			|	// cgrp was freed, UAF
			|	cgroup_path_ns_locked(cgrp,..);&lt;/p&gt;
&lt;p&gt;When the cpuset is initialized, the root node top_cpuset.css.cgrp
will point to &amp;amp;cgrp_dfl_root.cgrp. In cgroup v1, the mount operation will
allocate cgroup_root, and top_cpuset.css.cgrp will point to the allocated
&amp;amp;cgroup_root.cgrp. When the umount operation is executed,
top_cpuset.css.cgrp will be rebound to &amp;amp;cgrp_dfl_root.cgrp.&lt;/p&gt;
&lt;p&gt;The problem is that when rebinding to cgrp_dfl_root, there are cases
where the cgroup_root allocated by setting up the root for cgroup v1
is cached. This could lead to a Use-After-Free (UAF) if it is
subsequently freed. The descendant cgroups of cgroup v1 can only be
freed after the css is released. However,…&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;cgroup/cpuset: Prevent UAF in proc_cpuset_show()&lt;/p&gt;
&lt;p&gt;An UAF can happen when /proc/cpuset is read as reported in [1].&lt;/p&gt;
&lt;p&gt;This can be reproduced by the following methods:
1.add an mdelay(1000) before acquiring the cgroup_lock In the
 cgroup_path_ns function.
2.$cat /proc/&amp;lt;pid&amp;gt;/cpuset   repeatly.
3.$mount -t cgroup -o cpuset cpuset /sys/fs/cgroup/cpuset/
$umount /sys/fs/cgroup/cpuset/   repeatly.&lt;/p&gt;
&lt;p&gt;The race that cause this bug can be shown as below:&lt;/p&gt;
&lt;p&gt;(umount)		|	(cat /proc/&amp;lt;pid&amp;gt;/cpuset)
css_release		|	proc_cpuset_show
css_release_work_fn	|	css = task_get_css(tsk, cpuset_cgrp_id);
css_free_rwork_fn	|	cgroup_path_ns(css-&amp;gt;cgroup, ...);
cgroup_destroy_root	|	mutex_lock(&amp;amp;cgroup_mutex);
rebind_subsystems	|
cgroup_free_root 	|
			|	// cgrp was freed, UAF
			|	cgroup_path_ns_locked(cgrp,..);&lt;/p&gt;
&lt;p&gt;When the cpuset is initialized, the root node top_cpuset.css.cgrp
will point to &amp;amp;cgrp_dfl_root.cgrp. In cgroup v1, the mount operation will
allocate cgroup_root, and top_cpuset.css.cgrp will point to the allocated
&amp;amp;cgroup_root.cgrp. When the umount operation is executed,
top_cpuset.css.cgrp will be rebound to &amp;amp;cgrp_dfl_root.cgrp.&lt;/p&gt;
&lt;p&gt;The problem is that when rebinding to cgrp_dfl_root, there are cases
where the cgroup_root allocated by setting up the root for cgroup v1
is cached. This could lead to a Use-After-Free (UAF) if it is
subsequently freed. The descendant cgroups of cgroup v1 can only be
freed after the css is released. However,…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2024-43853</guid>
    </item>
    <item>
      <title>USN-7088-1 — linux, linux-gcp, linux-gcp-5.4, linux-gkeop, linux-hwe-5.4, linux-ibm, linux-ibm-5.4 vulnerabilities</title>
      <link>https://cve.radiocsirt.org/vuln/usn-7088-1</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:18.04:LTS: linux-gcp-5.4, Ubuntu:Pro:18.04:LTS: linux-hwe-5.4, Ubuntu:Pro:18.04:LTS: linux-ibm-5.4, Ubuntu:20.04:LTS: linux, Ubuntu:20.04:LTS: linux-gcp, Ubuntu:20.04:LTS: linux-gkeop, Ubuntu:20.04:LTS: linux-ibm&lt;/p&gt;
&lt;p&gt;Ziming Zhang discovered that the VMware Virtual GPU DRM driver in the Linux
kernel contained an integer overflow vulnerability. A local attacker could
use this to cause a denial of service (system crash). (CVE-2022-36402)&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;
  - PowerPC architecture;
  - User-Mode Linux (UML);
  - x86 architecture;
  - Block layer subsystem;
  - Cryptographic API;
  - Android drivers;
  - Serial ATA and Parallel ATA drivers;
  - ATM drivers;
  - Drivers core;
  - CPU frequency scaling framework;
  - Device frequency scaling framework;
  - GPU drivers;
  - HID subsystem;
  - Hardware monitoring drivers;
  - InfiniBand drivers;
  - Input Device core drivers;
  - IOMMU subsystem;
  - IRQ chip drivers;
  - ISDN/mISDN subsystem;
  - LED subsystem;
  - Multiple devices driver;
  - Media drivers;
  - EEPROM drivers;
  - VMware VMCI Driver;
  - MMC subsystem;
  - Network drivers;
  - Near Field Communication (NFC) drivers;
  - NVME drivers;
  - Device tree and open firmware driver;
  - Parport drivers;
  - PCI subsystem;
  - Pin controllers subsystem;
  - Remote Processor subsystem;
  - S/390 drivers;
  - SCSI drivers;
  - QCOM SoC drivers;
  - Direct Digital Synthesis drivers;
  - TTY drivers;
  - Userspace I/O drivers;
  - DesignWare USB3 driver;
  - USB subsystem;
  - BTRFS file system;
  - File sy…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:18.04:LTS: linux-gcp-5.4, Ubuntu:Pro:18.04:LTS: linux-hwe-5.4, Ubuntu:Pro:18.04:LTS: linux-ibm-5.4, Ubuntu:20.04:LTS: linux, Ubuntu:20.04:LTS: linux-gcp, Ubuntu:20.04:LTS: linux-gkeop, Ubuntu:20.04:LTS: linux-ibm&lt;/p&gt;
&lt;p&gt;Ziming Zhang discovered that the VMware Virtual GPU DRM driver in the Linux
kernel contained an integer overflow vulnerability. A local attacker could
use this to cause a denial of service (system crash). (CVE-2022-36402)&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;
  - PowerPC architecture;
  - User-Mode Linux (UML);
  - x86 architecture;
  - Block layer subsystem;
  - Cryptographic API;
  - Android drivers;
  - Serial ATA and Parallel ATA drivers;
  - ATM drivers;
  - Drivers core;
  - CPU frequency scaling framework;
  - Device frequency scaling framework;
  - GPU drivers;
  - HID subsystem;
  - Hardware monitoring drivers;
  - InfiniBand drivers;
  - Input Device core drivers;
  - IOMMU subsystem;
  - IRQ chip drivers;
  - ISDN/mISDN subsystem;
  - LED subsystem;
  - Multiple devices driver;
  - Media drivers;
  - EEPROM drivers;
  - VMware VMCI Driver;
  - MMC subsystem;
  - Network drivers;
  - Near Field Communication (NFC) drivers;
  - NVME drivers;
  - Device tree and open firmware driver;
  - Parport drivers;
  - PCI subsystem;
  - Pin controllers subsystem;
  - Remote Processor subsystem;
  - S/390 drivers;
  - SCSI drivers;
  - QCOM SoC drivers;
  - Direct Digital Synthesis drivers;
  - TTY drivers;
  - Userspace I/O drivers;
  - DesignWare USB3 driver;
  - USB subsystem;
  - BTRFS file system;
  - File sy…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/usn-7088-1</guid>
    </item>
  </channel>
</rss>
