<?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 06:03:33 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2024-56574</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2024-56574</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-56574</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-56574</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2024-56574</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; 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, Ubuntu:16.04:LTS: linux-hwe-edge and 195 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: media: ts2020: fix null-ptr-deref in ts2020_probe() KASAN reported a null-ptr-deref issue when executing the following command:   # echo ts2020 0x20 &amp;gt; /sys/bus/i2c/devices/i2c-0/new_device     KASAN: null-ptr-deref in range [0x0000000000000010-0x0000000000000017]     CPU: 53 UID: 0 PID: 970 Comm: systemd-udevd Not tainted 6.12.0-rc2+ #24     Hardware name: QEMU Standard PC (Q35 + ICH9, 2009)     RIP: 0010:ts2020_probe+0xad/0xe10 [ts2020]     RSP: 0018:ffffc9000abbf598 EFLAGS: 00010202     RAX: dffffc0000000000 RBX: 0000000000000000 RCX: ffffffffc0714809     RDX: 0000000000000002 RSI: ffff88811550be00 RDI: 0000000000000010     RBP: ffff888109868800 R08: 0000000000000001 R09: fffff52001577eb6     R10: 0000000000000000 R11: ffffc9000abbff50 R12: ffffffffc0714790     R13: 1ffff92001577eb8 R14: ffffffffc07190d0 R15: 0000000000000001     FS:  00007f95f13b98c0(0000) GS:ffff888149280000(0000) knlGS:0000000000000000     CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033     CR2: 0000555d2634b000 CR3: 0000000152236000 CR4: 00000000000006f0     DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000     DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400     Call Trace:      &amp;lt;TASK&amp;gt;      ts2020_probe+0xad/0xe10 [ts2020]      i2c_device_probe+0x421/0xb40      really_probe+0x266/0x850     ... The cause of the problem is that when using sysfs to dynamically register an i2c device, there is no platfor…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; 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, Ubuntu:16.04:LTS: linux-hwe-edge and 195 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: media: ts2020: fix null-ptr-deref in ts2020_probe() KASAN reported a null-ptr-deref issue when executing the following command:   # echo ts2020 0x20 &amp;gt; /sys/bus/i2c/devices/i2c-0/new_device     KASAN: null-ptr-deref in range [0x0000000000000010-0x0000000000000017]     CPU: 53 UID: 0 PID: 970 Comm: systemd-udevd Not tainted 6.12.0-rc2+ #24     Hardware name: QEMU Standard PC (Q35 + ICH9, 2009)     RIP: 0010:ts2020_probe+0xad/0xe10 [ts2020]     RSP: 0018:ffffc9000abbf598 EFLAGS: 00010202     RAX: dffffc0000000000 RBX: 0000000000000000 RCX: ffffffffc0714809     RDX: 0000000000000002 RSI: ffff88811550be00 RDI: 0000000000000010     RBP: ffff888109868800 R08: 0000000000000001 R09: fffff52001577eb6     R10: 0000000000000000 R11: ffffc9000abbff50 R12: ffffffffc0714790     R13: 1ffff92001577eb8 R14: ffffffffc07190d0 R15: 0000000000000001     FS:  00007f95f13b98c0(0000) GS:ffff888149280000(0000) knlGS:0000000000000000     CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033     CR2: 0000555d2634b000 CR3: 0000000152236000 CR4: 00000000000006f0     DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000     DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400     Call Trace:      &amp;lt;TASK&amp;gt;      ts2020_probe+0xad/0xe10 [ts2020]      i2c_device_probe+0x421/0xb40      really_probe+0x266/0x850     ... The cause of the problem is that when using sysfs to dynamically register an i2c device, there is no platfor…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2024-56574</guid>
    </item>
  </channel>
</rss>
