<?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, 02 Oct 2026 19:52:45 +0000</lastBuildDate>
    <item>
      <title>ALSA-2025:20518 — Moderate: kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/alsa-2025:20518</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; AlmaLinux:9: kernel, AlmaLinux:9: kernel-64k, AlmaLinux:9: kernel-64k-core, AlmaLinux:9: kernel-64k-debug, AlmaLinux:9: kernel-64k-debug-core, AlmaLinux:9: kernel-64k-debug-devel, AlmaLinux:9: kernel-64k-debug-devel-matched, AlmaLinux:9: kernel-64k-debug-modules, AlmaLinux:9: kernel-64k-debug-modules-core, AlmaLinux:9: kernel-64k-debug-modules-extra and 64 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: can: isotp: fix potential CAN frame reception race in isotp_rcv() (CVE-2022-48830)
  * kernel: soc: qcom: cmd-db: Map shared memory as WC, not WB (CVE-2024-46689)
  * kernel: Squashfs: sanity check symbolic link size (CVE-2024-46744)
  * kernel: vfs: fix race between evice_inodes() and find_inode()&amp;amp;#38;iput() (CVE-2024-47679)
  * kernel: x86/tdx: Fix &amp;#34;in-kernel MMIO&amp;#34; check (CVE-2024-47727)
  * kernel: rxrpc: Fix a race between socket set up and I/O thread creation (CVE-2024-49864)
  * kernel: io_uring: check if we need to reschedule during overflow flush (CVE-2024-50060)
  * kernel: can: m_can: pci: add missing m_can_class_free_dev() in probe/remove methods (CVE-2022-49024)
  * kernel: posix-clock: Fix missing timespec64 check in pc_clock_settime() (CVE-2024-50195)
  * kernel: rxrpc: Fix missing locking causing hanging calls (CVE-2024-50294)
  * kernel: io_uring/rw: fix missing NOWAIT check for O_DIRECT start write (CVE-2024-53052)
  * kernel: afs: Fix lock recursion (CVE-2024-53090)
  * kernel: virtio/vsock: Fix accept_queue memory leak (CVE-2024-53119)
  * kernel: KVM: VMX: Bury Intel PT virtualization (guest/host mode) behind CONFIG_BROKEN (CVE-2024-53135)
  * kernel: xen: Xen hypercall page unsafe against speculative attacks (Xen Security Advisory 466) (CVE-2024-53241)
  * kernel: RDMA/rxe: Fix the qp flush warnings in req (CVE-2024-53229)
  * kernel:…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; AlmaLinux:9: kernel, AlmaLinux:9: kernel-64k, AlmaLinux:9: kernel-64k-core, AlmaLinux:9: kernel-64k-debug, AlmaLinux:9: kernel-64k-debug-core, AlmaLinux:9: kernel-64k-debug-devel, AlmaLinux:9: kernel-64k-debug-devel-matched, AlmaLinux:9: kernel-64k-debug-modules, AlmaLinux:9: kernel-64k-debug-modules-core, AlmaLinux:9: kernel-64k-debug-modules-extra and 64 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: can: isotp: fix potential CAN frame reception race in isotp_rcv() (CVE-2022-48830)
  * kernel: soc: qcom: cmd-db: Map shared memory as WC, not WB (CVE-2024-46689)
  * kernel: Squashfs: sanity check symbolic link size (CVE-2024-46744)
  * kernel: vfs: fix race between evice_inodes() and find_inode()&amp;amp;#38;iput() (CVE-2024-47679)
  * kernel: x86/tdx: Fix &amp;#34;in-kernel MMIO&amp;#34; check (CVE-2024-47727)
  * kernel: rxrpc: Fix a race between socket set up and I/O thread creation (CVE-2024-49864)
  * kernel: io_uring: check if we need to reschedule during overflow flush (CVE-2024-50060)
  * kernel: can: m_can: pci: add missing m_can_class_free_dev() in probe/remove methods (CVE-2022-49024)
  * kernel: posix-clock: Fix missing timespec64 check in pc_clock_settime() (CVE-2024-50195)
  * kernel: rxrpc: Fix missing locking causing hanging calls (CVE-2024-50294)
  * kernel: io_uring/rw: fix missing NOWAIT check for O_DIRECT start write (CVE-2024-53052)
  * kernel: afs: Fix lock recursion (CVE-2024-53090)
  * kernel: virtio/vsock: Fix accept_queue memory leak (CVE-2024-53119)
  * kernel: KVM: VMX: Bury Intel PT virtualization (guest/host mode) behind CONFIG_BROKEN (CVE-2024-53135)
  * kernel: xen: Xen hypercall page unsafe against speculative attacks (Xen Security Advisory 466) (CVE-2024-53241)
  * kernel: RDMA/rxe: Fix the qp flush warnings in req (CVE-2024-53229)
  * kernel:…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/alsa-2025:20518</guid>
    </item>
    <item>
      <title>bdu:2025-05135</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2025-05135</link>
      <description>bdu:2025-05135</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2025-05135</guid>
    </item>
    <item>
      <title>BELL-CVE-2024-47679</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2024-47679</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-47679</guid>
    </item>
    <item>
      <title>certfr-2024-avi-1101 — De multiples vulnérabilités ont été découvertes dans le noyau Linux d'Ubuntu. Certaines d'entre elles permettent à un a…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2024-avi-1101</link>
      <description>certfr-2024-avi-1101</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2024-avi-1101</guid>
    </item>
    <item>
      <title>EUVD-2026-346166</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-346166</link>
      <description>EUVD-2026-346166</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-346166</guid>
    </item>
    <item>
      <title>fkie_cve-2024-47679</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2024-47679</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;vfs: fix race between evice_inodes() and find_inode()&amp;amp;iput()&lt;/p&gt;
