<?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>Sun, 04 Oct 2026 06:56:18 +0000</lastBuildDate>
    <item>
      <title>ALSA-2024:3618 — Moderate: kernel update</title>
      <link>https://cve.radiocsirt.org/vuln/alsa-2024:3618</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; AlmaLinux:8: bpftool, AlmaLinux:8: kernel, AlmaLinux:8: kernel-abi-stablelists, AlmaLinux:8: kernel-core, AlmaLinux:8: kernel-cross-headers, AlmaLinux:8: kernel-debug, AlmaLinux:8: kernel-debug-core, AlmaLinux:8: kernel-debug-devel, AlmaLinux:8: kernel-debug-modules, AlmaLinux:8: kernel-debug-modules-extra and 15 more&lt;/p&gt;
&lt;p&gt;The kernel packages contain the Linux kernel, the core of any Linux operating system.&lt;/p&gt;
&lt;p&gt;Security Fix(es):&lt;/p&gt;
&lt;p&gt;* kernel: Marvin vulnerability side-channel leakage in the RSA decryption
operation (CVE-2023-6240)
* kernel: Information disclosure in vhost/vhost.c:vhost_new_msg()
(CVE-2024-0340)
* kernel: untrusted VMM can trigger int80 syscall handling (CVE-2024-25744)
* kernel: i2c: i801: Fix block process call transactions (CVE-2024-26593)
* kernel: pvrusb2: fix use after free on context disconnection (CVE-2023-52445)
* kernel: x86/fpu: Stop relying on userspace for info to fault in xsave buffer
that cause loop forever (CVE-2024-26603)
* kernel: use after free in i2c (CVE-2019-25162)
* kernel: i2c: validate user data in compat ioctl (CVE-2021-46934)
* kernel: media: dvbdev: Fix memory leak in dvb_media_device_free()
(CVE-2020-36777)
* kernel: usb: hub: Guard against accesses to uninitialized BOS descriptors
(CVE-2023-52477)
* kernel: mtd: require write permissions for locking and badblock ioctls
(CVE-2021-47055)
* kernel: net/smc: fix illegal rmb_desc access in SMC-D connection dump
(CVE-2024-26615)
* kernel: vt: fix memory overlapping when deleting chars in the buffer
(CVE-2022-48627)
* kernel: Integer Overflow in raid5_cache_count (CVE-2024-23307)
* kernel: media: uvcvideo: out-of-bounds read in uvc_query_v4l2_menu()
(CVE-2023-52565)
* kernel: net: bridge: data races indata-races in br_handle_frame_finish()
(CVE-2023-52578)
* kernel: net: usb: smsc75xx: Fix uninit-value access i…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; AlmaLinux:8: bpftool, AlmaLinux:8: kernel, AlmaLinux:8: kernel-abi-stablelists, AlmaLinux:8: kernel-core, AlmaLinux:8: kernel-cross-headers, AlmaLinux:8: kernel-debug, AlmaLinux:8: kernel-debug-core, AlmaLinux:8: kernel-debug-devel, AlmaLinux:8: kernel-debug-modules, AlmaLinux:8: kernel-debug-modules-extra and 15 more&lt;/p&gt;
&lt;p&gt;The kernel packages contain the Linux kernel, the core of any Linux operating system.&lt;/p&gt;
&lt;p&gt;Security Fix(es):&lt;/p&gt;
&lt;p&gt;* kernel: Marvin vulnerability side-channel leakage in the RSA decryption
operation (CVE-2023-6240)
* kernel: Information disclosure in vhost/vhost.c:vhost_new_msg()
(CVE-2024-0340)
* kernel: untrusted VMM can trigger int80 syscall handling (CVE-2024-25744)
* kernel: i2c: i801: Fix block process call transactions (CVE-2024-26593)
* kernel: pvrusb2: fix use after free on context disconnection (CVE-2023-52445)
* kernel: x86/fpu: Stop relying on userspace for info to fault in xsave buffer
that cause loop forever (CVE-2024-26603)
* kernel: use after free in i2c (CVE-2019-25162)
* kernel: i2c: validate user data in compat ioctl (CVE-2021-46934)
* kernel: media: dvbdev: Fix memory leak in dvb_media_device_free()
(CVE-2020-36777)
* kernel: usb: hub: Guard against accesses to uninitialized BOS descriptors
(CVE-2023-52477)
* kernel: mtd: require write permissions for locking and badblock ioctls
(CVE-2021-47055)
* kernel: net/smc: fix illegal rmb_desc access in SMC-D connection dump
(CVE-2024-26615)
* kernel: vt: fix memory overlapping when deleting chars in the buffer
(CVE-2022-48627)
* kernel: Integer Overflow in raid5_cache_count (CVE-2024-23307)
* kernel: media: uvcvideo: out-of-bounds read in uvc_query_v4l2_menu()
(CVE-2023-52565)
* kernel: net: bridge: data races indata-races in br_handle_frame_finish()
(CVE-2023-52578)
* kernel: net: usb: smsc75xx: Fix uninit-value access i…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/alsa-2024:3618</guid>
    </item>
    <item>
      <title>bdu:2025-03651</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2025-03651</link>
      <description>bdu:2025-03651</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2025-03651</guid>
    </item>
    <item>
      <title>certfr-2024-avi-0363 — De multiples vulnérabilités ont été découvertes dans &lt;span
