<?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>Sat, 03 Oct 2026 19:20:51 +0000</lastBuildDate>
    <item>
      <title>bdu:2024-07925</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2024-07925</link>
      <description>bdu:2024-07925</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2024-07925</guid>
    </item>
    <item>
      <title>BELL-CVE-2024-41001</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2024-41001</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2024-41001</guid>
    </item>
    <item>
      <title>certfr-2024-avi-0613 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian. Elles permettent à un attaquant de provo…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2024-avi-0613</link>
      <description>certfr-2024-avi-0613</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2024-avi-0613</guid>
    </item>
    <item>
      <title>EUVD-2026-312979</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-312979</link>
      <description>EUVD-2026-312979</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-312979</guid>
    </item>
    <item>
      <title>fkie_cve-2024-41001</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2024-41001</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;io_uring/sqpoll: work around a potential audit memory leak&lt;/p&gt;
&lt;p&gt;kmemleak complains that there&amp;#39;s a memory leak related to connect
handling:&lt;/p&gt;
&lt;p&gt;unreferenced object 0xffff0001093bdf00 (size 128):
comm &amp;#34;iou-sqp-455&amp;#34;, pid 457, jiffies 4294894164
hex dump (first 32 bytes):
02 00 fa ea 7f 00 00 01 00 00 00 00 00 00 00 00  ................
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
backtrace (crc 2e481b1a):
[&amp;lt;00000000c0a26af4&amp;gt;] kmemleak_alloc+0x30/0x38
[&amp;lt;000000009c30bb45&amp;gt;] kmalloc_trace+0x228/0x358
[&amp;lt;000000009da9d39f&amp;gt;] __audit_sockaddr+0xd0/0x138
[&amp;lt;0000000089a93e34&amp;gt;] move_addr_to_kernel+0x1a0/0x1f8
[&amp;lt;000000000b4e80e6&amp;gt;] io_connect_prep+0x1ec/0x2d4
[&amp;lt;00000000abfbcd99&amp;gt;] io_submit_sqes+0x588/0x1e48
[&amp;lt;00000000e7c25e07&amp;gt;] io_sq_thread+0x8a4/0x10e4
[&amp;lt;00000000d999b491&amp;gt;] ret_from_fork+0x10/0x20&lt;/p&gt;
&lt;p&gt;which can can happen if:&lt;/p&gt;
&lt;p&gt;1) The command type does something on the prep side that triggers an
   audit call.
2) The thread hasn&amp;#39;t done any operations before this that triggered
   an audit call inside -&amp;gt;issue(), where we have audit_uring_entry()
   and audit_uring_exit().&lt;/p&gt;
&lt;p&gt;Work around this by issuing a blanket NOP operation before the SQPOLL
does anything.&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;io_uring/sqpoll: work around a potential audit memory leak&lt;/p&gt;
&lt;p&gt;kmemleak complains that there&amp;#39;s a memory leak related to connect
handling:&lt;/p&gt;
&lt;p&gt;unreferenced object 0xffff0001093bdf00 (size 128):
comm &amp;#34;iou-sqp-455&amp;#34;, pid 457, jiffies 4294894164
hex dump (first 32 bytes):
02 00 fa ea 7f 00 00 01 00 00 00 00 00 00 00 00  ................
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
backtrace (crc 2e481b1a):
[&amp;lt;00000000c0a26af4&amp;gt;] kmemleak_alloc+0x30/0x38
[&amp;lt;000000009c30bb45&amp;gt;] kmalloc_trace+0x228/0x358
[&amp;lt;000000009da9d39f&amp;gt;] __audit_sockaddr+0xd0/0x138
[&amp;lt;0000000089a93e34&amp;gt;] move_addr_to_kernel+0x1a0/0x1f8
[&amp;lt;000000000b4e80e6&amp;gt;] io_connect_prep+0x1ec/0x2d4
[&amp;lt;00000000abfbcd99&amp;gt;] io_submit_sqes+0x588/0x1e48
[&amp;lt;00000000e7c25e07&amp;gt;] io_sq_thread+0x8a4/0x10e4
[&amp;lt;00000000d999b491&amp;gt;] ret_from_fork+0x10/0x20&lt;/p&gt;
&lt;p&gt;which can can happen if:&lt;/p&gt;
&lt;p&gt;1) The command type does something on the prep side that triggers an
   audit call.