&lt;p&gt;Hi, all&lt;/p&gt;
&lt;p&gt;Recently I noticed a bug[1] in btrfs, after digged it into
and I believe it&amp;#39;a race in vfs.&lt;/p&gt;
&lt;p&gt;Let&amp;#39;s assume there&amp;#39;s a inode (ie ino 261) with i_count 1 is
called by iput(), and there&amp;#39;s a concurrent thread calling
generic_shutdown_super().&lt;/p&gt;
&lt;p&gt;cpu0:                              cpu1:
iput() // i_count is 1
  -&amp;gt;spin_lock(inode)
  -&amp;gt;dec i_count to 0
  -&amp;gt;iput_final()                    generic_shutdown_super()
    -&amp;gt;__inode_add_lru()               -&amp;gt;evict_inodes()
      // cause some reason[2]           -&amp;gt;if (atomic_read(inode-&amp;gt;i_count)) continue;
      // return before                  // inode 261 passed the above check
      // list_lru_add_obj()             // and then schedule out
   -&amp;gt;spin_unlock()
// note here: the inode 261
// was still at sb list and hash list,
// and I_FREEING|I_WILL_FREE was not been set&lt;/p&gt;
&lt;p&gt;btrfs_iget()
  // after some function calls
  -&amp;gt;find_inode()
    // found the above inode 261
    -&amp;gt;spin_lock(inode)
   // check I_FREEING|I_WILL_FREE
   // and passed
      -&amp;gt;__iget()
    -&amp;gt;spin_unlock(inode)                // schedule back
                                        -&amp;gt;spin_lock(inode)
                                        // check (I_NEW|I_FREEING|I_WILL_FREE) flags,
                                        // passed and set I_FREEING
iput()                                  -&amp;gt;spin_unlock(inode)
  -&amp;gt;spin_lock(inode)…&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;vfs: fix race between evice_inodes() and find_inode()&amp;amp;iput()&lt;/p&gt;
