{ "summary": { "snap": { "added": [], "removed": [], "diff": [] }, "deb": { "added": [ "linux-headers-6.8.0-36", "linux-headers-6.8.0-36-generic", "linux-image-6.8.0-36-generic", "linux-modules-6.8.0-36-generic", "linux-tools-6.8.0-36", "linux-tools-6.8.0-36-generic" ], "removed": [ "linux-headers-6.8.0-35", "linux-headers-6.8.0-35-generic", "linux-image-6.8.0-35-generic", "linux-modules-6.8.0-35-generic", "linux-tools-6.8.0-35", "linux-tools-6.8.0-35-generic" ], "diff": [ "dracut-install", "libnetplan1:armhf", "linux-headers-generic", "linux-headers-virtual", "linux-image-virtual", "linux-libc-dev:armhf", "linux-tools-common", "linux-virtual", "netplan-generator", "netplan.io", "python3-distupgrade", "python3-netplan", "ubuntu-release-upgrader-core", "wget" ] } }, "diff": { "deb": [ { "name": "dracut-install", "from_version": { "source_package_name": "dracut", "source_package_version": "060+5-1ubuntu3", "version": "060+5-1ubuntu3" }, "to_version": { "source_package_name": "dracut", "source_package_version": "060+5-1ubuntu3.1", "version": "060+5-1ubuntu3.1" }, "cves": [], "launchpad_bugs_fixed": [ 2065180 ], "changes": [ { "cves": [], "log": [ "", " * perf(dracut-install): preload kmod resources for quicker module lookup", " (LP: #2065180)", "" ], "package": "dracut", "version": "060+5-1ubuntu3.1", "urgency": "medium", "distributions": "noble", "launchpad_bugs_fixed": [ 2065180 ], "author": "Benjamin Drung ", "date": "Tue, 04 Jun 2024 17:21:56 +0200" } ], "notes": null }, { "name": "libnetplan1:armhf", "from_version": { "source_package_name": "netplan.io", "source_package_version": "1.0-2ubuntu1", "version": "1.0-2ubuntu1" }, "to_version": { "source_package_name": "netplan.io", "source_package_version": "1.0-2ubuntu1.1", "version": "1.0-2ubuntu1.1" }, "cves": [ { "cve": "CVE-2022-4968", "url": "https://ubuntu.com/security/CVE-2022-4968", "cve_description": "netplan leaks the private key of wireguard to local users. A security fix will be released soon.", "cve_priority": "medium", "cve_public_date": "2024-06-07 01:15:00 UTC" } ], "launchpad_bugs_fixed": [ 2065738, 1987842, 2066258 ], "changes": [ { "cves": [ { "cve": "CVE-2022-4968", "url": "https://ubuntu.com/security/CVE-2022-4968", "cve_description": "netplan leaks the private key of wireguard to local users. A security fix will be released soon.", "cve_priority": "medium", "cve_public_date": "2024-06-07 01:15:00 UTC" } ], "log": [ "", " * SECURITY UPDATE: weak permissions on secret files, command injection", " - d/p/lp2065738/0014-libnetplan-use-more-restrictive-file-permissions.patch:", " Use more restrictive file permissions to prevent unprivileged users to", " read sensitive data from back end files (LP: #2065738, #1987842)", " - CVE-2022-4968", " - d/p/lp2066258/0015-libnetplan-escape-control-characters.patch:", " Escape control characters in the parser and double quotes in backend", " files.", " - d/p/lp2066258/0016-backends-escape-file-paths.patch:", " Escape special characters in file paths.", " - d/p/lp2066258/0017-backends-escape-semicolons-in-service-units.patch:", " Escape isolated semicolons in systemd service units. (LP: #2066258)", " * debian/netplan-generator.postinst: Add a postinst maintainer script to call", " the generator. It's needed so the file permissions fixes will be applied", " automatically, thanks to danilogondolfo ", "" ], "package": "netplan.io", "version": "1.0-2ubuntu1.1", "urgency": "medium", "distributions": "noble-security", "launchpad_bugs_fixed": [ 2065738, 1987842, 2066258 ], "author": "Sudhakar Verma ", "date": "Tue, 25 Jun 2024 00:13:00 +0530" } ], "notes": null }, { "name": "linux-headers-generic", "from_version": { "source_package_name": "linux-meta", "source_package_version": "6.8.0-35.35", "version": "6.8.0-35.35" }, "to_version": { "source_package_name": "linux-meta", "source_package_version": "6.8.0-36.36", "version": "6.8.0-36.36" }, "cves": [], "launchpad_bugs_fixed": [], "changes": [ { "cves": [], "log": [ "", " * Main version: 6.8.0-36.36", "" ], "package": "linux-meta", "version": "6.8.0-36.36", "urgency": "medium", "distributions": "noble", "launchpad_bugs_fixed": [], "author": "Roxana Nicolescu ", "date": "Mon, 10 Jun 2024 11:29:30 +0200" } ], "notes": null }, { "name": "linux-headers-virtual", "from_version": { "source_package_name": "linux-meta", "source_package_version": "6.8.0-35.35", "version": "6.8.0-35.35" }, "to_version": { "source_package_name": "linux-meta", "source_package_version": "6.8.0-36.36", "version": "6.8.0-36.36" }, "cves": [], "launchpad_bugs_fixed": [], "changes": [ { "cves": [], "log": [ "", " * Main version: 6.8.0-36.36", "" ], "package": "linux-meta", "version": "6.8.0-36.36", "urgency": "medium", "distributions": "noble", "launchpad_bugs_fixed": [], "author": "Roxana Nicolescu ", "date": "Mon, 10 Jun 2024 11:29:30 +0200" } ], "notes": null }, { "name": "linux-image-virtual", "from_version": { "source_package_name": "linux-meta", "source_package_version": "6.8.0-35.35", "version": "6.8.0-35.35" }, "to_version": { "source_package_name": "linux-meta", "source_package_version": "6.8.0-36.36", "version": "6.8.0-36.36" }, "cves": [], "launchpad_bugs_fixed": [], "changes": [ { "cves": [], "log": [ "", " * Main version: 6.8.0-36.36", "" ], "package": "linux-meta", "version": "6.8.0-36.36", "urgency": "medium", "distributions": "noble", "launchpad_bugs_fixed": [], "author": "Roxana Nicolescu ", "date": "Mon, 10 Jun 2024 11:29:30 +0200" } ], "notes": null }, { "name": "linux-libc-dev:armhf", "from_version": { "source_package_name": "linux", "source_package_version": "6.8.0-35.35", "version": "6.8.0-35.35" }, "to_version": { "source_package_name": "linux", "source_package_version": "6.8.0-36.36", "version": "6.8.0-36.36" }, "cves": [ { "cve": "CVE-2024-26924", "url": "https://ubuntu.com/security/CVE-2024-26924", "cve_description": "In the Linux kernel, the following vulnerability has been resolved: netfilter: nft_set_pipapo: do not free live element Pablo reports a crash with large batches of elements with a back-to-back add/remove pattern. Quoting Pablo: add_elem(\"00000000\") timeout 100 ms ... add_elem(\"0000000X\") timeout 100 ms del_elem(\"0000000X\") <---------------- delete one that was just added ... add_elem(\"00005000\") timeout 100 ms 1) nft_pipapo_remove() removes element 0000000X Then, KASAN shows a splat. Looking at the remove function there is a chance that we will drop a rule that maps to a non-deactivated element. Removal happens in two steps, first we do a lookup for key k and return the to-be-removed element and mark it as inactive in the next generation. Then, in a second step, the element gets removed from the set/map. The _remove function does not work correctly if we have more than one element that share the same key. This can happen if we insert an element into a set when the set already holds an element with same key, but the element mapping to the existing key has timed out or is not active in the next generation. In such case its possible that removal will unmap the wrong element. If this happens, we will leak the non-deactivated element, it becomes unreachable. The element that got deactivated (and will be freed later) will remain reachable in the set data structure, this can result in a crash when such an element is retrieved during lookup (stale pointer). Add a check that the fully matching key does in fact map to the element that we have marked as inactive in the deactivation step. If not, we need to continue searching. Add a bug/warn trap at the end of the function as well, the remove function must not ever be called with an invisible/unreachable/non-existent element. v2: avoid uneeded temporary variable (Stefano)", "cve_priority": "high", "cve_public_date": "2024-04-25 06:15:00 UTC" } ], "launchpad_bugs_fixed": [ 2068150 ], "changes": [ { "cves": [ { "cve": "CVE-2024-26924", "url": "https://ubuntu.com/security/CVE-2024-26924", "cve_description": "In the Linux kernel, the following vulnerability has been resolved: netfilter: nft_set_pipapo: do not free live element Pablo reports a crash with large batches of elements with a back-to-back add/remove pattern. Quoting Pablo: add_elem(\"00000000\") timeout 100 ms ... add_elem(\"0000000X\") timeout 100 ms del_elem(\"0000000X\") <---------------- delete one that was just added ... add_elem(\"00005000\") timeout 100 ms 1) nft_pipapo_remove() removes element 0000000X Then, KASAN shows a splat. Looking at the remove function there is a chance that we will drop a rule that maps to a non-deactivated element. Removal happens in two steps, first we do a lookup for key k and return the to-be-removed element and mark it as inactive in the next generation. Then, in a second step, the element gets removed from the set/map. The _remove function does not work correctly if we have more than one element that share the same key. This can happen if we insert an element into a set when the set already holds an element with same key, but the element mapping to the existing key has timed out or is not active in the next generation. In such case its possible that removal will unmap the wrong element. If this happens, we will leak the non-deactivated element, it becomes unreachable. The element that got deactivated (and will be freed later) will remain reachable in the set data structure, this can result in a crash when such an element is retrieved during lookup (stale pointer). Add a check that the fully matching key does in fact map to the element that we have marked as inactive in the deactivation step. If not, we need to continue searching. Add a bug/warn trap at the end of the function as well, the remove function must not ever be called with an invisible/unreachable/non-existent element. v2: avoid uneeded temporary variable (Stefano)", "cve_priority": "high", "cve_public_date": "2024-04-25 06:15:00 UTC" } ], "log": [ "", " * noble/linux: 6.8.0-36.36 -proposed tracker (LP: #2068150)", "", " * CVE-2024-26924", " - netfilter: nft_set_pipapo: do not free live element", "" ], "package": "linux", "version": "6.8.0-36.36", "urgency": "medium", "distributions": "noble", "launchpad_bugs_fixed": [ 2068150 ], "author": "Roxana Nicolescu ", "date": "Mon, 10 Jun 2024 11:26:41 +0200" } ], "notes": null }, { "name": "linux-tools-common", "from_version": { "source_package_name": "linux", "source_package_version": "6.8.0-35.35", "version": "6.8.0-35.35" }, "to_version": { "source_package_name": "linux", "source_package_version": "6.8.0-36.36", "version": "6.8.0-36.36" }, "cves": [ { "cve": "CVE-2024-26924", "url": "https://ubuntu.com/security/CVE-2024-26924", "cve_description": "In the Linux kernel, the following vulnerability has been resolved: netfilter: nft_set_pipapo: do not free live element Pablo reports a crash with large batches of elements with a back-to-back add/remove pattern. Quoting Pablo: add_elem(\"00000000\") timeout 100 ms ... add_elem(\"0000000X\") timeout 100 ms del_elem(\"0000000X\") <---------------- delete one that was just added ... add_elem(\"00005000\") timeout 100 ms 1) nft_pipapo_remove() removes element 0000000X Then, KASAN shows a splat. Looking at the remove function there is a chance that we will drop a rule that maps to a non-deactivated element. Removal happens in two steps, first we do a lookup for key k and return the to-be-removed element and mark it as inactive in the next generation. Then, in a second step, the element gets removed from the set/map. The _remove function does not work correctly if we have more than one element that share the same key. This can happen if we insert an element into a set when the set already holds an element with same key, but the element mapping to the existing key has timed out or is not active in the next generation. In such case its possible that removal will unmap the wrong element. If this happens, we will leak the non-deactivated element, it becomes unreachable. The element that got deactivated (and will be freed later) will remain reachable in the set data structure, this can result in a crash when such an element is retrieved during lookup (stale pointer). Add a check that the fully matching key does in fact map to the element that we have marked as inactive in the deactivation step. If not, we need to continue searching. Add a bug/warn trap at the end of the function as well, the remove function must not ever be called with an invisible/unreachable/non-existent element. v2: avoid uneeded temporary variable (Stefano)", "cve_priority": "high", "cve_public_date": "2024-04-25 06:15:00 UTC" } ], "launchpad_bugs_fixed": [ 2068150 ], "changes": [ { "cves": [ { "cve": "CVE-2024-26924", "url": "https://ubuntu.com/security/CVE-2024-26924", "cve_description": "In the Linux kernel, the following vulnerability has been resolved: netfilter: nft_set_pipapo: do not free live element Pablo reports a crash with large batches of elements with a back-to-back add/remove pattern. Quoting Pablo: add_elem(\"00000000\") timeout 100 ms ... add_elem(\"0000000X\") timeout 100 ms del_elem(\"0000000X\") <---------------- delete one that was just added ... add_elem(\"00005000\") timeout 100 ms 1) nft_pipapo_remove() removes element 0000000X Then, KASAN shows a splat. Looking at the remove function there is a chance that we will drop a rule that maps to a non-deactivated element. Removal happens in two steps, first we do a lookup for key k and return the to-be-removed element and mark it as inactive in the next generation. Then, in a second step, the element gets removed from the set/map. The _remove function does not work correctly if we have more than one element that share the same key. This can happen if we insert an element into a set when the set already holds an element with same key, but the element mapping to the existing key has timed out or is not active in the next generation. In such case its possible that removal will unmap the wrong element. If this happens, we will leak the non-deactivated element, it becomes unreachable. The element that got deactivated (and will be freed later) will remain reachable in the set data structure, this can result in a crash when such an element is retrieved during lookup (stale pointer). Add a check that the fully matching key does in fact map to the element that we have marked as inactive in the deactivation step. If not, we need to continue searching. Add a bug/warn trap at the end of the function as well, the remove function must not ever be called with an invisible/unreachable/non-existent element. v2: avoid uneeded temporary variable (Stefano)", "cve_priority": "high", "cve_public_date": "2024-04-25 06:15:00 UTC" } ], "log": [ "", " * noble/linux: 6.8.0-36.36 -proposed tracker (LP: #2068150)", "", " * CVE-2024-26924", " - netfilter: nft_set_pipapo: do not free live element", "" ], "package": "linux", "version": "6.8.0-36.36", "urgency": "medium", "distributions": "noble", "launchpad_bugs_fixed": [ 2068150 ], "author": "Roxana Nicolescu ", "date": "Mon, 10 Jun 2024 11:26:41 +0200" } ], "notes": null }, { "name": "linux-virtual", "from_version": { "source_package_name": "linux-meta", "source_package_version": "6.8.0-35.35", "version": "6.8.0-35.35" }, "to_version": { "source_package_name": "linux-meta", "source_package_version": "6.8.0-36.36", "version": "6.8.0-36.36" }, "cves": [], "launchpad_bugs_fixed": [], "changes": [ { "cves": [], "log": [ "", " * Main version: 6.8.0-36.36", "" ], "package": "linux-meta", "version": "6.8.0-36.36", "urgency": "medium", "distributions": "noble", "launchpad_bugs_fixed": [], "author": "Roxana Nicolescu ", "date": "Mon, 10 Jun 2024 11:29:30 +0200" } ], "notes": null }, { "name": "netplan-generator", "from_version": { "source_package_name": "netplan.io", "source_package_version": "1.0-2ubuntu1", "version": "1.0-2ubuntu1" }, "to_version": { "source_package_name": "netplan.io", "source_package_version": "1.0-2ubuntu1.1", "version": "1.0-2ubuntu1.1" }, "cves": [ { "cve": "CVE-2022-4968", "url": "https://ubuntu.com/security/CVE-2022-4968", "cve_description": "netplan leaks the private key of wireguard to local users. A security fix will be released soon.", "cve_priority": "medium", "cve_public_date": "2024-06-07 01:15:00 UTC" } ], "launchpad_bugs_fixed": [ 2065738, 1987842, 2066258 ], "changes": [ { "cves": [ { "cve": "CVE-2022-4968", "url": "https://ubuntu.com/security/CVE-2022-4968", "cve_description": "netplan leaks the private key of wireguard to local users. A security fix will be released soon.", "cve_priority": "medium", "cve_public_date": "2024-06-07 01:15:00 UTC" } ], "log": [ "", " * SECURITY UPDATE: weak permissions on secret files, command injection", " - d/p/lp2065738/0014-libnetplan-use-more-restrictive-file-permissions.patch:", " Use more restrictive file permissions to prevent unprivileged users to", " read sensitive data from back end files (LP: #2065738, #1987842)", " - CVE-2022-4968", " - d/p/lp2066258/0015-libnetplan-escape-control-characters.patch:", " Escape control characters in the parser and double quotes in backend", " files.", " - d/p/lp2066258/0016-backends-escape-file-paths.patch:", " Escape special characters in file paths.", " - d/p/lp2066258/0017-backends-escape-semicolons-in-service-units.patch:", " Escape isolated semicolons in systemd service units. (LP: #2066258)", " * debian/netplan-generator.postinst: Add a postinst maintainer script to call", " the generator. It's needed so the file permissions fixes will be applied", " automatically, thanks to danilogondolfo ", "" ], "package": "netplan.io", "version": "1.0-2ubuntu1.1", "urgency": "medium", "distributions": "noble-security", "launchpad_bugs_fixed": [ 2065738, 1987842, 2066258 ], "author": "Sudhakar Verma ", "date": "Tue, 25 Jun 2024 00:13:00 +0530" } ], "notes": null }, { "name": "netplan.io", "from_version": { "source_package_name": "netplan.io", "source_package_version": "1.0-2ubuntu1", "version": "1.0-2ubuntu1" }, "to_version": { "source_package_name": "netplan.io", "source_package_version": "1.0-2ubuntu1.1", "version": "1.0-2ubuntu1.1" }, "cves": [ { "cve": "CVE-2022-4968", "url": "https://ubuntu.com/security/CVE-2022-4968", "cve_description": "netplan leaks the private key of wireguard to local users. A security fix will be released soon.", "cve_priority": "medium", "cve_public_date": "2024-06-07 01:15:00 UTC" } ], "launchpad_bugs_fixed": [ 2065738, 1987842, 2066258 ], "changes": [ { "cves": [ { "cve": "CVE-2022-4968", "url": "https://ubuntu.com/security/CVE-2022-4968", "cve_description": "netplan leaks the private key of wireguard to local users. A security fix will be released soon.", "cve_priority": "medium", "cve_public_date": "2024-06-07 01:15:00 UTC" } ], "log": [ "", " * SECURITY UPDATE: weak permissions on secret files, command injection", " - d/p/lp2065738/0014-libnetplan-use-more-restrictive-file-permissions.patch:", " Use more restrictive file permissions to prevent unprivileged users to", " read sensitive data from back end files (LP: #2065738, #1987842)", " - CVE-2022-4968", " - d/p/lp2066258/0015-libnetplan-escape-control-characters.patch:", " Escape control characters in the parser and double quotes in backend", " files.", " - d/p/lp2066258/0016-backends-escape-file-paths.patch:", " Escape special characters in file paths.", " - d/p/lp2066258/0017-backends-escape-semicolons-in-service-units.patch:", " Escape isolated semicolons in systemd service units. (LP: #2066258)", " * debian/netplan-generator.postinst: Add a postinst maintainer script to call", " the generator. It's needed so the file permissions fixes will be applied", " automatically, thanks to danilogondolfo ", "" ], "package": "netplan.io", "version": "1.0-2ubuntu1.1", "urgency": "medium", "distributions": "noble-security", "launchpad_bugs_fixed": [ 2065738, 1987842, 2066258 ], "author": "Sudhakar Verma ", "date": "Tue, 25 Jun 2024 00:13:00 +0530" } ], "notes": null }, { "name": "python3-distupgrade", "from_version": { "source_package_name": "ubuntu-release-upgrader", "source_package_version": "1:24.04.18", "version": "1:24.04.18" }, "to_version": { "source_package_name": "ubuntu-release-upgrader", "source_package_version": "1:24.04.19", "version": "1:24.04.19" }, "cves": [], "launchpad_bugs_fixed": [ 2067886, 2067071, 2067585 ], "changes": [ { "cves": [], "log": [ "", " * DistUpgrade: drop quirk for systems with BIOS and XFS /boot (LP: #2067886)", " * DistUpgradeQuirks: make sure replacement.candidate is not None", " (LP: #2067071)", " * DistUpgrade: use tempfile for apt extended_states during simulation", " (LP: #2067585)", " * Run pre-build.sh: updating mirrors, demotions, and translations.", "" ], "package": "ubuntu-release-upgrader", "version": "1:24.04.19", "urgency": "medium", "distributions": "noble", "launchpad_bugs_fixed": [ 2067886, 2067071, 2067585 ], "author": "Nick Rosbrook ", "date": "Tue, 04 Jun 2024 11:55:51 -0400" } ], "notes": null }, { "name": "python3-netplan", "from_version": { "source_package_name": "netplan.io", "source_package_version": "1.0-2ubuntu1", "version": "1.0-2ubuntu1" }, "to_version": { "source_package_name": "netplan.io", "source_package_version": "1.0-2ubuntu1.1", "version": "1.0-2ubuntu1.1" }, "cves": [ { "cve": "CVE-2022-4968", "url": "https://ubuntu.com/security/CVE-2022-4968", "cve_description": "netplan leaks the private key of wireguard to local users. A security fix will be released soon.", "cve_priority": "medium", "cve_public_date": "2024-06-07 01:15:00 UTC" } ], "launchpad_bugs_fixed": [ 2065738, 1987842, 2066258 ], "changes": [ { "cves": [ { "cve": "CVE-2022-4968", "url": "https://ubuntu.com/security/CVE-2022-4968", "cve_description": "netplan leaks the private key of wireguard to local users. A security fix will be released soon.", "cve_priority": "medium", "cve_public_date": "2024-06-07 01:15:00 UTC" } ], "log": [ "", " * SECURITY UPDATE: weak permissions on secret files, command injection", " - d/p/lp2065738/0014-libnetplan-use-more-restrictive-file-permissions.patch:", " Use more restrictive file permissions to prevent unprivileged users to", " read sensitive data from back end files (LP: #2065738, #1987842)", " - CVE-2022-4968", " - d/p/lp2066258/0015-libnetplan-escape-control-characters.patch:", " Escape control characters in the parser and double quotes in backend", " files.", " - d/p/lp2066258/0016-backends-escape-file-paths.patch:", " Escape special characters in file paths.", " - d/p/lp2066258/0017-backends-escape-semicolons-in-service-units.patch:", " Escape isolated semicolons in systemd service units. (LP: #2066258)", " * debian/netplan-generator.postinst: Add a postinst maintainer script to call", " the generator. It's needed so the file permissions fixes will be applied", " automatically, thanks to danilogondolfo ", "" ], "package": "netplan.io", "version": "1.0-2ubuntu1.1", "urgency": "medium", "distributions": "noble-security", "launchpad_bugs_fixed": [ 2065738, 1987842, 2066258 ], "author": "Sudhakar Verma ", "date": "Tue, 25 Jun 2024 00:13:00 +0530" } ], "notes": null }, { "name": "ubuntu-release-upgrader-core", "from_version": { "source_package_name": "ubuntu-release-upgrader", "source_package_version": "1:24.04.18", "version": "1:24.04.18" }, "to_version": { "source_package_name": "ubuntu-release-upgrader", "source_package_version": "1:24.04.19", "version": "1:24.04.19" }, "cves": [], "launchpad_bugs_fixed": [ 2067886, 2067071, 2067585 ], "changes": [ { "cves": [], "log": [ "", " * DistUpgrade: drop quirk for systems with BIOS and XFS /boot (LP: #2067886)", " * DistUpgradeQuirks: make sure replacement.candidate is not None", " (LP: #2067071)", " * DistUpgrade: use tempfile for apt extended_states during simulation", " (LP: #2067585)", " * Run pre-build.sh: updating mirrors, demotions, and translations.", "" ], "package": "ubuntu-release-upgrader", "version": "1:24.04.19", "urgency": "medium", "distributions": "noble", "launchpad_bugs_fixed": [ 2067886, 2067071, 2067585 ], "author": "Nick Rosbrook ", "date": "Tue, 04 Jun 2024 11:55:51 -0400" } ], "notes": null }, { "name": "wget", "from_version": { "source_package_name": "wget", "source_package_version": "1.21.4-1ubuntu4", "version": "1.21.4-1ubuntu4" }, "to_version": { "source_package_name": "wget", "source_package_version": "1.21.4-1ubuntu4.1", "version": "1.21.4-1ubuntu4.1" }, "cves": [ { "cve": "CVE-2024-38428", "url": "https://ubuntu.com/security/CVE-2024-38428", "cve_description": "url.c in GNU Wget through 1.24.5 mishandles semicolons in the userinfo subcomponent of a URI, and thus there may be insecure behavior in which data that was supposed to be in the userinfo subcomponent is misinterpreted to be part of the host subcomponent.", "cve_priority": "medium", "cve_public_date": "2024-06-16 03:15:00 UTC" } ], "launchpad_bugs_fixed": [], "changes": [ { "cves": [ { "cve": "CVE-2024-38428", "url": "https://ubuntu.com/security/CVE-2024-38428", "cve_description": "url.c in GNU Wget through 1.24.5 mishandles semicolons in the userinfo subcomponent of a URI, and thus there may be insecure behavior in which data that was supposed to be in the userinfo subcomponent is misinterpreted to be part of the host subcomponent.", "cve_priority": "medium", "cve_public_date": "2024-06-16 03:15:00 UTC" } ], "log": [ "", " * SECURITY UPDATE: mishandling of semicolons in userinfo", " - debian/patches/CVE-2024-38428.patch: properly re-implement userinfo", " parsing in src/url.c.", " - CVE-2024-38428", "" ], "package": "wget", "version": "1.21.4-1ubuntu4.1", "urgency": "medium", "distributions": "noble-security", "launchpad_bugs_fixed": [], "author": "Marc Deslauriers ", "date": "Wed, 19 Jun 2024 08:14:03 -0400" } ], "notes": null } ], "snap": [] }, "added": { "deb": [ { "name": "linux-headers-6.8.0-36", "from_version": { "source_package_name": "linux", "source_package_version": "6.8.0-35.35", "version": null }, "to_version": { "source_package_name": "linux", "source_package_version": "6.8.0-36.36", "version": "6.8.0-36.36" }, "cves": [ { "cve": "CVE-2024-26924", "url": "https://ubuntu.com/security/CVE-2024-26924", "cve_description": "In the Linux kernel, the following vulnerability has been resolved: netfilter: nft_set_pipapo: do not free live element Pablo reports a crash with large batches of elements with a back-to-back add/remove pattern. Quoting Pablo: add_elem(\"00000000\") timeout 100 ms ... add_elem(\"0000000X\") timeout 100 ms del_elem(\"0000000X\") <---------------- delete one that was just added ... add_elem(\"00005000\") timeout 100 ms 1) nft_pipapo_remove() removes element 0000000X Then, KASAN shows a splat. Looking at the remove function there is a chance that we will drop a rule that maps to a non-deactivated element. Removal happens in two steps, first we do a lookup for key k and return the to-be-removed element and mark it as inactive in the next generation. Then, in a second step, the element gets removed from the set/map. The _remove function does not work correctly if we have more than one element that share the same key. This can happen if we insert an element into a set when the set already holds an element with same key, but the element mapping to the existing key has timed out or is not active in the next generation. In such case its possible that removal will unmap the wrong element. If this happens, we will leak the non-deactivated element, it becomes unreachable. The element that got deactivated (and will be freed later) will remain reachable in the set data structure, this can result in a crash when such an element is retrieved during lookup (stale pointer). Add a check that the fully matching key does in fact map to the element that we have marked as inactive in the deactivation step. If not, we need to continue searching. Add a bug/warn trap at the end of the function as well, the remove function must not ever be called with an invisible/unreachable/non-existent element. v2: avoid uneeded temporary variable (Stefano)", "cve_priority": "high", "cve_public_date": "2024-04-25 06:15:00 UTC" } ], "launchpad_bugs_fixed": [ 2068150 ], "changes": [ { "cves": [ { "cve": "CVE-2024-26924", "url": "https://ubuntu.com/security/CVE-2024-26924", "cve_description": "In the Linux kernel, the following vulnerability has been resolved: netfilter: nft_set_pipapo: do not free live element Pablo reports a crash with large batches of elements with a back-to-back add/remove pattern. Quoting Pablo: add_elem(\"00000000\") timeout 100 ms ... add_elem(\"0000000X\") timeout 100 ms del_elem(\"0000000X\") <---------------- delete one that was just added ... add_elem(\"00005000\") timeout 100 ms 1) nft_pipapo_remove() removes element 0000000X Then, KASAN shows a splat. Looking at the remove function there is a chance that we will drop a rule that maps to a non-deactivated element. Removal happens in two steps, first we do a lookup for key k and return the to-be-removed element and mark it as inactive in the next generation. Then, in a second step, the element gets removed from the set/map. The _remove function does not work correctly if we have more than one element that share the same key. This can happen if we insert an element into a set when the set already holds an element with same key, but the element mapping to the existing key has timed out or is not active in the next generation. In such case its possible that removal will unmap the wrong element. If this happens, we will leak the non-deactivated element, it becomes unreachable. The element that got deactivated (and will be freed later) will remain reachable in the set data structure, this can result in a crash when such an element is retrieved during lookup (stale pointer). Add a check that the fully matching key does in fact map to the element that we have marked as inactive in the deactivation step. If not, we need to continue searching. Add a bug/warn trap at the end of the function as well, the remove function must not ever be called with an invisible/unreachable/non-existent element. v2: avoid uneeded temporary variable (Stefano)", "cve_priority": "high", "cve_public_date": "2024-04-25 06:15:00 UTC" } ], "log": [ "", " * noble/linux: 6.8.0-36.36 -proposed tracker (LP: #2068150)", "", " * CVE-2024-26924", " - netfilter: nft_set_pipapo: do not free live element", "" ], "package": "linux", "version": "6.8.0-36.36", "urgency": "medium", "distributions": "noble", "launchpad_bugs_fixed": [ 2068150 ], "author": "Roxana Nicolescu ", "date": "Mon, 10 Jun 2024 11:26:41 +0200" } ], "notes": "linux-headers-6.8.0-36 version '6.8.0-36.36' (source package linux version '6.8.0-36.36') was added. linux-headers-6.8.0-36 version '6.8.0-36.36' has the same source package name, linux, as removed package linux-headers-6.8.0-35. As such we can use the source package version of the removed package, '6.8.0-35.35', 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." }, { "name": "linux-headers-6.8.0-36-generic", "from_version": { "source_package_name": "linux", "source_package_version": "6.8.0-35.35", "version": null }, "to_version": { "source_package_name": "linux", "source_package_version": "6.8.0-36.36", "version": "6.8.0-36.36" }, "cves": [ { "cve": "CVE-2024-26924", "url": "https://ubuntu.com/security/CVE-2024-26924", "cve_description": "In the Linux kernel, the following vulnerability has been resolved: netfilter: nft_set_pipapo: do not free live element Pablo reports a crash with large batches of elements with a back-to-back add/remove pattern. Quoting Pablo: add_elem(\"00000000\") timeout 100 ms ... add_elem(\"0000000X\") timeout 100 ms del_elem(\"0000000X\") <---------------- delete one that was just added ... add_elem(\"00005000\") timeout 100 ms 1) nft_pipapo_remove() removes element 0000000X Then, KASAN shows a splat. Looking at the remove function there is a chance that we will drop a rule that maps to a non-deactivated element. Removal happens in two steps, first we do a lookup for key k and return the to-be-removed element and mark it as inactive in the next generation. Then, in a second step, the element gets removed from the set/map. The _remove function does not work correctly if we have more than one element that share the same key. This can happen if we insert an element into a set when the set already holds an element with same key, but the element mapping to the existing key has timed out or is not active in the next generation. In such case its possible that removal will unmap the wrong element. If this happens, we will leak the non-deactivated element, it becomes unreachable. The element that got deactivated (and will be freed later) will remain reachable in the set data structure, this can result in a crash when such an element is retrieved during lookup (stale pointer). Add a check that the fully matching key does in fact map to the element that we have marked as inactive in the deactivation step. If not, we need to continue searching. Add a bug/warn trap at the end of the function as well, the remove function must not ever be called with an invisible/unreachable/non-existent element. v2: avoid uneeded temporary variable (Stefano)", "cve_priority": "high", "cve_public_date": "2024-04-25 06:15:00 UTC" } ], "launchpad_bugs_fixed": [ 2068150 ], "changes": [ { "cves": [ { "cve": "CVE-2024-26924", "url": "https://ubuntu.com/security/CVE-2024-26924", "cve_description": "In the Linux kernel, the following vulnerability has been resolved: netfilter: nft_set_pipapo: do not free live element Pablo reports a crash with large batches of elements with a back-to-back add/remove pattern. Quoting Pablo: add_elem(\"00000000\") timeout 100 ms ... add_elem(\"0000000X\") timeout 100 ms del_elem(\"0000000X\") <---------------- delete one that was just added ... add_elem(\"00005000\") timeout 100 ms 1) nft_pipapo_remove() removes element 0000000X Then, KASAN shows a splat. Looking at the remove function there is a chance that we will drop a rule that maps to a non-deactivated element. Removal happens in two steps, first we do a lookup for key k and return the to-be-removed element and mark it as inactive in the next generation. Then, in a second step, the element gets removed from the set/map. The _remove function does not work correctly if we have more than one element that share the same key. This can happen if we insert an element into a set when the set already holds an element with same key, but the element mapping to the existing key has timed out or is not active in the next generation. In such case its possible that removal will unmap the wrong element. If this happens, we will leak the non-deactivated element, it becomes unreachable. The element that got deactivated (and will be freed later) will remain reachable in the set data structure, this can result in a crash when such an element is retrieved during lookup (stale pointer). Add a check that the fully matching key does in fact map to the element that we have marked as inactive in the deactivation step. If not, we need to continue searching. Add a bug/warn trap at the end of the function as well, the remove function must not ever be called with an invisible/unreachable/non-existent element. v2: avoid uneeded temporary variable (Stefano)", "cve_priority": "high", "cve_public_date": "2024-04-25 06:15:00 UTC" } ], "log": [ "", " * noble/linux: 6.8.0-36.36 -proposed tracker (LP: #2068150)", "", " * CVE-2024-26924", " - netfilter: nft_set_pipapo: do not free live element", "" ], "package": "linux", "version": "6.8.0-36.36", "urgency": "medium", "distributions": "noble", "launchpad_bugs_fixed": [ 2068150 ], "author": "Roxana Nicolescu ", "date": "Mon, 10 Jun 2024 11:26:41 +0200" } ], "notes": "linux-headers-6.8.0-36-generic version '6.8.0-36.36' (source package linux version '6.8.0-36.36') was added. linux-headers-6.8.0-36-generic version '6.8.0-36.36' has the same source package name, linux, as removed package linux-headers-6.8.0-35. As such we can use the source package version of the removed package, '6.8.0-35.35', 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." }, { "name": "linux-image-6.8.0-36-generic", "from_version": { "source_package_name": "linux", "source_package_version": "6.8.0-35.35", "version": null }, "to_version": { "source_package_name": "linux", "source_package_version": "6.8.0-36.36", "version": "6.8.0-36.36" }, "cves": [ { "cve": "CVE-2024-26924", "url": "https://ubuntu.com/security/CVE-2024-26924", "cve_description": "In the Linux kernel, the following vulnerability has been resolved: netfilter: nft_set_pipapo: do not free live element Pablo reports a crash with large batches of elements with a back-to-back add/remove pattern. Quoting Pablo: add_elem(\"00000000\") timeout 100 ms ... add_elem(\"0000000X\") timeout 100 ms del_elem(\"0000000X\") <---------------- delete one that was just added ... add_elem(\"00005000\") timeout 100 ms 1) nft_pipapo_remove() removes element 0000000X Then, KASAN shows a splat. Looking at the remove function there is a chance that we will drop a rule that maps to a non-deactivated element. Removal happens in two steps, first we do a lookup for key k and return the to-be-removed element and mark it as inactive in the next generation. Then, in a second step, the element gets removed from the set/map. The _remove function does not work correctly if we have more than one element that share the same key. This can happen if we insert an element into a set when the set already holds an element with same key, but the element mapping to the existing key has timed out or is not active in the next generation. In such case its possible that removal will unmap the wrong element. If this happens, we will leak the non-deactivated element, it becomes unreachable. The element that got deactivated (and will be freed later) will remain reachable in the set data structure, this can result in a crash when such an element is retrieved during lookup (stale pointer). Add a check that the fully matching key does in fact map to the element that we have marked as inactive in the deactivation step. If not, we need to continue searching. Add a bug/warn trap at the end of the function as well, the remove function must not ever be called with an invisible/unreachable/non-existent element. v2: avoid uneeded temporary variable (Stefano)", "cve_priority": "high", "cve_public_date": "2024-04-25 06:15:00 UTC" } ], "launchpad_bugs_fixed": [ 2068150 ], "changes": [ { "cves": [ { "cve": "CVE-2024-26924", "url": "https://ubuntu.com/security/CVE-2024-26924", "cve_description": "In the Linux kernel, the following vulnerability has been resolved: netfilter: nft_set_pipapo: do not free live element Pablo reports a crash with large batches of elements with a back-to-back add/remove pattern. Quoting Pablo: add_elem(\"00000000\") timeout 100 ms ... add_elem(\"0000000X\") timeout 100 ms del_elem(\"0000000X\") <---------------- delete one that was just added ... add_elem(\"00005000\") timeout 100 ms 1) nft_pipapo_remove() removes element 0000000X Then, KASAN shows a splat. Looking at the remove function there is a chance that we will drop a rule that maps to a non-deactivated element. Removal happens in two steps, first we do a lookup for key k and return the to-be-removed element and mark it as inactive in the next generation. Then, in a second step, the element gets removed from the set/map. The _remove function does not work correctly if we have more than one element that share the same key. This can happen if we insert an element into a set when the set already holds an element with same key, but the element mapping to the existing key has timed out or is not active in the next generation. In such case its possible that removal will unmap the wrong element. If this happens, we will leak the non-deactivated element, it becomes unreachable. The element that got deactivated (and will be freed later) will remain reachable in the set data structure, this can result in a crash when such an element is retrieved during lookup (stale pointer). Add a check that the fully matching key does in fact map to the element that we have marked as inactive in the deactivation step. If not, we need to continue searching. Add a bug/warn trap at the end of the function as well, the remove function must not ever be called with an invisible/unreachable/non-existent element. v2: avoid uneeded temporary variable (Stefano)", "cve_priority": "high", "cve_public_date": "2024-04-25 06:15:00 UTC" } ], "log": [ "", " * noble/linux: 6.8.0-36.36 -proposed tracker (LP: #2068150)", "", " * CVE-2024-26924", " - netfilter: nft_set_pipapo: do not free live element", "" ], "package": "linux", "version": "6.8.0-36.36", "urgency": "medium", "distributions": "noble", "launchpad_bugs_fixed": [ 2068150 ], "author": "Roxana Nicolescu ", "date": "Mon, 10 Jun 2024 11:26:41 +0200" } ], "notes": "linux-image-6.8.0-36-generic version '6.8.0-36.36' (source package linux version '6.8.0-36.36') was added. linux-image-6.8.0-36-generic version '6.8.0-36.36' has the same source package name, linux, as removed package linux-headers-6.8.0-35. As such we can use the source package version of the removed package, '6.8.0-35.35', 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." }, { "name": "linux-modules-6.8.0-36-generic", "from_version": { "source_package_name": "linux", "source_package_version": "6.8.0-35.35", "version": null }, "to_version": { "source_package_name": "linux", "source_package_version": "6.8.0-36.36", "version": "6.8.0-36.36" }, "cves": [ { "cve": "CVE-2024-26924", "url": "https://ubuntu.com/security/CVE-2024-26924", "cve_description": "In the Linux kernel, the following vulnerability has been resolved: netfilter: nft_set_pipapo: do not free live element Pablo reports a crash with large batches of elements with a back-to-back add/remove pattern. Quoting Pablo: add_elem(\"00000000\") timeout 100 ms ... add_elem(\"0000000X\") timeout 100 ms del_elem(\"0000000X\") <---------------- delete one that was just added ... add_elem(\"00005000\") timeout 100 ms 1) nft_pipapo_remove() removes element 0000000X Then, KASAN shows a splat. Looking at the remove function there is a chance that we will drop a rule that maps to a non-deactivated element. Removal happens in two steps, first we do a lookup for key k and return the to-be-removed element and mark it as inactive in the next generation. Then, in a second step, the element gets removed from the set/map. The _remove function does not work correctly if we have more than one element that share the same key. This can happen if we insert an element into a set when the set already holds an element with same key, but the element mapping to the existing key has timed out or is not active in the next generation. In such case its possible that removal will unmap the wrong element. If this happens, we will leak the non-deactivated element, it becomes unreachable. The element that got deactivated (and will be freed later) will remain reachable in the set data structure, this can result in a crash when such an element is retrieved during lookup (stale pointer). Add a check that the fully matching key does in fact map to the element that we have marked as inactive in the deactivation step. If not, we need to continue searching. Add a bug/warn trap at the end of the function as well, the remove function must not ever be called with an invisible/unreachable/non-existent element. v2: avoid uneeded temporary variable (Stefano)", "cve_priority": "high", "cve_public_date": "2024-04-25 06:15:00 UTC" } ], "launchpad_bugs_fixed": [ 2068150 ], "changes": [ { "cves": [ { "cve": "CVE-2024-26924", "url": "https://ubuntu.com/security/CVE-2024-26924", "cve_description": "In the Linux kernel, the following vulnerability has been resolved: netfilter: nft_set_pipapo: do not free live element Pablo reports a crash with large batches of elements with a back-to-back add/remove pattern. Quoting Pablo: add_elem(\"00000000\") timeout 100 ms ... add_elem(\"0000000X\") timeout 100 ms del_elem(\"0000000X\") <---------------- delete one that was just added ... add_elem(\"00005000\") timeout 100 ms 1) nft_pipapo_remove() removes element 0000000X Then, KASAN shows a splat. Looking at the remove function there is a chance that we will drop a rule that maps to a non-deactivated element. Removal happens in two steps, first we do a lookup for key k and return the to-be-removed element and mark it as inactive in the next generation. Then, in a second step, the element gets removed from the set/map. The _remove function does not work correctly if we have more than one element that share the same key. This can happen if we insert an element into a set when the set already holds an element with same key, but the element mapping to the existing key has timed out or is not active in the next generation. In such case its possible that removal will unmap the wrong element. If this happens, we will leak the non-deactivated element, it becomes unreachable. The element that got deactivated (and will be freed later) will remain reachable in the set data structure, this can result in a crash when such an element is retrieved during lookup (stale pointer). Add a check that the fully matching key does in fact map to the element that we have marked as inactive in the deactivation step. If not, we need to continue searching. Add a bug/warn trap at the end of the function as well, the remove function must not ever be called with an invisible/unreachable/non-existent element. v2: avoid uneeded temporary variable (Stefano)", "cve_priority": "high", "cve_public_date": "2024-04-25 06:15:00 UTC" } ], "log": [ "", " * noble/linux: 6.8.0-36.36 -proposed tracker (LP: #2068150)", "", " * CVE-2024-26924", " - netfilter: nft_set_pipapo: do not free live element", "" ], "package": "linux", "version": "6.8.0-36.36", "urgency": "medium", "distributions": "noble", "launchpad_bugs_fixed": [ 2068150 ], "author": "Roxana Nicolescu ", "date": "Mon, 10 Jun 2024 11:26:41 +0200" } ], "notes": "linux-modules-6.8.0-36-generic version '6.8.0-36.36' (source package linux version '6.8.0-36.36') was added. linux-modules-6.8.0-36-generic version '6.8.0-36.36' has the same source package name, linux, as removed package linux-headers-6.8.0-35. As such we can use the source package version of the removed package, '6.8.0-35.35', 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." }, { "name": "linux-tools-6.8.0-36", "from_version": { "source_package_name": "linux", "source_package_version": "6.8.0-35.35", "version": null }, "to_version": { "source_package_name": "linux", "source_package_version": "6.8.0-36.36", "version": "6.8.0-36.36" }, "cves": [ { "cve": "CVE-2024-26924", "url": "https://ubuntu.com/security/CVE-2024-26924", "cve_description": "In the Linux kernel, the following vulnerability has been resolved: netfilter: nft_set_pipapo: do not free live element Pablo reports a crash with large batches of elements with a back-to-back add/remove pattern. Quoting Pablo: add_elem(\"00000000\") timeout 100 ms ... add_elem(\"0000000X\") timeout 100 ms del_elem(\"0000000X\") <---------------- delete one that was just added ... add_elem(\"00005000\") timeout 100 ms 1) nft_pipapo_remove() removes element 0000000X Then, KASAN shows a splat. Looking at the remove function there is a chance that we will drop a rule that maps to a non-deactivated element. Removal happens in two steps, first we do a lookup for key k and return the to-be-removed element and mark it as inactive in the next generation. Then, in a second step, the element gets removed from the set/map. The _remove function does not work correctly if we have more than one element that share the same key. This can happen if we insert an element into a set when the set already holds an element with same key, but the element mapping to the existing key has timed out or is not active in the next generation. In such case its possible that removal will unmap the wrong element. If this happens, we will leak the non-deactivated element, it becomes unreachable. The element that got deactivated (and will be freed later) will remain reachable in the set data structure, this can result in a crash when such an element is retrieved during lookup (stale pointer). Add a check that the fully matching key does in fact map to the element that we have marked as inactive in the deactivation step. If not, we need to continue searching. Add a bug/warn trap at the end of the function as well, the remove function must not ever be called with an invisible/unreachable/non-existent element. v2: avoid uneeded temporary variable (Stefano)", "cve_priority": "high", "cve_public_date": "2024-04-25 06:15:00 UTC" } ], "launchpad_bugs_fixed": [ 2068150 ], "changes": [ { "cves": [ { "cve": "CVE-2024-26924", "url": "https://ubuntu.com/security/CVE-2024-26924", "cve_description": "In the Linux kernel, the following vulnerability has been resolved: netfilter: nft_set_pipapo: do not free live element Pablo reports a crash with large batches of elements with a back-to-back add/remove pattern. Quoting Pablo: add_elem(\"00000000\") timeout 100 ms ... add_elem(\"0000000X\") timeout 100 ms del_elem(\"0000000X\") <---------------- delete one that was just added ... add_elem(\"00005000\") timeout 100 ms 1) nft_pipapo_remove() removes element 0000000X Then, KASAN shows a splat. Looking at the remove function there is a chance that we will drop a rule that maps to a non-deactivated element. Removal happens in two steps, first we do a lookup for key k and return the to-be-removed element and mark it as inactive in the next generation. Then, in a second step, the element gets removed from the set/map. The _remove function does not work correctly if we have more than one element that share the same key. This can happen if we insert an element into a set when the set already holds an element with same key, but the element mapping to the existing key has timed out or is not active in the next generation. In such case its possible that removal will unmap the wrong element. If this happens, we will leak the non-deactivated element, it becomes unreachable. The element that got deactivated (and will be freed later) will remain reachable in the set data structure, this can result in a crash when such an element is retrieved during lookup (stale pointer). Add a check that the fully matching key does in fact map to the element that we have marked as inactive in the deactivation step. If not, we need to continue searching. Add a bug/warn trap at the end of the function as well, the remove function must not ever be called with an invisible/unreachable/non-existent element. v2: avoid uneeded temporary variable (Stefano)", "cve_priority": "high", "cve_public_date": "2024-04-25 06:15:00 UTC" } ], "log": [ "", " * noble/linux: 6.8.0-36.36 -proposed tracker (LP: #2068150)", "", " * CVE-2024-26924", " - netfilter: nft_set_pipapo: do not free live element", "" ], "package": "linux", "version": "6.8.0-36.36", "urgency": "medium", "distributions": "noble", "launchpad_bugs_fixed": [ 2068150 ], "author": "Roxana Nicolescu ", "date": "Mon, 10 Jun 2024 11:26:41 +0200" } ], "notes": "linux-tools-6.8.0-36 version '6.8.0-36.36' (source package linux version '6.8.0-36.36') was added. linux-tools-6.8.0-36 version '6.8.0-36.36' has the same source package name, linux, as removed package linux-headers-6.8.0-35. As such we can use the source package version of the removed package, '6.8.0-35.35', 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." }, { "name": "linux-tools-6.8.0-36-generic", "from_version": { "source_package_name": "linux", "source_package_version": "6.8.0-35.35", "version": null }, "to_version": { "source_package_name": "linux", "source_package_version": "6.8.0-36.36", "version": "6.8.0-36.36" }, "cves": [ { "cve": "CVE-2024-26924", "url": "https://ubuntu.com/security/CVE-2024-26924", "cve_description": "In the Linux kernel, the following vulnerability has been resolved: netfilter: nft_set_pipapo: do not free live element Pablo reports a crash with large batches of elements with a back-to-back add/remove pattern. Quoting Pablo: add_elem(\"00000000\") timeout 100 ms ... add_elem(\"0000000X\") timeout 100 ms del_elem(\"0000000X\") <---------------- delete one that was just added ... add_elem(\"00005000\") timeout 100 ms 1) nft_pipapo_remove() removes element 0000000X Then, KASAN shows a splat. Looking at the remove function there is a chance that we will drop a rule that maps to a non-deactivated element. Removal happens in two steps, first we do a lookup for key k and return the to-be-removed element and mark it as inactive in the next generation. Then, in a second step, the element gets removed from the set/map. The _remove function does not work correctly if we have more than one element that share the same key. This can happen if we insert an element into a set when the set already holds an element with same key, but the element mapping to the existing key has timed out or is not active in the next generation. In such case its possible that removal will unmap the wrong element. If this happens, we will leak the non-deactivated element, it becomes unreachable. The element that got deactivated (and will be freed later) will remain reachable in the set data structure, this can result in a crash when such an element is retrieved during lookup (stale pointer). Add a check that the fully matching key does in fact map to the element that we have marked as inactive in the deactivation step. If not, we need to continue searching. Add a bug/warn trap at the end of the function as well, the remove function must not ever be called with an invisible/unreachable/non-existent element. v2: avoid uneeded temporary variable (Stefano)", "cve_priority": "high", "cve_public_date": "2024-04-25 06:15:00 UTC" } ], "launchpad_bugs_fixed": [ 2068150 ], "changes": [ { "cves": [ { "cve": "CVE-2024-26924", "url": "https://ubuntu.com/security/CVE-2024-26924", "cve_description": "In the Linux kernel, the following vulnerability has been resolved: netfilter: nft_set_pipapo: do not free live element Pablo reports a crash with large batches of elements with a back-to-back add/remove pattern. Quoting Pablo: add_elem(\"00000000\") timeout 100 ms ... add_elem(\"0000000X\") timeout 100 ms del_elem(\"0000000X\") <---------------- delete one that was just added ... add_elem(\"00005000\") timeout 100 ms 1) nft_pipapo_remove() removes element 0000000X Then, KASAN shows a splat. Looking at the remove function there is a chance that we will drop a rule that maps to a non-deactivated element. Removal happens in two steps, first we do a lookup for key k and return the to-be-removed element and mark it as inactive in the next generation. Then, in a second step, the element gets removed from the set/map. The _remove function does not work correctly if we have more than one element that share the same key. This can happen if we insert an element into a set when the set already holds an element with same key, but the element mapping to the existing key has timed out or is not active in the next generation. In such case its possible that removal will unmap the wrong element. If this happens, we will leak the non-deactivated element, it becomes unreachable. The element that got deactivated (and will be freed later) will remain reachable in the set data structure, this can result in a crash when such an element is retrieved during lookup (stale pointer). Add a check that the fully matching key does in fact map to the element that we have marked as inactive in the deactivation step. If not, we need to continue searching. Add a bug/warn trap at the end of the function as well, the remove function must not ever be called with an invisible/unreachable/non-existent element. v2: avoid uneeded temporary variable (Stefano)", "cve_priority": "high", "cve_public_date": "2024-04-25 06:15:00 UTC" } ], "log": [ "", " * noble/linux: 6.8.0-36.36 -proposed tracker (LP: #2068150)", "", " * CVE-2024-26924", " - netfilter: nft_set_pipapo: do not free live element", "" ], "package": "linux", "version": "6.8.0-36.36", "urgency": "medium", "distributions": "noble", "launchpad_bugs_fixed": [ 2068150 ], "author": "Roxana Nicolescu ", "date": "Mon, 10 Jun 2024 11:26:41 +0200" } ], "notes": "linux-tools-6.8.0-36-generic version '6.8.0-36.36' (source package linux version '6.8.0-36.36') was added. linux-tools-6.8.0-36-generic version '6.8.0-36.36' has the same source package name, linux, as removed package linux-headers-6.8.0-35. As such we can use the source package version of the removed package, '6.8.0-35.35', 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." } ], "snap": [] }, "removed": { "deb": [ { "name": "linux-headers-6.8.0-35", "from_version": { "source_package_name": "linux", "source_package_version": "6.8.0-35.35", "version": "6.8.0-35.35" }, "to_version": { "source_package_name": null, "source_package_version": null, "version": null }, "cves": [], "launchpad_bugs_fixed": [], "changes": [], "notes": null }, { "name": "linux-headers-6.8.0-35-generic", "from_version": { "source_package_name": "linux", "source_package_version": "6.8.0-35.35", "version": "6.8.0-35.35" }, "to_version": { "source_package_name": null, "source_package_version": null, "version": null }, "cves": [], "launchpad_bugs_fixed": [], "changes": [], "notes": null }, { "name": "linux-image-6.8.0-35-generic", "from_version": { "source_package_name": "linux", "source_package_version": "6.8.0-35.35", "version": "6.8.0-35.35" }, "to_version": { "source_package_name": null, "source_package_version": null, "version": null }, "cves": [], "launchpad_bugs_fixed": [], "changes": [], "notes": null }, { "name": "linux-modules-6.8.0-35-generic", "from_version": { "source_package_name": "linux", "source_package_version": "6.8.0-35.35", "version": "6.8.0-35.35" }, "to_version": { "source_package_name": null, "source_package_version": null, "version": null }, "cves": [], "launchpad_bugs_fixed": [], "changes": [], "notes": null }, { "name": "linux-tools-6.8.0-35", "from_version": { "source_package_name": "linux", "source_package_version": "6.8.0-35.35", "version": "6.8.0-35.35" }, "to_version": { "source_package_name": null, "source_package_version": null, "version": null }, "cves": [], "launchpad_bugs_fixed": [], "changes": [], "notes": null }, { "name": "linux-tools-6.8.0-35-generic", "from_version": { "source_package_name": "linux", "source_package_version": "6.8.0-35.35", "version": "6.8.0-35.35" }, "to_version": { "source_package_name": null, "source_package_version": null, "version": null }, "cves": [], "launchpad_bugs_fixed": [], "changes": [], "notes": null } ], "snap": [] }, "notes": "Changelog diff for Ubuntu 24.04 noble image from release image serial 20240622 to 20240628", "from_series": "noble", "to_series": "noble", "from_serial": "20240622", "to_serial": "20240628", "from_manifest_filename": "release_manifest.previous", "to_manifest_filename": "manifest.current" }