<?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 06:22:28 +0000</lastBuildDate>
    <item>
      <title>bdu:2024-08076</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2024-08076</link>
      <description>bdu:2024-08076</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2024-08076</guid>
    </item>
    <item>
      <title>BELL-CVE-2024-46796</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2024-46796</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; 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:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2024-46796</guid>
    </item>
    <item>
      <title>certfr-2025-avi-0307 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de SUSE. Certaines d'entre elles permettent à un at…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2025-avi-0307</link>
      <description>certfr-2025-avi-0307</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2025-avi-0307</guid>
    </item>
    <item>
      <title>EUVD-2026-346123</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-346123</link>
      <description>EUVD-2026-346123</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-346123</guid>
    </item>
    <item>
      <title>fkie_cve-2024-46796</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2024-46796</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;smb: client: fix double put of @cfile in smb2_set_path_size()&lt;/p&gt;
&lt;p&gt;If smb2_compound_op() is called with a valid @cfile and returned
-EINVAL, we need to call cifs_get_writable_path() before retrying it
as the reference of @cfile was already dropped by previous call.&lt;/p&gt;
&lt;p&gt;This fixes the following KASAN splat when running fstests generic/013
against Windows Server 2022:&lt;/p&gt;
&lt;p&gt;CIFS: Attempting to mount //w22-fs0/scratch
  run fstests generic/013 at 2024-09-02 19:48:59
  ==================================================================
  BUG: KASAN: slab-use-after-free in detach_if_pending+0xab/0x200
  Write of size 8 at addr ffff88811f1a3730 by task kworker/3:2/176&lt;/p&gt;
&lt;p&gt;CPU: 3 UID: 0 PID: 176 Comm: kworker/3:2 Not tainted 6.11.0-rc6 #2
  Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-2.fc40
  04/01/2014
  Workqueue: cifsoplockd cifs_oplock_break [cifs]
  Call Trace:
   &amp;lt;TASK&amp;gt;
   dump_stack_lvl+0x5d/0x80
   ? detach_if_pending+0xab/0x200
   print_report+0x156/0x4d9
   ? detach_if_pending+0xab/0x200
   ? __virt_addr_valid+0x145/0x300
   ? __phys_addr+0x46/0x90
   ? detach_if_pending+0xab/0x200
   kasan_report+0xda/0x110
   ? detach_if_pending+0xab/0x200
   detach_if_pending+0xab/0x200
   timer_delete+0x96/0xe0
   ? __pfx_timer_delete+0x10/0x10
   ? rcu_is_watching+0x20/0x50
   try_to_grab_pending+0x46/0x3b0
   __cancel_work+0x89/0x1b0
   ? __pfx___cancel_work+0x10/0x10
   ? kasan_save_track+0x14/0x30
   cifs…&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;smb: client: fix double put of @cfile in smb2_set_path_size()&lt;/p&gt;
&lt;p&gt;If smb2_compound_op() is called with a valid @cfile and returned
-EINVAL, we need to call cifs_get_writable_path() before retrying it
as the reference of @cfile was already dropped by previous call.&lt;/p&gt;
&lt;p&gt;This fixes the following KASAN splat when running fstests generic/013
against Windows Server 2022:&lt;/p&gt;
&lt;p&gt;CIFS: Attempting to mount //w22-fs0/scratch
  run fstests generic/013 at 2024-09-02 19:48:59
  ==================================================================
  BUG: KASAN: slab-use-after-free in detach_if_pending+0xab/0x200
  Write of size 8 at addr ffff88811f1a3730 by task kworker/3:2/176&lt;/p&gt;