&lt;p&gt;Hi, all&lt;/p&gt;
&lt;p&gt;Recently I noticed a bug[1] in btrfs, after digged it into
and I believe it&amp;#39;a race in vfs.&lt;/p&gt;
&lt;p&gt;Let&amp;#39;s assume there&amp;#39;s a inode (ie ino 261) with i_count 1 is
called by iput(), and there&amp;#39;s a concurrent thread calling
generic_shutdown_super().&lt;/p&gt;
&lt;p&gt;cpu0:                              cpu1:
iput() // i_count is 1
  -&amp;gt;spin_lock(inode)
  -&amp;gt;dec i_count to 0
  -&amp;gt;iput_final()                    generic_shutdown_super()
    -&amp;gt;__inode_add_lru()               -&amp;gt;evict_inodes()
      // cause some reason[2]           -&amp;gt;if (atomic_read(inode-&amp;gt;i_count)) continue;
      // return before                  // inode 261 passed the above check
      // list_lru_add_obj()             // and then schedule out
   -&amp;gt;spin_unlock()
// note here: the inode 261
// was still at sb list and hash list,
// and I_FREEING|I_WILL_FREE was not been set&lt;/p&gt;
&lt;p&gt;btrfs_iget()
  // after some function calls
  -&amp;gt;find_inode()
    // found the above inode 261
    -&amp;gt;spin_lock(inode)
   // check I_FREEING|I_WILL_FREE
   // and passed
      -&amp;gt;__iget()
    -&amp;gt;spin_unlock(inode)                // schedule back
                                        -&amp;gt;spin_lock(inode)
                                        // check (I_NEW|I_FREEING|I_WILL_FREE) flags,
                                        // passed and set I_FREEING
iput()                                  -&amp;gt;spin_unlock(inode)
  -&amp;gt;spin_lock(inode)…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2024-47679</guid>
    </item>
    <item>
      <title>GHSA-9p2r-69c4-v82v</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-9p2r-69c4-v82v</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;vfs: fix race between evice_inodes() and find_inode()&amp;amp;iput()&lt;/p&gt;
&lt;p&gt;Hi, all&lt;/p&gt;
&lt;p&gt;Recently I noticed a bug[1] in btrfs, after digged it into
and I believe it&amp;#39;a race in vfs.&lt;/p&gt;
&lt;p&gt;Let&amp;#39;s assume there&amp;#39;s a inode (ie ino 261) with i_count 1 is
called by iput(), and there&amp;#39;s a concurrent thread calling
generic_shutdown_super().&lt;/p&gt;
&lt;p&gt;cpu0:                              cpu1:
iput() // i_count is 1
  -&amp;gt;spin_lock(inode)
  -&amp;gt;dec i_count to 0
  -&amp;gt;iput_final()                    generic_shutdown_super()
    -&amp;gt;__inode_add_lru()               -&amp;gt;evict_inodes()
      // cause some reason[2]           -&amp;gt;if (atomic_read(inode-&amp;gt;i_count)) continue;
      // return before                  // inode 261 passed the above check
      // list_lru_add_obj()             // and then schedule out
   -&amp;gt;spin_unlock()
// note here: the inode 261
// was still at sb list and hash list,
// and I_FREEING|I_WILL_FREE was not been set&lt;/p&gt;
&lt;p&gt;btrfs_iget()
  // after some function calls
  -&amp;gt;find_inode()
    // found the above inode 261
    -&amp;gt;spin_lock(inode)
   // check I_FREEING|I_WILL_FREE
   // and passed
      -&amp;gt;__iget()
    -&amp;gt;spin_unlock(inode)                // schedule back
                                        -&amp;gt;spin_lock(inode)
                                        // check (I_NEW|I_FREEING|I_WILL_FREE) flags,
                                        // passed and set I_FREEING
iput()                                  -&amp;gt;spin_unlock(inode)
  -&amp;gt;spin_lock(inode)…&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;vfs: fix race between evice_inodes() and find_inode()&amp;amp;iput()&lt;/p&gt;
