<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://db.gcve.eu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-11-19T17:17:41.491924+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@gcve.eu</email>
  </author>
  <link href="https://db.gcve.eu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://db.gcve.eu/vuln/cve-2024-36016</id>
    <title>CVE-2024-36016 — tty: n_gsm: fix possible out-of-bounds in gsm0_receive()</title>
    <updated>2026-11-19T17:17:41.589732+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Linux, linux_kernel</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>tty: n_gsm: fix possible out-of-bounds in gsm0_receive()</p>
<p>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-&gt;len
  Reason: gsm-&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-&gt;buf
  Reason: Neither gsm-&gt;state nor gsm-&gt;len have been reset after
  reconfiguration.</p>
<p>Fix this by changing gsm-&gt;count to gsm-&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-&gt;len and gsm-&gt;mru.</p>
<p>All other checks remain as we still need to limit the data according to the
user configuration and actual payload size.</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/cve-2024-36016"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/lsn-0106-1</id>
    <title>LSN-0106-1 — Kernel Live Patch Security Notice</title>
    <updated>2026-11-19T17:17:41.589825+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:18.04:LTS: linux-aws, Ubuntu:Pro:18.04:LTS: linux-azure-4.15, Ubuntu:Pro:18.04:LTS: linux-gcp-4.15 and 28 more</p>
<p>In the Linux kernel, the following vulnerability has been
resolved: netfilter: nf_tables: disallow timeout for anonymous sets Never
used from userspace, disallow these parameters.(CVE-2023-52620)</p>
<p>In the Linux kernel, the following vulnerability has been
resolved: tls: fix race between tx work scheduling and socket close
Similarly to previous commit, the submitting thread (recvmsg/sendmsg) may
exit as soon as the async crypto handler calls complete(). Reorder
scheduling the work before calling complete(). This seems more logical in
the first place, as it's the inverse order of what the submitting thread
will do.(CVE-2024-26585)</p>
<p>In the Linux kernel, the following vulnerability has been
resolved: tty: n_gsm: fix possible out-of-bounds in gsm0_receive() 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-&gt;len Reason: gsm-&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-&gt;buf Reason: Neither gsm-&gt;state nor gsm-&gt;len have been
reset after reconfiguration. Fix this by changing gsm-&gt;count to gsm-&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-&gt;len and gsm-&gt;mru. All other checks remai…</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/lsn-0106-1"/>
  </entry>
</feed>
