<?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>Mon, 05 Oct 2026 01:36:50 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-36016 — tty: n_gsm: fix possible out-of-bounds in gsm0_receive()</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2024-36016</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux, linux_kernel&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;tty: n_gsm: fix possible out-of-bounds in gsm0_receive()&lt;/p&gt;
&lt;p&gt;Assuming the following:
- side A configures the n_gsm in basic option mode
- side B sends the header of a basic option mode frame with data length 1
- side A switches to advanced option mode
- side B sends 2 data bytes which exceeds gsm-&amp;gt;len
  Reason: gsm-&amp;gt;len is not used in advanced option mode.
- side A switches to basic option mode
- side B keeps sending until gsm0_receive() writes past gsm-&amp;gt;buf
  Reason: Neither gsm-&amp;gt;state nor gsm-&amp;gt;len have been reset after
  reconfiguration.&lt;/p&gt;
&lt;p&gt;Fix this by changing gsm-&amp;gt;count to gsm-&amp;gt;len comparison from equal to less
than. Also add upper limit checks against the constant MAX_MRU in
gsm0_receive() and gsm1_receive() to harden against memory corruption of
gsm-&amp;gt;len and gsm-&amp;gt;mru.&lt;/p&gt;
&lt;p&gt;All other checks remain as we still need to limit the data according to the
user configuration and actual payload size.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux, linux_kernel&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;tty: n_gsm: fix possible out-of-bounds in gsm0_receive()&lt;/p&gt;
&lt;p&gt;Assuming the following:
- side A configures the n_gsm in basic option mode
- side B sends the header of a basic option mode frame with data length 1
- side A switches to advanced option mode
- side B sends 2 data bytes which exceeds gsm-&amp;gt;len
  Reason: gsm-&amp;gt;len is not used in advanced option mode.
- side A switches to basic option mode
- side B keeps sending until gsm0_receive() writes past gsm-&amp;gt;buf
  Reason: Neither gsm-&amp;gt;state nor gsm-&amp;gt;len have been reset after
  reconfiguration.&lt;/p&gt;
&lt;p&gt;Fix this by changing gsm-&amp;gt;count to gsm-&amp;gt;len comparison from equal to less
than. Also add upper limit checks against the constant MAX_MRU in
gsm0_receive() and gsm1_receive() to harden against memory corruption of
gsm-&amp;gt;len and gsm-&amp;gt;mru.&lt;/p&gt;
&lt;p&gt;All other checks remain as we still need to limit the data according to the
user configuration and actual payload size.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2024-36016</guid>
    </item>
  </channel>
</rss>