class="textit"&gt;le noyau Linux de SUSE&lt;/span&gt;. Certaines d'en…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2024-avi-0363</link>
      <description>certfr-2024-avi-0363</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2024-avi-0363</guid>
    </item>
    <item>
      <title>EUVD-2026-309550</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-309550</link>
      <description>EUVD-2026-309550</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-309550</guid>
    </item>
    <item>
      <title>fkie_cve-2021-47118</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2021-47118</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;pid: take a reference when initializing `cad_pid`&lt;/p&gt;
&lt;p&gt;During boot, kernel_init_freeable() initializes `cad_pid` to the init
task&amp;#39;s struct pid.  Later on, we may change `cad_pid` via a sysctl, and
when this happens proc_do_cad_pid() will increment the refcount on the
new pid via get_pid(), and will decrement the refcount on the old pid
via put_pid().  As we never called get_pid() when we initialized
`cad_pid`, we decrement a reference we never incremented, can therefore
free the init task&amp;#39;s struct pid early.  As there can be dangling
references to the struct pid, we can later encounter a use-after-free
(e.g.  when delivering signals).&lt;/p&gt;
&lt;p&gt;This was spotted when fuzzing v5.13-rc3 with Syzkaller, but seems to
have been around since the conversion of `cad_pid` to struct pid in
commit 9ec52099e4b8 (&amp;#34;[PATCH] replace cad_pid by a struct pid&amp;#34;) from the
pre-KASAN stone age of v2.6.19.&lt;/p&gt;
&lt;p&gt;Fix this by getting a reference to the init task&amp;#39;s struct pid when we
assign it to `cad_pid`.&lt;/p&gt;
&lt;p&gt;Full KASAN splat below.&lt;/p&gt;
&lt;p&gt;==================================================================
   BUG: KASAN: use-after-free in ns_of_pid include/linux/pid.h:153 [inline]
   BUG: KASAN: use-after-free in task_active_pid_ns+0xc0/0xc8 kernel/pid.c:509
   Read of size 4 at addr ffff23794dda0004 by task syz-executor.0/273&lt;/p&gt;
&lt;p&gt;CPU: 1 PID: 273 Comm: syz-executor.0 Not tainted 5.12.0-00001-g9aef892b2d15 #1
   Hardware name: linux,dummy-virt (DT)
   Call t…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;pid: take a reference when initializing `cad_pid`&lt;/p&gt;
&lt;p&gt;During boot, kernel_init_freeable() initializes `cad_pid` to the init
task&amp;#39;s struct pid.  Later on, we may change `cad_pid` via a sysctl, and
when this happens proc_do_cad_pid() will increment the refcount on the
new pid via get_pid(), and will decrement the refcount on the old pid
via put_pid().  As we never called get_pid() when we initialized
`cad_pid`, we decrement a reference we never incremented, can therefore
free the init task&amp;#39;s struct pid early.  As there can be dangling
references to the struct pid, we can later encounter a use-after-free
(e.g.  when delivering signals).&lt;/p&gt;
&lt;p&gt;This was spotted when fuzzing v5.13-rc3 with Syzkaller, but seems to
have been around since the conversion of `cad_pid` to struct pid in
commit 9ec52099e4b8 (&amp;#34;[PATCH] replace cad_pid by a struct pid&amp;#34;) from the
pre-KASAN stone age of v2.6.19.&lt;/p&gt;
&lt;p&gt;Fix this by getting a reference to the init task&amp;#39;s struct pid when we
assign it to `cad_pid`.&lt;/p&gt;
&lt;p&gt;Full KASAN splat below.&lt;/p&gt;
&lt;p&gt;==================================================================
   BUG: KASAN: use-after-free in ns_of_pid include/linux/pid.h:153 [inline]
   BUG: KASAN: use-after-free in task_active_pid_ns+0xc0/0xc8 kernel/pid.c:509
   Read of size 4 at addr ffff23794dda0004 by task syz-executor.0/273&lt;/p&gt;
&lt;p&gt;CPU: 1 PID: 273 Comm: syz-executor.0 Not tainted 5.12.0-00001-g9aef892b2d15 #1
   Hardware name: linux,dummy-virt (DT)
   Call t…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2021-47118</guid>
    </item>
    <item>
      <title>GHSA-f22j-p6f5-7h8x</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-f22j-p6f5-7h8x</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;pid: take a reference when initializing `cad_pid`&lt;/p&gt;
&lt;p&gt;During boot, kernel_init_freeable() initializes `cad_pid` to the init
task&amp;#39;s struct pid.  Later on, we may change `cad_pid` via a sysctl, and
when this happens proc_do_cad_pid() will increment the refcount on the
new pid via get_pid(), and will decrement the refcount on the old pid
via put_pid().  As we never called get_pid() when we initialized
`cad_pid`, we decrement a reference we never incremented, can therefore
free the init task&amp;#39;s struct pid early.  As there can be dangling
references to the struct pid, we can later encounter a use-after-free
(e.g.  when delivering signals).&lt;/p&gt;
&lt;p&gt;This was spotted when fuzzing v5.13-rc3 with Syzkaller, but seems to
have been around since the conversion of `cad_pid` to struct pid in
commit 9ec52099e4b8 (&amp;#34;[PATCH] replace cad_pid by a struct pid&amp;#34;) from the
pre-KASAN stone age of v2.6.19.&lt;/p&gt;
&lt;p&gt;Fix this by getting a reference to the init task&amp;#39;s struct pid when we
assign it to `cad_pid`.&lt;/p&gt;
&lt;p&gt;Full KASAN splat below.&lt;/p&gt;
&lt;p&gt;==================================================================
   BUG: KASAN: use-after-free in ns_of_pid include/linux/pid.h:153 [inline]
   BUG: KASAN: use-after-free in task_active_pid_ns+0xc0/0xc8 kernel/pid.c:509
   Read of size 4 at addr ffff23794dda0004 by task syz-executor.0/273&lt;/p&gt;
&lt;p&gt;CPU: 1 PID: 273 Comm: syz-executor.0 Not tainted 5.12.0-00001-g9aef892b2d15 #1
   Hardware name: linux,dummy-virt (DT)
   Call t…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;pid: take a reference when initializing `cad_pid`&lt;/p&gt;
&lt;p&gt;During boot, kernel_init_freeable() initializes `cad_pid` to the init
task&amp;#39;s struct pid.  Later on, we may change `cad_pid` via a sysctl, and
when this happens proc_do_cad_pid() will increment the refcount on the
new pid via get_pid(), and will decrement the refcount on the old pid
via put_pid().  As we never called get_pid() when we initialized
`cad_pid`, we decrement a reference we never incremented, can therefore
free the init task&amp;#39;s struct pid early.  As there can be dangling
references to the struct pid, we can later encounter a use-after-free
(e.g.  when delivering signals).&lt;/p&gt;
&lt;p&gt;This was spotted when fuzzing v5.13-rc3 with Syzkaller, but seems to
have been around since the conversion of `cad_pid` to struct pid in
commit 9ec52099e4b8 (&amp;#34;[PATCH] replace cad_pid by a struct pid&amp;#34;) from the
pre-KASAN stone age of v2.6.19.&lt;/p&gt;
&lt;p&gt;Fix this by getting a reference to the init task&amp;#39;s struct pid when we
assign it to `cad_pid`.&lt;/p&gt;
&lt;p&gt;Full KASAN splat below.&lt;/p&gt;
&lt;p&gt;==================================================================
   BUG: KASAN: use-after-free in ns_of_pid include/linux/pid.h:153 [inline]
   BUG: KASAN: use-after-free in task_active_pid_ns+0xc0/0xc8 kernel/pid.c:509
   Read of size 4 at addr ffff23794dda0004 by task syz-executor.0/273&lt;/p&gt;
&lt;p&gt;CPU: 1 PID: 273 Comm: syz-executor.0 Not tainted 5.12.0-00001-g9aef892b2d15 #1
   Hardware name: linux,dummy-virt (DT)
   Call t…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-f22j-p6f5-7h8x</guid>
    </item>
    <item>
      <title>gsd-2021-47118</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2021-47118</link>
      <description>gsd-2021-47118</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2021-47118</guid>
    </item>
    <item>
      <title>RHSA-2024:3618 — Red Hat Security Advisory: kernel update</title>
      <link>https://cve.radiocsirt.org/vuln/rhsa-2024:3618</link>
      <description>&lt;p&gt;kernel: use after free in i2c kernel: media: dvbdev: Fix memory leak in dvb_media_device_free() kernel: i2c: validate user data in compat ioctl kernel: net:emac/emac-mac: Fix a use after free in emac_mac_tx_buf_send kernel: mtd: require write permissions for locking and badblock ioctls kernel: pid: take a reference when initializing `cad_pid` kernel: i2c: i801: Don&amp;amp;#39;t generate an interrupt on bus reset kernel: net: usb: fix memory leak in smsc75xx_bind kernel: tty: tty_buffer: Fix the softlockup issue in flush_to_ldisc kernel: vt: fix memory overlapping when deleting chars in the buffer kernel: powerpc/pseries: Fix potential memleak in papr_get_attr() kernel: Marvin vulnerability side-channel leakage in the RSA decryption operation kernel: uio: Fix use-after-free in uio_open kernel: pvrusb2: fix use after free on context disconnection kernel: usb: hub: Guard against accesses to uninitialized BOS descriptors kernel: RDMA/siw: Fix connection failure handling kernel: platform/x86: think-lmi: Fix reference leak kernel: net: usb: smsc75xx: Fix uninit-value access in __smsc75xx_read_reg kernel: media: uvcvideo: out-of-bounds read in uvc_query_v4l2_menu() kernel: net: bridge: data races indata-races in br_handle_frame_finish() kernel: wifi: ath9k: Fix potential array-index-out-of-bounds read in ath9k_htc_txstatus() kernel: wifi: rt2x00: restart beacon queue when hardware reset kernel: s390/ptrace: handle setting of fpc register correctly kernel: powerpc/lib: Validate size for ve…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;kernel: use after free in i2c kernel: media: dvbdev: Fix memory leak in dvb_media_device_free() kernel: i2c: validate user data in compat ioctl kernel: net:emac/emac-mac: Fix a use after free in emac_mac_tx_buf_send kernel: mtd: require write permissions for locking and badblock ioctls kernel: pid: take a reference when initializing `cad_pid` kernel: i2c: i801: Don&amp;amp;#39;t generate an interrupt on bus reset kernel: net: usb: fix memory leak in smsc75xx_bind kernel: tty: tty_buffer: Fix the softlockup issue in flush_to_ldisc kernel: vt: fix memory overlapping when deleting chars in the buffer kernel: powerpc/pseries: Fix potential memleak in papr_get_attr() kernel: Marvin vulnerability side-channel leakage in the RSA decryption operation kernel: uio: Fix use-after-free in uio_open kernel: pvrusb2: fix use after free on context disconnection kernel: usb: hub: Guard against accesses to uninitialized BOS descriptors kernel: RDMA/siw: Fix connection failure handling kernel: platform/x86: think-lmi: Fix reference leak kernel: net: usb: smsc75xx: Fix uninit-value access in __smsc75xx_read_reg kernel: media: uvcvideo: out-of-bounds read in uvc_query_v4l2_menu() kernel: net: bridge: data races indata-races in br_handle_frame_finish() kernel: wifi: ath9k: Fix potential array-index-out-of-bounds read in ath9k_htc_txstatus() kernel: wifi: rt2x00: restart beacon queue when hardware reset kernel: s390/ptrace: handle setting of fpc register correctly kernel: powerpc/lib: Validate size for ve…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rhsa-2024:3618</guid>
    </item>
    <item>
      <title>RHSA-2024:3627 — Red Hat Security Advisory: kernel-rt security and bug fix update</title>
      <link>https://cve.radiocsirt.org/vuln/rhsa-2024:3627</link>
      <description>&lt;p&gt;kernel: use after free in i2c kernel: media: dvbdev: Fix memory leak in dvb_media_device_free() kernel: i2c: validate user data in compat ioctl kernel: net:emac/emac-mac: Fix a use after free in emac_mac_tx_buf_send kernel: mtd: require write permissions for locking and badblock ioctls kernel: pid: take a reference when initializing `cad_pid` kernel: i2c: i801: Don&amp;amp;#39;t generate an interrupt on bus reset kernel: net: usb: fix memory leak in smsc75xx_bind kernel: tty: tty_buffer: Fix the softlockup issue in flush_to_ldisc kernel: vt: fix memory overlapping when deleting chars in the buffer kernel: Marvin vulnerability side-channel leakage in the RSA decryption operation kernel: uio: Fix use-after-free in uio_open kernel: pvrusb2: fix use after free on context disconnection kernel: usb: hub: Guard against accesses to uninitialized BOS descriptors kernel: RDMA/siw: Fix connection failure handling kernel: platform/x86: think-lmi: Fix reference leak kernel: net: usb: smsc75xx: Fix uninit-value access in __smsc75xx_read_reg kernel: media: uvcvideo: out-of-bounds read in uvc_query_v4l2_menu() kernel: net: bridge: data races indata-races in br_handle_frame_finish() kernel: wifi: ath9k: Fix potential array-index-out-of-bounds read in ath9k_htc_txstatus() kernel: wifi: rt2x00: restart beacon queue when hardware reset kernel: net/sched: act_ct: fix skb leak and crash on ooo frags kernel: Information disclosure in vhost/vhost.c:vhost_new_msg() kernel: Integer Overflow in raid5_cache_co…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;kernel: use after free in i2c kernel: media: dvbdev: Fix memory leak in dvb_media_device_free() kernel: i2c: validate user data in compat ioctl kernel: net:emac/emac-mac: Fix a use after free in emac_mac_tx_buf_send kernel: mtd: require write permissions for locking and badblock ioctls kernel: pid: take a reference when initializing `cad_pid` kernel: i2c: i801: Don&amp;amp;#39;t generate an interrupt on bus reset kernel: net: usb: fix memory leak in smsc75xx_bind kernel: tty: tty_buffer: Fix the softlockup issue in flush_to_ldisc kernel: vt: fix memory overlapping when deleting chars in the buffer kernel: Marvin vulnerability side-channel leakage in the RSA decryption operation kernel: uio: Fix use-after-free in uio_open kernel: pvrusb2: fix use after free on context disconnection kernel: usb: hub: Guard against accesses to uninitialized BOS descriptors kernel: RDMA/siw: Fix connection failure handling kernel: platform/x86: think-lmi: Fix reference leak kernel: net: usb: smsc75xx: Fix uninit-value access in __smsc75xx_read_reg kernel: media: uvcvideo: out-of-bounds read in uvc_query_v4l2_menu() kernel: net: bridge: data races indata-races in br_handle_frame_finish() kernel: wifi: ath9k: Fix potential array-index-out-of-bounds read in ath9k_htc_txstatus() kernel: wifi: rt2x00: restart beacon queue when hardware reset kernel: net/sched: act_ct: fix skb leak and crash on ooo frags kernel: Information disclosure in vhost/vhost.c:vhost_new_msg() kernel: Integer Overflow in raid5_cache_co…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rhsa-2024:3627</guid>
    </item>
    <item>
      <title>SUSE-SU-2024:1454-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2024:1454-1</link>
      <description>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/suse-su-2024:1454-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2021-47118</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2021-47118</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe and 107 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: pid: take a reference when initializing `cad_pid` During boot, kernel_init_freeable() initializes `cad_pid` to the init task&amp;#39;s struct pid.  Later on, we may change `cad_pid` via a sysctl, and when this happens proc_do_cad_pid() will increment the refcount on the new pid via get_pid(), and will decrement the refcount on the old pid via put_pid().  As we never called get_pid() when we initialized `cad_pid`, we decrement a reference we never incremented, can therefore free the init task&amp;#39;s struct pid early.  As there can be dangling references to the struct pid, we can later encounter a use-after-free (e.g.  when delivering signals). This was spotted when fuzzing v5.13-rc3 with Syzkaller, but seems to have been around since the conversion of `cad_pid` to struct pid in commit 9ec52099e4b8 (&amp;#34;[PATCH] replace cad_pid by a struct pid&amp;#34;) from the pre-KASAN stone age of v2.6.19. Fix this by getting a reference to the init task&amp;#39;s struct pid when we assign it to `cad_pid`. Full KASAN splat below.    ==================================================================    BUG: KASAN: use-after-free in ns_of_pid include/linux/pid.h:153 [inline]    BUG: KASAN: use-after-free in task_active_pid_ns+0xc0/0xc8 kernel/pid.c:509    Read of size 4 at addr ffff23794dda0004 by task syz-executor.0/273    CPU: 1 PID: 273 Comm: syz-executor.0 Not tainted 5.12.0-00001-g9aef892b2d15 #1    Hardware name: linux,dummy-virt (DT)    Call trace:…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe and 107 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: pid: take a reference when initializing `cad_pid` During boot, kernel_init_freeable() initializes `cad_pid` to the init task&amp;#39;s struct pid.  Later on, we may change `cad_pid` via a sysctl, and when this happens proc_do_cad_pid() will increment the refcount on the new pid via get_pid(), and will decrement the refcount on the old pid via put_pid().  As we never called get_pid() when we initialized `cad_pid`, we decrement a reference we never incremented, can therefore free the init task&amp;#39;s struct pid early.  As there can be dangling references to the struct pid, we can later encounter a use-after-free (e.g.  when delivering signals). This was spotted when fuzzing v5.13-rc3 with Syzkaller, but seems to have been around since the conversion of `cad_pid` to struct pid in commit 9ec52099e4b8 (&amp;#34;[PATCH] replace cad_pid by a struct pid&amp;#34;) from the pre-KASAN stone age of v2.6.19. Fix this by getting a reference to the init task&amp;#39;s struct pid when we assign it to `cad_pid`. Full KASAN splat below.    ==================================================================    BUG: KASAN: use-after-free in ns_of_pid include/linux/pid.h:153 [inline]    BUG: KASAN: use-after-free in task_active_pid_ns+0xc0/0xc8 kernel/pid.c:509    Read of size 4 at addr ffff23794dda0004 by task syz-executor.0/273    CPU: 1 PID: 273 Comm: syz-executor.0 Not tainted 5.12.0-00001-g9aef892b2d15 #1    Hardware name: linux,dummy-virt (DT)    Call trace:…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2021-47118</guid>
    </item>
    <item>
      <title>WID-SEC-W-2024-0652 — Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2024-0652</link>
      <description>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen im Linux-Kernel ausnutzen, um einen Denial-of-Service-Zustand herbeizuführen oder einen nicht spezifizierten Angriff durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen im Linux-Kernel ausnutzen, um einen Denial-of-Service-Zustand herbeizuführen oder einen nicht spezifizierten Angriff durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2024-0652</guid>
    </item>
  </channel>
</rss>
