<?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://db.gcve.eu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-27T10:23:52.123945+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@gcve.eu</email>
  </author>
  <link href="https://db.gcve.eu" 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://db.gcve.eu/vuln/cve-2026-98937</id>
    <title>CVE-2026-98937 — perf/core: Check kernel access when kernel callchains are requested</title>
    <updated>2026-10-27T10:23:52.125535+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>perf/core: Check kernel access when kernel callchains are requested</p>
<p>perf_event_open() currently gates perf_allow_kernel() only on
!attr.exclude_kernel.</p>
<p>However, users can still request kernel callchain collection with
attr.exclude_callchain_kernel == 0 even when attr.exclude_kernel == 1.
That still requires kernel profiling privilege, but the existing check
does not enforce it.</p>
<p>Update the permission check to call perf_allow_kernel() when either
kernel sampling is requested or kernel callchains are requested.</p>
<p>This keeps permission checks aligned with requested data and prevents
unprivileged use of kernel callchain capture.</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/cve-2026-98937"/>
  </entry>
</feed>
