<?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 13:56:28 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-53038</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2026-53038</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; 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:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/bell-cve-2026-53038</guid>
    </item>
    <item>
      <title>certfr-2026-avi-0926 — De multiples vulnérabilités ont été découvertes dans le noyau Linux d'Ubuntu. Certaines d'entre elles permettent à un a…</title>
      <link>https://127.0.0.1:10001/vuln/certfr-2026-avi-0926</link>
      <description>certfr-2026-avi-0926</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2026-avi-0926</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-53038</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2026-53038</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 127 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: ima_fs: Correctly create securityfs files for unsupported hash algos ima_tpm_chip-&amp;gt;allocated_banks[i].crypto_id is initialized to HASH_ALGO__LAST if the TPM algorithm is not supported. However there are places relying on the algorithm to be valid because it is accessed by hash_algo_name[]. On 6.12.40 I observe the following read out-of-bounds in hash_algo_name:   ==================================================================   BUG: KASAN: global-out-of-bounds in create_securityfs_measurement_lists+0x396/0x440   Read of size 8 at addr ffffffff83e18138 by task swapper/0/1   CPU: 4 UID: 0 PID: 1 Comm: swapper/0 Not tainted 6.12.40 #3   Call Trace:    &amp;lt;TASK&amp;gt;    dump_stack_lvl+0x61/0x90    print_report+0xc4/0x580    ? kasan_addr_to_slab+0x26/0x80    ? create_securityfs_measurement_lists+0x396/0x440    kasan_report+0xc2/0x100    ? create_securityfs_measurement_lists+0x396/0x440    create_securityfs_measurement_lists+0x396/0x440    ima_fs_init+0xa3/0x300    ima_init+0x7d/0xd0    init_ima+0x28/0x100    do_one_initcall+0xa6/0x3e0    kernel_init_freeable+0x455/0x740    kernel_init+0x24/0x1d0    ret_from_fork+0x38/0x80    ret_from_fork_asm+0x11/0x20    &amp;lt;/TASK&amp;gt;   The buggy address belongs to the variable:    hash_algo_name+0xb8/0x420   Memory state around the buggy address:    ffffffff83e18000: 00 01 f9 f9 f9 f9 f9 f9 00 01 f9 f9 f9 f9 f9 f9    ffffffff83e18080: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00   &amp;gt;fff…&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 127 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: ima_fs: Correctly create securityfs files for unsupported hash algos ima_tpm_chip-&amp;gt;allocated_banks[i].crypto_id is initialized to HASH_ALGO__LAST if the TPM algorithm is not supported. However there are places relying on the algorithm to be valid because it is accessed by hash_algo_name[]. On 6.12.40 I observe the following read out-of-bounds in hash_algo_name:   ==================================================================   BUG: KASAN: global-out-of-bounds in create_securityfs_measurement_lists+0x396/0x440   Read of size 8 at addr ffffffff83e18138 by task swapper/0/1   CPU: 4 UID: 0 PID: 1 Comm: swapper/0 Not tainted 6.12.40 #3   Call Trace:    &amp;lt;TASK&amp;gt;    dump_stack_lvl+0x61/0x90    print_report+0xc4/0x580    ? kasan_addr_to_slab+0x26/0x80    ? create_securityfs_measurement_lists+0x396/0x440    kasan_report+0xc2/0x100    ? create_securityfs_measurement_lists+0x396/0x440    create_securityfs_measurement_lists+0x396/0x440    ima_fs_init+0xa3/0x300    ima_init+0x7d/0xd0    init_ima+0x28/0x100    do_one_initcall+0xa6/0x3e0    kernel_init_freeable+0x455/0x740    kernel_init+0x24/0x1d0    ret_from_fork+0x38/0x80    ret_from_fork_asm+0x11/0x20    &amp;lt;/TASK&amp;gt;   The buggy address belongs to the variable:    hash_algo_name+0xb8/0x420   Memory state around the buggy address:    ffffffff83e18000: 00 01 f9 f9 f9 f9 f9 f9 00 01 f9 f9 f9 f9 f9 f9    ffffffff83e18080: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00   &amp;gt;fff…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2026-53038</guid>
    </item>
  </channel>
</rss>
