<?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:46:08 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2025-38328</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2025-38328</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-2025-38328</guid>
    </item>
    <item>
      <title>certfr-2025-avi-0698 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian. Certaines d'entre elles permettent à un…</title>
      <link>https://127.0.0.1:10001/vuln/certfr-2025-avi-0698</link>
      <description>certfr-2025-avi-0698</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2025-avi-0698</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2025-38328</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2025-38328</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 214 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: jffs2: check jffs2_prealloc_raw_node_refs() result in few other places Fuzzing hit another invalid pointer dereference due to the lack of checking whether jffs2_prealloc_raw_node_refs() completed successfully. Subsequent logic implies that the node refs have been allocated. Handle that. The code is ready for propagating the error upwards. KASAN: null-ptr-deref in range [0x0000000000000008-0x000000000000000f] CPU: 1 PID: 5835 Comm: syz-executor145 Not tainted 5.10.234-syzkaller #0 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.12.0-1 04/01/2014 RIP: 0010:jffs2_link_node_ref+0xac/0x690 fs/jffs2/nodelist.c:600 Call Trace:  jffs2_mark_erased_block fs/jffs2/erase.c:460 [inline]  jffs2_erase_pending_blocks+0x688/0x1860 fs/jffs2/erase.c:118  jffs2_garbage_collect_pass+0x638/0x1a00 fs/jffs2/gc.c:253  jffs2_reserve_space+0x3f4/0xad0 fs/jffs2/nodemgmt.c:167  jffs2_write_inode_range+0x246/0xb50 fs/jffs2/write.c:362  jffs2_write_end+0x712/0x1110 fs/jffs2/file.c:302  generic_perform_write+0x2c2/0x500 mm/filemap.c:3347  __generic_file_write_iter+0x252/0x610 mm/filemap.c:3465  generic_file_write_iter+0xdb/0x230 mm/filemap.c:3497  call_write_iter include/linux/fs.h:2039 [inline]  do_iter_readv_writev+0x46d/0x750 fs/read_write.c:740  do_iter_write+0x18c/0x710 fs/read_write.c:866  vfs_writev+0x1db/0x6a0 fs/read_write.c:939  do_pwritev fs/read_write.c:1036 [inline]  __do_sys_pwritev fs/read_write.c:1083 [inline]…&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 214 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: jffs2: check jffs2_prealloc_raw_node_refs() result in few other places Fuzzing hit another invalid pointer dereference due to the lack of checking whether jffs2_prealloc_raw_node_refs() completed successfully. Subsequent logic implies that the node refs have been allocated. Handle that. The code is ready for propagating the error upwards. KASAN: null-ptr-deref in range [0x0000000000000008-0x000000000000000f] CPU: 1 PID: 5835 Comm: syz-executor145 Not tainted 5.10.234-syzkaller #0 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.12.0-1 04/01/2014 RIP: 0010:jffs2_link_node_ref+0xac/0x690 fs/jffs2/nodelist.c:600 Call Trace:  jffs2_mark_erased_block fs/jffs2/erase.c:460 [inline]  jffs2_erase_pending_blocks+0x688/0x1860 fs/jffs2/erase.c:118  jffs2_garbage_collect_pass+0x638/0x1a00 fs/jffs2/gc.c:253  jffs2_reserve_space+0x3f4/0xad0 fs/jffs2/nodemgmt.c:167  jffs2_write_inode_range+0x246/0xb50 fs/jffs2/write.c:362  jffs2_write_end+0x712/0x1110 fs/jffs2/file.c:302  generic_perform_write+0x2c2/0x500 mm/filemap.c:3347  __generic_file_write_iter+0x252/0x610 mm/filemap.c:3465  generic_file_write_iter+0xdb/0x230 mm/filemap.c:3497  call_write_iter include/linux/fs.h:2039 [inline]  do_iter_readv_writev+0x46d/0x750 fs/read_write.c:740  do_iter_write+0x18c/0x710 fs/read_write.c:866  vfs_writev+0x1db/0x6a0 fs/read_write.c:939  do_pwritev fs/read_write.c:1036 [inline]  __do_sys_pwritev fs/read_write.c:1083 [inline]…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2025-38328</guid>
    </item>
  </channel>
</rss>