&lt;p&gt;CPU: 3 UID: 0 PID: 176 Comm: kworker/3:2 Not tainted 6.11.0-rc6 #2
  Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-2.fc40
  04/01/2014
  Workqueue: cifsoplockd cifs_oplock_break [cifs]
  Call Trace:
   &amp;lt;TASK&amp;gt;
   dump_stack_lvl+0x5d/0x80
   ? detach_if_pending+0xab/0x200
   print_report+0x156/0x4d9
   ? detach_if_pending+0xab/0x200
   ? __virt_addr_valid+0x145/0x300
   ? __phys_addr+0x46/0x90
   ? detach_if_pending+0xab/0x200
   kasan_report+0xda/0x110
   ? detach_if_pending+0xab/0x200
   detach_if_pending+0xab/0x200
   timer_delete+0x96/0xe0
   ? __pfx_timer_delete+0x10/0x10
   ? rcu_is_watching+0x20/0x50
   try_to_grab_pending+0x46/0x3b0
   __cancel_work+0x89/0x1b0
   ? __pfx___cancel_work+0x10/0x10
   ? kasan_save_track+0x14/0x30
   cifs…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2024-46796</guid>
    </item>
    <item>
      <title>GHSA-m8jr-w275-x227</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-m8jr-w275-x227</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;smb: client: fix double put of @cfile in smb2_set_path_size()&lt;/p&gt;
&lt;p&gt;If smb2_compound_op() is called with a valid @cfile and returned
-EINVAL, we need to call cifs_get_writable_path() before retrying it
as the reference of @cfile was already dropped by previous call.&lt;/p&gt;
&lt;p&gt;This fixes the following KASAN splat when running fstests generic/013
against Windows Server 2022:&lt;/p&gt;
&lt;p&gt;CIFS: Attempting to mount //w22-fs0/scratch
  run fstests generic/013 at 2024-09-02 19:48:59
  ==================================================================
  BUG: KASAN: slab-use-after-free in detach_if_pending+0xab/0x200
  Write of size 8 at addr ffff88811f1a3730 by task kworker/3:2/176&lt;/p&gt;
&lt;p&gt;CPU: 3 UID: 0 PID: 176 Comm: kworker/3:2 Not tainted 6.11.0-rc6 #2
  Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-2.fc40
  04/01/2014
  Workqueue: cifsoplockd cifs_oplock_break [cifs]
  Call Trace:
   &amp;lt;TASK&amp;gt;
   dump_stack_lvl+0x5d/0x80
   ? detach_if_pending+0xab/0x200
   print_report+0x156/0x4d9
   ? detach_if_pending+0xab/0x200
   ? __virt_addr_valid+0x145/0x300
   ? __phys_addr+0x46/0x90
   ? detach_if_pending+0xab/0x200
   kasan_report+0xda/0x110
   ? detach_if_pending+0xab/0x200
   detach_if_pending+0xab/0x200
   timer_delete+0x96/0xe0
   ? __pfx_timer_delete+0x10/0x10
   ? rcu_is_watching+0x20/0x50
   try_to_grab_pending+0x46/0x3b0
   __cancel_work+0x89/0x1b0
   ? __pfx___cancel_work+0x10/0x10
   ? kasan_save_track+0x14/0x30
   cifs…&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;smb: client: fix double put of @cfile in smb2_set_path_size()&lt;/p&gt;
&lt;p&gt;If smb2_compound_op() is called with a valid @cfile and returned
-EINVAL, we need to call cifs_get_writable_path() before retrying it
as the reference of @cfile was already dropped by previous call.&lt;/p&gt;
&lt;p&gt;This fixes the following KASAN splat when running fstests generic/013
against Windows Server 2022:&lt;/p&gt;
&lt;p&gt;CIFS: Attempting to mount //w22-fs0/scratch
  run fstests generic/013 at 2024-09-02 19:48:59
  ==================================================================
  BUG: KASAN: slab-use-after-free in detach_if_pending+0xab/0x200
  Write of size 8 at addr ffff88811f1a3730 by task kworker/3:2/176&lt;/p&gt;
