<?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://db.gcve.eu</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>Mon, 12 Oct 2026 12:54:12 +0000</lastBuildDate>
    <item>
      <title>bdu:2024-09821</title>
      <link>https://db.gcve.eu/vuln/bdu:2024-09821</link>
      <description>bdu:2024-09821</description>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/bdu:2024-09821</guid>
    </item>
    <item>
      <title>certfr-2024-avi-0527 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian LTS. Elles permettent à un attaquant de p…</title>
      <link>https://db.gcve.eu/vuln/certfr-2024-avi-0527</link>
      <description>certfr-2024-avi-0527</description>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/certfr-2024-avi-0527</guid>
    </item>
    <item>
      <title>fkie_cve-2023-52672</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2023-52672</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;pipe: wakeup wr_wait after setting max_usage&lt;/p&gt;
&lt;p&gt;Commit c73be61cede5 (&amp;#34;pipe: Add general notification queue support&amp;#34;) a
regression was introduced that would lock up resized pipes under certain
conditions. See the reproducer in [1].&lt;/p&gt;
&lt;p&gt;The commit resizing the pipe ring size was moved to a different
function, doing that moved the wakeup for pipe-&amp;gt;wr_wait before actually
raising pipe-&amp;gt;max_usage. If a pipe was full before the resize occured it
would result in the wakeup never actually triggering pipe_write.&lt;/p&gt;
&lt;p&gt;Set @max_usage and @nr_accounted before waking writers if this isn&amp;#39;t a
watch queue.&lt;/p&gt;
&lt;p&gt;[Christian Brauner &amp;lt;brauner@kernel.org&amp;gt;: rewrite to account for watch queues]&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;pipe: wakeup wr_wait after setting max_usage&lt;/p&gt;
&lt;p&gt;Commit c73be61cede5 (&amp;#34;pipe: Add general notification queue support&amp;#34;) a
regression was introduced that would lock up resized pipes under certain
conditions. See the reproducer in [1].&lt;/p&gt;
&lt;p&gt;The commit resizing the pipe ring size was moved to a different
function, doing that moved the wakeup for pipe-&amp;gt;wr_wait before actually
raising pipe-&amp;gt;max_usage. If a pipe was full before the resize occured it
would result in the wakeup never actually triggering pipe_write.&lt;/p&gt;
&lt;p&gt;Set @max_usage and @nr_accounted before waking writers if this isn&amp;#39;t a
watch queue.&lt;/p&gt;
&lt;p&gt;[Christian Brauner &amp;lt;brauner@kernel.org&amp;gt;: rewrite to account for watch queues]&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2023-52672</guid>
    </item>
    <item>
      <title>GHSA-7gxw-6q7r-q63r</title>
      <link>https://db.gcve.eu/vuln/ghsa-7gxw-6q7r-q63r</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;pipe: wakeup wr_wait after setting max_usage&lt;/p&gt;
&lt;p&gt;Commit c73be61cede5 (&amp;#34;pipe: Add general notification queue support&amp;#34;) a
regression was introduced that would lock up resized pipes under certain
conditions. See the reproducer in [1].&lt;/p&gt;
&lt;p&gt;The commit resizing the pipe ring size was moved to a different
function, doing that moved the wakeup for pipe-&amp;gt;wr_wait before actually
raising pipe-&amp;gt;max_usage. If a pipe was full before the resize occured it
would result in the wakeup never actually triggering pipe_write.&lt;/p&gt;
&lt;p&gt;Set @max_usage and @nr_accounted before waking writers if this isn&amp;#39;t a
watch queue.&lt;/p&gt;
&lt;p&gt;[Christian Brauner &amp;lt;brauner@kernel.org&amp;gt;: rewrite to account for watch queues]&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;pipe: wakeup wr_wait after setting max_usage&lt;/p&gt;
&lt;p&gt;Commit c73be61cede5 (&amp;#34;pipe: Add general notification queue support&amp;#34;) a
regression was introduced that would lock up resized pipes under certain
conditions. See the reproducer in [1].&lt;/p&gt;
&lt;p&gt;The commit resizing the pipe ring size was moved to a different
function, doing that moved the wakeup for pipe-&amp;gt;wr_wait before actually
raising pipe-&amp;gt;max_usage. If a pipe was full before the resize occured it
would result in the wakeup never actually triggering pipe_write.&lt;/p&gt;
&lt;p&gt;Set @max_usage and @nr_accounted before waking writers if this isn&amp;#39;t a
watch queue.&lt;/p&gt;
&lt;p&gt;[Christian Brauner &amp;lt;brauner@kernel.org&amp;gt;: rewrite to account for watch queues]&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-7gxw-6q7r-q63r</guid>
    </item>
    <item>
      <title>gsd-2023-52672</title>
      <link>https://db.gcve.eu/vuln/gsd-2023-52672</link>
      <description>gsd-2023-52672</description>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/gsd-2023-52672</guid>
    </item>
    <item>
      <title>OESA-2024-1707 — kernel security update</title>
      <link>https://db.gcve.eu/vuln/oesa-2024-1707</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;
net/mlx5e: Fix use-after-free of encap entry in neigh update handler&#13;
&#13;
Function mlx5e_rep_neigh_update() wasn&amp;amp;apos;t updated to accommodate rtnl lock
removal from TC filter update path and properly handle concurrent encap
entry insertion/deletion which can lead to following use-after-free:&#13;
&#13;
 [23827.464923] ==================================================================
 [23827.469446] BUG: KASAN: use-after-free in mlx5e_encap_take+0x72/0x140 [mlx5_core]
 [23827.470971] Read of size 4 at addr ffff8881d132228c by task kworker/u20:6/21635
 [23827.472251]
 [23827.472615] CPU: 9 PID: 21635 Comm: kworker/u20:6 Not tainted 5.13.0-rc3+ #5
 [23827.473788] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.13.0-0-gf21b5a4aeb02-prebuilt.qemu.org 04/01/2014
 [23827.475639] Workqueue: mlx5e mlx5e_rep_neigh_update [mlx5_core]
 [23827.476731] Call Trace:
 [23827.477260]  dump_stack+0xbb/0x107
 [23827.477906]  print_address_description.constprop.0+0x18/0x140
 [23827.478896]  ? mlx5e_encap_take+0x72/0x140 [mlx5_core]
 [23827.479879]  ? mlx5e_encap_take+0x72/0x140 [mlx5_core]
 [23827.480905]  kasan_report.cold+0x7c/0xd8
 [23827.481701]  ? mlx5e_encap_take+0x72/0x140 [mlx5_core]
 [23827.482744]  kasan_check_range+0x145/0x1a0
 [23827.493112]  mlx5e_encap_take+0x72/0x140 [mlx5_core]
 [23827.494054]  ? mlx5e_tc_tun_encap_info_equal_ge…&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;
net/mlx5e: Fix use-after-free of encap entry in neigh update handler&#13;
&#13;
Function mlx5e_rep_neigh_update() wasn&amp;amp;apos;t updated to accommodate rtnl lock
removal from TC filter update path and properly handle concurrent encap
entry insertion/deletion which can lead to following use-after-free:&#13;
&#13;
 [23827.464923] ==================================================================
 [23827.469446] BUG: KASAN: use-after-free in mlx5e_encap_take+0x72/0x140 [mlx5_core]
 [23827.470971] Read of size 4 at addr ffff8881d132228c by task kworker/u20:6/21635
 [23827.472251]
 [23827.472615] CPU: 9 PID: 21635 Comm: kworker/u20:6 Not tainted 5.13.0-rc3+ #5
 [23827.473788] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.13.0-0-gf21b5a4aeb02-prebuilt.qemu.org 04/01/2014
 [23827.475639] Workqueue: mlx5e mlx5e_rep_neigh_update [mlx5_core]
 [23827.476731] Call Trace:
 [23827.477260]  dump_stack+0xbb/0x107
 [23827.477906]  print_address_description.constprop.0+0x18/0x140
 [23827.478896]  ? mlx5e_encap_take+0x72/0x140 [mlx5_core]
 [23827.479879]  ? mlx5e_encap_take+0x72/0x140 [mlx5_core]
 [23827.480905]  kasan_report.cold+0x7c/0xd8
 [23827.481701]  ? mlx5e_encap_take+0x72/0x140 [mlx5_core]
 [23827.482744]  kasan_check_range+0x145/0x1a0
 [23827.493112]  mlx5e_encap_take+0x72/0x140 [mlx5_core]
 [23827.494054]  ? mlx5e_tc_tun_encap_info_equal_ge…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/oesa-2024-1707</guid>
    </item>
    <item>
      <title>RHSA-2025:6966 — security update for kernel</title>
      <link>https://db.gcve.eu/vuln/rhsa-2025:6966</link>
      <description>&lt;p&gt;security update for kernel&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;security update for kernel&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/rhsa-2025:6966</guid>
    </item>
    <item>
      <title>SUSE-SU-2024:2372-1 — Security update for the Linux Kernel</title>
      <link>https://db.gcve.eu/vuln/suse-su-2024:2372-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://db.gcve.eu/vuln/suse-su-2024:2372-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2023-52672</title>
      <link>https://db.gcve.eu/vuln/ubuntu-cve-2023-52672</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 104 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: pipe: wakeup wr_wait after setting max_usage Commit c73be61cede5 (&amp;#34;pipe: Add general notification queue support&amp;#34;) a regression was introduced that would lock up resized pipes under certain conditions. See the reproducer in [1]. The commit resizing the pipe ring size was moved to a different function, doing that moved the wakeup for pipe-&amp;gt;wr_wait before actually raising pipe-&amp;gt;max_usage. If a pipe was full before the resize occured it would result in the wakeup never actually triggering pipe_write. Set @max_usage and @nr_accounted before waking writers if this isn&amp;#39;t a watch queue. [Christian Brauner &amp;lt;brauner@kernel.org&amp;gt;: rewrite to account for watch queues]&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 104 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: pipe: wakeup wr_wait after setting max_usage Commit c73be61cede5 (&amp;#34;pipe: Add general notification queue support&amp;#34;) a regression was introduced that would lock up resized pipes under certain conditions. See the reproducer in [1]. The commit resizing the pipe ring size was moved to a different function, doing that moved the wakeup for pipe-&amp;gt;wr_wait before actually raising pipe-&amp;gt;max_usage. If a pipe was full before the resize occured it would result in the wakeup never actually triggering pipe_write. Set @max_usage and @nr_accounted before waking writers if this isn&amp;#39;t a watch queue. [Christian Brauner &amp;lt;brauner@kernel.org&amp;gt;: rewrite to account for watch queues]&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ubuntu-cve-2023-52672</guid>
    </item>
    <item>
      <title>WID-SEC-W-2024-1188 — Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service</title>
      <link>https://db.gcve.eu/vuln/wid-sec-w-2024-1188</link>
      <description>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen.&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.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/wid-sec-w-2024-1188</guid>
    </item>
  </channel>
</rss>
