<?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>Tue, 29 Sep 2026 22:24:21 +0000</lastBuildDate>
    <item>
      <title>CVE-2022-49940 — tty: n_gsm: add sanity check for gsm-&gt;receive in gsm_receive_buf()</title>
      <link>https://db.gcve.eu/vuln/cve-2022-49940</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;tty: n_gsm: add sanity check for gsm-&amp;gt;receive in gsm_receive_buf()&lt;/p&gt;
&lt;p&gt;A null pointer dereference can happen when attempting to access the
&amp;#34;gsm-&amp;gt;receive()&amp;#34; function in gsmld_receive_buf(). Currently, the code
assumes that gsm-&amp;gt;recieve is only called after MUX activation.
Since the gsmld_receive_buf() function can be accessed without the need to
initialize the MUX, the gsm-&amp;gt;receive() function will not be set and a
NULL pointer dereference will occur.&lt;/p&gt;
&lt;p&gt;Fix this by avoiding the call to &amp;#34;gsm-&amp;gt;receive()&amp;#34; in case the function is
not initialized by adding a sanity check.&lt;/p&gt;
&lt;p&gt;Call Trace:
 &amp;lt;TASK&amp;gt;
 gsmld_receive_buf+0x1c2/0x2f0 drivers/tty/n_gsm.c:2861
 tiocsti drivers/tty/tty_io.c:2293 [inline]
 tty_ioctl+0xa75/0x15d0 drivers/tty/tty_io.c:2692
 vfs_ioctl fs/ioctl.c:51 [inline]
 __do_sys_ioctl fs/ioctl.c:870 [inline]
 __se_sys_ioctl fs/ioctl.c:856 [inline]
 __x64_sys_ioctl+0x193/0x200 fs/ioctl.c:856
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x63/0xcd&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;tty: n_gsm: add sanity check for gsm-&amp;gt;receive in gsm_receive_buf()&lt;/p&gt;
&lt;p&gt;A null pointer dereference can happen when attempting to access the
&amp;#34;gsm-&amp;gt;receive()&amp;#34; function in gsmld_receive_buf(). Currently, the code
assumes that gsm-&amp;gt;recieve is only called after MUX activation.
Since the gsmld_receive_buf() function can be accessed without the need to
initialize the MUX, the gsm-&amp;gt;receive() function will not be set and a
NULL pointer dereference will occur.&lt;/p&gt;
&lt;p&gt;Fix this by avoiding the call to &amp;#34;gsm-&amp;gt;receive()&amp;#34; in case the function is
not initialized by adding a sanity check.&lt;/p&gt;
&lt;p&gt;Call Trace:
 &amp;lt;TASK&amp;gt;
 gsmld_receive_buf+0x1c2/0x2f0 drivers/tty/n_gsm.c:2861
 tiocsti drivers/tty/tty_io.c:2293 [inline]
 tty_ioctl+0xa75/0x15d0 drivers/tty/tty_io.c:2692
 vfs_ioctl fs/ioctl.c:51 [inline]
 __do_sys_ioctl fs/ioctl.c:870 [inline]
 __se_sys_ioctl fs/ioctl.c:856 [inline]
 __x64_sys_ioctl+0x193/0x200 fs/ioctl.c:856
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x63/0xcd&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2022-49940</guid>
    </item>
  </channel>
</rss>