&lt;p&gt;CPU: 3 UID: 0 PID: 176 Comm: kworker/3:2 Not tainted 6.11.0-rc6 #2
  Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-2.fc40
  04/01/2014
  Workqueue: cifsoplockd cifs_oplock_break [cifs]
  Call Trace:
   &amp;lt;TASK&amp;gt;
   dump_stack_lvl+0x5d/0x80
   ? detach_if_pending+0xab/0x200
   print_report+0x156/0x4d9
   ? detach_if_pending+0xab/0x200
   ? __virt_addr_valid+0x145/0x300
   ? __phys_addr+0x46/0x90
   ? detach_if_pending+0xab/0x200
   kasan_report+0xda/0x110
   ? detach_if_pending+0xab/0x200
   detach_if_pending+0xab/0x200
   timer_delete+0x96/0xe0
   ? __pfx_timer_delete+0x10/0x10
   ? rcu_is_watching+0x20/0x50
   try_to_grab_pending+0x46/0x3b0
   __cancel_work+0x89/0x1b0
   ? __pfx___cancel_work+0x10/0x10
   ? kasan_save_track+0x14/0x30
   cifs…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-m8jr-w275-x227</guid>
    </item>
    <item>
      <title>msrc_CVE-2024-46796 — smb: client: fix double put of @cfile in smb2_set_path_size()</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2024-46796</link>
      <description>msrc_CVE-2024-46796</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2024-46796</guid>
    </item>
    <item>
      <title>OESA-2024-2219 — kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/oesa-2024-2219</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):&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
