<?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://vulnerability.circl.lu</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>Mon, 28 Sep 2026 08:08:17 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-98065 — bpf: Reject key-less BTF for hash maps</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-98065</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;bpf: Reject key-less BTF for hash maps&lt;/p&gt;
&lt;p&gt;map_check_btf() allows a key-less BTF (btf_key_type_id == 0) only for
maps that have a -&amp;gt;map_check_btf callback, and leaves the actual
decision to that callback. Hash maps used to have no -&amp;gt;map_check_btf,
so a key-less BTF was rejected outright.&lt;/p&gt;
&lt;p&gt;That changed when htab and rhtab gained a -&amp;gt;map_check_btf to register a
dtor - htab in commit 1df97a7453ee (&amp;#34;bpf: Register dtor for freeing
special fields&amp;#34;) and rhtab in commit 6905f8601298 (&amp;#34;bpf: Allow special
fields in resizable hashtab&amp;#34;). Neither looks at the key, so a key-less
hash map now passes map_check_btf() and gets created. Reading it back
through bpffs feeds the key type_id 0 into btf_type_seq_show();
btf_type_by_id() returns the void type, kind_ops[BTF_KIND_UNKN] is NULL,
and btf_type_show() dereferences it:&lt;/p&gt;
&lt;p&gt;RIP: 0010:btf_type_show+0x223/0x2e0 kernel/bpf/btf.c:8232
RSP: 0018:ffffc9000399f868 EFLAGS: 00010206
RAX: dffffc0000000000 RBX: 0000000000000000 RCX: 0000000000000000
RDX: 0000000000000005 RSI: 0000000000000000 RDI: 0000000000000028
RBP: 0000000000000000 R08: 0000000000000001 R09: 0000000000000000
R10: ffffc9000399f970 R11: 0000000000000001 R12: ffffffff9b96b140
R13: ffffc9000399f8e0 R14: ffff88803d393c00 R15: 0000000000000003
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000200000000000 CR3: 000000003d213000 CR4: 0000000000352ef0
DR0: 0000000039ae8f55 DR1: 0000000000000000 DR2: 0000000000000000
DR…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;bpf: Reject key-less BTF for hash maps&lt;/p&gt;
&lt;p&gt;map_check_btf() allows a key-less BTF (btf_key_type_id == 0) only for
maps that have a -&amp;gt;map_check_btf callback, and leaves the actual
decision to that callback. Hash maps used to have no -&amp;gt;map_check_btf,
so a key-less BTF was rejected outright.&lt;/p&gt;
&lt;p&gt;That changed when htab and rhtab gained a -&amp;gt;map_check_btf to register a
dtor - htab in commit 1df97a7453ee (&amp;#34;bpf: Register dtor for freeing
special fields&amp;#34;) and rhtab in commit 6905f8601298 (&amp;#34;bpf: Allow special
fields in resizable hashtab&amp;#34;). Neither looks at the key, so a key-less
hash map now passes map_check_btf() and gets created. Reading it back
through bpffs feeds the key type_id 0 into btf_type_seq_show();
btf_type_by_id() returns the void type, kind_ops[BTF_KIND_UNKN] is NULL,
and btf_type_show() dereferences it:&lt;/p&gt;
&lt;p&gt;RIP: 0010:btf_type_show+0x223/0x2e0 kernel/bpf/btf.c:8232
RSP: 0018:ffffc9000399f868 EFLAGS: 00010206
RAX: dffffc0000000000 RBX: 0000000000000000 RCX: 0000000000000000
RDX: 0000000000000005 RSI: 0000000000000000 RDI: 0000000000000028
RBP: 0000000000000000 R08: 0000000000000001 R09: 0000000000000000
R10: ffffc9000399f970 R11: 0000000000000001 R12: ffffffff9b96b140
R13: ffffc9000399f8e0 R14: ffff88803d393c00 R15: 0000000000000003
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000200000000000 CR3: 000000003d213000 CR4: 0000000000352ef0
DR0: 0000000039ae8f55 DR1: 0000000000000000 DR2: 0000000000000000
DR…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-98065</guid>
    </item>
  </channel>
</rss>
