{ "summary": { "snap": { "added": [], "removed": [], "diff": [] }, "deb": { "added": [ "linux-headers-5.15.0-1098-kvm", "linux-image-5.15.0-1098-kvm", "linux-kvm-headers-5.15.0-1098", "linux-modules-5.15.0-1098-kvm" ], "removed": [ "linux-headers-5.15.0-1097-kvm", "linux-image-5.15.0-1097-kvm", "linux-kvm-headers-5.15.0-1097", "linux-modules-5.15.0-1097-kvm" ], "diff": [ "kmod", "libkmod2", "linux-headers-kvm", "linux-image-kvm", "linux-kvm" ] } }, "diff": { "deb": [ { "name": "kmod", "from_version": { "source_package_name": "kmod", "source_package_version": "29-1ubuntu1", "version": "29-1ubuntu1" }, "to_version": { "source_package_name": "kmod", "source_package_version": "29-1ubuntu1.1", "version": "29-1ubuntu1.1" }, "cves": [ { "cve": "CVE-2026-31431", "url": "https://ubuntu.com/security/CVE-2026-31431", "cve_description": "In the Linux kernel, the following vulnerability has been resolved: crypto: algif_aead - Revert to operating out-of-place This mostly reverts commit 72548b093ee3 except for the copying of the associated data. There is no benefit in operating in-place in algif_aead since the source and destination come from different mappings. Get rid of all the complexity added for in-place operation and just copy the AD directly.", "cve_priority": "high", "cve_public_date": "2026-04-23" } ], "launchpad_bugs_fixed": [ 2150743 ], "changes": [ { "cves": [ { "cve": "CVE-2026-31431", "url": "https://ubuntu.com/security/CVE-2026-31431", "cve_description": "In the Linux kernel, the following vulnerability has been resolved: crypto: algif_aead - Revert to operating out-of-place This mostly reverts commit 72548b093ee3 except for the copying of the associated data. There is no benefit in operating in-place in algif_aead since the source and destination come from different mappings. Get rid of all the complexity added for in-place operation and just copy the AD directly.", "cve_priority": "high", "cve_public_date": "2026-04-23" } ], "log": [ "", " * Disable loading of algif_aead module to mitigate CVE-2026-31431", " (LP: #2150743)", " - debian/modprobe.d/disable-algif_aead.conf", "" ], "package": "kmod", "version": "29-1ubuntu1.1", "urgency": "medium", "distributions": "jammy-security", "launchpad_bugs_fixed": [ 2150743 ], "author": "Marc Deslauriers ", "date": "Thu, 30 Apr 2026 08:32:42 -0400" } ], "notes": null, "is_version_downgrade": false }, { "name": "libkmod2", "from_version": { "source_package_name": "kmod", "source_package_version": "29-1ubuntu1", "version": "29-1ubuntu1" }, "to_version": { "source_package_name": "kmod", "source_package_version": "29-1ubuntu1.1", "version": "29-1ubuntu1.1" }, "cves": [ { "cve": "CVE-2026-31431", "url": "https://ubuntu.com/security/CVE-2026-31431", "cve_description": "In the Linux kernel, the following vulnerability has been resolved: crypto: algif_aead - Revert to operating out-of-place This mostly reverts commit 72548b093ee3 except for the copying of the associated data. There is no benefit in operating in-place in algif_aead since the source and destination come from different mappings. Get rid of all the complexity added for in-place operation and just copy the AD directly.", "cve_priority": "high", "cve_public_date": "2026-04-23" } ], "launchpad_bugs_fixed": [ 2150743 ], "changes": [ { "cves": [ { "cve": "CVE-2026-31431", "url": "https://ubuntu.com/security/CVE-2026-31431", "cve_description": "In the Linux kernel, the following vulnerability has been resolved: crypto: algif_aead - Revert to operating out-of-place This mostly reverts commit 72548b093ee3 except for the copying of the associated data. There is no benefit in operating in-place in algif_aead since the source and destination come from different mappings. Get rid of all the complexity added for in-place operation and just copy the AD directly.", "cve_priority": "high", "cve_public_date": "2026-04-23" } ], "log": [ "", " * Disable loading of algif_aead module to mitigate CVE-2026-31431", " (LP: #2150743)", " - debian/modprobe.d/disable-algif_aead.conf", "" ], "package": "kmod", "version": "29-1ubuntu1.1", "urgency": "medium", "distributions": "jammy-security", "launchpad_bugs_fixed": [ 2150743 ], "author": "Marc Deslauriers ", "date": "Thu, 30 Apr 2026 08:32:42 -0400" } ], "notes": null, "is_version_downgrade": false }, { "name": "linux-headers-kvm", "from_version": { "source_package_name": "linux-meta-kvm", "source_package_version": "5.15.0.1097.93", "version": "5.15.0.1097.93" }, "to_version": { "source_package_name": "linux-meta-kvm", "source_package_version": "5.15.0.1098.94", "version": "5.15.0.1098.94" }, "cves": [], "launchpad_bugs_fixed": [], "changes": [ { "cves": [], "log": [ "", " * Bump ABI 5.15.0-1098", "" ], "package": "linux-meta-kvm", "version": "5.15.0.1098.94", "urgency": "medium", "distributions": "jammy", "launchpad_bugs_fixed": [], "author": "Austin Rhodes ", "date": "Tue, 21 Apr 2026 10:58:16 -0400" } ], "notes": null, "is_version_downgrade": false }, { "name": "linux-image-kvm", "from_version": { "source_package_name": "linux-meta-kvm", "source_package_version": "5.15.0.1097.93", "version": "5.15.0.1097.93" }, "to_version": { "source_package_name": "linux-meta-kvm", "source_package_version": "5.15.0.1098.94", "version": "5.15.0.1098.94" }, "cves": [], "launchpad_bugs_fixed": [], "changes": [ { "cves": [], "log": [ "", " * Bump ABI 5.15.0-1098", "" ], "package": "linux-meta-kvm", "version": "5.15.0.1098.94", "urgency": "medium", "distributions": "jammy", "launchpad_bugs_fixed": [], "author": "Austin Rhodes ", "date": "Tue, 21 Apr 2026 10:58:16 -0400" } ], "notes": null, "is_version_downgrade": false }, { "name": "linux-kvm", "from_version": { "source_package_name": "linux-meta-kvm", "source_package_version": "5.15.0.1097.93", "version": "5.15.0.1097.93" }, "to_version": { "source_package_name": "linux-meta-kvm", "source_package_version": "5.15.0.1098.94", "version": "5.15.0.1098.94" }, "cves": [], "launchpad_bugs_fixed": [], "changes": [ { "cves": [], "log": [ "", " * Bump ABI 5.15.0-1098", "" ], "package": "linux-meta-kvm", "version": "5.15.0.1098.94", "urgency": "medium", "distributions": "jammy", "launchpad_bugs_fixed": [], "author": "Austin Rhodes ", "date": "Tue, 21 Apr 2026 10:58:16 -0400" } ], "notes": null, "is_version_downgrade": false } ], "snap": [] }, "added": { "deb": [ { "name": "linux-headers-5.15.0-1098-kvm", "from_version": { "source_package_name": "linux-kvm", "source_package_version": "5.15.0-1097.102", "version": null }, "to_version": { "source_package_name": "linux-kvm", "source_package_version": "5.15.0-1098.103", "version": "5.15.0-1098.103" }, "cves": [ { "cve": "CVE-2026-23209", "url": "https://ubuntu.com/security/CVE-2026-23209", "cve_description": "In the Linux kernel, the following vulnerability has been resolved: macvlan: fix error recovery in macvlan_common_newlink() valis provided a nice repro to crash the kernel: 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 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 ping -c1 -I p1 1.2.3.4 He also gave a very detailed analysis: 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). In this case macvlan_hash_add_source is called from macvlan_change_sources() / macvlan_common_newlink(): This adds a reference to vlan to the port's vlan_source_hash using macvlan_source_entry. vlan is a pointer to the priv data of the link that is being created. When register_netdevice() fails, the error is returned from macvlan_newlink() to rtnl_newlink_create(): if (ops->newlink) err = ops->newlink(dev, ¶ms, extack); else err = register_netdevice(dev); if (err < 0) { free_netdev(dev); goto out; } and free_netdev() is called, causing a kvfree() on the struct net_device that is still referenced in the source entry attached to the lower device's macvlan port. Now all packets sent on the macvlan port with a matching source mac address will trigger a use-after-free in macvlan_forward_source(). With all that, my fix is to make sure we call macvlan_flush_sources() regardless of @create value whenever \"goto destroy_macvlan_port;\" path is taken. Many thanks to valis for following up on this issue.", "cve_priority": "medium", "cve_public_date": "2026-02-14 17:15:00 UTC" }, { "cve": "CVE-2023-2640", "url": "https://ubuntu.com/security/CVE-2023-2640", "cve_description": "On Ubuntu kernels carrying both c914c0e27eb0 and \"UBUNTU: SAUCE: overlayfs: Skip permission checking for trusted.overlayfs.* xattrs\", an unprivileged user may set privileged extended attributes on the mounted files, leading them to be set on the upper files without the appropriate security checks.", "cve_priority": "high", "cve_public_date": "2023-07-26 02:15:00 UTC" }, { "cve": "CVE-2023-32629", "url": "https://ubuntu.com/security/CVE-2023-32629", "cve_description": "Local privilege escalation vulnerability in Ubuntu Kernels overlayfs ovl_copy_up_meta_inode_data skip permission checks when calling ovl_do_setxattr on Ubuntu kernels", "cve_priority": "high", "cve_public_date": "2023-07-26 02:15:00 UTC" }, { "cve": "CVE-2026-23112", "url": "https://ubuntu.com/security/CVE-2026-23112", "cve_description": "In the Linux kernel, the following vulnerability has been resolved: nvmet-tcp: add bounds checks in nvmet_tcp_build_pdu_iovec nvmet_tcp_build_pdu_iovec() could walk past cmd->req.sg when a PDU length or offset exceeds sg_cnt and then use bogus sg->length/offset values, leading to _copy_to_iter() GPF/KASAN. Guard sg_idx, remaining entries, and sg->length/offset before building the bvec.", "cve_priority": "high", "cve_public_date": "2026-02-13 14:16:00 UTC" } ], "launchpad_bugs_fixed": [ 2147825, 2147840, 2144380 ], "changes": [ { "cves": [ { "cve": "CVE-2026-23209", "url": "https://ubuntu.com/security/CVE-2026-23209", "cve_description": "In the Linux kernel, the following vulnerability has been resolved: macvlan: fix error recovery in macvlan_common_newlink() valis provided a nice repro to crash the kernel: 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 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 ping -c1 -I p1 1.2.3.4 He also gave a very detailed analysis: 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). In this case macvlan_hash_add_source is called from macvlan_change_sources() / macvlan_common_newlink(): This adds a reference to vlan to the port's vlan_source_hash using macvlan_source_entry. vlan is a pointer to the priv data of the link that is being created. When register_netdevice() fails, the error is returned from macvlan_newlink() to rtnl_newlink_create(): if (ops->newlink) err = ops->newlink(dev, ¶ms, extack); else err = register_netdevice(dev); if (err < 0) { free_netdev(dev); goto out; } and free_netdev() is called, causing a kvfree() on the struct net_device that is still referenced in the source entry attached to the lower device's macvlan port. Now all packets sent on the macvlan port with a matching source mac address will trigger a use-after-free in macvlan_forward_source(). With all that, my fix is to make sure we call macvlan_flush_sources() regardless of @create value whenever \"goto destroy_macvlan_port;\" path is taken. Many thanks to valis for following up on this issue.", "cve_priority": "medium", "cve_public_date": "2026-02-14 17:15:00 UTC" }, { "cve": "CVE-2023-2640", "url": "https://ubuntu.com/security/CVE-2023-2640", "cve_description": "On Ubuntu kernels carrying both c914c0e27eb0 and \"UBUNTU: SAUCE: overlayfs: Skip permission checking for trusted.overlayfs.* xattrs\", an unprivileged user may set privileged extended attributes on the mounted files, leading them to be set on the upper files without the appropriate security checks.", "cve_priority": "high", "cve_public_date": "2023-07-26 02:15:00 UTC" }, { "cve": "CVE-2023-32629", "url": "https://ubuntu.com/security/CVE-2023-32629", "cve_description": "Local privilege escalation vulnerability in Ubuntu Kernels overlayfs ovl_copy_up_meta_inode_data skip permission checks when calling ovl_do_setxattr on Ubuntu kernels", "cve_priority": "high", "cve_public_date": "2023-07-26 02:15:00 UTC" }, { "cve": "CVE-2026-23112", "url": "https://ubuntu.com/security/CVE-2026-23112", "cve_description": "In the Linux kernel, the following vulnerability has been resolved: nvmet-tcp: add bounds checks in nvmet_tcp_build_pdu_iovec nvmet_tcp_build_pdu_iovec() could walk past cmd->req.sg when a PDU length or offset exceeds sg_cnt and then use bogus sg->length/offset values, leading to _copy_to_iter() GPF/KASAN. Guard sg_idx, remaining entries, and sg->length/offset before building the bvec.", "cve_priority": "high", "cve_public_date": "2026-02-13 14:16:00 UTC" } ], "log": [ "", " * jammy/linux-kvm: 5.15.0-1098.103 -proposed tracker (LP: #2147825)", "", " [ Ubuntu: 5.15.0-177.187 ]", "", " * jammy/linux: 5.15.0-177.187 -proposed tracker (LP: #2147840)", " * macvlan: observe an RCU grace period in macvlan_common_newlink() error", " path (LP: #2144380) // CVE-2026-23209", " - macvlan: observe an RCU grace period in macvlan_common_newlink() error", " path", " * CVE-2023-2640 // CVE-2023-32629", " - SAUCE: Revert \"UBUNTU: SAUCE: overlayfs: Skip permission checking for", " trusted.overlayfs.* xattrs\"", " - SAUCE: overlayfs: default to userxattr when mounted from non initial", " user namespace", " * CVE-2026-23112", " - nvmet-tcp: add bounds checks in nvmet_tcp_build_pdu_iovec", "" ], "package": "linux-kvm", "version": "5.15.0-1098.103", "urgency": "medium", "distributions": "jammy", "launchpad_bugs_fixed": [ 2147825, 2147840, 2144380 ], "author": "Austin Rhodes ", "date": "Mon, 20 Apr 2026 16:26:42 -0400" } ], "notes": "linux-headers-5.15.0-1098-kvm version '5.15.0-1098.103' (source package linux-kvm version '5.15.0-1098.103') was added. linux-headers-5.15.0-1098-kvm version '5.15.0-1098.103' has the same source package name, linux-kvm, as removed package linux-headers-5.15.0-1097-kvm. As such we can use the source package version of the removed package, '5.15.0-1097.102', as the starting point in our changelog diff. Kernel packages are an example of where the binary package name changes for the same source package. Using the removed package source package version as our starting point means we can still get meaningful changelog diffs even for what appears to be a new package.", "is_version_downgrade": false }, { "name": "linux-image-5.15.0-1098-kvm", "from_version": { "source_package_name": "linux-signed-kvm", "source_package_version": "5.15.0-1097.102", "version": null }, "to_version": { "source_package_name": "linux-signed-kvm", "source_package_version": "5.15.0-1098.103", "version": "5.15.0-1098.103" }, "cves": [], "launchpad_bugs_fixed": [ 1786013 ], "changes": [ { "cves": [], "log": [ "", " * Main version: 5.15.0-1098.103", "", " * Packaging resync (LP: #1786013)", " - [Packaging] debian/tracking-bug -- resync from main package", "" ], "package": "linux-signed-kvm", "version": "5.15.0-1098.103", "urgency": "medium", "distributions": "jammy", "launchpad_bugs_fixed": [ 1786013 ], "author": "Austin Rhodes ", "date": "Tue, 21 Apr 2026 10:30:10 -0400" } ], "notes": "linux-image-5.15.0-1098-kvm version '5.15.0-1098.103' (source package linux-signed-kvm version '5.15.0-1098.103') was added. linux-image-5.15.0-1098-kvm version '5.15.0-1098.103' has the same source package name, linux-signed-kvm, as removed package linux-image-5.15.0-1097-kvm. As such we can use the source package version of the removed package, '5.15.0-1097.102', as the starting point in our changelog diff. Kernel packages are an example of where the binary package name changes for the same source package. Using the removed package source package version as our starting point means we can still get meaningful changelog diffs even for what appears to be a new package.", "is_version_downgrade": false }, { "name": "linux-kvm-headers-5.15.0-1098", "from_version": { "source_package_name": "linux-kvm", "source_package_version": "5.15.0-1097.102", "version": null }, "to_version": { "source_package_name": "linux-kvm", "source_package_version": "5.15.0-1098.103", "version": "5.15.0-1098.103" }, "cves": [ { "cve": "CVE-2026-23209", "url": "https://ubuntu.com/security/CVE-2026-23209", "cve_description": "In the Linux kernel, the following vulnerability has been resolved: macvlan: fix error recovery in macvlan_common_newlink() valis provided a nice repro to crash the kernel: 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 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 ping -c1 -I p1 1.2.3.4 He also gave a very detailed analysis: 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). In this case macvlan_hash_add_source is called from macvlan_change_sources() / macvlan_common_newlink(): This adds a reference to vlan to the port's vlan_source_hash using macvlan_source_entry. vlan is a pointer to the priv data of the link that is being created. When register_netdevice() fails, the error is returned from macvlan_newlink() to rtnl_newlink_create(): if (ops->newlink) err = ops->newlink(dev, ¶ms, extack); else err = register_netdevice(dev); if (err < 0) { free_netdev(dev); goto out; } and free_netdev() is called, causing a kvfree() on the struct net_device that is still referenced in the source entry attached to the lower device's macvlan port. Now all packets sent on the macvlan port with a matching source mac address will trigger a use-after-free in macvlan_forward_source(). With all that, my fix is to make sure we call macvlan_flush_sources() regardless of @create value whenever \"goto destroy_macvlan_port;\" path is taken. Many thanks to valis for following up on this issue.", "cve_priority": "medium", "cve_public_date": "2026-02-14 17:15:00 UTC" }, { "cve": "CVE-2023-2640", "url": "https://ubuntu.com/security/CVE-2023-2640", "cve_description": "On Ubuntu kernels carrying both c914c0e27eb0 and \"UBUNTU: SAUCE: overlayfs: Skip permission checking for trusted.overlayfs.* xattrs\", an unprivileged user may set privileged extended attributes on the mounted files, leading them to be set on the upper files without the appropriate security checks.", "cve_priority": "high", "cve_public_date": "2023-07-26 02:15:00 UTC" }, { "cve": "CVE-2023-32629", "url": "https://ubuntu.com/security/CVE-2023-32629", "cve_description": "Local privilege escalation vulnerability in Ubuntu Kernels overlayfs ovl_copy_up_meta_inode_data skip permission checks when calling ovl_do_setxattr on Ubuntu kernels", "cve_priority": "high", "cve_public_date": "2023-07-26 02:15:00 UTC" }, { "cve": "CVE-2026-23112", "url": "https://ubuntu.com/security/CVE-2026-23112", "cve_description": "In the Linux kernel, the following vulnerability has been resolved: nvmet-tcp: add bounds checks in nvmet_tcp_build_pdu_iovec nvmet_tcp_build_pdu_iovec() could walk past cmd->req.sg when a PDU length or offset exceeds sg_cnt and then use bogus sg->length/offset values, leading to _copy_to_iter() GPF/KASAN. Guard sg_idx, remaining entries, and sg->length/offset before building the bvec.", "cve_priority": "high", "cve_public_date": "2026-02-13 14:16:00 UTC" } ], "launchpad_bugs_fixed": [ 2147825, 2147840, 2144380 ], "changes": [ { "cves": [ { "cve": "CVE-2026-23209", "url": "https://ubuntu.com/security/CVE-2026-23209", "cve_description": "In the Linux kernel, the following vulnerability has been resolved: macvlan: fix error recovery in macvlan_common_newlink() valis provided a nice repro to crash the kernel: 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 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 ping -c1 -I p1 1.2.3.4 He also gave a very detailed analysis: 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). In this case macvlan_hash_add_source is called from macvlan_change_sources() / macvlan_common_newlink(): This adds a reference to vlan to the port's vlan_source_hash using macvlan_source_entry. vlan is a pointer to the priv data of the link that is being created. When register_netdevice() fails, the error is returned from macvlan_newlink() to rtnl_newlink_create(): if (ops->newlink) err = ops->newlink(dev, ¶ms, extack); else err = register_netdevice(dev); if (err < 0) { free_netdev(dev); goto out; } and free_netdev() is called, causing a kvfree() on the struct net_device that is still referenced in the source entry attached to the lower device's macvlan port. Now all packets sent on the macvlan port with a matching source mac address will trigger a use-after-free in macvlan_forward_source(). With all that, my fix is to make sure we call macvlan_flush_sources() regardless of @create value whenever \"goto destroy_macvlan_port;\" path is taken. Many thanks to valis for following up on this issue.", "cve_priority": "medium", "cve_public_date": "2026-02-14 17:15:00 UTC" }, { "cve": "CVE-2023-2640", "url": "https://ubuntu.com/security/CVE-2023-2640", "cve_description": "On Ubuntu kernels carrying both c914c0e27eb0 and \"UBUNTU: SAUCE: overlayfs: Skip permission checking for trusted.overlayfs.* xattrs\", an unprivileged user may set privileged extended attributes on the mounted files, leading them to be set on the upper files without the appropriate security checks.", "cve_priority": "high", "cve_public_date": "2023-07-26 02:15:00 UTC" }, { "cve": "CVE-2023-32629", "url": "https://ubuntu.com/security/CVE-2023-32629", "cve_description": "Local privilege escalation vulnerability in Ubuntu Kernels overlayfs ovl_copy_up_meta_inode_data skip permission checks when calling ovl_do_setxattr on Ubuntu kernels", "cve_priority": "high", "cve_public_date": "2023-07-26 02:15:00 UTC" }, { "cve": "CVE-2026-23112", "url": "https://ubuntu.com/security/CVE-2026-23112", "cve_description": "In the Linux kernel, the following vulnerability has been resolved: nvmet-tcp: add bounds checks in nvmet_tcp_build_pdu_iovec nvmet_tcp_build_pdu_iovec() could walk past cmd->req.sg when a PDU length or offset exceeds sg_cnt and then use bogus sg->length/offset values, leading to _copy_to_iter() GPF/KASAN. Guard sg_idx, remaining entries, and sg->length/offset before building the bvec.", "cve_priority": "high", "cve_public_date": "2026-02-13 14:16:00 UTC" } ], "log": [ "", " * jammy/linux-kvm: 5.15.0-1098.103 -proposed tracker (LP: #2147825)", "", " [ Ubuntu: 5.15.0-177.187 ]", "", " * jammy/linux: 5.15.0-177.187 -proposed tracker (LP: #2147840)", " * macvlan: observe an RCU grace period in macvlan_common_newlink() error", " path (LP: #2144380) // CVE-2026-23209", " - macvlan: observe an RCU grace period in macvlan_common_newlink() error", " path", " * CVE-2023-2640 // CVE-2023-32629", " - SAUCE: Revert \"UBUNTU: SAUCE: overlayfs: Skip permission checking for", " trusted.overlayfs.* xattrs\"", " - SAUCE: overlayfs: default to userxattr when mounted from non initial", " user namespace", " * CVE-2026-23112", " - nvmet-tcp: add bounds checks in nvmet_tcp_build_pdu_iovec", "" ], "package": "linux-kvm", "version": "5.15.0-1098.103", "urgency": "medium", "distributions": "jammy", "launchpad_bugs_fixed": [ 2147825, 2147840, 2144380 ], "author": "Austin Rhodes ", "date": "Mon, 20 Apr 2026 16:26:42 -0400" } ], "notes": "linux-kvm-headers-5.15.0-1098 version '5.15.0-1098.103' (source package linux-kvm version '5.15.0-1098.103') was added. linux-kvm-headers-5.15.0-1098 version '5.15.0-1098.103' has the same source package name, linux-kvm, as removed package linux-headers-5.15.0-1097-kvm. As such we can use the source package version of the removed package, '5.15.0-1097.102', as the starting point in our changelog diff. Kernel packages are an example of where the binary package name changes for the same source package. Using the removed package source package version as our starting point means we can still get meaningful changelog diffs even for what appears to be a new package.", "is_version_downgrade": false }, { "name": "linux-modules-5.15.0-1098-kvm", "from_version": { "source_package_name": "linux-kvm", "source_package_version": "5.15.0-1097.102", "version": null }, "to_version": { "source_package_name": "linux-kvm", "source_package_version": "5.15.0-1098.103", "version": "5.15.0-1098.103" }, "cves": [ { "cve": "CVE-2026-23209", "url": "https://ubuntu.com/security/CVE-2026-23209", "cve_description": "In the Linux kernel, the following vulnerability has been resolved: macvlan: fix error recovery in macvlan_common_newlink() valis provided a nice repro to crash the kernel: 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 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 ping -c1 -I p1 1.2.3.4 He also gave a very detailed analysis: 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). In this case macvlan_hash_add_source is called from macvlan_change_sources() / macvlan_common_newlink(): This adds a reference to vlan to the port's vlan_source_hash using macvlan_source_entry. vlan is a pointer to the priv data of the link that is being created. When register_netdevice() fails, the error is returned from macvlan_newlink() to rtnl_newlink_create(): if (ops->newlink) err = ops->newlink(dev, ¶ms, extack); else err = register_netdevice(dev); if (err < 0) { free_netdev(dev); goto out; } and free_netdev() is called, causing a kvfree() on the struct net_device that is still referenced in the source entry attached to the lower device's macvlan port. Now all packets sent on the macvlan port with a matching source mac address will trigger a use-after-free in macvlan_forward_source(). With all that, my fix is to make sure we call macvlan_flush_sources() regardless of @create value whenever \"goto destroy_macvlan_port;\" path is taken. Many thanks to valis for following up on this issue.", "cve_priority": "medium", "cve_public_date": "2026-02-14 17:15:00 UTC" }, { "cve": "CVE-2023-2640", "url": "https://ubuntu.com/security/CVE-2023-2640", "cve_description": "On Ubuntu kernels carrying both c914c0e27eb0 and \"UBUNTU: SAUCE: overlayfs: Skip permission checking for trusted.overlayfs.* xattrs\", an unprivileged user may set privileged extended attributes on the mounted files, leading them to be set on the upper files without the appropriate security checks.", "cve_priority": "high", "cve_public_date": "2023-07-26 02:15:00 UTC" }, { "cve": "CVE-2023-32629", "url": "https://ubuntu.com/security/CVE-2023-32629", "cve_description": "Local privilege escalation vulnerability in Ubuntu Kernels overlayfs ovl_copy_up_meta_inode_data skip permission checks when calling ovl_do_setxattr on Ubuntu kernels", "cve_priority": "high", "cve_public_date": "2023-07-26 02:15:00 UTC" }, { "cve": "CVE-2026-23112", "url": "https://ubuntu.com/security/CVE-2026-23112", "cve_description": "In the Linux kernel, the following vulnerability has been resolved: nvmet-tcp: add bounds checks in nvmet_tcp_build_pdu_iovec nvmet_tcp_build_pdu_iovec() could walk past cmd->req.sg when a PDU length or offset exceeds sg_cnt and then use bogus sg->length/offset values, leading to _copy_to_iter() GPF/KASAN. Guard sg_idx, remaining entries, and sg->length/offset before building the bvec.", "cve_priority": "high", "cve_public_date": "2026-02-13 14:16:00 UTC" } ], "launchpad_bugs_fixed": [ 2147825, 2147840, 2144380 ], "changes": [ { "cves": [ { "cve": "CVE-2026-23209", "url": "https://ubuntu.com/security/CVE-2026-23209", "cve_description": "In the Linux kernel, the following vulnerability has been resolved: macvlan: fix error recovery in macvlan_common_newlink() valis provided a nice repro to crash the kernel: 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 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 ping -c1 -I p1 1.2.3.4 He also gave a very detailed analysis: 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). In this case macvlan_hash_add_source is called from macvlan_change_sources() / macvlan_common_newlink(): This adds a reference to vlan to the port's vlan_source_hash using macvlan_source_entry. vlan is a pointer to the priv data of the link that is being created. When register_netdevice() fails, the error is returned from macvlan_newlink() to rtnl_newlink_create(): if (ops->newlink) err = ops->newlink(dev, ¶ms, extack); else err = register_netdevice(dev); if (err < 0) { free_netdev(dev); goto out; } and free_netdev() is called, causing a kvfree() on the struct net_device that is still referenced in the source entry attached to the lower device's macvlan port. Now all packets sent on the macvlan port with a matching source mac address will trigger a use-after-free in macvlan_forward_source(). With all that, my fix is to make sure we call macvlan_flush_sources() regardless of @create value whenever \"goto destroy_macvlan_port;\" path is taken. Many thanks to valis for following up on this issue.", "cve_priority": "medium", "cve_public_date": "2026-02-14 17:15:00 UTC" }, { "cve": "CVE-2023-2640", "url": "https://ubuntu.com/security/CVE-2023-2640", "cve_description": "On Ubuntu kernels carrying both c914c0e27eb0 and \"UBUNTU: SAUCE: overlayfs: Skip permission checking for trusted.overlayfs.* xattrs\", an unprivileged user may set privileged extended attributes on the mounted files, leading them to be set on the upper files without the appropriate security checks.", "cve_priority": "high", "cve_public_date": "2023-07-26 02:15:00 UTC" }, { "cve": "CVE-2023-32629", "url": "https://ubuntu.com/security/CVE-2023-32629", "cve_description": "Local privilege escalation vulnerability in Ubuntu Kernels overlayfs ovl_copy_up_meta_inode_data skip permission checks when calling ovl_do_setxattr on Ubuntu kernels", "cve_priority": "high", "cve_public_date": "2023-07-26 02:15:00 UTC" }, { "cve": "CVE-2026-23112", "url": "https://ubuntu.com/security/CVE-2026-23112", "cve_description": "In the Linux kernel, the following vulnerability has been resolved: nvmet-tcp: add bounds checks in nvmet_tcp_build_pdu_iovec nvmet_tcp_build_pdu_iovec() could walk past cmd->req.sg when a PDU length or offset exceeds sg_cnt and then use bogus sg->length/offset values, leading to _copy_to_iter() GPF/KASAN. Guard sg_idx, remaining entries, and sg->length/offset before building the bvec.", "cve_priority": "high", "cve_public_date": "2026-02-13 14:16:00 UTC" } ], "log": [ "", " * jammy/linux-kvm: 5.15.0-1098.103 -proposed tracker (LP: #2147825)", "", " [ Ubuntu: 5.15.0-177.187 ]", "", " * jammy/linux: 5.15.0-177.187 -proposed tracker (LP: #2147840)", " * macvlan: observe an RCU grace period in macvlan_common_newlink() error", " path (LP: #2144380) // CVE-2026-23209", " - macvlan: observe an RCU grace period in macvlan_common_newlink() error", " path", " * CVE-2023-2640 // CVE-2023-32629", " - SAUCE: Revert \"UBUNTU: SAUCE: overlayfs: Skip permission checking for", " trusted.overlayfs.* xattrs\"", " - SAUCE: overlayfs: default to userxattr when mounted from non initial", " user namespace", " * CVE-2026-23112", " - nvmet-tcp: add bounds checks in nvmet_tcp_build_pdu_iovec", "" ], "package": "linux-kvm", "version": "5.15.0-1098.103", "urgency": "medium", "distributions": "jammy", "launchpad_bugs_fixed": [ 2147825, 2147840, 2144380 ], "author": "Austin Rhodes ", "date": "Mon, 20 Apr 2026 16:26:42 -0400" } ], "notes": "linux-modules-5.15.0-1098-kvm version '5.15.0-1098.103' (source package linux-kvm version '5.15.0-1098.103') was added. linux-modules-5.15.0-1098-kvm version '5.15.0-1098.103' has the same source package name, linux-kvm, as removed package linux-headers-5.15.0-1097-kvm. As such we can use the source package version of the removed package, '5.15.0-1097.102', as the starting point in our changelog diff. Kernel packages are an example of where the binary package name changes for the same source package. Using the removed package source package version as our starting point means we can still get meaningful changelog diffs even for what appears to be a new package.", "is_version_downgrade": false } ], "snap": [] }, "removed": { "deb": [ { "name": "linux-headers-5.15.0-1097-kvm", "from_version": { "source_package_name": "linux-kvm", "source_package_version": "5.15.0-1097.102", "version": "5.15.0-1097.102" }, "to_version": { "source_package_name": null, "source_package_version": null, "version": null }, "cves": [], "launchpad_bugs_fixed": [], "changes": [], "notes": null, "is_version_downgrade": false }, { "name": "linux-image-5.15.0-1097-kvm", "from_version": { "source_package_name": "linux-signed-kvm", "source_package_version": "5.15.0-1097.102", "version": "5.15.0-1097.102" }, "to_version": { "source_package_name": null, "source_package_version": null, "version": null }, "cves": [], "launchpad_bugs_fixed": [], "changes": [], "notes": null, "is_version_downgrade": false }, { "name": "linux-kvm-headers-5.15.0-1097", "from_version": { "source_package_name": "linux-kvm", "source_package_version": "5.15.0-1097.102", "version": "5.15.0-1097.102" }, "to_version": { "source_package_name": null, "source_package_version": null, "version": null }, "cves": [], "launchpad_bugs_fixed": [], "changes": [], "notes": null, "is_version_downgrade": false }, { "name": "linux-modules-5.15.0-1097-kvm", "from_version": { "source_package_name": "linux-kvm", "source_package_version": "5.15.0-1097.102", "version": "5.15.0-1097.102" }, "to_version": { "source_package_name": null, "source_package_version": null, "version": null }, "cves": [], "launchpad_bugs_fixed": [], "changes": [], "notes": null, "is_version_downgrade": false } ], "snap": [] }, "notes": "Changelog diff for Ubuntu 22.04 jammy image from daily image serial 20260429 to 20260430", "from_series": "jammy", "to_series": "jammy", "from_serial": "20260429", "to_serial": "20260430", "from_manifest_filename": "daily_manifest.previous", "to_manifest_filename": "manifest.current" }