&lt;p&gt;Hi, all&lt;/p&gt;
&lt;p&gt;Recently I noticed a bug[1] in btrfs, after digged it into
and I believe it&amp;#39;a race in vfs.&lt;/p&gt;
&lt;p&gt;Let&amp;#39;s assume there&amp;#39;s a inode (ie ino 261) with i_count 1 is
called by iput(), and there&amp;#39;s a concurrent thread calling
generic_shutdown_super().&lt;/p&gt;
&lt;p&gt;cpu0:                              cpu1:
iput() // i_count is 1
  -&amp;gt;spin_lock(inode)
  -&amp;gt;dec i_count to 0
  -&amp;gt;iput_final()                    generic_shutdown_super()
    -&amp;gt;__inode_add_lru()               -&amp;gt;evict_inodes()
      // cause some reason[2]           -&amp;gt;if (atomic_read(inode-&amp;gt;i_count)) continue;
      // return before                  // inode 261 passed the above check
      // list_lru_add_obj()             // and then schedule out
   -&amp;gt;spin_unlock()
// note here: the inode 261
// was still at sb list and hash list,
// and I_FREEING|I_WILL_FREE was not been set&lt;/p&gt;
&lt;p&gt;btrfs_iget()
  // after some function calls
  -&amp;gt;find_inode()
    // found the above inode 261
    -&amp;gt;spin_lock(inode)
   // check I_FREEING|I_WILL_FREE
   // and passed
      -&amp;gt;__iget()
    -&amp;gt;spin_unlock(inode)                // schedule back
                                        -&amp;gt;spin_lock(inode)
                                        // check (I_NEW|I_FREEING|I_WILL_FREE) flags,
                                        // passed and set I_FREEING
iput()                                  -&amp;gt;spin_unlock(inode)
  -&amp;gt;spin_lock(inode)…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-9p2r-69c4-v82v</guid>
    </item>
    <item>
      <title>ICSA-25-226-07 — Siemens Third-Party Components in SINEC OS</title>
      <link>https://cve.radiocsirt.org/vuln/icsa-25-226-07</link>
      <description>&lt;p&gt;nfsd: NULL dereference in nfs3svc_encode_getaclres. scsi: core: use-after-free vulnerability. NFSD: vulnerability caused by loff_t overflow on the server when a client reads near the maximum offset, causing the server to return an EINVAL error, which the client retries indefinitely, instead of handling out-of-range READ requests by returning a short result with an EOF flag. NFSD: Vulnerability caused by an underflow in ia_size due to a mismatch between signed and unsigned 64-bit file size values, which can cause issues when handling large file sizes from NFS clients. NFSD: Vulnerability handling large file sizes for NFSv3 improperly capping client size values larger than s64_max, leading to unexpected behavior and potential data corruption. sh: cpuinfo: warning for CONFIG_CPUMASK_OFFSTACK. When CONFIG_CPUMASK_OFFSTACK and CONFIG_DEBUG_PER_CPU_MAPS are selected, cpu_max_bits_warn() generates a runtime warning when showing /proc/cpuinfo. A failure in the -fstack-protector feature in GCC-based toolchains 
that target AArch64 allows an attacker to exploit an existing buffer 
overflow in dynamically-sized local variables in your application 
without this being detected. This stack-protector failure only applies 
to C99-style dynamically-sized local variables or those created using 
alloca(). The stack-protector operates as intended for statically-sized 
local variables.&lt;/p&gt;
&lt;p&gt;The default behavior when the stack-protector 
detects an overflow is to terminate your application, resulting…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;nfsd: NULL dereference in nfs3svc_encode_getaclres. scsi: core: use-after-free vulnerability. NFSD: vulnerability caused by loff_t overflow on the server when a client reads near the maximum offset, causing the server to return an EINVAL error, which the client retries indefinitely, instead of handling out-of-range READ requests by returning a short result with an EOF flag. NFSD: Vulnerability caused by an underflow in ia_size due to a mismatch between signed and unsigned 64-bit file size values, which can cause issues when handling large file sizes from NFS clients. NFSD: Vulnerability handling large file sizes for NFSv3 improperly capping client size values larger than s64_max, leading to unexpected behavior and potential data corruption. sh: cpuinfo: warning for CONFIG_CPUMASK_OFFSTACK. When CONFIG_CPUMASK_OFFSTACK and CONFIG_DEBUG_PER_CPU_MAPS are selected, cpu_max_bits_warn() generates a runtime warning when showing /proc/cpuinfo. A failure in the -fstack-protector feature in GCC-based toolchains 
that target AArch64 allows an attacker to exploit an existing buffer 
overflow in dynamically-sized local variables in your application 
without this being detected. This stack-protector failure only applies 
to C99-style dynamically-sized local variables or those created using 
alloca(). The stack-protector operates as intended for statically-sized 
local variables.&lt;/p&gt;
&lt;p&gt;The default behavior when the stack-protector 
detects an overflow is to terminate your application, resulting…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/icsa-25-226-07</guid>
    </item>
    <item>
      <title>msrc_CVE-2024-47679 — vfs: fix race between evice_inodes() and find_inode()&amp;iput()</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2024-47679</link>
      <description>msrc_CVE-2024-47679</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2024-47679</guid>
    </item>
    <item>
      <title>OESA-2024-2367 — kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/oesa-2024-2367</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;
