<?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-28T06:45:57.496663+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-2022-50575</id>
    <title>CVE-2022-50575 — xen/privcmd: Fix a possible warning in privcmd_ioctl_mmap_resource()</title>
    <updated>2026-09-28T06:45:57.512078+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>xen/privcmd: Fix a possible warning in privcmd_ioctl_mmap_resource()</p>
<p>As 'kdata.num' is user-controlled data, if user tries to allocate
memory larger than(&gt;=) MAX_ORDER, then kcalloc() will fail, it
creates a stack trace and messes up dmesg with a warning.</p>
<p>Call trace:
-&gt; privcmd_ioctl
--&gt; privcmd_ioctl_mmap_resource</p>
<p>Add __GFP_NOWARN in order to avoid too large allocation warning.
This is detected by static analysis using smatch.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2022-50575"/>
  </entry>
</feed>
