<?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>Thu, 19 Nov 2026 17:21:55 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-53140 — netlink: terminate outstanding dump on socket close</title>
      <link>https://db.gcve.eu/vuln/cve-2024-53140</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux, Siemens SIMATIC S7-1500 CPU 1518-4 PN/DP MFP, Siemens SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP, Siemens SIPLUS S7-1500 CPU 1518-4 PN/DP MFP&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;netlink: terminate outstanding dump on socket close&lt;/p&gt;
&lt;p&gt;Netlink supports iterative dumping of data. It provides the families
the following ops:
 - start - (optional) kicks off the dumping process
 - dump  - actual dump helper, keeps getting called until it returns 0
 - done  - (optional) pairs with .start, can be used for cleanup
The whole process is asynchronous and the repeated calls to .dump
don&amp;#39;t actually happen in a tight loop, but rather are triggered
in response to recvmsg() on the socket.&lt;/p&gt;
&lt;p&gt;This gives the user full control over the dump, but also means that
the user can close the socket without getting to the end of the dump.
To make sure .start is always paired with .done we check if there
is an ongoing dump before freeing the socket, and if so call .done.&lt;/p&gt;
&lt;p&gt;The complication is that sockets can get freed from BH and .done
is allowed to sleep. So we use a workqueue to defer the call, when
needed.&lt;/p&gt;
&lt;p&gt;Unfortunately this does not work correctly. What we defer is not
the cleanup but rather releasing a reference on the socket.
We have no guarantee that we own the last reference, if someone
else holds the socket they may release it in BH and we&amp;#39;re back
to square one.&lt;/p&gt;
&lt;p&gt;The whole dance, however, appears to be unnecessary. Only the user
can interact with dumps, so we can clean up when socket is closed.
And close always happens in process context. Some async code may
still access the socket after close, queue notifi…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux, Siemens SIMATIC S7-1500 CPU 1518-4 PN/DP MFP, Siemens SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP, Siemens SIPLUS S7-1500 CPU 1518-4 PN/DP MFP&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;netlink: terminate outstanding dump on socket close&lt;/p&gt;
&lt;p&gt;Netlink supports iterative dumping of data. It provides the families
the following ops:
 - start - (optional) kicks off the dumping process
 - dump  - actual dump helper, keeps getting called until it returns 0
 - done  - (optional) pairs with .start, can be used for cleanup
The whole process is asynchronous and the repeated calls to .dump
don&amp;#39;t actually happen in a tight loop, but rather are triggered
in response to recvmsg() on the socket.&lt;/p&gt;
&lt;p&gt;This gives the user full control over the dump, but also means that
the user can close the socket without getting to the end of the dump.
To make sure .start is always paired with .done we check if there
is an ongoing dump before freeing the socket, and if so call .done.&lt;/p&gt;
&lt;p&gt;The complication is that sockets can get freed from BH and .done
is allowed to sleep. So we use a workqueue to defer the call, when
needed.&lt;/p&gt;
&lt;p&gt;Unfortunately this does not work correctly. What we defer is not
the cleanup but rather releasing a reference on the socket.
We have no guarantee that we own the last reference, if someone
else holds the socket they may release it in BH and we&amp;#39;re back
to square one.&lt;/p&gt;
&lt;p&gt;The whole dance, however, appears to be unnecessary. Only the user
can interact with dumps, so we can clean up when socket is closed.
And close always happens in process context. Some async code may
still access the socket after close, queue notifi…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2024-53140</guid>
    </item>
    <item>
      <title>LSN-0110-1 — Kernel Live Patch Security Notice</title>
      <link>https://db.gcve.eu/vuln/lsn-0110-1</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; 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&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been
resolved: tty: n_gsm: require CAP_NET_ADMIN to attach N_GSM0710 ldisc Any
unprivileged user can attach N_GSM0710 ldisc, but it requires CAP_NET_ADMIN
to create a GSM network anyway. Require initial namespace CAP_NET_ADMIN to
do that.)(CVE-2023-52880)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been
resolved: net: openvswitch: fix overwriting ct original tuple for ICMPv6
OVS_PACKET_CMD_EXECUTE has 3 main attributes: - OVS_PACKET_ATTR_KEY -
Packet metadata in a netlink format. - OVS_PACKET_ATTR_PACKET - Binary
packet content. - OVS_PACKET_ATTR_ACTIONS - Actions to execute on the
packet. OVS_PACKET_ATTR_KEY is parsed first to populate sw_flow_key
structure with the metadata like conntrack state, input port, recirculation
id, etc. Then the packet itself gets parsed to populate the rest of the
keys from the packet headers. Whenever the packet parsing code starts
parsing the ICMPv6 header, it first zeroes out fields in the key
corresponding to Neighbor Discovery information even if it is not an ND
packet. It is an &amp;#39;ipv6.nd&amp;#39; field. However, the &amp;#39;ipv6&amp;#39; is a union that
shares the space between &amp;#39;nd&amp;#39; and &amp;#39;ct_orig&amp;#39; that holds the original tuple
conntrack metadata parsed from the OVS_PACKET_ATTR_KEY. ND packets should
not normally have conntrack state, so it&amp;#39;s fine to share the space, but
normal ICMPv6 Echo packets or maybe other types of ICMPv6 can have the
state attached and it should not be overwritten. The issue resu…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; 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&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been
resolved: tty: n_gsm: require CAP_NET_ADMIN to attach N_GSM0710 ldisc Any
unprivileged user can attach N_GSM0710 ldisc, but it requires CAP_NET_ADMIN
to create a GSM network anyway. Require initial namespace CAP_NET_ADMIN to
do that.)(CVE-2023-52880)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been
resolved: net: openvswitch: fix overwriting ct original tuple for ICMPv6
OVS_PACKET_CMD_EXECUTE has 3 main attributes: - OVS_PACKET_ATTR_KEY -
Packet metadata in a netlink format. - OVS_PACKET_ATTR_PACKET - Binary
packet content. - OVS_PACKET_ATTR_ACTIONS - Actions to execute on the
packet. OVS_PACKET_ATTR_KEY is parsed first to populate sw_flow_key
structure with the metadata like conntrack state, input port, recirculation
id, etc. Then the packet itself gets parsed to populate the rest of the
keys from the packet headers. Whenever the packet parsing code starts
parsing the ICMPv6 header, it first zeroes out fields in the key
corresponding to Neighbor Discovery information even if it is not an ND
packet. It is an &amp;#39;ipv6.nd&amp;#39; field. However, the &amp;#39;ipv6&amp;#39; is a union that
shares the space between &amp;#39;nd&amp;#39; and &amp;#39;ct_orig&amp;#39; that holds the original tuple
conntrack metadata parsed from the OVS_PACKET_ATTR_KEY. ND packets should
not normally have conntrack state, so it&amp;#39;s fine to share the space, but
normal ICMPv6 Echo packets or maybe other types of ICMPv6 can have the
state attached and it should not be overwritten. The issue resu…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/lsn-0110-1</guid>
    </item>
  </channel>
</rss>
