<?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://127.0.0.1:10001</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, 21 Nov 2026 00:05:59 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2024-56643</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2024-56643</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://127.0.0.1:10001/vuln/bell-cve-2024-56643</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://127.0.0.1:10001/vuln/certfr-2025-avi-0088</link>
      <description>certfr-2025-avi-0088</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2025-avi-0088</guid>
    </item>
    <item>
      <title>OESA-2025-1286 — kernel security update</title>
      <link>https://127.0.0.1:10001/vuln/oesa-2025-1286</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;IORING_OP_READ did not correctly consume the provided buffer list when
read i/o returned &amp;amp;lt; 0 (except for -EAGAIN and -EIOCBQUEUED return).
This can lead to a potential use-after-free when the completion via
io_rw_done runs at separate context.(CVE-2023-52926)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;f2fs: fix to shrink read extent node in batches&lt;/p&gt;
&lt;p&gt;We use rwlock to protect core structure data of extent tree during
its shrink, however, if there is a huge number of extent nodes in
extent tree, during shrink of extent tree, it may hold rwlock for
a very long time, which may trigger kernel hang issue.&lt;/p&gt;
&lt;p&gt;This patch fixes to shrink read extent node in batches, so that,
critical region of the rwlock can be shrunk to avoid its extreme
long time hold.(CVE-2024-41935)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;dma-debug: fix a possible deadlock on radix_lock&lt;/p&gt;
&lt;p&gt;radix_lock() shouldn&amp;amp;apos;t be held while holding dma_hash_entry[idx].lock
otherwise, there&amp;amp;apos;s a possible deadlock scenario when
dma debug API is called holding rq_lock():&lt;/p&gt;
&lt;p&gt;CPU0                   CPU1                       CPU2
dma_free_attrs()
check_unmap()          add_dma_entry()            __schedule() //out
                                                  (A) rq_lock()
get_hash_bucket()
(A) dma_entry_hash…&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;IORING_OP_READ did not correctly consume the provided buffer list when
read i/o returned &amp;amp;lt; 0 (except for -EAGAIN and -EIOCBQUEUED return).
This can lead to a potential use-after-free when the completion via
io_rw_done runs at separate context.(CVE-2023-52926)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;f2fs: fix to shrink read extent node in batches&lt;/p&gt;
&lt;p&gt;We use rwlock to protect core structure data of extent tree during
its shrink, however, if there is a huge number of extent nodes in
extent tree, during shrink of extent tree, it may hold rwlock for
a very long time, which may trigger kernel hang issue.&lt;/p&gt;
&lt;p&gt;This patch fixes to shrink read extent node in batches, so that,
critical region of the rwlock can be shrunk to avoid its extreme
long time hold.(CVE-2024-41935)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;dma-debug: fix a possible deadlock on radix_lock&lt;/p&gt;
&lt;p&gt;radix_lock() shouldn&amp;amp;apos;t be held while holding dma_hash_entry[idx].lock
otherwise, there&amp;amp;apos;s a possible deadlock scenario when
dma debug API is called holding rq_lock():&lt;/p&gt;
&lt;p&gt;CPU0                   CPU1                       CPU2
dma_free_attrs()
check_unmap()          add_dma_entry()            __schedule() //out
                                                  (A) rq_lock()
