<?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-10-02T14:49:05.016864+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-2026-45927</id>
    <title>CVE-2026-45927 — bpf: Require frozen map for calculating map hash</title>
    <updated>2026-10-02T14:49:05.019858+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: Require frozen map for calculating map hash</p>
<p>Currently, bpf_map_get_info_by_fd calculates and caches the hash of the
map regardless of the map's frozen state.</p>
<p>This leads to a TOCTOU bug where userspace can call
BPF_OBJ_GET_INFO_BY_FD to cache the hash and then modify the map
contents before freezing.</p>
<p>Therefore, a trusted loader can be tricked into verifying the stale hash
while loading the modified contents.</p>
<p>Fix this by returning -EPERM if the map is not frozen when the hash is
requested. This ensures the hash is only generated for the final,
immutable state of the map.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2026-45927"/>
  </entry>
</feed>
