<?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 02:11:24 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-64546</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2026-64546</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-2026-64546</guid>
    </item>
    <item>
      <title>certfr-2026-avi-0981 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian. Elles permettent à un attaquant de provo…</title>
      <link>https://127.0.0.1:10001/vuln/certfr-2026-avi-0981</link>
      <description>certfr-2026-avi-0981</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2026-avi-0981</guid>
    </item>
    <item>
      <title>OESA-2026-3452 — kernel security update</title>
      <link>https://127.0.0.1:10001/vuln/oesa-2026-3452</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:20.03-LTS-SP4: 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;RDMA/core: Prefer NLA_NUL_STRING&lt;/p&gt;
&lt;p&gt;These attributes are evaluated as c-string (passed to strcmp), but
NLA_STRING doesn&amp;amp;apos;t check for the presence of a \0 terminator.&lt;/p&gt;
&lt;p&gt;Either this needs to switch to nla_strcmp() and needs to adjust printf fmt
specifier to not use plain %s, or this needs to use NLA_NUL_STRING.&lt;/p&gt;
&lt;p&gt;As the code has been this way for long time, it seems to me that userspace
does include the terminating nul, even tough its not enforced so far, and
thus NLA_NUL_STRING use is the simpler solution.(CVE-2026-63860)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;drm/edid: fix OOB read in drm_parse_tiled_block()&lt;/p&gt;
&lt;p&gt;drm_parse_tiled_block() casts the DisplayID block to a
struct displayid_tiled_block and reads the full fixed layout up to
tile-&amp;amp;gt;topology_id[7] without checking block-&amp;amp;gt;num_bytes. The DisplayID
iterator only validates the declared payload length, so a crafted EDID
can advertise a tiled-display block (tag DATA_BLOCK_TILED_DISPLAY, or
DATA_BLOCK_2_TILED_DISPLAY_TOPOLOGY for v2.0) with a small num_bytes at
the end of a DisplayID extension. The read then runs past the end of the
exact-sized kmemdup()&amp;amp;apos;d EDID allocation, a heap out-of-bounds read.&lt;/p&gt;
&lt;p&gt;Reject blocks shorter than the spec&amp;amp;apos;s 22-byte tiled payload before
reading the fixed struct, as drm_parse_vesa_mso_data() already does.&lt;/p&gt;
&lt;p&gt;BUG: K…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:20.03-LTS-SP4: 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;RDMA/core: Prefer NLA_NUL_STRING&lt;/p&gt;
&lt;p&gt;These attributes are evaluated as c-string (passed to strcmp), but
NLA_STRING doesn&amp;amp;apos;t check for the presence of a \0 terminator.&lt;/p&gt;
&lt;p&gt;Either this needs to switch to nla_strcmp() and needs to adjust printf fmt
specifier to not use plain %s, or this needs to use NLA_NUL_STRING.&lt;/p&gt;
&lt;p&gt;As the code has been this way for long time, it seems to me that userspace
does include the terminating nul, even tough its not enforced so far, and
thus NLA_NUL_STRING use is the simpler solution.(CVE-2026-63860)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;drm/edid: fix OOB read in drm_parse_tiled_block()&lt;/p&gt;
&lt;p&gt;drm_parse_tiled_block() casts the DisplayID block to a
struct displayid_tiled_block and reads the full fixed layout up to
tile-&amp;amp;gt;topology_id[7] without checking block-&amp;amp;gt;num_bytes. The DisplayID
iterator only validates the declared payload length, so a crafted EDID
can advertise a tiled-display block (tag DATA_BLOCK_TILED_DISPLAY, or
DATA_BLOCK_2_TILED_DISPLAY_TOPOLOGY for v2.0) with a small num_bytes at
the end of a DisplayID extension. The read then runs past the end of the
exact-sized kmemdup()&amp;amp;apos;d EDID allocation, a heap out-of-bounds read.&lt;/p&gt;
&lt;p&gt;Reject blocks shorter than the spec&amp;amp;apos;s 22-byte tiled payload before
reading the fixed struct, as drm_parse_vesa_mso_data() already does.&lt;/p&gt;
&lt;p&gt;BUG: K…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/oesa-2026-3452</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-64546</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2026-64546</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 247 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: drm/edid: fix OOB read in drm_parse_tiled_block() drm_parse_tiled_block() casts the DisplayID block to a struct displayid_tiled_block and reads the full fixed layout up to tile-&amp;gt;topology_id[7] without checking block-&amp;gt;num_bytes. The DisplayID iterator only validates the declared payload length, so a crafted EDID can advertise a tiled-display block (tag DATA_BLOCK_TILED_DISPLAY, or DATA_BLOCK_2_TILED_DISPLAY_TOPOLOGY for v2.0) with a small num_bytes at the end of a DisplayID extension. The read then runs past the end of the exact-sized kmemdup()&amp;#39;d EDID allocation, a heap out-of-bounds read. Reject blocks shorter than the spec&amp;#39;s 22-byte tiled payload before reading the fixed struct, as drm_parse_vesa_mso_data() already does.   BUG: KASAN: slab-out-of-bounds in drm_edid_connector_update   Read of size 2 at addr ffff888010077700 by task exploit/147    dump_stack_lvl (lib/dump_stack.c:94 ...)    print_report (mm/kasan/report.c:378 ...)    kasan_report (mm/kasan/report.c:595)    drm_edid_connector_update (drivers/gpu/drm/drm_edid.c:7581)    bochs_connector_helper_get_modes (drivers/gpu/drm/tiny/bochs.c:574)    drm_helper_probe_single_connector_modes (drivers/gpu/drm/drm_probe_helper.c:426)    status_store (drivers/gpu/drm/drm_sysfs.c:219)    ...    vfs_write (fs/read_write.c:595 fs/read_write.c:688)    ksys_write (fs/read_write.c:740)&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 247 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: drm/edid: fix OOB read in drm_parse_tiled_block() drm_parse_tiled_block() casts the DisplayID block to a struct displayid_tiled_block and reads the full fixed layout up to tile-&amp;gt;topology_id[7] without checking block-&amp;gt;num_bytes. The DisplayID iterator only validates the declared payload length, so a crafted EDID can advertise a tiled-display block (tag DATA_BLOCK_TILED_DISPLAY, or DATA_BLOCK_2_TILED_DISPLAY_TOPOLOGY for v2.0) with a small num_bytes at the end of a DisplayID extension. The read then runs past the end of the exact-sized kmemdup()&amp;#39;d EDID allocation, a heap out-of-bounds read. Reject blocks shorter than the spec&amp;#39;s 22-byte tiled payload before reading the fixed struct, as drm_parse_vesa_mso_data() already does.   BUG: KASAN: slab-out-of-bounds in drm_edid_connector_update   Read of size 2 at addr ffff888010077700 by task exploit/147    dump_stack_lvl (lib/dump_stack.c:94 ...)    print_report (mm/kasan/report.c:378 ...)    kasan_report (mm/kasan/report.c:595)    drm_edid_connector_update (drivers/gpu/drm/drm_edid.c:7581)    bochs_connector_helper_get_modes (drivers/gpu/drm/tiny/bochs.c:574)    drm_helper_probe_single_connector_modes (drivers/gpu/drm/drm_probe_helper.c:426)    status_store (drivers/gpu/drm/drm_sysfs.c:219)    ...    vfs_write (fs/read_write.c:595 fs/read_write.c:688)    ksys_write (fs/read_write.c:740)&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2026-64546</guid>
    </item>
  </channel>
</rss>
