<?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://vulnerability.circl.lu</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, 29 Sep 2026 17:22:02 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-31412 — usb: gadget: f_mass_storage: Fix potential integer overflow in check_command_size_in_blocks()</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-31412</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: gadget: f_mass_storage: Fix potential integer overflow in check_command_size_in_blocks()&lt;/p&gt;
&lt;p&gt;The `check_command_size_in_blocks()` function calculates the data size
in bytes by left shifting `common-&amp;gt;data_size_from_cmnd` by the block
size (`common-&amp;gt;curlun-&amp;gt;blkbits`). However, it does not validate whether
this shift operation will cause an integer overflow.&lt;/p&gt;
&lt;p&gt;Initially, the block size is set up in `fsg_lun_open()` , and the
`common-&amp;gt;data_size_from_cmnd` is set up in `do_scsi_command()`. During
initialization, there is no integer overflow check for the interaction
between two variables.&lt;/p&gt;
&lt;p&gt;So if a malicious USB host sends a SCSI READ or WRITE command
requesting a large amount of data (`common-&amp;gt;data_size_from_cmnd`), the
left shift operation can wrap around. This results in a truncated data
size, which can bypass boundary checks and potentially lead to memory
corruption or out-of-bounds accesses.&lt;/p&gt;
&lt;p&gt;Fix this by using the check_shl_overflow() macro to safely perform the
shift and catch any overflows.&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: gadget: f_mass_storage: Fix potential integer overflow in check_command_size_in_blocks()&lt;/p&gt;
&lt;p&gt;The `check_command_size_in_blocks()` function calculates the data size
in bytes by left shifting `common-&amp;gt;data_size_from_cmnd` by the block
size (`common-&amp;gt;curlun-&amp;gt;blkbits`). However, it does not validate whether
this shift operation will cause an integer overflow.&lt;/p&gt;
&lt;p&gt;Initially, the block size is set up in `fsg_lun_open()` , and the
`common-&amp;gt;data_size_from_cmnd` is set up in `do_scsi_command()`. During
initialization, there is no integer overflow check for the interaction
between two variables.&lt;/p&gt;
&lt;p&gt;So if a malicious USB host sends a SCSI READ or WRITE command
requesting a large amount of data (`common-&amp;gt;data_size_from_cmnd`), the
left shift operation can wrap around. This results in a truncated data
size, which can bypass boundary checks and potentially lead to memory
corruption or out-of-bounds accesses.&lt;/p&gt;
&lt;p&gt;Fix this by using the check_shl_overflow() macro to safely perform the
shift and catch any overflows.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-31412</guid>
    </item>
  </channel>
</rss>