2) The thread hasn&amp;#39;t done any operations before this that triggered
   an audit call inside -&amp;gt;issue(), where we have audit_uring_entry()
   and audit_uring_exit().&lt;/p&gt;
&lt;p&gt;Work around this by issuing a blanket NOP operation before the SQPOLL
does anything.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2024-41001</guid>
    </item>
    <item>
      <title>GHSA-25v2-v763-x228</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-25v2-v763-x228</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;io_uring/sqpoll: work around a potential audit memory leak&lt;/p&gt;
&lt;p&gt;kmemleak complains that there&amp;#39;s a memory leak related to connect
handling:&lt;/p&gt;
&lt;p&gt;unreferenced object 0xffff0001093bdf00 (size 128):
comm &amp;#34;iou-sqp-455&amp;#34;, pid 457, jiffies 4294894164
hex dump (first 32 bytes):
02 00 fa ea 7f 00 00 01 00 00 00 00 00 00 00 00  ................
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
backtrace (crc 2e481b1a):
[&amp;lt;00000000c0a26af4&amp;gt;] kmemleak_alloc+0x30/0x38
[&amp;lt;000000009c30bb45&amp;gt;] kmalloc_trace+0x228/0x358
[&amp;lt;000000009da9d39f&amp;gt;] __audit_sockaddr+0xd0/0x138
[&amp;lt;0000000089a93e34&amp;gt;] move_addr_to_kernel+0x1a0/0x1f8
[&amp;lt;000000000b4e80e6&amp;gt;] io_connect_prep+0x1ec/0x2d4
[&amp;lt;00000000abfbcd99&amp;gt;] io_submit_sqes+0x588/0x1e48
[&amp;lt;00000000e7c25e07&amp;gt;] io_sq_thread+0x8a4/0x10e4
[&amp;lt;00000000d999b491&amp;gt;] ret_from_fork+0x10/0x20&lt;/p&gt;
&lt;p&gt;which can can happen if:&lt;/p&gt;
&lt;p&gt;1) The command type does something on the prep side that triggers an
   audit call.
2) The thread hasn&amp;#39;t done any operations before this that triggered
   an audit call inside -&amp;gt;issue(), where we have audit_uring_entry()
   and audit_uring_exit().&lt;/p&gt;
&lt;p&gt;Work around this by issuing a blanket NOP operation before the SQPOLL
does anything.&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;io_uring/sqpoll: work around a potential audit memory leak&lt;/p&gt;
&lt;p&gt;kmemleak complains that there&amp;#39;s a memory leak related to connect
handling:&lt;/p&gt;
&lt;p&gt;unreferenced object 0xffff0001093bdf00 (size 128):
comm &amp;#34;iou-sqp-455&amp;#34;, pid 457, jiffies 4294894164
hex dump (first 32 bytes):
02 00 fa ea 7f 00 00 01 00 00 00 00 00 00 00 00  ................
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
backtrace (crc 2e481b1a):
[&amp;lt;00000000c0a26af4&amp;gt;] kmemleak_alloc+0x30/0x38
[&amp;lt;000000009c30bb45&amp;gt;] kmalloc_trace+0x228/0x358
[&amp;lt;000000009da9d39f&amp;gt;] __audit_sockaddr+0xd0/0x138
[&amp;lt;0000000089a93e34&amp;gt;] move_addr_to_kernel+0x1a0/0x1f8
[&amp;lt;000000000b4e80e6&amp;gt;] io_connect_prep+0x1ec/0x2d4
[&amp;lt;00000000abfbcd99&amp;gt;] io_submit_sqes+0x588/0x1e48
[&amp;lt;00000000e7c25e07&amp;gt;] io_sq_thread+0x8a4/0x10e4
[&amp;lt;00000000d999b491&amp;gt;] ret_from_fork+0x10/0x20&lt;/p&gt;
&lt;p&gt;which can can happen if:&lt;/p&gt;
&lt;p&gt;1) The command type does something on the prep side that triggers an
   audit call.
