<?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:28:09 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-23209 — macvlan: fix error recovery in macvlan_common_newlink()</title>
      <link>https://db.gcve.eu/vuln/cve-2026-23209</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;macvlan: fix error recovery in macvlan_common_newlink()&lt;/p&gt;
&lt;p&gt;valis provided a nice repro to crash the kernel:&lt;/p&gt;
&lt;p&gt;ip link add p1 type veth peer p2
ip link set address 00:00:00:00:00:20 dev p1
ip link set up dev p1
ip link set up dev p2&lt;/p&gt;
&lt;p&gt;ip link add mv0 link p2 type macvlan mode source
ip link add invalid% link p2 type macvlan mode source macaddr add 00:00:00:00:00:20&lt;/p&gt;
&lt;p&gt;ping -c1 -I p1 1.2.3.4&lt;/p&gt;
&lt;p&gt;He also gave a very detailed analysis:&lt;/p&gt;
&lt;p&gt;&amp;lt;quote valis&amp;gt;&lt;/p&gt;
&lt;p&gt;The issue is triggered when a new macvlan link is created  with
MACVLAN_MODE_SOURCE mode and MACVLAN_MACADDR_ADD (or
MACVLAN_MACADDR_SET) parameter, lower device already has a macvlan
port and register_netdevice() called from macvlan_common_newlink()
fails (e.g. because of the invalid link name).&lt;/p&gt;
&lt;p&gt;In this case macvlan_hash_add_source is called from
macvlan_change_sources() / macvlan_common_newlink():&lt;/p&gt;
&lt;p&gt;This adds a reference to vlan to the port&amp;#39;s vlan_source_hash using
macvlan_source_entry.&lt;/p&gt;
&lt;p&gt;vlan is a pointer to the priv data of the link that is being created.&lt;/p&gt;
&lt;p&gt;When register_netdevice() fails, the error is returned from
macvlan_newlink() to rtnl_newlink_create():&lt;/p&gt;
&lt;p&gt;if (ops-&amp;gt;newlink)
                err = ops-&amp;gt;newlink(dev, &amp;amp;params, extack);
        else
                err = register_netdevice(dev);
        if (err &amp;lt; 0) {
                free_netdev(dev);
                goto out;
        }&lt;/p&gt;
&lt;p&gt;and free_netdev() is called, causing a kvfree() on the struct
net_device that…&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;macvlan: fix error recovery in macvlan_common_newlink()&lt;/p&gt;
&lt;p&gt;valis provided a nice repro to crash the kernel:&lt;/p&gt;
&lt;p&gt;ip link add p1 type veth peer p2
ip link set address 00:00:00:00:00:20 dev p1
ip link set up dev p1
ip link set up dev p2&lt;/p&gt;
&lt;p&gt;ip link add mv0 link p2 type macvlan mode source
ip link add invalid% link p2 type macvlan mode source macaddr add 00:00:00:00:00:20&lt;/p&gt;
&lt;p&gt;ping -c1 -I p1 1.2.3.4&lt;/p&gt;
&lt;p&gt;He also gave a very detailed analysis:&lt;/p&gt;
&lt;p&gt;&amp;lt;quote valis&amp;gt;&lt;/p&gt;
&lt;p&gt;The issue is triggered when a new macvlan link is created  with
MACVLAN_MODE_SOURCE mode and MACVLAN_MACADDR_ADD (or
MACVLAN_MACADDR_SET) parameter, lower device already has a macvlan
port and register_netdevice() called from macvlan_common_newlink()
fails (e.g. because of the invalid link name).&lt;/p&gt;
&lt;p&gt;In this case macvlan_hash_add_source is called from
macvlan_change_sources() / macvlan_common_newlink():&lt;/p&gt;
&lt;p&gt;This adds a reference to vlan to the port&amp;#39;s vlan_source_hash using
macvlan_source_entry.&lt;/p&gt;
&lt;p&gt;vlan is a pointer to the priv data of the link that is being created.&lt;/p&gt;
&lt;p&gt;When register_netdevice() fails, the error is returned from
macvlan_newlink() to rtnl_newlink_create():&lt;/p&gt;
&lt;p&gt;if (ops-&amp;gt;newlink)
                err = ops-&amp;gt;newlink(dev, &amp;amp;params, extack);
        else
                err = register_netdevice(dev);
        if (err &amp;lt; 0) {
                free_netdev(dev);
                goto out;
        }&lt;/p&gt;
