<?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://cve.radiocsirt.org</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>Tue, 06 Oct 2026 20:17:13 +0000</lastBuildDate>
    <item>
      <title>CVE-2021-47170 — USB: usbfs: Don't WARN about excessively large memory allocations</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2021-47170</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;USB: usbfs: Don&amp;#39;t WARN about excessively large memory allocations&lt;/p&gt;
&lt;p&gt;Syzbot found that the kernel generates a WARNing if the user tries to
submit a bulk transfer through usbfs with a buffer that is way too
large.  This isn&amp;#39;t a bug in the kernel; it&amp;#39;s merely an invalid request
from the user and the usbfs code does handle it correctly.&lt;/p&gt;
&lt;p&gt;In theory the same thing can happen with async transfers, or with the
packet descriptor table for isochronous transfers.&lt;/p&gt;
&lt;p&gt;To prevent the MM subsystem from complaining about these bad
allocation requests, add the __GFP_NOWARN flag to the kmalloc calls
for these buffers.&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;USB: usbfs: Don&amp;#39;t WARN about excessively large memory allocations&lt;/p&gt;
&lt;p&gt;Syzbot found that the kernel generates a WARNing if the user tries to
submit a bulk transfer through usbfs with a buffer that is way too
large.  This isn&amp;#39;t a bug in the kernel; it&amp;#39;s merely an invalid request
from the user and the usbfs code does handle it correctly.&lt;/p&gt;
&lt;p&gt;In theory the same thing can happen with async transfers, or with the
packet descriptor table for isochronous transfers.&lt;/p&gt;
&lt;p&gt;To prevent the MM subsystem from complaining about these bad
allocation requests, add the __GFP_NOWARN flag to the kmalloc calls
for these buffers.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2021-47170</guid>
    </item>
  </channel>
</rss>
