<?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 17:47:04 +0000</lastBuildDate>
    <item>
      <title>ALSA-2024:3306 — Moderate: kernel security and bug fix update</title>
      <link>https://cve.radiocsirt.org/vuln/alsa-2024:3306</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; AlmaLinux:9: bpftool, 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 and 52 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: netfilter: nf_tables: mark set as dead when unbinding anonymous set with timeout (CVE-2024-26643)
  * kernel: netfilter: nf_tables: disallow anonymous set with timeout flag (CVE-2024-26642)
  * kernel: netfilter: nft_ct: sanitize layer 3 and 4 protocol number in custom expectations (CVE-2024-26673)
  * kernel: net: ip_tunnel: prevent perpetual headroom growth (CVE-2024-26804)&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; AlmaLinux:9: bpftool, 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 and 52 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: netfilter: nf_tables: mark set as dead when unbinding anonymous set with timeout (CVE-2024-26643)
  * kernel: netfilter: nf_tables: disallow anonymous set with timeout flag (CVE-2024-26642)
  * kernel: netfilter: nft_ct: sanitize layer 3 and 4 protocol number in custom expectations (CVE-2024-26673)
  * kernel: net: ip_tunnel: prevent perpetual headroom growth (CVE-2024-26804)&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/alsa-2024:3306</guid>
    </item>
    <item>
      <title>bdu:2024-03771</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2024-03771</link>
      <description>bdu:2024-03771</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2024-03771</guid>
    </item>
    <item>
      <title>BELL-CVE-2024-26643</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2024-26643</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-26643</guid>
    </item>
    <item>
      <title>certfr-2024-avi-0334 — De multiples vulnérabilités ont été découvertes dans &lt;span
class="textit"&gt;le noyau Linux de Debian&lt;/span&gt;. Elles permet…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2024-avi-0334</link>
      <description>certfr-2024-avi-0334</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2024-avi-0334</guid>
    </item>
    <item>
      <title>EUVD-2026-345477</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-345477</link>
      <description>EUVD-2026-345477</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-345477</guid>
    </item>
    <item>
      <title>fkie_cve-2024-26643</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2024-26643</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;netfilter: nf_tables: mark set as dead when unbinding anonymous set with timeout&lt;/p&gt;
