<?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:06:58 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2025-38163</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2025-38163</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-38163</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>OESA-2025-1823 — kernel security update</title>
      <link>https://127.0.0.1:10001/vuln/oesa-2025-1823</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:24.03-LTS: 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;arm64: Don&amp;amp;apos;t call NULL in do_compat_alignment_fixup()&lt;/p&gt;
&lt;p&gt;do_alignment_t32_to_handler() only fixes up alignment faults for
specific instructions; it returns NULL otherwise (e.g. LDREX). When
that&amp;amp;apos;s the case, signal to the caller that it needs to proceed with the
regular alignment fault handling (i.e. SIGBUS). Without this patch, the
kernel panics:&lt;/p&gt;
&lt;p&gt;Unable to handle kernel NULL pointer dereference at virtual address 0000000000000000
  Mem abort info:
    ESR = 0x0000000086000006
    EC = 0x21: IABT (current EL), IL = 32 bits
    SET = 0, FnV = 0
    EA = 0, S1PTW = 0
    FSC = 0x06: level 2 translation fault
  user pgtable: 4k pages, 48-bit VAs, pgdp=00000800164aa000
  [0000000000000000] pgd=0800081fdbd22003, p4d=0800081fdbd22003, pud=08000815d51c6003, pmd=0000000000000000
  Internal error: Oops: 0000000086000006 [#1] SMP
  Modules linked in: cfg80211 rfkill xt_nat xt_tcpudp xt_conntrack nft_chain_nat xt_MASQUERADE nf_nat nf_conntrack_netlink nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 xfrm_user xfrm_algo xt_addrtype nft_compat br_netfilter veth nvme_fa&amp;amp;gt;
   libcrc32c crc32c_generic raid0 multipath linear dm_mod dax raid1 md_mod xhci_pci nvme xhci_hcd nvme_core t10_pi usbcore igb crc64_rocksoft crc64 crc_t10dif crct10dif_generic crct10dif_ce crct10dif_common usb_common i2c_algo_bit i2c&amp;amp;gt;
  CPU: 2 PID: 3932954 Comm: WPEWebPr…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:24.03-LTS: 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;arm64: Don&amp;amp;apos;t call NULL in do_compat_alignment_fixup()&lt;/p&gt;
&lt;p&gt;do_alignment_t32_to_handler() only fixes up alignment faults for
specific instructions; it returns NULL otherwise (e.g. LDREX). When
that&amp;amp;apos;s the case, signal to the caller that it needs to proceed with the
regular alignment fault handling (i.e. SIGBUS). Without this patch, the
kernel panics:&lt;/p&gt;
&lt;p&gt;Unable to handle kernel NULL pointer dereference at virtual address 0000000000000000
  Mem abort info:
    ESR = 0x0000000086000006
    EC = 0x21: IABT (current EL), IL = 32 bits
    SET = 0, FnV = 0
    EA = 0, S1PTW = 0
    FSC = 0x06: level 2 translation fault
  user pgtable: 4k pages, 48-bit VAs, pgdp=00000800164aa000
  [0000000000000000] pgd=0800081fdbd22003, p4d=0800081fdbd22003, pud=08000815d51c6003, pmd=0000000000000000
  Internal error: Oops: 0000000086000006 [#1] SMP
  Modules linked in: cfg80211 rfkill xt_nat xt_tcpudp xt_conntrack nft_chain_nat xt_MASQUERADE nf_nat nf_conntrack_netlink nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 xfrm_user xfrm_algo xt_addrtype nft_compat br_netfilter veth nvme_fa&amp;amp;gt;
   libcrc32c crc32c_generic raid0 multipath linear dm_mod dax raid1 md_mod xhci_pci nvme xhci_hcd nvme_core t10_pi usbcore igb crc64_rocksoft crc64 crc_t10dif crct10dif_generic crct10dif_ce crct10dif_common usb_common i2c_algo_bit i2c&amp;amp;gt;
  CPU: 2 PID: 3932954 Comm: WPEWebPr…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/oesa-2025-1823</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2025-38163</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2025-38163</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 213 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: f2fs: fix to do sanity check on sbi-&amp;gt;total_valid_block_count syzbot reported a f2fs bug as below: ------------[ cut here ]------------ kernel BUG at fs/f2fs/f2fs.h:2521! RIP: 0010:dec_valid_block_count+0x3b2/0x3c0 fs/f2fs/f2fs.h:2521 Call Trace:  f2fs_truncate_data_blocks_range+0xc8c/0x11a0 fs/f2fs/file.c:695  truncate_dnode+0x417/0x740 fs/f2fs/node.c:973  truncate_nodes+0x3ec/0xf50 fs/f2fs/node.c:1014  f2fs_truncate_inode_blocks+0x8e3/0x1370 fs/f2fs/node.c:1197  f2fs_do_truncate_blocks+0x840/0x12b0 fs/f2fs/file.c:810  f2fs_truncate_blocks+0x10d/0x300 fs/f2fs/file.c:838  f2fs_truncate+0x417/0x720 fs/f2fs/file.c:888  f2fs_setattr+0xc4f/0x12f0 fs/f2fs/file.c:1112  notify_change+0xbca/0xe90 fs/attr.c:552  do_truncate+0x222/0x310 fs/open.c:65  handle_truncate fs/namei.c:3466 [inline]  do_open fs/namei.c:3849 [inline]  path_openat+0x2e4f/0x35d0 fs/namei.c:4004  do_filp_open+0x284/0x4e0 fs/namei.c:4031  do_sys_openat2+0x12b/0x1d0 fs/open.c:1429  do_sys_open fs/open.c:1444 [inline]  __do_sys_creat fs/open.c:1522 [inline]  __se_sys_creat fs/open.c:1516 [inline]  __x64_sys_creat+0x124/0x170 fs/open.c:1516  do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]  do_syscall_64+0xf3/0x230 arch/x86/entry/syscall_64.c:94 The reason is: in fuzzed image, sbi-&amp;gt;total_valid_block_count is inconsistent w/ mapped blocks indexed by inode, so, we should not trigger panic for such case, instead, let&amp;#39;s print log and set fsck flag.&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 213 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: f2fs: fix to do sanity check on sbi-&amp;gt;total_valid_block_count syzbot reported a f2fs bug as below: ------------[ cut here ]------------ kernel BUG at fs/f2fs/f2fs.h:2521! RIP: 0010:dec_valid_block_count+0x3b2/0x3c0 fs/f2fs/f2fs.h:2521 Call Trace:  f2fs_truncate_data_blocks_range+0xc8c/0x11a0 fs/f2fs/file.c:695  truncate_dnode+0x417/0x740 fs/f2fs/node.c:973  truncate_nodes+0x3ec/0xf50 fs/f2fs/node.c:1014  f2fs_truncate_inode_blocks+0x8e3/0x1370 fs/f2fs/node.c:1197  f2fs_do_truncate_blocks+0x840/0x12b0 fs/f2fs/file.c:810  f2fs_truncate_blocks+0x10d/0x300 fs/f2fs/file.c:838  f2fs_truncate+0x417/0x720 fs/f2fs/file.c:888  f2fs_setattr+0xc4f/0x12f0 fs/f2fs/file.c:1112  notify_change+0xbca/0xe90 fs/attr.c:552  do_truncate+0x222/0x310 fs/open.c:65  handle_truncate fs/namei.c:3466 [inline]  do_open fs/namei.c:3849 [inline]  path_openat+0x2e4f/0x35d0 fs/namei.c:4004  do_filp_open+0x284/0x4e0 fs/namei.c:4031  do_sys_openat2+0x12b/0x1d0 fs/open.c:1429  do_sys_open fs/open.c:1444 [inline]  __do_sys_creat fs/open.c:1522 [inline]  __se_sys_creat fs/open.c:1516 [inline]  __x64_sys_creat+0x124/0x170 fs/open.c:1516  do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]  do_syscall_64+0xf3/0x230 arch/x86/entry/syscall_64.c:94 The reason is: in fuzzed image, sbi-&amp;gt;total_valid_block_count is inconsistent w/ mapped blocks indexed by inode, so, we should not trigger panic for such case, instead, let&amp;#39;s print log and set fsck flag.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2025-38163</guid>
    </item>
  </channel>
</rss>