2) The thread hasn&amp;#39;t done any operations before this that triggered
   an audit call inside -&amp;gt;issue(), where we have audit_uring_entry()
   and audit_uring_exit().&lt;/p&gt;
&lt;p&gt;Work around this by issuing a blanket NOP operation before the SQPOLL
does anything.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-25v2-v763-x228</guid>
    </item>
    <item>
      <title>msrc_CVE-2024-41001 — io_uring/sqpoll: work around a potential audit memory leak</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2024-41001</link>
      <description>msrc_CVE-2024-41001</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2024-41001</guid>
    </item>
    <item>
      <title>OESA-2025-1097 — kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/oesa-2025-1097</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:24.03-LTS: kernel&lt;/p&gt;
&lt;p&gt;The Linux Kernel, the operating system core itself.&#13;
&#13;
Security Fix(es):&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ksmbd: fix potencial out-of-bounds when buffer offset is invalid&lt;/p&gt;
&lt;p&gt;I found potencial out-of-bounds when buffer offset fields of a few requests
is invalid. This patch set the minimum value of buffer offset field to
-&amp;amp;gt;Buffer offset to validate buffer length.(CVE-2024-26952)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ksmbd: fix slab-out-of-bounds in smb_strndup_from_utf16()&lt;/p&gt;
&lt;p&gt;If -&amp;amp;gt;NameOffset of smb2_create_req is smaller than Buffer offset of
smb2_create_req, slab-out-of-bounds read can happen from smb2_open.
This patch set the minimum value of the name offset to the buffer offset
to validate name length of smb2_create_req().(CVE-2024-26954)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;fpga: bridge: add owner module and take its refcount&lt;/p&gt;
&lt;p&gt;The current implementation of the fpga bridge assumes that the low-level
module registers a driver for the parent device and uses its owner pointer
to take the module&amp;amp;apos;s refcount. This approach is problematic since it can
lead to a null pointer dereference while attempting to get the bridge if
the parent device does not have a driver.&lt;/p&gt;
&lt;p&gt;To address this problem, add a module owner pointer to the fpga_bridge
struct and use it to take the module&amp;amp;apos;s refcount. Modify the function for
registering a bridge to take an additional owner module paramet…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:24.03-LTS: kernel&lt;/p&gt;
&lt;p&gt;The Linux Kernel, the operating system core itself.&#13;
&#13;
Security Fix(es):&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ksmbd: fix potencial out-of-bounds when buffer offset is invalid&lt;/p&gt;
&lt;p&gt;I found potencial out-of-bounds when buffer offset fields of a few requests
is invalid. This patch set the minimum value of buffer offset field to
-&amp;amp;gt;Buffer offset to validate buffer length.(CVE-2024-26952)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ksmbd: fix slab-out-of-bounds in smb_strndup_from_utf16()&lt;/p&gt;
&lt;p&gt;If -&amp;amp;gt;NameOffset of smb2_create_req is smaller than Buffer offset of
smb2_create_req, slab-out-of-bounds read can happen from smb2_open.
This patch set the minimum value of the name offset to the buffer offset
to validate name length of smb2_create_req().(CVE-2024-26954)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;fpga: bridge: add owner module and take its refcount&lt;/p&gt;
&lt;p&gt;The current implementation of the fpga bridge assumes that the low-level
module registers a driver for the parent device and uses its owner pointer
to take the module&amp;amp;apos;s refcount. This approach is problematic since it can
lead to a null pointer dereference while attempting to get the bridge if
the parent device does not have a driver.&lt;/p&gt;
&lt;p&gt;To address this problem, add a module owner pointer to the fpga_bridge
struct and use it to take the module&amp;amp;apos;s refcount. Modify the function for
registering a bridge to take an additional owner module paramet…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/oesa-2025-1097</guid>
    </item>
    <item>
      <title>RHSA-2024:9315 — Red Hat Security Advisory: kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/rhsa-2024:9315</link>
      <description>&lt;p&gt;kernel: use after free in i2c kernel: bluetooth: BR/EDR Bluetooth Impersonation Attacks (BIAS) kernel: hwmon: (lm90) Prevent integer overflow/underflow in hysteresis calculations kernel: asix: fix uninit-value in asix_mdio_read() kernel: tty: tty_buffer: Fix the softlockup issue in flush_to_ldisc kernel: hwmon: (w83793) Fix NULL pointer dereference by removing unnecessary structure field kernel: hwmon: (w83791d) Fix NULL pointer dereference by removing unnecessary structure field kernel: powerpc/64s: fix program check interrupt emergency stack path kernel: powerpc/64s: Fix unrecoverable MCE calling async handler from NMI kernel: lib/generic-radix-tree.c: Don&amp;#39;t overflow in peek() kernel: powerpc/smp: do not decrement idle task preempt count in CPU offline kernel: can: isotp: isotp_sendmsg(): add result check for wait_event_interruptible() kernel: usbnet: sanity check for maxpacket kernel: nvmem: Fix shift-out-of-bound (UBSAN) with byte size cells kernel: aio: fix use-after-free due to missing POLLFREE handling kernel: powerpc/pseries: Fix potential memleak in papr_get_attr() kernel: of: fdt: fix off-by-one error in unflatten_dt_nodes() kernel: thermal/int340x_thermal: handle data_vault when the value is ZERO_SIZE_PTR kernel: vt_ioctl: fix array_index_nospec in vt_setactivate kernel: bpf: Fix crash due to out of bounds access into reg2btf_ids. kernel: lz4: fix LZ4_decompress_safe_partial read out of bound kernel: x86/mce: Work around an erratum on fast string copy instructions…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;kernel: use after free in i2c kernel: bluetooth: BR/EDR Bluetooth Impersonation Attacks (BIAS) kernel: hwmon: (lm90) Prevent integer overflow/underflow in hysteresis calculations kernel: asix: fix uninit-value in asix_mdio_read() kernel: tty: tty_buffer: Fix the softlockup issue in flush_to_ldisc kernel: hwmon: (w83793) Fix NULL pointer dereference by removing unnecessary structure field kernel: hwmon: (w83791d) Fix NULL pointer dereference by removing unnecessary structure field kernel: powerpc/64s: fix program check interrupt emergency stack path kernel: powerpc/64s: Fix unrecoverable MCE calling async handler from NMI kernel: lib/generic-radix-tree.c: Don&amp;#39;t overflow in peek() kernel: powerpc/smp: do not decrement idle task preempt count in CPU offline kernel: can: isotp: isotp_sendmsg(): add result check for wait_event_interruptible() kernel: usbnet: sanity check for maxpacket kernel: nvmem: Fix shift-out-of-bound (UBSAN) with byte size cells kernel: aio: fix use-after-free due to missing POLLFREE handling kernel: powerpc/pseries: Fix potential memleak in papr_get_attr() kernel: of: fdt: fix off-by-one error in unflatten_dt_nodes() kernel: thermal/int340x_thermal: handle data_vault when the value is ZERO_SIZE_PTR kernel: vt_ioctl: fix array_index_nospec in vt_setactivate kernel: bpf: Fix crash due to out of bounds access into reg2btf_ids. kernel: lz4: fix LZ4_decompress_safe_partial read out of bound kernel: x86/mce: Work around an erratum on fast string copy instructions…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rhsa-2024:9315</guid>
    </item>
    <item>
      <title>SUSE-SU-2024:3194-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2024:3194-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:3194-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2024-41001</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-41001</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:Pro:18.04:LTS: linux-aws-5.4, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:Pro:18.04:LTS: linux-azure-5.4, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3 and 159 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: io_uring/sqpoll: work around a potential audit memory leak kmemleak complains that there&amp;#39;s a memory leak related to connect handling: unreferenced object 0xffff0001093bdf00 (size 128): comm &amp;#34;iou-sqp-455&amp;#34;, pid 457, jiffies 4294894164 hex dump (first 32 bytes): 02 00 fa ea 7f 00 00 01 00 00 00 00 00 00 00 00  ................ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................ backtrace (crc 2e481b1a): [&amp;lt;00000000c0a26af4&amp;gt;] kmemleak_alloc+0x30/0x38 [&amp;lt;000000009c30bb45&amp;gt;] kmalloc_trace+0x228/0x358 [&amp;lt;000000009da9d39f&amp;gt;] __audit_sockaddr+0xd0/0x138 [&amp;lt;0000000089a93e34&amp;gt;] move_addr_to_kernel+0x1a0/0x1f8 [&amp;lt;000000000b4e80e6&amp;gt;] io_connect_prep+0x1ec/0x2d4 [&amp;lt;00000000abfbcd99&amp;gt;] io_submit_sqes+0x588/0x1e48 [&amp;lt;00000000e7c25e07&amp;gt;] io_sq_thread+0x8a4/0x10e4 [&amp;lt;00000000d999b491&amp;gt;] ret_from_fork+0x10/0x20 which can can happen if: 1) The command type does something on the prep side that triggers an    audit call. 2) The thread hasn&amp;#39;t done any operations before this that triggered    an audit call inside -&amp;gt;issue(), where we have audit_uring_entry()    and audit_uring_exit(). Work around this by issuing a blanket NOP operation before the SQPOLL does anything.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:Pro:18.04:LTS: linux-aws-5.4, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:Pro:18.04:LTS: linux-azure-5.4, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3 and 159 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: io_uring/sqpoll: work around a potential audit memory leak kmemleak complains that there&amp;#39;s a memory leak related to connect handling: unreferenced object 0xffff0001093bdf00 (size 128): comm &amp;#34;iou-sqp-455&amp;#34;, pid 457, jiffies 4294894164 hex dump (first 32 bytes): 02 00 fa ea 7f 00 00 01 00 00 00 00 00 00 00 00  ................ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................ backtrace (crc 2e481b1a): [&amp;lt;00000000c0a26af4&amp;gt;] kmemleak_alloc+0x30/0x38 [&amp;lt;000000009c30bb45&amp;gt;] kmalloc_trace+0x228/0x358 [&amp;lt;000000009da9d39f&amp;gt;] __audit_sockaddr+0xd0/0x138 [&amp;lt;0000000089a93e34&amp;gt;] move_addr_to_kernel+0x1a0/0x1f8 [&amp;lt;000000000b4e80e6&amp;gt;] io_connect_prep+0x1ec/0x2d4 [&amp;lt;00000000abfbcd99&amp;gt;] io_submit_sqes+0x588/0x1e48 [&amp;lt;00000000e7c25e07&amp;gt;] io_sq_thread+0x8a4/0x10e4 [&amp;lt;00000000d999b491&amp;gt;] ret_from_fork+0x10/0x20 which can can happen if: 1) The command type does something on the prep side that triggers an    audit call. 2) The thread hasn&amp;#39;t done any operations before this that triggered    an audit call inside -&amp;gt;issue(), where we have audit_uring_entry()    and audit_uring_exit(). Work around this by issuing a blanket NOP operation before the SQPOLL does anything.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-41001</guid>
    </item>
    <item>
      <title>WID-SEC-W-2024-1607 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2024-1607</link>
      <description>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen im Linux-Kernel ausnutzen, um seine Privilegien zu erweitern, einen Denial-of-Service-Zustand zu erzeugen, vertrauliche Informationen offenzulegen oder einen unspezifischen Angriff durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen im Linux-Kernel ausnutzen, um seine Privilegien zu erweitern, einen Denial-of-Service-Zustand zu erzeugen, vertrauliche Informationen offenzulegen oder einen unspezifischen Angriff durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2024-1607</guid>
    </item>
  </channel>
</rss>