get_hash_bucket()
(A) dma_entry_hash…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/oesa-2025-1286</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2024-56643</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2024-56643</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 196 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: dccp: Fix memory leak in dccp_feat_change_recv If dccp_feat_push_confirm() fails after new value for SP feature was accepted without reconciliation (&amp;#39;entry == NULL&amp;#39; branch), memory allocated for that value with dccp_feat_clone_sp_val() is never freed. Here is the kmemleak stack for this: unreferenced object 0xffff88801d4ab488 (size 8):   comm &amp;#34;syz-executor310&amp;#34;, pid 1127, jiffies 4295085598 (age 41.666s)   hex dump (first 8 bytes):     01 b4 4a 1d 80 88 ff ff                          ..J.....   backtrace:     [&amp;lt;00000000db7cabfe&amp;gt;] kmemdup+0x23/0x50 mm/util.c:128     [&amp;lt;0000000019b38405&amp;gt;] kmemdup include/linux/string.h:465 [inline]     [&amp;lt;0000000019b38405&amp;gt;] dccp_feat_clone_sp_val net/dccp/feat.c:371 [inline]     [&amp;lt;0000000019b38405&amp;gt;] dccp_feat_clone_sp_val net/dccp/feat.c:367 [inline]     [&amp;lt;0000000019b38405&amp;gt;] dccp_feat_change_recv net/dccp/feat.c:1145 [inline]     [&amp;lt;0000000019b38405&amp;gt;] dccp_feat_parse_options+0x1196/0x2180 net/dccp/feat.c:1416     [&amp;lt;00000000b1f6d94a&amp;gt;] dccp_parse_options+0xa2a/0x1260 net/dccp/options.c:125     [&amp;lt;0000000030d7b621&amp;gt;] dccp_rcv_state_process+0x197/0x13d0 net/dccp/input.c:650     [&amp;lt;000000001f74c72e&amp;gt;] dccp_v4_do_rcv+0xf9/0x1a0 net/dccp/ipv4.c:688     [&amp;lt;00000000a6c24128&amp;gt;] sk_backlog_rcv include/net/sock.h:1041 [inline]     [&amp;lt;00000000a6c24128&amp;gt;] __release_sock+0x139/0x3b0 net/core/sock.c:2570     [&amp;lt;00000000cf1f3a53&amp;gt;] release_sock+0x54/0x1b0 net/core/sock.c:3111     [&amp;lt;000000008422fa23&amp;gt;] inet_w…&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 196 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: dccp: Fix memory leak in dccp_feat_change_recv If dccp_feat_push_confirm() fails after new value for SP feature was accepted without reconciliation (&amp;#39;entry == NULL&amp;#39; branch), memory allocated for that value with dccp_feat_clone_sp_val() is never freed. Here is the kmemleak stack for this: unreferenced object 0xffff88801d4ab488 (size 8):   comm &amp;#34;syz-executor310&amp;#34;, pid 1127, jiffies 4295085598 (age 41.666s)   hex dump (first 8 bytes):     01 b4 4a 1d 80 88 ff ff                          ..J.....   backtrace:     [&amp;lt;00000000db7cabfe&amp;gt;] kmemdup+0x23/0x50 mm/util.c:128     [&amp;lt;0000000019b38405&amp;gt;] kmemdup include/linux/string.h:465 [inline]     [&amp;lt;0000000019b38405&amp;gt;] dccp_feat_clone_sp_val net/dccp/feat.c:371 [inline]     [&amp;lt;0000000019b38405&amp;gt;] dccp_feat_clone_sp_val net/dccp/feat.c:367 [inline]     [&amp;lt;0000000019b38405&amp;gt;] dccp_feat_change_recv net/dccp/feat.c:1145 [inline]     [&amp;lt;0000000019b38405&amp;gt;] dccp_feat_parse_options+0x1196/0x2180 net/dccp/feat.c:1416     [&amp;lt;00000000b1f6d94a&amp;gt;] dccp_parse_options+0xa2a/0x1260 net/dccp/options.c:125     [&amp;lt;0000000030d7b621&amp;gt;] dccp_rcv_state_process+0x197/0x13d0 net/dccp/input.c:650     [&amp;lt;000000001f74c72e&amp;gt;] dccp_v4_do_rcv+0xf9/0x1a0 net/dccp/ipv4.c:688     [&amp;lt;00000000a6c24128&amp;gt;] sk_backlog_rcv include/net/sock.h:1041 [inline]     [&amp;lt;00000000a6c24128&amp;gt;] __release_sock+0x139/0x3b0 net/core/sock.c:2570     [&amp;lt;00000000cf1f3a53&amp;gt;] release_sock+0x54/0x1b0 net/core/sock.c:3111     [&amp;lt;000000008422fa23&amp;gt;] inet_w…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2024-56643</guid>
    </item>
  </channel>
</rss>
