<?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://db.gcve.eu</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 23:55:41 +0000</lastBuildDate>
    <item>
      <title>CVE-2022-50271 — vhost/vsock: Use kvmalloc/kvfree for larger packets.</title>
      <link>https://db.gcve.eu/vuln/cve-2022-50271</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;vhost/vsock: Use kvmalloc/kvfree for larger packets.&lt;/p&gt;
&lt;p&gt;When copying a large file over sftp over vsock, data size is usually 32kB,
and kmalloc seems to fail to try to allocate 32 32kB regions.&lt;/p&gt;
&lt;p&gt;vhost-5837: page allocation failure: order:4, mode:0x24040c0
 Call Trace:
  [&amp;lt;ffffffffb6a0df64&amp;gt;] dump_stack+0x97/0xdb
  [&amp;lt;ffffffffb68d6aed&amp;gt;] warn_alloc_failed+0x10f/0x138
  [&amp;lt;ffffffffb68d868a&amp;gt;] ? __alloc_pages_direct_compact+0x38/0xc8
  [&amp;lt;ffffffffb664619f&amp;gt;] __alloc_pages_nodemask+0x84c/0x90d
  [&amp;lt;ffffffffb6646e56&amp;gt;] alloc_kmem_pages+0x17/0x19
  [&amp;lt;ffffffffb6653a26&amp;gt;] kmalloc_order_trace+0x2b/0xdb
  [&amp;lt;ffffffffb66682f3&amp;gt;] __kmalloc+0x177/0x1f7
  [&amp;lt;ffffffffb66e0d94&amp;gt;] ? copy_from_iter+0x8d/0x31d
  [&amp;lt;ffffffffc0689ab7&amp;gt;] vhost_vsock_handle_tx_kick+0x1fa/0x301 [vhost_vsock]
  [&amp;lt;ffffffffc06828d9&amp;gt;] vhost_worker+0xf7/0x157 [vhost]
  [&amp;lt;ffffffffb683ddce&amp;gt;] kthread+0xfd/0x105
  [&amp;lt;ffffffffc06827e2&amp;gt;] ? vhost_dev_set_owner+0x22e/0x22e [vhost]
  [&amp;lt;ffffffffb683dcd1&amp;gt;] ? flush_kthread_worker+0xf3/0xf3
  [&amp;lt;ffffffffb6eb332e&amp;gt;] ret_from_fork+0x4e/0x80
  [&amp;lt;ffffffffb683dcd1&amp;gt;] ? flush_kthread_worker+0xf3/0xf3&lt;/p&gt;
&lt;p&gt;Work around by doing kvmalloc instead.&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;vhost/vsock: Use kvmalloc/kvfree for larger packets.&lt;/p&gt;
&lt;p&gt;When copying a large file over sftp over vsock, data size is usually 32kB,
and kmalloc seems to fail to try to allocate 32 32kB regions.&lt;/p&gt;
&lt;p&gt;vhost-5837: page allocation failure: order:4, mode:0x24040c0
 Call Trace:
  [&amp;lt;ffffffffb6a0df64&amp;gt;] dump_stack+0x97/0xdb
  [&amp;lt;ffffffffb68d6aed&amp;gt;] warn_alloc_failed+0x10f/0x138
  [&amp;lt;ffffffffb68d868a&amp;gt;] ? __alloc_pages_direct_compact+0x38/0xc8
  [&amp;lt;ffffffffb664619f&amp;gt;] __alloc_pages_nodemask+0x84c/0x90d
  [&amp;lt;ffffffffb6646e56&amp;gt;] alloc_kmem_pages+0x17/0x19
  [&amp;lt;ffffffffb6653a26&amp;gt;] kmalloc_order_trace+0x2b/0xdb
  [&amp;lt;ffffffffb66682f3&amp;gt;] __kmalloc+0x177/0x1f7
  [&amp;lt;ffffffffb66e0d94&amp;gt;] ? copy_from_iter+0x8d/0x31d
  [&amp;lt;ffffffffc0689ab7&amp;gt;] vhost_vsock_handle_tx_kick+0x1fa/0x301 [vhost_vsock]
  [&amp;lt;ffffffffc06828d9&amp;gt;] vhost_worker+0xf7/0x157 [vhost]
  [&amp;lt;ffffffffb683ddce&amp;gt;] kthread+0xfd/0x105
  [&amp;lt;ffffffffc06827e2&amp;gt;] ? vhost_dev_set_owner+0x22e/0x22e [vhost]
  [&amp;lt;ffffffffb683dcd1&amp;gt;] ? flush_kthread_worker+0xf3/0xf3
  [&amp;lt;ffffffffb6eb332e&amp;gt;] ret_from_fork+0x4e/0x80
  [&amp;lt;ffffffffb683dcd1&amp;gt;] ? flush_kthread_worker+0xf3/0xf3&lt;/p&gt;
&lt;p&gt;Work around by doing kvmalloc instead.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2022-50271</guid>
    </item>
  </channel>
</rss>