bpf: Take return from set_memory_rox() into account with bpf_jit_binary_lock_ro()&#13;
&#13;
set_memory_rox() can fail, leaving memory unprotected.&#13;
&#13;
Check return and bail out when bpf_jit_binary_lock_ro() returns
an error.(CVE-2024-42067)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
sysctl: always initialize i_uid/i_gid&#13;
&#13;
Always initialize i_uid/i_gid inside the sysfs core so set_ownership()
can safely skip setting them.&#13;
&#13;
Commit 5ec27ec735ba (&amp;amp;quot;fs/proc/proc_sysctl.c: fix the default values of
i_uid/i_gid on /proc/sys inodes.&amp;amp;quot;) added defaults for i_uid/i_gid when
set_ownership() was not implemented. It also missed adjusting
net_ctl_set_ownership() to use the same default values in case the
computation of a better value failed.(CVE-2024-42312)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
parisc: fix a possible DMA corruption&#13;
&#13;
ARCH_DMA_MINALIGN was defined as 16 - this is too small - it may be
possible that two unrelated 16-byte allocations share a cache line. If
one of these allocations is written using DMA and the other is written
using cached write, the value that was written with DMA may be
corrupted.&#13;
&#13;
This commit changes ARCH_DMA_MINALIGN to be 128 on PA20 and 32 on PA1.1 -
that&amp;amp;apos;s the largest possible cache line size.&#13;
&#13;
As different parisc microarchitectur…&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):&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
bpf: Take return from set_memory_rox() into account with bpf_jit_binary_lock_ro()&#13;
&#13;
set_memory_rox() can fail, leaving memory unprotected.&#13;
&#13;
Check return and bail out when bpf_jit_binary_lock_ro() returns
an error.(CVE-2024-42067)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
sysctl: always initialize i_uid/i_gid&#13;
&#13;
Always initialize i_uid/i_gid inside the sysfs core so set_ownership()
can safely skip setting them.&#13;
&#13;
Commit 5ec27ec735ba (&amp;amp;quot;fs/proc/proc_sysctl.c: fix the default values of
i_uid/i_gid on /proc/sys inodes.&amp;amp;quot;) added defaults for i_uid/i_gid when
set_ownership() was not implemented. It also missed adjusting
net_ctl_set_ownership() to use the same default values in case the
computation of a better value failed.(CVE-2024-42312)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
parisc: fix a possible DMA corruption&#13;
&#13;
ARCH_DMA_MINALIGN was defined as 16 - this is too small - it may be
possible that two unrelated 16-byte allocations share a cache line. If
one of these allocations is written using DMA and the other is written
using cached write, the value that was written with DMA may be
corrupted.&#13;
&#13;
This commit changes ARCH_DMA_MINALIGN to be 128 on PA20 and 32 on PA1.1 -
that&amp;amp;apos;s the largest possible cache line size.&#13;
&#13;
As different parisc microarchitectur…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/oesa-2024-2219</guid>
    </item>
    <item>
      <title>SUSE-SU-2025:01919-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2025:01919-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-2025:01919-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2024-46796</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-46796</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:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 66 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: smb: client: fix double put of @cfile in smb2_set_path_size() If smb2_compound_op() is called with a valid @cfile and returned -EINVAL, we need to call cifs_get_writable_path() before retrying it as the reference of @cfile was already dropped by previous call. This fixes the following KASAN splat when running fstests generic/013 against Windows Server 2022:   CIFS: Attempting to mount //w22-fs0/scratch   run fstests generic/013 at 2024-09-02 19:48:59   ==================================================================   BUG: KASAN: slab-use-after-free in detach_if_pending+0xab/0x200   Write of size 8 at addr ffff88811f1a3730 by task kworker/3:2/176   CPU: 3 UID: 0 PID: 176 Comm: kworker/3:2 Not tainted 6.11.0-rc6 #2   Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-2.fc40   04/01/2014   Workqueue: cifsoplockd cifs_oplock_break [cifs]   Call Trace:    &amp;lt;TASK&amp;gt;    dump_stack_lvl+0x5d/0x80    ? detach_if_pending+0xab/0x200    print_report+0x156/0x4d9    ? detach_if_pending+0xab/0x200    ? __virt_addr_valid+0x145/0x300    ? __phys_addr+0x46/0x90    ? detach_if_pending+0xab/0x200    kasan_report+0xda/0x110    ? detach_if_pending+0xab/0x200    detach_if_pending+0xab/0x200    timer_delete+0x96/0xe0    ? __pfx_timer_delete+0x10/0x10    ? rcu_is_watching+0x20/0x50    try_to_grab_pending+0x46/0x3b0    __cancel_work+0x89/0x1b0    ? __pfx___cancel_work+0x10/0x10    ? kasan_save_track+0x14/0x30    cifs_clos…&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:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 66 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: smb: client: fix double put of @cfile in smb2_set_path_size() If smb2_compound_op() is called with a valid @cfile and returned -EINVAL, we need to call cifs_get_writable_path() before retrying it as the reference of @cfile was already dropped by previous call. This fixes the following KASAN splat when running fstests generic/013 against Windows Server 2022:   CIFS: Attempting to mount //w22-fs0/scratch   run fstests generic/013 at 2024-09-02 19:48:59   ==================================================================   BUG: KASAN: slab-use-after-free in detach_if_pending+0xab/0x200   Write of size 8 at addr ffff88811f1a3730 by task kworker/3:2/176   CPU: 3 UID: 0 PID: 176 Comm: kworker/3:2 Not tainted 6.11.0-rc6 #2   Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-2.fc40   04/01/2014   Workqueue: cifsoplockd cifs_oplock_break [cifs]   Call Trace:    &amp;lt;TASK&amp;gt;    dump_stack_lvl+0x5d/0x80    ? detach_if_pending+0xab/0x200    print_report+0x156/0x4d9    ? detach_if_pending+0xab/0x200    ? __virt_addr_valid+0x145/0x300    ? __phys_addr+0x46/0x90    ? detach_if_pending+0xab/0x200    kasan_report+0xda/0x110    ? detach_if_pending+0xab/0x200    detach_if_pending+0xab/0x200    timer_delete+0x96/0xe0    ? __pfx_timer_delete+0x10/0x10    ? rcu_is_watching+0x20/0x50    try_to_grab_pending+0x46/0x3b0    __cancel_work+0x89/0x1b0    ? __pfx___cancel_work+0x10/0x10    ? kasan_save_track+0x14/0x30    cifs_clos…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-46796</guid>
    </item>
    <item>
      <title>WID-SEC-W-2024-2173 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2024-2173</link>
      <description>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen 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 einen Denial of Service Angriff durchzuführen oder einen unspezifischen Angriff durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2024-2173</guid>
    </item>
  </channel>
</rss>