drm/amd/display: Add NULL pointer check for kzalloc&#13;
&#13;
[Why &amp;amp;amp; How]
Check return pointer of kzalloc before using it.(CVE-2024-42122)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
mm: gup: stop abusing try_grab_folio&#13;
&#13;
A kernel warning was reported when pinning folio in CMA memory when
launching SEV virtual machine.  The splat looks like:&#13;
&#13;
[  464.325306] WARNING: CPU: 13 PID: 6734 at mm/gup.c:1313 __get_user_pages+0x423/0x520
[  464.325464] CPU: 13 PID: 6734 Comm: qemu-kvm Kdump: loaded Not tainted 6.6.33+ #6
[  464.325477] RIP: 0010:__get_user_pages+0x423/0x520
[  464.325515] Call Trace:
[  464.325520]  &amp;amp;lt;TASK&amp;amp;gt;
[  464.325523]  ? __get_user_pages+0x423/0x520
[  464.325528]  ? __warn+0x81/0x130
[  464.325536]  ? __get_user_pages+0x423/0x520
[  464.325541]  ? report_bug+0x171/0x1a0
[  464.325549]  ? handle_bug+0x3c/0x70
[  464.325554]  ? exc_invalid_op+0x17/0x70
[  464.325558]  ? asm_exc_invalid_op+0x1a/0x20
[  464.325567]  ? __get_user_pages+0x423/0x520
[  464.325575]  __gup_longterm_locked+0x212/0x7a0
[  464.325583]  internal_get_user_pages_fast+0xfb/0x190
[  464.325590]  pin_user_pages_fast+0x47/0x60
[  464.325598]  sev_pin_memory+0xca/0x170 [kvm_amd]
[  464.325616]  sev_mem_enc_register_region+0x81/0x130 [kvm_amd]&#13;
&#13;
Per the analysis done by yangge, when starting the SEV virtual machine, it…&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;
drm/amd/display: Add NULL pointer check for kzalloc&#13;
&#13;
[Why &amp;amp;amp; How]
Check return pointer of kzalloc before using it.(CVE-2024-42122)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
mm: gup: stop abusing try_grab_folio&#13;
&#13;
A kernel warning was reported when pinning folio in CMA memory when
launching SEV virtual machine.  The splat looks like:&#13;
&#13;
[  464.325306] WARNING: CPU: 13 PID: 6734 at mm/gup.c:1313 __get_user_pages+0x423/0x520
[  464.325464] CPU: 13 PID: 6734 Comm: qemu-kvm Kdump: loaded Not tainted 6.6.33+ #6
[  464.325477] RIP: 0010:__get_user_pages+0x423/0x520
[  464.325515] Call Trace:
[  464.325520]  &amp;amp;lt;TASK&amp;amp;gt;
[  464.325523]  ? __get_user_pages+0x423/0x520
[  464.325528]  ? __warn+0x81/0x130
[  464.325536]  ? __get_user_pages+0x423/0x520
[  464.325541]  ? report_bug+0x171/0x1a0
[  464.325549]  ? handle_bug+0x3c/0x70
[  464.325554]  ? exc_invalid_op+0x17/0x70
[  464.325558]  ? asm_exc_invalid_op+0x1a/0x20
[  464.325567]  ? __get_user_pages+0x423/0x520
[  464.325575]  __gup_longterm_locked+0x212/0x7a0
[  464.325583]  internal_get_user_pages_fast+0xfb/0x190
[  464.325590]  pin_user_pages_fast+0x47/0x60
[  464.325598]  sev_pin_memory+0xca/0x170 [kvm_amd]
[  464.325616]  sev_mem_enc_register_region+0x81/0x130 [kvm_amd]&#13;
&#13;
Per the analysis done by yangge, when starting the SEV virtual machine, it…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/oesa-2024-2367</guid>
    </item>
    <item>
      <title>openSUSE-SU-2024:14500-1 — kernel-devel-6.11.8-1.1 on GA media</title>
      <link>https://cve.radiocsirt.org/vuln/opensuse-su-2024:14500-1</link>
      <description>&lt;p&gt;kernel-devel-6.11.8-1.1 on GA media&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;kernel-devel-6.11.8-1.1 on GA media&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/opensuse-su-2024:14500-1</guid>
    </item>
    <item>
      <title>SSA-355557 — SSA-355557: Multiple Vulnerabilities in Third-Party Components in SINEC OS before V3.2</title>
      <link>https://cve.radiocsirt.org/vuln/ssa-355557</link>
      <description>&lt;p&gt;nfsd: NULL dereference in nfs3svc_encode_getaclres. scsi: core: use-after-free vulnerability. NFSD: vulnerability caused by loff_t overflow on the server when a client reads near the maximum offset, causing the server to return an EINVAL error, which the client retries indefinitely, instead of handling out-of-range READ requests by returning a short result with an EOF flag. NFSD: Vulnerability caused by an underflow in ia_size due to a mismatch between signed and unsigned 64-bit file size values, which can cause issues when handling large file sizes from NFS clients. NFSD: Vulnerability handling large file sizes for NFSv3 improperly capping client size values larger than s64_max, leading to unexpected behavior and potential data corruption. sh: cpuinfo: warning for CONFIG_CPUMASK_OFFSTACK. When CONFIG_CPUMASK_OFFSTACK and CONFIG_DEBUG_PER_CPU_MAPS are selected, cpu_max_bits_warn() generates a runtime warning when showing /proc/cpuinfo. A failure in the -fstack-protector feature in GCC-based toolchains 
