<?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 21:28:00 +0000</lastBuildDate>
    <item>
      <title>bdu:2025-01119</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2025-01119</link>
      <description>bdu:2025-01119</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2025-01119</guid>
    </item>
    <item>
      <title>BELL-CVE-2024-56614</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2024-56614</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-56614</guid>
    </item>
    <item>
      <title>certfr-2025-avi-0088 — 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-0088</link>
      <description>certfr-2025-avi-0088</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2025-avi-0088</guid>
    </item>
    <item>
      <title>cnvd-2025-01679</title>
      <link>https://cve.radiocsirt.org/vuln/cnvd-2025-01679</link>
      <description>cnvd-2025-01679</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cnvd-2025-01679</guid>
    </item>
    <item>
      <title>EUVD-2026-313760</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-313760</link>
      <description>EUVD-2026-313760</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-313760</guid>
    </item>
    <item>
      <title>fkie_cve-2024-56614</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2024-56614</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;xsk: fix OOB map writes when deleting elements&lt;/p&gt;
&lt;p&gt;Jordy says:&lt;/p&gt;
&lt;p&gt;&amp;#34;
In the xsk_map_delete_elem function an unsigned integer
(map-&amp;gt;max_entries) is compared with a user-controlled signed integer
(k). Due to implicit type conversion, a large unsigned value for
map-&amp;gt;max_entries can bypass the intended bounds check:&lt;/p&gt;
&lt;p&gt;if (k &amp;gt;= map-&amp;gt;max_entries)
		return -EINVAL;&lt;/p&gt;
&lt;p&gt;This allows k to hold a negative value (between -2147483648 and -2),
which is then used as an array index in m-&amp;gt;xsk_map[k], which results
in an out-of-bounds access.&lt;/p&gt;
&lt;p&gt;spin_lock_bh(&amp;amp;m-&amp;gt;lock);
	map_entry = &amp;amp;m-&amp;gt;xsk_map[k]; // Out-of-bounds map_entry
	old_xs = unrcu_pointer(xchg(map_entry, NULL));  // Oob write
	if (old_xs)
		xsk_map_sock_delete(old_xs, map_entry);
	spin_unlock_bh(&amp;amp;m-&amp;gt;lock);&lt;/p&gt;