&lt;p&gt;and free_netdev() is called, causing a kvfree() on the struct
net_device that…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-23209</guid>
    </item>
    <item>
      <title>LSN-0122-1 — Kernel Live Patch Security Notice</title>
      <link>https://db.gcve.eu/vuln/lsn-0122-1</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; 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, Ubuntu:Pro:18.04:LTS: linux and 25 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been
resolved: fs: dlm: fix use after free in midcomms commit While working on
processing dlm message in softirq context I experienced the following KASAN
use-after-free warning: .&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been
resolved: wifi: brcmfmac: Fix oops due to NULL pointer dereference in
brcmf_sdiod_sglist_rw() This patch fixes a NULL pointer dereference bug in
brcmfmac that occurs when a high &amp;#39;sd_sgentry_align&amp;#39; value applies (e.g.
512) and a lot of queued SKBs are sent from the pkt queue.&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been
resolved: padata: fix UAF in padata_reorder A bug was found when run ltp
test: BUG: KASAN: slab-use-after-free in padata_find_next+0x29/0x1a0 Read
of size 4 at addr ffff88bbfe003524 by task kworker/u113:2/3039206 CPU: 0
PID: 3039206 Comm: kworker/u113:2 Kdump: loaded Not tainted 6.6.0+
Workqueue: pdecrypt_parallel padata_parallel_worker Call Trace: &amp;lt;TASK&amp;gt;
dump_stack_lvl+0x32/0x50 print_address_description.constprop.0+0x6b/0x3d0
print_report+0xdd/0x2c0 kasan_report+0xa5/0xd0 padata_find_next+0x29/0x1a0
padata_reorder+0x131/0x220 padata_parallel_worker+0x3d/0xc0
process_one_work+0x2ec/0x5a0 If &amp;#39;mdelay(10)&amp;#39; is added before calling
&amp;#39;padata_find_next&amp;#39; in the &amp;#39;padata_reorder&amp;#39; function, this issue could be
reproduced easily with ltp test (pcrypt_aead01).&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been
resolved: geneve: Fix use-after-free in geneve_find_de…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; 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, Ubuntu:Pro:18.04:LTS: linux and 25 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been
resolved: fs: dlm: fix use after free in midcomms commit While working on
processing dlm message in softirq context I experienced the following KASAN
use-after-free warning: .&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been
resolved: wifi: brcmfmac: Fix oops due to NULL pointer dereference in
brcmf_sdiod_sglist_rw() This patch fixes a NULL pointer dereference bug in
brcmfmac that occurs when a high &amp;#39;sd_sgentry_align&amp;#39; value applies (e.g.
512) and a lot of queued SKBs are sent from the pkt queue.&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been
resolved: padata: fix UAF in padata_reorder A bug was found when run ltp
test: BUG: KASAN: slab-use-after-free in padata_find_next+0x29/0x1a0 Read
of size 4 at addr ffff88bbfe003524 by task kworker/u113:2/3039206 CPU: 0
PID: 3039206 Comm: kworker/u113:2 Kdump: loaded Not tainted 6.6.0+
Workqueue: pdecrypt_parallel padata_parallel_worker Call Trace: &amp;lt;TASK&amp;gt;
dump_stack_lvl+0x32/0x50 print_address_description.constprop.0+0x6b/0x3d0
print_report+0xdd/0x2c0 kasan_report+0xa5/0xd0 padata_find_next+0x29/0x1a0
padata_reorder+0x131/0x220 padata_parallel_worker+0x3d/0xc0
process_one_work+0x2ec/0x5a0 If &amp;#39;mdelay(10)&amp;#39; is added before calling
&amp;#39;padata_find_next&amp;#39; in the &amp;#39;padata_reorder&amp;#39; function, this issue could be
reproduced easily with ltp test (pcrypt_aead01).&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been
resolved: geneve: Fix use-after-free in geneve_find_de…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/lsn-0122-1</guid>
    </item>
  </channel>
</rss>