that target AArch64 allows an attacker to exploit an existing buffer 
overflow in dynamically-sized local variables in your application 
without this being detected. This stack-protector failure only applies 
to C99-style dynamically-sized local variables or those created using 
alloca(). The stack-protector operates as intended for statically-sized 
local variables.&lt;/p&gt;
&lt;p&gt;The default behavior when the stack-protector 
detects an overflow is to terminate your application, resulting…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;nfsd: NULL dereference in nfs3svc_encode_getaclres. scsi: core: use-after-free vulnerability. NFSD: vulnerability caused by loff_t overflow on the server when a client reads near the maximum offset, causing the server to return an EINVAL error, which the client retries indefinitely, instead of handling out-of-range READ requests by returning a short result with an EOF flag. NFSD: Vulnerability caused by an underflow in ia_size due to a mismatch between signed and unsigned 64-bit file size values, which can cause issues when handling large file sizes from NFS clients. NFSD: Vulnerability handling large file sizes for NFSv3 improperly capping client size values larger than s64_max, leading to unexpected behavior and potential data corruption. sh: cpuinfo: warning for CONFIG_CPUMASK_OFFSTACK. When CONFIG_CPUMASK_OFFSTACK and CONFIG_DEBUG_PER_CPU_MAPS are selected, cpu_max_bits_warn() generates a runtime warning when showing /proc/cpuinfo. A failure in the -fstack-protector feature in GCC-based toolchains 
that target AArch64 allows an attacker to exploit an existing buffer 
overflow in dynamically-sized local variables in your application 
without this being detected. This stack-protector failure only applies 
to C99-style dynamically-sized local variables or those created using 
alloca(). The stack-protector operates as intended for statically-sized 
local variables.&lt;/p&gt;
&lt;p&gt;The default behavior when the stack-protector 
detects an overflow is to terminate your application, resulting…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ssa-355557</guid>
    </item>
    <item>
      <title>SUSE-SU-2024:4314-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2024:4314-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:4314-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2024-47679</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-47679</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, 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 192 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: vfs: fix race between evice_inodes() and find_inode()&amp;amp;iput() Hi, all Recently I noticed a bug[1] in btrfs, after digged it into and I believe it&amp;#39;a race in vfs. Let&amp;#39;s assume there&amp;#39;s a inode (ie ino 261) with i_count 1 is called by iput(), and there&amp;#39;s a concurrent thread calling generic_shutdown_super(). cpu0:                              cpu1: iput() // i_count is 1   -&amp;gt;spin_lock(inode)   -&amp;gt;dec i_count to 0   -&amp;gt;iput_final()                    generic_shutdown_super()     -&amp;gt;__inode_add_lru()               -&amp;gt;evict_inodes()       // cause some reason[2]           -&amp;gt;if (atomic_read(inode-&amp;gt;i_count)) continue;       // return before                  // inode 261 passed the above check       // list_lru_add_obj()             // and then schedule out    -&amp;gt;spin_unlock() // note here: the inode 261 // was still at sb list and hash list, // and I_FREEING|I_WILL_FREE was not been set btrfs_iget()   // after some function calls   -&amp;gt;find_inode()     // found the above inode 261     -&amp;gt;spin_lock(inode)    // check I_FREEING|I_WILL_FREE    // and passed       -&amp;gt;__iget()     -&amp;gt;spin_unlock(inode)                // schedule back                                         -&amp;gt;spin_lock(inode)                                         // check (I_NEW|I_FREEING|I_WILL_FREE) flags,                                         // passed and set I_FREEING iput()                                  -&amp;gt;spin_unlock(inode)   -&amp;gt;spin_lock(inode)			  -&amp;gt;evic…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, 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 192 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: vfs: fix race between evice_inodes() and find_inode()&amp;amp;iput() Hi, all Recently I noticed a bug[1] in btrfs, after digged it into and I believe it&amp;#39;a race in vfs. Let&amp;#39;s assume there&amp;#39;s a inode (ie ino 261) with i_count 1 is called by iput(), and there&amp;#39;s a concurrent thread calling generic_shutdown_super(). cpu0:                              cpu1: iput() // i_count is 1   -&amp;gt;spin_lock(inode)   -&amp;gt;dec i_count to 0   -&amp;gt;iput_final()                    generic_shutdown_super()     -&amp;gt;__inode_add_lru()               -&amp;gt;evict_inodes()       // cause some reason[2]           -&amp;gt;if (atomic_read(inode-&amp;gt;i_count)) continue;       // return before                  // inode 261 passed the above check       // list_lru_add_obj()             // and then schedule out    -&amp;gt;spin_unlock() // note here: the inode 261 // was still at sb list and hash list, // and I_FREEING|I_WILL_FREE was not been set btrfs_iget()   // after some function calls   -&amp;gt;find_inode()     // found the above inode 261     -&amp;gt;spin_lock(inode)    // check I_FREEING|I_WILL_FREE    // and passed       -&amp;gt;__iget()     -&amp;gt;spin_unlock(inode)                // schedule back                                         -&amp;gt;spin_lock(inode)                                         // check (I_NEW|I_FREEING|I_WILL_FREE) flags,                                         // passed and set I_FREEING iput()                                  -&amp;gt;spin_unlock(inode)   -&amp;gt;spin_lock(inode)			  -&amp;gt;evic…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-47679</guid>
    </item>
    <item>
      <title>WID-SEC-W-2024-3251 — Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2024-3251</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder andere, nicht näher bekannte Auswirkungen zu erzielen..&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder andere, nicht näher bekannte Auswirkungen zu erzielen..&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2024-3251</guid>
    </item>
  </channel>
</rss>