&lt;p&gt;The xchg operation can then be used to cause an out-of-bounds write.
Moreover, the invalid map_entry passed to xsk_map_sock_delete can lead
to further memory corruption.
&amp;#34;&lt;/p&gt;
&lt;p&gt;It indeed results in following splat:&lt;/p&gt;
&lt;p&gt;[76612.897343] BUG: unable to handle page fault for address: ffffc8fc2e461108
[76612.904330] #PF: supervisor write access in kernel mode
[76612.909639] #PF: error_code(0x0002) - not-present page
[76612.914855] PGD 0 P4D 0
[76612.917431] Oops: Oops: 0002 [#1] PREEMPT SMP
[76612.921859] CPU: 11 UID: 0 PID: 10318 Comm: a.out Not tainted 6.12.0-rc1+ #470
[76612.929189] Hardware name: Intel Corporation S2600WFT/S2600WFT, BIOS SE5C620.86B.02.01.0008.031920191559 03/19/20…&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;xsk: fix OOB map writes when deleting elements&lt;/p&gt;
&lt;p&gt;Jordy says:&lt;/p&gt;
&lt;p&gt;&amp;#34;
In the xsk_map_delete_elem function an unsigned integer
(map-&amp;gt;max_entries) is compared with a user-controlled signed integer
(k). Due to implicit type conversion, a large unsigned value for
map-&amp;gt;max_entries can bypass the intended bounds check:&lt;/p&gt;
&lt;p&gt;if (k &amp;gt;= map-&amp;gt;max_entries)
		return -EINVAL;&lt;/p&gt;
&lt;p&gt;This allows k to hold a negative value (between -2147483648 and -2),
which is then used as an array index in m-&amp;gt;xsk_map[k], which results
in an out-of-bounds access.&lt;/p&gt;
&lt;p&gt;spin_lock_bh(&amp;amp;m-&amp;gt;lock);
	map_entry = &amp;amp;m-&amp;gt;xsk_map[k]; // Out-of-bounds map_entry
	old_xs = unrcu_pointer(xchg(map_entry, NULL));  // Oob write
	if (old_xs)
		xsk_map_sock_delete(old_xs, map_entry);
	spin_unlock_bh(&amp;amp;m-&amp;gt;lock);&lt;/p&gt;
&lt;p&gt;The xchg operation can then be used to cause an out-of-bounds write.
Moreover, the invalid map_entry passed to xsk_map_sock_delete can lead
to further memory corruption.
&amp;#34;&lt;/p&gt;
&lt;p&gt;It indeed results in following splat:&lt;/p&gt;
&lt;p&gt;[76612.897343] BUG: unable to handle page fault for address: ffffc8fc2e461108
[76612.904330] #PF: supervisor write access in kernel mode
[76612.909639] #PF: error_code(0x0002) - not-present page
[76612.914855] PGD 0 P4D 0
[76612.917431] Oops: Oops: 0002 [#1] PREEMPT SMP
[76612.921859] CPU: 11 UID: 0 PID: 10318 Comm: a.out Not tainted 6.12.0-rc1+ #470
[76612.929189] Hardware name: Intel Corporation S2600WFT/S2600WFT, BIOS SE5C620.86B.02.01.0008.031920191559 03/19/20…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2024-56614</guid>
    </item>
    <item>
      <title>GHSA-v9jf-g2rr-85c3</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-v9jf-g2rr-85c3</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;xsk: fix OOB map writes when deleting elements&lt;/p&gt;
&lt;p&gt;Jordy says:&lt;/p&gt;
&lt;p&gt;&amp;#34;
In the xsk_map_delete_elem function an unsigned integer
(map-&amp;gt;max_entries) is compared with a user-controlled signed integer
(k). Due to implicit type conversion, a large unsigned value for
map-&amp;gt;max_entries can bypass the intended bounds check:&lt;/p&gt;
&lt;p&gt;if (k &amp;gt;= map-&amp;gt;max_entries)
		return -EINVAL;&lt;/p&gt;
&lt;p&gt;This allows k to hold a negative value (between -2147483648 and -2),
which is then used as an array index in m-&amp;gt;xsk_map[k], which results
in an out-of-bounds access.&lt;/p&gt;
&lt;p&gt;spin_lock_bh(&amp;amp;m-&amp;gt;lock);
	map_entry = &amp;amp;m-&amp;gt;xsk_map[k]; // Out-of-bounds map_entry
	old_xs = unrcu_pointer(xchg(map_entry, NULL));  // Oob write
	if (old_xs)
		xsk_map_sock_delete(old_xs, map_entry);
	spin_unlock_bh(&amp;amp;m-&amp;gt;lock);&lt;/p&gt;
&lt;p&gt;The xchg operation can then be used to cause an out-of-bounds write.
Moreover, the invalid map_entry passed to xsk_map_sock_delete can lead
to further memory corruption.
&amp;#34;&lt;/p&gt;
&lt;p&gt;It indeed results in following splat:&lt;/p&gt;
&lt;p&gt;[76612.897343] BUG: unable to handle page fault for address: ffffc8fc2e461108
[76612.904330] #PF: supervisor write access in kernel mode
[76612.909639] #PF: error_code(0x0002) - not-present page
[76612.914855] PGD 0 P4D 0
[76612.917431] Oops: Oops: 0002 [#1] PREEMPT SMP
[76612.921859] CPU: 11 UID: 0 PID: 10318 Comm: a.out Not tainted 6.12.0-rc1+ #470
[76612.929189] Hardware name: Intel Corporation S2600WFT/S2600WFT, BIOS SE5C620.86B.02.01.0008.031920191559 03/19/20…&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;xsk: fix OOB map writes when deleting elements&lt;/p&gt;
&lt;p&gt;Jordy says:&lt;/p&gt;
&lt;p&gt;&amp;#34;
In the xsk_map_delete_elem function an unsigned integer
(map-&amp;gt;max_entries) is compared with a user-controlled signed integer
(k). Due to implicit type conversion, a large unsigned value for
map-&amp;gt;max_entries can bypass the intended bounds check:&lt;/p&gt;
&lt;p&gt;if (k &amp;gt;= map-&amp;gt;max_entries)
		return -EINVAL;&lt;/p&gt;
&lt;p&gt;This allows k to hold a negative value (between -2147483648 and -2),
which is then used as an array index in m-&amp;gt;xsk_map[k], which results
in an out-of-bounds access.&lt;/p&gt;
&lt;p&gt;spin_lock_bh(&amp;amp;m-&amp;gt;lock);
	map_entry = &amp;amp;m-&amp;gt;xsk_map[k]; // Out-of-bounds map_entry
	old_xs = unrcu_pointer(xchg(map_entry, NULL));  // Oob write
	if (old_xs)
		xsk_map_sock_delete(old_xs, map_entry);
	spin_unlock_bh(&amp;amp;m-&amp;gt;lock);&lt;/p&gt;
&lt;p&gt;The xchg operation can then be used to cause an out-of-bounds write.
Moreover, the invalid map_entry passed to xsk_map_sock_delete can lead
to further memory corruption.
&amp;#34;&lt;/p&gt;
&lt;p&gt;It indeed results in following splat:&lt;/p&gt;
&lt;p&gt;[76612.897343] BUG: unable to handle page fault for address: ffffc8fc2e461108
[76612.904330] #PF: supervisor write access in kernel mode
[76612.909639] #PF: error_code(0x0002) - not-present page
[76612.914855] PGD 0 P4D 0
[76612.917431] Oops: Oops: 0002 [#1] PREEMPT SMP
[76612.921859] CPU: 11 UID: 0 PID: 10318 Comm: a.out Not tainted 6.12.0-rc1+ #470
[76612.929189] Hardware name: Intel Corporation S2600WFT/S2600WFT, BIOS SE5C620.86B.02.01.0008.031920191559 03/19/20…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-v9jf-g2rr-85c3</guid>
    </item>
    <item>
      <title>msrc_CVE-2024-56614 — xsk: fix OOB map writes when deleting elements</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2024-56614</link>
      <description>msrc_CVE-2024-56614</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2024-56614</guid>
    </item>
    <item>
      <title>OESA-2025-1093 — kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/oesa-2025-1093</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:24.03-LTS-SP1: 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;net: dsa: improve shutdown sequence&lt;/p&gt;
&lt;p&gt;Alexander Sverdlin presents 2 problems during shutdown with the
lan9303 driver. One is specific to lan9303 and the other just happens
to reproduce there.&lt;/p&gt;
&lt;p&gt;The first problem is that lan9303 is unique among DSA drivers in that it
calls dev_get_drvdata() at &amp;amp;quot;arbitrary runtime&amp;amp;quot; (not probe, not shutdown,
not remove):&lt;/p&gt;
&lt;p&gt;phy_state_machine()
-&amp;amp;gt; ...
   -&amp;amp;gt; dsa_user_phy_read()
      -&amp;amp;gt; ds-&amp;amp;gt;ops-&amp;amp;gt;phy_read()
         -&amp;amp;gt; lan9303_phy_read()
            -&amp;amp;gt; chip-&amp;amp;gt;ops-&amp;amp;gt;phy_read()
               -&amp;amp;gt; lan9303_mdio_phy_read()
                  -&amp;amp;gt;…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:24.03-LTS-SP1: 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;net: dsa: improve shutdown sequence&lt;/p&gt;
&lt;p&gt;Alexander Sverdlin presents 2 problems during shutdown with the
lan9303 driver. One is specific to lan9303 and the other just happens
to reproduce there.&lt;/p&gt;
&lt;p&gt;The first problem is that lan9303 is unique among DSA drivers in that it
calls dev_get_drvdata() at &amp;amp;quot;arbitrary runtime&amp;amp;quot; (not probe, not shutdown,
not remove):&lt;/p&gt;
&lt;p&gt;phy_state_machine()
-&amp;amp;gt; ...
   -&amp;amp;gt; dsa_user_phy_read()
      -&amp;amp;gt; ds-&amp;amp;gt;ops-&amp;amp;gt;phy_read()
         -&amp;amp;gt; lan9303_phy_read()
            -&amp;amp;gt; chip-&amp;amp;gt;ops-&amp;amp;gt;phy_read()
               -&amp;amp;gt; lan9303_mdio_phy_read()
                  -&amp;amp;gt;…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/oesa-2025-1093</guid>
    </item>
    <item>
      <title>RHSA-2025:10536 — Red Hat Security Advisory: kernel-rt security update</title>
      <link>https://cve.radiocsirt.org/vuln/rhsa-2025:10536</link>
      <description>&lt;p&gt;kernel: xsk: fix OOB map writes when deleting elements kernel: bpf: fix OOB devmap writes when deleting elements kernel: md: fix mddev uaf while iterating all_mddevs list&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;kernel: xsk: fix OOB map writes when deleting elements kernel: bpf: fix OOB devmap writes when deleting elements kernel: md: fix mddev uaf while iterating all_mddevs list&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rhsa-2025:10536</guid>
    </item>
    <item>
      <title>RHSA-2025:6966 — Red Hat Security Advisory: kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/rhsa-2025:6966</link>
      <description>&lt;p&gt;kernel: xen-netfront: Fix NULL sring after live migration kernel: fscache: Fix oops due to race with cookie_lru and use_cookie kernel: tracing: Free buffers when a used dynamic event is removed kernel: net: tun: Fix use-after-free in tun_detach() kernel: hwmon: (ibmpex) Fix possible UAF when ibmpex_register_bmc() fails kernel: erofs/zmap.c: Fix incorrect offset calculation kernel: arm64/mm: fix incorrect file_map_count for non-leaf pmd/pud kernel: s390: avoid using global register for current_stack_pointer kernel: erofs: fix missing xas_retry() in fscache mode kernel: rpmsg: qcom_smd: Fix refcount leak in qcom_smd_parse_edge kernel: remoteproc: k3-r5: Fix refcount leak in k3_r5_cluster_of_init kernel: of: check previous kernel&amp;#39;s ima-kexec-buffer against memory bounds kernel: coresight: Clear the connection field properly kernel: Linux kernel: Denial of Service in coresight: trbe kernel: rpmsg: char: Avoid double destroy of default endpoint kernel: coresight: cti: Fix hang in cti_disable_hw() kernel: lib/fonts: fix undefined behavior in bit shift for get_default_font kernel: Kernel: Denial of Service in pci_endpoint_test due to zero-length DMA mapping kernel: Linux kernel: Denial of Service in erofs due to memory leak kernel: erofs: fix missing unmap if z_erofs_get_extent_compressedlen() fails kernel: pipe: wakeup wr_wait after setting max_usage kernel: ntb: intel: Fix the NULL vs IS_ERR() bug for debugfs_create_dir() kernel: qed/qed_sriov: guard against NULL derefs from qed_…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;kernel: xen-netfront: Fix NULL sring after live migration kernel: fscache: Fix oops due to race with cookie_lru and use_cookie kernel: tracing: Free buffers when a used dynamic event is removed kernel: net: tun: Fix use-after-free in tun_detach() kernel: hwmon: (ibmpex) Fix possible UAF when ibmpex_register_bmc() fails kernel: erofs/zmap.c: Fix incorrect offset calculation kernel: arm64/mm: fix incorrect file_map_count for non-leaf pmd/pud kernel: s390: avoid using global register for current_stack_pointer kernel: erofs: fix missing xas_retry() in fscache mode kernel: rpmsg: qcom_smd: Fix refcount leak in qcom_smd_parse_edge kernel: remoteproc: k3-r5: Fix refcount leak in k3_r5_cluster_of_init kernel: of: check previous kernel&amp;#39;s ima-kexec-buffer against memory bounds kernel: coresight: Clear the connection field properly kernel: Linux kernel: Denial of Service in coresight: trbe kernel: rpmsg: char: Avoid double destroy of default endpoint kernel: coresight: cti: Fix hang in cti_disable_hw() kernel: lib/fonts: fix undefined behavior in bit shift for get_default_font kernel: Kernel: Denial of Service in pci_endpoint_test due to zero-length DMA mapping kernel: Linux kernel: Denial of Service in erofs due to memory leak kernel: erofs: fix missing unmap if z_erofs_get_extent_compressedlen() fails kernel: pipe: wakeup wr_wait after setting max_usage kernel: ntb: intel: Fix the NULL vs IS_ERR() bug for debugfs_create_dir() kernel: qed/qed_sriov: guard against NULL derefs from qed_…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rhsa-2025:6966</guid>
    </item>
    <item>
      <title>SUSE-SU-2025:0289-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2025:0289-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:0289-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2024-56614</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-56614</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 168 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: xsk: fix OOB map writes when deleting elements Jordy says: &amp;#34; In the xsk_map_delete_elem function an unsigned integer (map-&amp;gt;max_entries) is compared with a user-controlled signed integer (k). Due to implicit type conversion, a large unsigned value for map-&amp;gt;max_entries can bypass the intended bounds check: 	if (k &amp;gt;= map-&amp;gt;max_entries) 		return -EINVAL; This allows k to hold a negative value (between -2147483648 and -2), which is then used as an array index in m-&amp;gt;xsk_map[k], which results in an out-of-bounds access. 	spin_lock_bh(&amp;amp;m-&amp;gt;lock); 	map_entry = &amp;amp;m-&amp;gt;xsk_map[k]; // Out-of-bounds map_entry 	old_xs = unrcu_pointer(xchg(map_entry, NULL));  // Oob write 	if (old_xs) 		xsk_map_sock_delete(old_xs, map_entry); 	spin_unlock_bh(&amp;amp;m-&amp;gt;lock); The xchg operation can then be used to cause an out-of-bounds write. Moreover, the invalid map_entry passed to xsk_map_sock_delete can lead to further memory corruption. &amp;#34; It indeed results in following splat: [76612.897343] BUG: unable to handle page fault for address: ffffc8fc2e461108 [76612.904330] #PF: supervisor write access in kernel mode [76612.909639] #PF: error_code(0x0002) - not-present page [76612.914855] PGD 0 P4D 0 [76612.917431] Oops: Oops: 0002 [#1] PREEMPT SMP [76612.921859] CPU: 11 UID: 0 PID: 10318 Comm: a.out Not tainted 6.12.0-rc1+ #470 [76612.929189] Hardware name: Intel Corporation S2600WFT/S2600WFT, BIOS SE5C620.86B.02.01.0008.031920191559 03/19/2019 [76612…&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 168 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: xsk: fix OOB map writes when deleting elements Jordy says: &amp;#34; In the xsk_map_delete_elem function an unsigned integer (map-&amp;gt;max_entries) is compared with a user-controlled signed integer (k). Due to implicit type conversion, a large unsigned value for map-&amp;gt;max_entries can bypass the intended bounds check: 	if (k &amp;gt;= map-&amp;gt;max_entries) 		return -EINVAL; This allows k to hold a negative value (between -2147483648 and -2), which is then used as an array index in m-&amp;gt;xsk_map[k], which results in an out-of-bounds access. 	spin_lock_bh(&amp;amp;m-&amp;gt;lock); 	map_entry = &amp;amp;m-&amp;gt;xsk_map[k]; // Out-of-bounds map_entry 	old_xs = unrcu_pointer(xchg(map_entry, NULL));  // Oob write 	if (old_xs) 		xsk_map_sock_delete(old_xs, map_entry); 	spin_unlock_bh(&amp;amp;m-&amp;gt;lock); The xchg operation can then be used to cause an out-of-bounds write. Moreover, the invalid map_entry passed to xsk_map_sock_delete can lead to further memory corruption. &amp;#34; It indeed results in following splat: [76612.897343] BUG: unable to handle page fault for address: ffffc8fc2e461108 [76612.904330] #PF: supervisor write access in kernel mode [76612.909639] #PF: error_code(0x0002) - not-present page [76612.914855] PGD 0 P4D 0 [76612.917431] Oops: Oops: 0002 [#1] PREEMPT SMP [76612.921859] CPU: 11 UID: 0 PID: 10318 Comm: a.out Not tainted 6.12.0-rc1+ #470 [76612.929189] Hardware name: Intel Corporation S2600WFT/S2600WFT, BIOS SE5C620.86B.02.01.0008.031920191559 03/19/2019 [76612…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-56614</guid>
    </item>
    <item>
      <title>WID-SEC-W-2024-3762 — Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2024-3762</link>
      <description>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen und um nicht näher beschriebene Effekte zu erzielen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen und um nicht näher beschriebene Effekte zu erzielen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2024-3762</guid>
    </item>
  </channel>
</rss>
