<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-09-30T08:26:59.104740+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/cve-2024-49850</id>
    <title>CVE-2024-49850 — bpf: correctly handle malformed BPF_CORE_TYPE_ID_LOCAL relos</title>
    <updated>2026-09-30T08:27:00.597691+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Linux</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>bpf: correctly handle malformed BPF_CORE_TYPE_ID_LOCAL relos</p>
<p>In case of malformed relocation record of kind BPF_CORE_TYPE_ID_LOCAL
referencing a non-existing BTF type, function bpf_core_calc_relo_insn
would cause a null pointer deference.</p>
<p>Fix this by adding a proper check upper in call stack, as malformed
relocation records could be passed from user space.</p>
<p>Simplest reproducer is a program:</p>
<p>r0 = 0
    exit</p>
<p>With a single relocation record:</p>
<p>.insn_off = 0,          /* patch first instruction */
    .type_id = 100500,      /* this type id does not exist */
    .access_str_off = 6,    /* offset of string "0" */
    .kind = BPF_CORE_TYPE_ID_LOCAL,</p>
<p>See the link for original reproducer or next commit for a test case.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2024-49850"/>
  </entry>
</feed>