&lt;p&gt;While the rhashtable set gc runs asynchronously, a race allows it to
collect elements from anonymous sets with timeouts while it is being
released from the commit path.&lt;/p&gt;
&lt;p&gt;Mingi Cho originally reported this issue in a different path in 6.1.x
with a pipapo set with low timeouts which is not possible upstream since
7395dfacfff6 (&amp;#34;netfilter: nf_tables: use timestamp to check for set
element timeout&amp;#34;).&lt;/p&gt;
&lt;p&gt;Fix this by setting on the dead flag for anonymous sets to skip async gc
in this case.&lt;/p&gt;
&lt;p&gt;According to 08e4c8c5919f (&amp;#34;netfilter: nf_tables: mark newset as dead on
transaction abort&amp;#34;), Florian plans to accelerate abort path by releasing
objects via workqueue, therefore, this sets on the dead flag for abort
path too.&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;netfilter: nf_tables: mark set as dead when unbinding anonymous set with timeout&lt;/p&gt;
&lt;p&gt;While the rhashtable set gc runs asynchronously, a race allows it to
collect elements from anonymous sets with timeouts while it is being
released from the commit path.&lt;/p&gt;
&lt;p&gt;Mingi Cho originally reported this issue in a different path in 6.1.x
with a pipapo set with low timeouts which is not possible upstream since
7395dfacfff6 (&amp;#34;netfilter: nf_tables: use timestamp to check for set
element timeout&amp;#34;).&lt;/p&gt;
&lt;p&gt;Fix this by setting on the dead flag for anonymous sets to skip async gc
in this case.&lt;/p&gt;
&lt;p&gt;According to 08e4c8c5919f (&amp;#34;netfilter: nf_tables: mark newset as dead on
transaction abort&amp;#34;), Florian plans to accelerate abort path by releasing
objects via workqueue, therefore, this sets on the dead flag for abort
path too.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2024-26643</guid>
    </item>
    <item>
      <title>GHSA-ph5r-c8gc-xg6f</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-ph5r-c8gc-xg6f</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;netfilter: nf_tables: mark set as dead when unbinding anonymous set with timeout&lt;/p&gt;
&lt;p&gt;While the rhashtable set gc runs asynchronously, a race allows it to
collect elements from anonymous sets with timeouts while it is being
released from the commit path.&lt;/p&gt;
&lt;p&gt;Mingi Cho originally reported this issue in a different path in 6.1.x
with a pipapo set with low timeouts which is not possible upstream since
7395dfacfff6 (&amp;#34;netfilter: nf_tables: use timestamp to check for set
element timeout&amp;#34;).&lt;/p&gt;
&lt;p&gt;Fix this by setting on the dead flag for anonymous sets to skip async gc
in this case.&lt;/p&gt;
&lt;p&gt;According to 08e4c8c5919f (&amp;#34;netfilter: nf_tables: mark newset as dead on
transaction abort&amp;#34;), Florian plans to accelerate abort path by releasing
objects via workqueue, therefore, this sets on the dead flag for abort
path too.&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;netfilter: nf_tables: mark set as dead when unbinding anonymous set with timeout&lt;/p&gt;
&lt;p&gt;While the rhashtable set gc runs asynchronously, a race allows it to
collect elements from anonymous sets with timeouts while it is being
released from the commit path.&lt;/p&gt;
&lt;p&gt;Mingi Cho originally reported this issue in a different path in 6.1.x
with a pipapo set with low timeouts which is not possible upstream since
7395dfacfff6 (&amp;#34;netfilter: nf_tables: use timestamp to check for set
element timeout&amp;#34;).&lt;/p&gt;
&lt;p&gt;Fix this by setting on the dead flag for anonymous sets to skip async gc
in this case.&lt;/p&gt;
&lt;p&gt;According to 08e4c8c5919f (&amp;#34;netfilter: nf_tables: mark newset as dead on
transaction abort&amp;#34;), Florian plans to accelerate abort path by releasing
objects via workqueue, therefore, this sets on the dead flag for abort
path too.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-ph5r-c8gc-xg6f</guid>
    </item>
    <item>
      <title>gsd-2024-26643</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2024-26643</link>
      <description>gsd-2024-26643</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2024-26643</guid>
    </item>
    <item>
      <title>ICSA-24-102-01 — Siemens SIMATIC S7-1500 TM MFP</title>
      <link>https://cve.radiocsirt.org/vuln/icsa-24-102-01</link>
      <description>&lt;p&gt;An out-of-bounds (OOB) memory write flaw was found in the NFSD in the Linux kernel. Missing sanity may lead to a write beyond bmval[bmlen-1] in nfsd4_decode_bitmap4 in fs/nfsd/nfs4xdr.c. In this flaw, a local attacker with user privilege may gain access to out-of-bounds memory, leading to a system integrity and confidentiality threat. fs/nfsd/trace.h in the Linux kernel before 5.13.4 might allow remote attackers to cause a denial of service (out-of-bounds read in strlen) by sending NFS traffic when the trace event framework is being used for nfsd. SUNRPC: null pointer dereference in svc_rqst_free(). When alloc_pages_node() returns null in svc_rqst_alloc(), the null rq_scratch_page pointer will be dereferenced when calling put_page() in svc_rqst_free(). NFSD: READDIR buffer overflow. If a client sends a READDIR count argument that is too small (say, zero), then the buffer size calculation in the new init_dirlist helper functions results in an underflow, allowing the XDR stream functions to write beyond the actual buffer. This calculation has always been suspect. NFSD has never sanity- checked the READDIR count argument, but the old entry encoders managed the problem correctly. With the commits below, entry encoding changed, exposing the underflow to the pointer arithmetic in xdr_reserve_space(). Modern NFS clients attempt to retrieve as much data as possible for each READDIR request. nfsd: NULL dereference in nfs3svc_encode_getaclres. A NULL pointer dereference vulnerability…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;An out-of-bounds (OOB) memory write flaw was found in the NFSD in the Linux kernel. Missing sanity may lead to a write beyond bmval[bmlen-1] in nfsd4_decode_bitmap4 in fs/nfsd/nfs4xdr.c. In this flaw, a local attacker with user privilege may gain access to out-of-bounds memory, leading to a system integrity and confidentiality threat. fs/nfsd/trace.h in the Linux kernel before 5.13.4 might allow remote attackers to cause a denial of service (out-of-bounds read in strlen) by sending NFS traffic when the trace event framework is being used for nfsd. SUNRPC: null pointer dereference in svc_rqst_free(). When alloc_pages_node() returns null in svc_rqst_alloc(), the null rq_scratch_page pointer will be dereferenced when calling put_page() in svc_rqst_free(). NFSD: READDIR buffer overflow. If a client sends a READDIR count argument that is too small (say, zero), then the buffer size calculation in the new init_dirlist helper functions results in an underflow, allowing the XDR stream functions to write beyond the actual buffer. This calculation has always been suspect. NFSD has never sanity- checked the READDIR count argument, but the old entry encoders managed the problem correctly. With the commits below, entry encoding changed, exposing the underflow to the pointer arithmetic in xdr_reserve_space(). Modern NFS clients attempt to retrieve as much data as possible for each READDIR request. nfsd: NULL dereference in nfs3svc_encode_getaclres. A NULL pointer dereference vulnerability…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/icsa-24-102-01</guid>
    </item>
    <item>
      <title>OESA-2024-1682 — kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/oesa-2024-1682</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:22.03-LTS-SP3: 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/amdgpu: handle the case of pci_channel_io_frozen only in amdgpu_pci_resume&#13;
&#13;
In current code, when a PCI error state pci_channel_io_normal is detectd,
it will report PCI_ERS_RESULT_CAN_RECOVER status to PCI driver, and PCI
driver will continue the execution of PCI resume callback report_resume by
pci_walk_bridge, and the callback will go into amdgpu_pci_resume
finally, where write lock is releasd unconditionally without acquiring
such lock first. In this case, a deadlock will happen when other threads
start to acquire the read lock.&#13;
&#13;
To fix this, add a member in amdgpu_device strucutre to cache
pci_channel_state, and only continue the execution in amdgpu_pci_resume
when it&amp;amp;apos;s pci_channel_io_frozen.(CVE-2021-47421)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
ptp: Fix possible memory leak in ptp_clock_register()&#13;
&#13;
I got memory leak as follows when doing fault injection test:&#13;
&#13;
unreferenced object 0xffff88800906c618 (size 8):
  comm &amp;amp;quot;i2c-idt82p33931&amp;amp;quot;, pid 4421, jiffies 4294948083 (age 13.188s)
  hex dump (first 8 bytes):
    70 74 70 30 00 00 00 00                          ptp0....
  backtrace:
    [&amp;amp;lt;00000000312ed458&amp;amp;gt;] __kmalloc_track_caller+0x19f/0x3a0
    [&amp;amp;lt;0000000079f6e2ff&amp;amp;gt;] kvasprintf+0xb5/0x150
    [&amp;amp;lt;0000000026aae54f&amp;amp;gt;] kvasprintf_const+0x60/0x190
    [&amp;amp;lt;000…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:22.03-LTS-SP3: 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/amdgpu: handle the case of pci_channel_io_frozen only in amdgpu_pci_resume&#13;
&#13;
In current code, when a PCI error state pci_channel_io_normal is detectd,
it will report PCI_ERS_RESULT_CAN_RECOVER status to PCI driver, and PCI
driver will continue the execution of PCI resume callback report_resume by
pci_walk_bridge, and the callback will go into amdgpu_pci_resume
finally, where write lock is releasd unconditionally without acquiring
such lock first. In this case, a deadlock will happen when other threads
start to acquire the read lock.&#13;
&#13;
To fix this, add a member in amdgpu_device strucutre to cache
pci_channel_state, and only continue the execution in amdgpu_pci_resume
when it&amp;amp;apos;s pci_channel_io_frozen.(CVE-2021-47421)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
ptp: Fix possible memory leak in ptp_clock_register()&#13;
&#13;
I got memory leak as follows when doing fault injection test:&#13;
&#13;
unreferenced object 0xffff88800906c618 (size 8):
  comm &amp;amp;quot;i2c-idt82p33931&amp;amp;quot;, pid 4421, jiffies 4294948083 (age 13.188s)
  hex dump (first 8 bytes):
    70 74 70 30 00 00 00 00                          ptp0....
  backtrace:
    [&amp;amp;lt;00000000312ed458&amp;amp;gt;] __kmalloc_track_caller+0x19f/0x3a0
    [&amp;amp;lt;0000000079f6e2ff&amp;amp;gt;] kvasprintf+0xb5/0x150
    [&amp;amp;lt;0000000026aae54f&amp;amp;gt;] kvasprintf_const+0x60/0x190
    [&amp;amp;lt;000…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/oesa-2024-1682</guid>
    </item>
    <item>
      <title>RHSA-2024:3306 — Red Hat Security Advisory: kernel security and bug fix update</title>
      <link>https://cve.radiocsirt.org/vuln/rhsa-2024:3306</link>
      <description>&lt;p&gt;kernel: netfilter: nf_tables: disallow anonymous set with timeout flag kernel: netfilter: nf_tables: mark set as dead when unbinding anonymous set with timeout kernel: netfilter: nft_ct: sanitize layer 3 and 4 protocol number in custom expectations kernel: net: ip_tunnel: prevent perpetual headroom growth kernel: gro: fix ownership transfer&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;kernel: netfilter: nf_tables: disallow anonymous set with timeout flag kernel: netfilter: nf_tables: mark set as dead when unbinding anonymous set with timeout kernel: netfilter: nft_ct: sanitize layer 3 and 4 protocol number in custom expectations kernel: net: ip_tunnel: prevent perpetual headroom growth kernel: gro: fix ownership transfer&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rhsa-2024:3306</guid>
    </item>
    <item>
      <title>RHSA-2024:3460 — Red Hat Security Advisory: kernel-rt security and bug fix update</title>
      <link>https://cve.radiocsirt.org/vuln/rhsa-2024:3460</link>
      <description>&lt;p&gt;kernel: netfilter: nf_tables: disallow anonymous set with timeout flag kernel: netfilter: nf_tables: mark set as dead when unbinding anonymous set with timeout kernel: netfilter: nft_ct: sanitize layer 3 and 4 protocol number in custom expectations kernel: ipv6: sr: fix possible use-after-free and null-ptr-deref kernel: net: ip_tunnel: prevent perpetual headroom growth kernel: cifs: fix underflow in parse_server_interfaces() kernel: fs: sysfs: Fix reference leak in sysfs_break_active_protection()&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;kernel: netfilter: nf_tables: disallow anonymous set with timeout flag kernel: netfilter: nf_tables: mark set as dead when unbinding anonymous set with timeout kernel: netfilter: nft_ct: sanitize layer 3 and 4 protocol number in custom expectations kernel: ipv6: sr: fix possible use-after-free and null-ptr-deref kernel: net: ip_tunnel: prevent perpetual headroom growth kernel: cifs: fix underflow in parse_server_interfaces() kernel: fs: sysfs: Fix reference leak in sysfs_break_active_protection()&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rhsa-2024:3460</guid>
    </item>
    <item>
      <title>SSA-265688 — SSA-265688: Vulnerabilities in the additional GNU/Linux subsystem of the SIMATIC S7-1500 TM MFP V1.1</title>
      <link>https://cve.radiocsirt.org/vuln/ssa-265688</link>
      <description>&lt;p&gt;An out-of-bounds (OOB) memory write flaw was found in the NFSD in the Linux kernel. Missing sanity may lead to a write beyond bmval[bmlen-1] in nfsd4_decode_bitmap4 in fs/nfsd/nfs4xdr.c. In this flaw, a local attacker with user privilege may gain access to out-of-bounds memory, leading to a system integrity and confidentiality threat. fs/nfsd/trace.h in the Linux kernel before 5.13.4 might allow remote attackers to cause a denial of service (out-of-bounds read in strlen) by sending NFS traffic when the trace event framework is being used for nfsd. SUNRPC: null pointer dereference in svc_rqst_free(). When alloc_pages_node() returns null in svc_rqst_alloc(), the null rq_scratch_page pointer will be dereferenced when calling put_page() in svc_rqst_free(). NFSD: READDIR buffer overflow. If a client sends a READDIR count argument that is too small (say, zero), then the buffer size calculation in the new init_dirlist helper functions results in an underflow, allowing the XDR stream functions to write beyond the actual buffer. This calculation has always been suspect. NFSD has never sanity- checked the READDIR count argument, but the old entry encoders managed the problem correctly. With the commits below, entry encoding changed, exposing the underflow to the pointer arithmetic in xdr_reserve_space(). Modern NFS clients attempt to retrieve as much data as possible for each READDIR request. nfsd: NULL dereference in nfs3svc_encode_getaclres. A NULL pointer dereference vulnerability…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;An out-of-bounds (OOB) memory write flaw was found in the NFSD in the Linux kernel. Missing sanity may lead to a write beyond bmval[bmlen-1] in nfsd4_decode_bitmap4 in fs/nfsd/nfs4xdr.c. In this flaw, a local attacker with user privilege may gain access to out-of-bounds memory, leading to a system integrity and confidentiality threat. fs/nfsd/trace.h in the Linux kernel before 5.13.4 might allow remote attackers to cause a denial of service (out-of-bounds read in strlen) by sending NFS traffic when the trace event framework is being used for nfsd. SUNRPC: null pointer dereference in svc_rqst_free(). When alloc_pages_node() returns null in svc_rqst_alloc(), the null rq_scratch_page pointer will be dereferenced when calling put_page() in svc_rqst_free(). NFSD: READDIR buffer overflow. If a client sends a READDIR count argument that is too small (say, zero), then the buffer size calculation in the new init_dirlist helper functions results in an underflow, allowing the XDR stream functions to write beyond the actual buffer. This calculation has always been suspect. NFSD has never sanity- checked the READDIR count argument, but the old entry encoders managed the problem correctly. With the commits below, entry encoding changed, exposing the underflow to the pointer arithmetic in xdr_reserve_space(). Modern NFS clients attempt to retrieve as much data as possible for each READDIR request. nfsd: NULL dereference in nfs3svc_encode_getaclres. A NULL pointer dereference vulnerability…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ssa-265688</guid>
    </item>
    <item>
      <title>SUSE-SU-2024:2008-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2024:2008-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:2008-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2024-26643</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-26643</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 126 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: netfilter: nf_tables: mark set as dead when unbinding anonymous set with timeout While the rhashtable set gc runs asynchronously, a race allows it to collect elements from anonymous sets with timeouts while it is being released from the commit path. Mingi Cho originally reported this issue in a different path in 6.1.x with a pipapo set with low timeouts which is not possible upstream since 7395dfacfff6 (&amp;#34;netfilter: nf_tables: use timestamp to check for set element timeout&amp;#34;). Fix this by setting on the dead flag for anonymous sets to skip async gc in this case. According to 08e4c8c5919f (&amp;#34;netfilter: nf_tables: mark newset as dead on transaction abort&amp;#34;), Florian plans to accelerate abort path by releasing objects via workqueue, therefore, this sets on the dead flag for abort path too.&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 126 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: netfilter: nf_tables: mark set as dead when unbinding anonymous set with timeout While the rhashtable set gc runs asynchronously, a race allows it to collect elements from anonymous sets with timeouts while it is being released from the commit path. Mingi Cho originally reported this issue in a different path in 6.1.x with a pipapo set with low timeouts which is not possible upstream since 7395dfacfff6 (&amp;#34;netfilter: nf_tables: use timestamp to check for set element timeout&amp;#34;). Fix this by setting on the dead flag for anonymous sets to skip async gc in this case. According to 08e4c8c5919f (&amp;#34;netfilter: nf_tables: mark newset as dead on transaction abort&amp;#34;), Florian plans to accelerate abort path by releasing objects via workqueue, therefore, this sets on the dead flag for abort path too.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-26643</guid>
    </item>
    <item>
      <title>WID-SEC-W-2024-0694 — Linux Kernel: Schwachstelle ermöglicht nicht spezifizierten Angriff</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2024-0694</link>
      <description>&lt;p&gt;Ein lokaler Angreifer kann eine Schwachstelle im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein lokaler Angreifer kann eine Schwachstelle im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2024-0694</guid>
    </item>
  </channel>
</rss>
