{ "summary": { "snap": { "added": [], "removed": [], "diff": [ "lxd" ] }, "deb": { "added": [ "linux-headers-6.5.0-28-generic", "linux-image-6.5.0-28-generic", "linux-modules-6.5.0-28-generic", "linux-riscv-6.5-headers-6.5.0-28" ], "removed": [ "linux-headers-6.5.0-27-generic", "linux-image-6.5.0-27-generic", "linux-modules-6.5.0-27-generic", "linux-riscv-6.5-headers-6.5.0-27" ], "diff": [ "cloud-init", "klibc-utils", "libc-bin", "libc6:riscv64", "libklibc:riscv64", "libnghttp2-14:riscv64", "linux-headers-generic", "linux-headers-virtual", "linux-image-virtual", "linux-virtual", "locales", "openssh-client", "openssh-server", "openssh-sftp-server" ] } }, "diff": { "deb": [ { "name": "cloud-init", "from_version": { "source_package_name": "cloud-init", "source_package_version": "23.4.4-0ubuntu0~22.04.1", "version": "23.4.4-0ubuntu0~22.04.1" }, "to_version": { "source_package_name": "cloud-init", "source_package_version": "24.1.3-0ubuntu1~22.04.1", "version": "24.1.3-0ubuntu1~22.04.1" }, "cves": [], "launchpad_bugs_fixed": [ 2056100, 2056100, 2053157, 2056100 ], "changes": [ { "cves": [], "log": [ "", " * Upstream snapshot based on 24.1.3. (LP: #2056100).", " List of changes from upstream can be found at", " https://raw.githubusercontent.com/canonical/cloud-init/24.1.3/ChangeLog", "" ], "package": "cloud-init", "version": "24.1.3-0ubuntu1~22.04.1", "urgency": "medium", "distributions": "jammy", "launchpad_bugs_fixed": [ 2056100 ], "author": "James Falcon ", "date": "Wed, 27 Mar 2024 08:36:38 -0500" }, { "cves": [], "log": [ "", " * refresh patches:", " - d/p/retain-ec2-default-net-update-events.patch", " * Upstream snapshot based on 24.1.2. (LP: #2056100).", " List of changes from upstream can be found at", " https://raw.githubusercontent.com/canonical/cloud-init/24.1.2/ChangeLog", "" ], "package": "cloud-init", "version": "24.1.2-0ubuntu1~22.04.1", "urgency": "medium", "distributions": "jammy", "launchpad_bugs_fixed": [ 2056100 ], "author": "Chad Smith ", "date": "Thu, 21 Mar 2024 09:22:13 -0600" }, { "cves": [], "log": [ "", " * d/apport-general-hook.py: Move apport hook to main branch", " * d/cloud-init.maintscript: remove /etc/cloud/clean.d/README", " * d/cloud-init.logrotate: add logrotate config for cloud-init", " * d/cloud-init.templates: enable WSL datasource by default", " * Drop d/p/retain-netplan-world-readable.patch:", " - Limit perms to 600 of /etc/netplan/50-cloud-init.yaml instead of 644", " (LP: #2053157)", " * d/p/keep-dhclient-as-priority-client.patch:", " - keep dhclient as default client", " * d/p/revert-551f560d-cloud-config-after-snap-seeding.patch", " - Retain systemd ordering cloud-config.service After=snapd.seeded.service", " * d/p/retain-ec2-default-net-update-events.patch:", " Reverts 4dbb08f5f0cc4f41cf9dd1474f0600a11510a3c9 to not change behavior", " on stable releases.", " * d/po/templates.pot: update for wsl", " * d/cloud-init.postinst: change priority of hotplug rules.", " Avoids LP #1946003 on upgraded systems. References:", " [0] https://github.com/canonical/cloud-init/pull/4799", " [1] commit/b519d861aff8b44a0610c176cb34adcbe28df144", " * refresh patches:", " - d/p/status-do-not-remove-duplicated-data.patch", " - d/p/status-retain-recoverable-error-exit-code.patch", " * Upstream snapshot based on 24.1.1. (LP: #2056100).", " List of changes from upstream can be found at", " https://raw.githubusercontent.com/canonical/cloud-init/24.1.1/ChangeLog", "" ], "package": "cloud-init", "version": "24.1.1-0ubuntu1~22.04.1", "urgency": "medium", "distributions": "jammy", "launchpad_bugs_fixed": [ 2053157, 2056100 ], "author": "Brett Holman ", "date": "Wed, 13 Mar 2024 16:38:18 -0600" } ], "notes": null }, { "name": "klibc-utils", "from_version": { "source_package_name": "klibc", "source_package_version": "2.0.10-4", "version": "2.0.10-4" }, "to_version": { "source_package_name": "klibc", "source_package_version": "2.0.10-4ubuntu0.1", "version": "2.0.10-4ubuntu0.1" }, "cves": [ { "cve": "CVE-2016-9840", "url": "https://ubuntu.com/security/CVE-2016-9840", "cve_description": "inftrees.c in zlib 1.2.8 might allow context-dependent attackers to have unspecified impact by leveraging improper pointer arithmetic.", "cve_priority": "low", "cve_public_date": "2017-05-23 04:29:00 UTC" }, { "cve": "CVE-2016-9841", "url": "https://ubuntu.com/security/CVE-2016-9841", "cve_description": "inffast.c in zlib 1.2.8 might allow context-dependent attackers to have unspecified impact by leveraging improper pointer arithmetic.", "cve_priority": "low", "cve_public_date": "2017-05-23 04:29:00 UTC" }, { "cve": "CVE-2018-25032", "url": "https://ubuntu.com/security/CVE-2018-25032", "cve_description": "zlib before 1.2.12 allows memory corruption when deflating (i.e., when compressing) if the input has many distant matches.", "cve_priority": "medium", "cve_public_date": "2022-03-25 09:15:00 UTC" }, { "cve": "CVE-2022-37434", "url": "https://ubuntu.com/security/CVE-2022-37434", "cve_description": "zlib through 1.2.12 has a heap-based buffer over-read or buffer overflow in inflate in inflate.c via a large gzip header extra field. NOTE: only applications that call inflateGetHeader are affected. Some common applications bundle the affected zlib source code but may be unable to call inflateGetHeader (e.g., see the nodejs/node reference).", "cve_priority": "medium", "cve_public_date": "2022-08-05 07:15:00 UTC" } ], "launchpad_bugs_fixed": [], "changes": [ { "cves": [ { "cve": "CVE-2016-9840", "url": "https://ubuntu.com/security/CVE-2016-9840", "cve_description": "inftrees.c in zlib 1.2.8 might allow context-dependent attackers to have unspecified impact by leveraging improper pointer arithmetic.", "cve_priority": "low", "cve_public_date": "2017-05-23 04:29:00 UTC" }, { "cve": "CVE-2016-9841", "url": "https://ubuntu.com/security/CVE-2016-9841", "cve_description": "inffast.c in zlib 1.2.8 might allow context-dependent attackers to have unspecified impact by leveraging improper pointer arithmetic.", "cve_priority": "low", "cve_public_date": "2017-05-23 04:29:00 UTC" }, { "cve": "CVE-2018-25032", "url": "https://ubuntu.com/security/CVE-2018-25032", "cve_description": "zlib before 1.2.12 allows memory corruption when deflating (i.e., when compressing) if the input has many distant matches.", "cve_priority": "medium", "cve_public_date": "2022-03-25 09:15:00 UTC" }, { "cve": "CVE-2022-37434", "url": "https://ubuntu.com/security/CVE-2022-37434", "cve_description": "zlib through 1.2.12 has a heap-based buffer over-read or buffer overflow in inflate in inflate.c via a large gzip header extra field. NOTE: only applications that call inflateGetHeader are affected. Some common applications bundle the affected zlib source code but may be unable to call inflateGetHeader (e.g., see the nodejs/node reference).", "cve_priority": "medium", "cve_public_date": "2022-08-05 07:15:00 UTC" } ], "log": [ "", " * SECURITY UPDATE: improper pointer arithmetic", " - debian/patches/CVE-2016-9840.patch: remove offset pointer optimization", " in usr/klibc/zlib/inftrees.c.", " - CVE-2016-9840", " * SECURITY UPDATE: improper pointer arithmetic", " - debian/patches/CVE-2016-9841.patch: remove offset pointer optimization", " in usr/klibc/zlib/inffast.c.", " - CVE-2016-9841", " * SECURITY UPDATE: memory corruption during compression", " - debian/patches/CVE-2018-25032.patch: addresses a bug that can crash", " deflate on rare inputs when using Z_FIXED.", " - CVE-2018-25032", " * SECURITY UPDATE: heap-based buffer over-read", " - debian/patches/CVE-2022-37434-1.patch: adds an extra condition to check", " if state->head->extra_max is greater than len before copying, and moves", " the len assignment to be placed before the check in", " usr/klibc/zlib/inflate.c.", " - debian/patches/CVE-2022-37434-2.patch: in the previous patch, the", " placement of the len assignment was causing issues so it was moved", " within the conditional check.", " - CVE-2022-37434", "" ], "package": "klibc", "version": "2.0.10-4ubuntu0.1", "urgency": "medium", "distributions": "jammy-security", "launchpad_bugs_fixed": [], "author": "Ian Constantin ", "date": "Sat, 13 Apr 2024 12:34:04 +0300" } ], "notes": null }, { "name": "libc-bin", "from_version": { "source_package_name": "glibc", "source_package_version": "2.35-0ubuntu3.6", "version": "2.35-0ubuntu3.6" }, "to_version": { "source_package_name": "glibc", "source_package_version": "2.35-0ubuntu3.7", "version": "2.35-0ubuntu3.7" }, "cves": [ { "cve": "CVE-2024-2961", "url": "https://ubuntu.com/security/CVE-2024-2961", "cve_description": "The iconv() function in the GNU C Library versions 2.39 and older may overflow the output buffer passed to it by up to 4 bytes when converting strings to the ISO-2022-CN-EXT character set, which may be used to crash an application or overwrite a neighbouring variable.", "cve_priority": "medium", "cve_public_date": "2024-04-17 18:15:00 UTC" } ], "launchpad_bugs_fixed": [], "changes": [ { "cves": [ { "cve": "CVE-2024-2961", "url": "https://ubuntu.com/security/CVE-2024-2961", "cve_description": "The iconv() function in the GNU C Library versions 2.39 and older may overflow the output buffer passed to it by up to 4 bytes when converting strings to the ISO-2022-CN-EXT character set, which may be used to crash an application or overwrite a neighbouring variable.", "cve_priority": "medium", "cve_public_date": "2024-04-17 18:15:00 UTC" } ], "log": [ "", " * SECURITY UPDATE: OOB write in iconv plugin ISO-2022-CN-EXT", " - debian/patches/any/CVE-2024-2961.patch: fix out-of-bound writes when", " writing escape sequence in iconvdata/Makefile,", " iconvdata/iso-2022-cn-ext.c, iconvdata/tst-iconv-iso-2022-cn-ext.c.", " - CVE-2024-2961", "" ], "package": "glibc", "version": "2.35-0ubuntu3.7", "urgency": "medium", "distributions": "jammy-security", "launchpad_bugs_fixed": [], "author": "Marc Deslauriers ", "date": "Tue, 16 Apr 2024 09:40:36 -0400" } ], "notes": null }, { "name": "libc6:riscv64", "from_version": { "source_package_name": "glibc", "source_package_version": "2.35-0ubuntu3.6", "version": "2.35-0ubuntu3.6" }, "to_version": { "source_package_name": "glibc", "source_package_version": "2.35-0ubuntu3.7", "version": "2.35-0ubuntu3.7" }, "cves": [ { "cve": "CVE-2024-2961", "url": "https://ubuntu.com/security/CVE-2024-2961", "cve_description": "The iconv() function in the GNU C Library versions 2.39 and older may overflow the output buffer passed to it by up to 4 bytes when converting strings to the ISO-2022-CN-EXT character set, which may be used to crash an application or overwrite a neighbouring variable.", "cve_priority": "medium", "cve_public_date": "2024-04-17 18:15:00 UTC" } ], "launchpad_bugs_fixed": [], "changes": [ { "cves": [ { "cve": "CVE-2024-2961", "url": "https://ubuntu.com/security/CVE-2024-2961", "cve_description": "The iconv() function in the GNU C Library versions 2.39 and older may overflow the output buffer passed to it by up to 4 bytes when converting strings to the ISO-2022-CN-EXT character set, which may be used to crash an application or overwrite a neighbouring variable.", "cve_priority": "medium", "cve_public_date": "2024-04-17 18:15:00 UTC" } ], "log": [ "", " * SECURITY UPDATE: OOB write in iconv plugin ISO-2022-CN-EXT", " - debian/patches/any/CVE-2024-2961.patch: fix out-of-bound writes when", " writing escape sequence in iconvdata/Makefile,", " iconvdata/iso-2022-cn-ext.c, iconvdata/tst-iconv-iso-2022-cn-ext.c.", " - CVE-2024-2961", "" ], "package": "glibc", "version": "2.35-0ubuntu3.7", "urgency": "medium", "distributions": "jammy-security", "launchpad_bugs_fixed": [], "author": "Marc Deslauriers ", "date": "Tue, 16 Apr 2024 09:40:36 -0400" } ], "notes": null }, { "name": "libklibc:riscv64", "from_version": { "source_package_name": "klibc", "source_package_version": "2.0.10-4", "version": "2.0.10-4" }, "to_version": { "source_package_name": "klibc", "source_package_version": "2.0.10-4ubuntu0.1", "version": "2.0.10-4ubuntu0.1" }, "cves": [ { "cve": "CVE-2016-9840", "url": "https://ubuntu.com/security/CVE-2016-9840", "cve_description": "inftrees.c in zlib 1.2.8 might allow context-dependent attackers to have unspecified impact by leveraging improper pointer arithmetic.", "cve_priority": "low", "cve_public_date": "2017-05-23 04:29:00 UTC" }, { "cve": "CVE-2016-9841", "url": "https://ubuntu.com/security/CVE-2016-9841", "cve_description": "inffast.c in zlib 1.2.8 might allow context-dependent attackers to have unspecified impact by leveraging improper pointer arithmetic.", "cve_priority": "low", "cve_public_date": "2017-05-23 04:29:00 UTC" }, { "cve": "CVE-2018-25032", "url": "https://ubuntu.com/security/CVE-2018-25032", "cve_description": "zlib before 1.2.12 allows memory corruption when deflating (i.e., when compressing) if the input has many distant matches.", "cve_priority": "medium", "cve_public_date": "2022-03-25 09:15:00 UTC" }, { "cve": "CVE-2022-37434", "url": "https://ubuntu.com/security/CVE-2022-37434", "cve_description": "zlib through 1.2.12 has a heap-based buffer over-read or buffer overflow in inflate in inflate.c via a large gzip header extra field. NOTE: only applications that call inflateGetHeader are affected. Some common applications bundle the affected zlib source code but may be unable to call inflateGetHeader (e.g., see the nodejs/node reference).", "cve_priority": "medium", "cve_public_date": "2022-08-05 07:15:00 UTC" } ], "launchpad_bugs_fixed": [], "changes": [ { "cves": [ { "cve": "CVE-2016-9840", "url": "https://ubuntu.com/security/CVE-2016-9840", "cve_description": "inftrees.c in zlib 1.2.8 might allow context-dependent attackers to have unspecified impact by leveraging improper pointer arithmetic.", "cve_priority": "low", "cve_public_date": "2017-05-23 04:29:00 UTC" }, { "cve": "CVE-2016-9841", "url": "https://ubuntu.com/security/CVE-2016-9841", "cve_description": "inffast.c in zlib 1.2.8 might allow context-dependent attackers to have unspecified impact by leveraging improper pointer arithmetic.", "cve_priority": "low", "cve_public_date": "2017-05-23 04:29:00 UTC" }, { "cve": "CVE-2018-25032", "url": "https://ubuntu.com/security/CVE-2018-25032", "cve_description": "zlib before 1.2.12 allows memory corruption when deflating (i.e., when compressing) if the input has many distant matches.", "cve_priority": "medium", "cve_public_date": "2022-03-25 09:15:00 UTC" }, { "cve": "CVE-2022-37434", "url": "https://ubuntu.com/security/CVE-2022-37434", "cve_description": "zlib through 1.2.12 has a heap-based buffer over-read or buffer overflow in inflate in inflate.c via a large gzip header extra field. NOTE: only applications that call inflateGetHeader are affected. Some common applications bundle the affected zlib source code but may be unable to call inflateGetHeader (e.g., see the nodejs/node reference).", "cve_priority": "medium", "cve_public_date": "2022-08-05 07:15:00 UTC" } ], "log": [ "", " * SECURITY UPDATE: improper pointer arithmetic", " - debian/patches/CVE-2016-9840.patch: remove offset pointer optimization", " in usr/klibc/zlib/inftrees.c.", " - CVE-2016-9840", " * SECURITY UPDATE: improper pointer arithmetic", " - debian/patches/CVE-2016-9841.patch: remove offset pointer optimization", " in usr/klibc/zlib/inffast.c.", " - CVE-2016-9841", " * SECURITY UPDATE: memory corruption during compression", " - debian/patches/CVE-2018-25032.patch: addresses a bug that can crash", " deflate on rare inputs when using Z_FIXED.", " - CVE-2018-25032", " * SECURITY UPDATE: heap-based buffer over-read", " - debian/patches/CVE-2022-37434-1.patch: adds an extra condition to check", " if state->head->extra_max is greater than len before copying, and moves", " the len assignment to be placed before the check in", " usr/klibc/zlib/inflate.c.", " - debian/patches/CVE-2022-37434-2.patch: in the previous patch, the", " placement of the len assignment was causing issues so it was moved", " within the conditional check.", " - CVE-2022-37434", "" ], "package": "klibc", "version": "2.0.10-4ubuntu0.1", "urgency": "medium", "distributions": "jammy-security", "launchpad_bugs_fixed": [], "author": "Ian Constantin ", "date": "Sat, 13 Apr 2024 12:34:04 +0300" } ], "notes": null }, { "name": "libnghttp2-14:riscv64", "from_version": { "source_package_name": "nghttp2", "source_package_version": "1.43.0-1ubuntu0.1", "version": "1.43.0-1ubuntu0.1" }, "to_version": { "source_package_name": "nghttp2", "source_package_version": "1.43.0-1ubuntu0.2", "version": "1.43.0-1ubuntu0.2" }, "cves": [ { "cve": "CVE-2024-28182", "url": "https://ubuntu.com/security/CVE-2024-28182", "cve_description": "nghttp2 is an implementation of the Hypertext Transfer Protocol version 2 in C. The nghttp2 library prior to version 1.61.0 keeps reading the unbounded number of HTTP/2 CONTINUATION frames even after a stream is reset to keep HPACK context in sync. This causes excessive CPU usage to decode HPACK stream. nghttp2 v1.61.0 mitigates this vulnerability by limiting the number of CONTINUATION frames it accepts per stream. There is no workaround for this vulnerability.", "cve_priority": "medium", "cve_public_date": "2024-04-04 15:15:00 UTC" } ], "launchpad_bugs_fixed": [], "changes": [ { "cves": [ { "cve": "CVE-2024-28182", "url": "https://ubuntu.com/security/CVE-2024-28182", "cve_description": "nghttp2 is an implementation of the Hypertext Transfer Protocol version 2 in C. The nghttp2 library prior to version 1.61.0 keeps reading the unbounded number of HTTP/2 CONTINUATION frames even after a stream is reset to keep HPACK context in sync. This causes excessive CPU usage to decode HPACK stream. nghttp2 v1.61.0 mitigates this vulnerability by limiting the number of CONTINUATION frames it accepts per stream. There is no workaround for this vulnerability.", "cve_priority": "medium", "cve_public_date": "2024-04-04 15:15:00 UTC" } ], "log": [ "", " * SECURITY UPDATE: HTTP/2 protocol denial of service", " - debian/patches/CVE-2024-28182-1.patch: Add", " nghttp2_option_set_max_continuations", " - debian/patches/CVE-2024-28182-2.patch: Limit CONTINUATION frames", " following an incoming HEADER frame", " - CVE-2024-28182", "" ], "package": "nghttp2", "version": "1.43.0-1ubuntu0.2", "urgency": "medium", "distributions": "jammy-security", "launchpad_bugs_fixed": [], "author": "Fabian Toepfer ", "date": "Thu, 18 Apr 2024 09:14:38 +0200" } ], "notes": null }, { "name": "linux-headers-generic", "from_version": { "source_package_name": "linux-meta-riscv-6.5", "source_package_version": "6.5.0.27.28.1~22.04.1", "version": "6.5.0.27.28.1~22.04.1" }, "to_version": { "source_package_name": "linux-meta-riscv-6.5", "source_package_version": "6.5.0.28.29.1~22.04.1", "version": "6.5.0.28.29.1~22.04.1" }, "cves": [], "launchpad_bugs_fixed": [], "changes": [ { "cves": [], "log": [ "", " * Bump ABI 6.5.0-28.29.1~22.04", "" ], "package": "linux-meta-riscv-6.5", "version": "6.5.0.28.29.1~22.04.1", "urgency": "medium", "distributions": "jammy", "launchpad_bugs_fixed": [], "author": "Hannah Peuckmann ", "date": "Mon, 08 Apr 2024 09:12:39 +0200" } ], "notes": null }, { "name": "linux-headers-virtual", "from_version": { "source_package_name": "linux-meta-riscv-6.5", "source_package_version": "6.5.0.27.28.1~22.04.1", "version": "6.5.0.27.28.1~22.04.1" }, "to_version": { "source_package_name": "linux-meta-riscv-6.5", "source_package_version": "6.5.0.28.29.1~22.04.1", "version": "6.5.0.28.29.1~22.04.1" }, "cves": [], "launchpad_bugs_fixed": [], "changes": [ { "cves": [], "log": [ "", " * Bump ABI 6.5.0-28.29.1~22.04", "" ], "package": "linux-meta-riscv-6.5", "version": "6.5.0.28.29.1~22.04.1", "urgency": "medium", "distributions": "jammy", "launchpad_bugs_fixed": [], "author": "Hannah Peuckmann ", "date": "Mon, 08 Apr 2024 09:12:39 +0200" } ], "notes": null }, { "name": "linux-image-virtual", "from_version": { "source_package_name": "linux-meta-riscv-6.5", "source_package_version": "6.5.0.27.28.1~22.04.1", "version": "6.5.0.27.28.1~22.04.1" }, "to_version": { "source_package_name": "linux-meta-riscv-6.5", "source_package_version": "6.5.0.28.29.1~22.04.1", "version": "6.5.0.28.29.1~22.04.1" }, "cves": [], "launchpad_bugs_fixed": [], "changes": [ { "cves": [], "log": [ "", " * Bump ABI 6.5.0-28.29.1~22.04", "" ], "package": "linux-meta-riscv-6.5", "version": "6.5.0.28.29.1~22.04.1", "urgency": "medium", "distributions": "jammy", "launchpad_bugs_fixed": [], "author": "Hannah Peuckmann ", "date": "Mon, 08 Apr 2024 09:12:39 +0200" } ], "notes": null }, { "name": "linux-virtual", "from_version": { "source_package_name": "linux-meta-riscv-6.5", "source_package_version": "6.5.0.27.28.1~22.04.1", "version": "6.5.0.27.28.1~22.04.1" }, "to_version": { "source_package_name": "linux-meta-riscv-6.5", "source_package_version": "6.5.0.28.29.1~22.04.1", "version": "6.5.0.28.29.1~22.04.1" }, "cves": [], "launchpad_bugs_fixed": [], "changes": [ { "cves": [], "log": [ "", " * Bump ABI 6.5.0-28.29.1~22.04", "" ], "package": "linux-meta-riscv-6.5", "version": "6.5.0.28.29.1~22.04.1", "urgency": "medium", "distributions": "jammy", "launchpad_bugs_fixed": [], "author": "Hannah Peuckmann ", "date": "Mon, 08 Apr 2024 09:12:39 +0200" } ], "notes": null }, { "name": "locales", "from_version": { "source_package_name": "glibc", "source_package_version": "2.35-0ubuntu3.6", "version": "2.35-0ubuntu3.6" }, "to_version": { "source_package_name": "glibc", "source_package_version": "2.35-0ubuntu3.7", "version": "2.35-0ubuntu3.7" }, "cves": [ { "cve": "CVE-2024-2961", "url": "https://ubuntu.com/security/CVE-2024-2961", "cve_description": "The iconv() function in the GNU C Library versions 2.39 and older may overflow the output buffer passed to it by up to 4 bytes when converting strings to the ISO-2022-CN-EXT character set, which may be used to crash an application or overwrite a neighbouring variable.", "cve_priority": "medium", "cve_public_date": "2024-04-17 18:15:00 UTC" } ], "launchpad_bugs_fixed": [], "changes": [ { "cves": [ { "cve": "CVE-2024-2961", "url": "https://ubuntu.com/security/CVE-2024-2961", "cve_description": "The iconv() function in the GNU C Library versions 2.39 and older may overflow the output buffer passed to it by up to 4 bytes when converting strings to the ISO-2022-CN-EXT character set, which may be used to crash an application or overwrite a neighbouring variable.", "cve_priority": "medium", "cve_public_date": "2024-04-17 18:15:00 UTC" } ], "log": [ "", " * SECURITY UPDATE: OOB write in iconv plugin ISO-2022-CN-EXT", " - debian/patches/any/CVE-2024-2961.patch: fix out-of-bound writes when", " writing escape sequence in iconvdata/Makefile,", " iconvdata/iso-2022-cn-ext.c, iconvdata/tst-iconv-iso-2022-cn-ext.c.", " - CVE-2024-2961", "" ], "package": "glibc", "version": "2.35-0ubuntu3.7", "urgency": "medium", "distributions": "jammy-security", "launchpad_bugs_fixed": [], "author": "Marc Deslauriers ", "date": "Tue, 16 Apr 2024 09:40:36 -0400" } ], "notes": null }, { "name": "openssh-client", "from_version": { "source_package_name": "openssh", "source_package_version": "1:8.9p1-3ubuntu0.6", "version": "1:8.9p1-3ubuntu0.6" }, "to_version": { "source_package_name": "openssh", "source_package_version": "1:8.9p1-3ubuntu0.7", "version": "1:8.9p1-3ubuntu0.7" }, "cves": [], "launchpad_bugs_fixed": [ 2053146 ], "changes": [ { "cves": [], "log": [ "", " * d/p/gssapi.patch: fix method_gsskeyex structure and", " userauth_gsskeyex function regarding changes introduced in upstream", " commit dbb339f015c33d63484261d140c84ad875a9e548 (\"prepare for", " multiple names for authmethods\") (LP: #2053146)", " * d/t/{ssh-gssapi,util}: ssh-gssapi DEP8 test for gssapi-with-mic", " and gssapi-keyex authentication methods", "" ], "package": "openssh", "version": "1:8.9p1-3ubuntu0.7", "urgency": "medium", "distributions": "jammy", "launchpad_bugs_fixed": [ 2053146 ], "author": "Andreas Hasenack ", "date": "Fri, 15 Mar 2024 17:28:22 -0300" } ], "notes": null }, { "name": "openssh-server", "from_version": { "source_package_name": "openssh", "source_package_version": "1:8.9p1-3ubuntu0.6", "version": "1:8.9p1-3ubuntu0.6" }, "to_version": { "source_package_name": "openssh", "source_package_version": "1:8.9p1-3ubuntu0.7", "version": "1:8.9p1-3ubuntu0.7" }, "cves": [], "launchpad_bugs_fixed": [ 2053146 ], "changes": [ { "cves": [], "log": [ "", " * d/p/gssapi.patch: fix method_gsskeyex structure and", " userauth_gsskeyex function regarding changes introduced in upstream", " commit dbb339f015c33d63484261d140c84ad875a9e548 (\"prepare for", " multiple names for authmethods\") (LP: #2053146)", " * d/t/{ssh-gssapi,util}: ssh-gssapi DEP8 test for gssapi-with-mic", " and gssapi-keyex authentication methods", "" ], "package": "openssh", "version": "1:8.9p1-3ubuntu0.7", "urgency": "medium", "distributions": "jammy", "launchpad_bugs_fixed": [ 2053146 ], "author": "Andreas Hasenack ", "date": "Fri, 15 Mar 2024 17:28:22 -0300" } ], "notes": null }, { "name": "openssh-sftp-server", "from_version": { "source_package_name": "openssh", "source_package_version": "1:8.9p1-3ubuntu0.6", "version": "1:8.9p1-3ubuntu0.6" }, "to_version": { "source_package_name": "openssh", "source_package_version": "1:8.9p1-3ubuntu0.7", "version": "1:8.9p1-3ubuntu0.7" }, "cves": [], "launchpad_bugs_fixed": [ 2053146 ], "changes": [ { "cves": [], "log": [ "", " * d/p/gssapi.patch: fix method_gsskeyex structure and", " userauth_gsskeyex function regarding changes introduced in upstream", " commit dbb339f015c33d63484261d140c84ad875a9e548 (\"prepare for", " multiple names for authmethods\") (LP: #2053146)", " * d/t/{ssh-gssapi,util}: ssh-gssapi DEP8 test for gssapi-with-mic", " and gssapi-keyex authentication methods", "" ], "package": "openssh", "version": "1:8.9p1-3ubuntu0.7", "urgency": "medium", "distributions": "jammy", "launchpad_bugs_fixed": [ 2053146 ], "author": "Andreas Hasenack ", "date": "Fri, 15 Mar 2024 17:28:22 -0300" } ], "notes": null } ], "snap": [ { "name": "lxd", "from_version": { "source_package_name": null, "source_package_version": null, "version": "27981" }, "to_version": { "source_package_name": null, "source_package_version": null, "version": "28388" } } ] }, "added": { "deb": [ { "name": "linux-headers-6.5.0-28-generic", "from_version": { "source_package_name": "linux-riscv-6.5", "source_package_version": "6.5.0-27.28.1~22.04.1", "version": null }, "to_version": { "source_package_name": "linux-riscv-6.5", "source_package_version": "6.5.0-28.29.1~22.04.1", "version": "6.5.0-28.29.1~22.04.1" }, "cves": [ { "cve": "CVE-2023-52600", "url": "https://ubuntu.com/security/CVE-2023-52600", "cve_description": "In the Linux kernel, the following vulnerability has been resolved: jfs: fix uaf in jfs_evict_inode When the execution of diMount(ipimap) fails, the object ipimap that has been released may be accessed in diFreeSpecial(). Asynchronous ipimap release occurs when rcu_core() calls jfs_free_node(). Therefore, when diMount(ipimap) fails, sbi->ipimap should not be initialized as ipimap.", "cve_priority": "medium", "cve_public_date": "2024-03-06 07:15:00 UTC" }, { "cve": "CVE-2023-52603", "url": "https://ubuntu.com/security/CVE-2023-52603", "cve_description": "In the Linux kernel, the following vulnerability has been resolved: UBSAN: array-index-out-of-bounds in dtSplitRoot Syzkaller reported the following issue: oop0: detected capacity change from 0 to 32768 UBSAN: array-index-out-of-bounds in fs/jfs/jfs_dtree.c:1971:9 index -2 is out of range for type 'struct dtslot [128]' CPU: 0 PID: 3613 Comm: syz-executor270 Not tainted 6.0.0-syzkaller-09423-g493ffd6605b2 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/22/2022 Call Trace: __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0x1b1/0x28e lib/dump_stack.c:106 ubsan_epilogue lib/ubsan.c:151 [inline] __ubsan_handle_out_of_bounds+0xdb/0x130 lib/ubsan.c:283 dtSplitRoot+0x8d8/0x1900 fs/jfs/jfs_dtree.c:1971 dtSplitUp fs/jfs/jfs_dtree.c:985 [inline] dtInsert+0x1189/0x6b80 fs/jfs/jfs_dtree.c:863 jfs_mkdir+0x757/0xb00 fs/jfs/namei.c:270 vfs_mkdir+0x3b3/0x590 fs/namei.c:4013 do_mkdirat+0x279/0x550 fs/namei.c:4038 __do_sys_mkdirat fs/namei.c:4053 [inline] __se_sys_mkdirat fs/namei.c:4051 [inline] __x64_sys_mkdirat+0x85/0x90 fs/namei.c:4051 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x63/0xcd RIP: 0033:0x7fcdc0113fd9 Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 c0 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007ffeb8bc67d8 EFLAGS: 00000246 ORIG_RAX: 0000000000000102 RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007fcdc0113fd9 RDX: 0000000000000000 RSI: 0000000020000340 RDI: 0000000000000003 RBP: 00007fcdc00d37a0 R08: 0000000000000000 R09: 00007fcdc00d37a0 R10: 00005555559a72c0 R11: 0000000000000246 R12: 00000000f8008000 R13: 0000000000000000 R14: 00083878000000f8 R15: 0000000000000000 The issue is caused when the value of fsi becomes less than -1. The check to break the loop when fsi value becomes -1 is present but syzbot was able to produce value less than -1 which cause the error. This patch simply add the change for the values less than 0. The patch is tested via syzbot.", "cve_priority": "medium", "cve_public_date": "2024-03-06 07:15:00 UTC" }, { "cve": "CVE-2024-26581", "url": "https://ubuntu.com/security/CVE-2024-26581", "cve_description": "In the Linux kernel, the following vulnerability has been resolved: netfilter: nft_set_rbtree: skip end interval element from gc rbtree lazy gc on insert might collect an end interval element that has been just added in this transactions, skip end interval elements that are not yet active.", "cve_priority": "medium", "cve_public_date": "2024-02-20 13:15:00 UTC" }, { "cve": "CVE-2024-26589", "url": "https://ubuntu.com/security/CVE-2024-26589", "cve_description": "In the Linux kernel, the following vulnerability has been resolved: bpf: Reject variable offset alu on PTR_TO_FLOW_KEYS For PTR_TO_FLOW_KEYS, check_flow_keys_access() only uses fixed off for validation. However, variable offset ptr alu is not prohibited for this ptr kind. So the variable offset is not checked. The following prog is accepted: func#0 @0 0: R1=ctx() R10=fp0 0: (bf) r6 = r1 ; R1=ctx() R6_w=ctx() 1: (79) r7 = *(u64 *)(r6 +144) ; R6_w=ctx() R7_w=flow_keys() 2: (b7) r8 = 1024 ; R8_w=1024 3: (37) r8 /= 1 ; R8_w=scalar() 4: (57) r8 &= 1024 ; R8_w=scalar(smin=smin32=0, smax=umax=smax32=umax32=1024,var_off=(0x0; 0x400)) 5: (0f) r7 += r8 mark_precise: frame0: last_idx 5 first_idx 0 subseq_idx -1 mark_precise: frame0: regs=r8 stack= before 4: (57) r8 &= 1024 mark_precise: frame0: regs=r8 stack= before 3: (37) r8 /= 1 mark_precise: frame0: regs=r8 stack= before 2: (b7) r8 = 1024 6: R7_w=flow_keys(smin=smin32=0,smax=umax=smax32=umax32=1024,var_off =(0x0; 0x400)) R8_w=scalar(smin=smin32=0,smax=umax=smax32=umax32=1024, var_off=(0x0; 0x400)) 6: (79) r0 = *(u64 *)(r7 +0) ; R0_w=scalar() 7: (95) exit This prog loads flow_keys to r7, and adds the variable offset r8 to r7, and finally causes out-of-bounds access: BUG: unable to handle page fault for address: ffffc90014c80038 [...] Call Trace: bpf_dispatcher_nop_func include/linux/bpf.h:1231 [inline] __bpf_prog_run include/linux/filter.h:651 [inline] bpf_prog_run include/linux/filter.h:658 [inline] bpf_prog_run_pin_on_cpu include/linux/filter.h:675 [inline] bpf_flow_dissect+0x15f/0x350 net/core/flow_dissector.c:991 bpf_prog_test_run_flow_dissector+0x39d/0x620 net/bpf/test_run.c:1359 bpf_prog_test_run kernel/bpf/syscall.c:4107 [inline] __sys_bpf+0xf8f/0x4560 kernel/bpf/syscall.c:5475 __do_sys_bpf kernel/bpf/syscall.c:5561 [inline] __se_sys_bpf kernel/bpf/syscall.c:5559 [inline] __x64_sys_bpf+0x73/0xb0 kernel/bpf/syscall.c:5559 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0x3f/0x110 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x63/0x6b Fix this by rejecting ptr alu with variable offset on flow_keys. Applying the patch rejects the program with \"R7 pointer arithmetic on flow_keys prohibited\".", "cve_priority": "medium", "cve_public_date": "2024-02-22 17:15:00 UTC" }, { "cve": "CVE-2024-26591", "url": "https://ubuntu.com/security/CVE-2024-26591", "cve_description": "In the Linux kernel, the following vulnerability has been resolved: bpf: Fix re-attachment branch in bpf_tracing_prog_attach The following case can cause a crash due to missing attach_btf: 1) load rawtp program 2) load fentry program with rawtp as target_fd 3) create tracing link for fentry program with target_fd = 0 4) repeat 3 In the end we have: - prog->aux->dst_trampoline == NULL - tgt_prog == NULL (because we did not provide target_fd to link_create) - prog->aux->attach_btf == NULL (the program was loaded with attach_prog_fd=X) - the program was loaded for tgt_prog but we have no way to find out which one BUG: kernel NULL pointer dereference, address: 0000000000000058 Call Trace: ? __die+0x20/0x70 ? page_fault_oops+0x15b/0x430 ? fixup_exception+0x22/0x330 ? exc_page_fault+0x6f/0x170 ? asm_exc_page_fault+0x22/0x30 ? bpf_tracing_prog_attach+0x279/0x560 ? btf_obj_id+0x5/0x10 bpf_tracing_prog_attach+0x439/0x560 __sys_bpf+0x1cf4/0x2de0 __x64_sys_bpf+0x1c/0x30 do_syscall_64+0x41/0xf0 entry_SYSCALL_64_after_hwframe+0x6e/0x76 Return -EINVAL in this situation.", "cve_priority": "medium", "cve_public_date": "2024-02-22 17:15:00 UTC" } ], "launchpad_bugs_fixed": [ 2059697, 1786013, 2059698, 1786013, 2059706, 1786013, 2059143, 2059284, 2056403, 2056403, 2058808 ], "changes": [ { "cves": [ { "cve": "CVE-2023-52600", "url": "https://ubuntu.com/security/CVE-2023-52600", "cve_description": "In the Linux kernel, the following vulnerability has been resolved: jfs: fix uaf in jfs_evict_inode When the execution of diMount(ipimap) fails, the object ipimap that has been released may be accessed in diFreeSpecial(). Asynchronous ipimap release occurs when rcu_core() calls jfs_free_node(). Therefore, when diMount(ipimap) fails, sbi->ipimap should not be initialized as ipimap.", "cve_priority": "medium", "cve_public_date": "2024-03-06 07:15:00 UTC" }, { "cve": "CVE-2023-52603", "url": "https://ubuntu.com/security/CVE-2023-52603", "cve_description": "In the Linux kernel, the following vulnerability has been resolved: UBSAN: array-index-out-of-bounds in dtSplitRoot Syzkaller reported the following issue: oop0: detected capacity change from 0 to 32768 UBSAN: array-index-out-of-bounds in fs/jfs/jfs_dtree.c:1971:9 index -2 is out of range for type 'struct dtslot [128]' CPU: 0 PID: 3613 Comm: syz-executor270 Not tainted 6.0.0-syzkaller-09423-g493ffd6605b2 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/22/2022 Call Trace: __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0x1b1/0x28e lib/dump_stack.c:106 ubsan_epilogue lib/ubsan.c:151 [inline] __ubsan_handle_out_of_bounds+0xdb/0x130 lib/ubsan.c:283 dtSplitRoot+0x8d8/0x1900 fs/jfs/jfs_dtree.c:1971 dtSplitUp fs/jfs/jfs_dtree.c:985 [inline] dtInsert+0x1189/0x6b80 fs/jfs/jfs_dtree.c:863 jfs_mkdir+0x757/0xb00 fs/jfs/namei.c:270 vfs_mkdir+0x3b3/0x590 fs/namei.c:4013 do_mkdirat+0x279/0x550 fs/namei.c:4038 __do_sys_mkdirat fs/namei.c:4053 [inline] __se_sys_mkdirat fs/namei.c:4051 [inline] __x64_sys_mkdirat+0x85/0x90 fs/namei.c:4051 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x63/0xcd RIP: 0033:0x7fcdc0113fd9 Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 c0 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007ffeb8bc67d8 EFLAGS: 00000246 ORIG_RAX: 0000000000000102 RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007fcdc0113fd9 RDX: 0000000000000000 RSI: 0000000020000340 RDI: 0000000000000003 RBP: 00007fcdc00d37a0 R08: 0000000000000000 R09: 00007fcdc00d37a0 R10: 00005555559a72c0 R11: 0000000000000246 R12: 00000000f8008000 R13: 0000000000000000 R14: 00083878000000f8 R15: 0000000000000000 The issue is caused when the value of fsi becomes less than -1. The check to break the loop when fsi value becomes -1 is present but syzbot was able to produce value less than -1 which cause the error. This patch simply add the change for the values less than 0. The patch is tested via syzbot.", "cve_priority": "medium", "cve_public_date": "2024-03-06 07:15:00 UTC" }, { "cve": "CVE-2024-26581", "url": "https://ubuntu.com/security/CVE-2024-26581", "cve_description": "In the Linux kernel, the following vulnerability has been resolved: netfilter: nft_set_rbtree: skip end interval element from gc rbtree lazy gc on insert might collect an end interval element that has been just added in this transactions, skip end interval elements that are not yet active.", "cve_priority": "medium", "cve_public_date": "2024-02-20 13:15:00 UTC" }, { "cve": "CVE-2024-26589", "url": "https://ubuntu.com/security/CVE-2024-26589", "cve_description": "In the Linux kernel, the following vulnerability has been resolved: bpf: Reject variable offset alu on PTR_TO_FLOW_KEYS For PTR_TO_FLOW_KEYS, check_flow_keys_access() only uses fixed off for validation. However, variable offset ptr alu is not prohibited for this ptr kind. So the variable offset is not checked. The following prog is accepted: func#0 @0 0: R1=ctx() R10=fp0 0: (bf) r6 = r1 ; R1=ctx() R6_w=ctx() 1: (79) r7 = *(u64 *)(r6 +144) ; R6_w=ctx() R7_w=flow_keys() 2: (b7) r8 = 1024 ; R8_w=1024 3: (37) r8 /= 1 ; R8_w=scalar() 4: (57) r8 &= 1024 ; R8_w=scalar(smin=smin32=0, smax=umax=smax32=umax32=1024,var_off=(0x0; 0x400)) 5: (0f) r7 += r8 mark_precise: frame0: last_idx 5 first_idx 0 subseq_idx -1 mark_precise: frame0: regs=r8 stack= before 4: (57) r8 &= 1024 mark_precise: frame0: regs=r8 stack= before 3: (37) r8 /= 1 mark_precise: frame0: regs=r8 stack= before 2: (b7) r8 = 1024 6: R7_w=flow_keys(smin=smin32=0,smax=umax=smax32=umax32=1024,var_off =(0x0; 0x400)) R8_w=scalar(smin=smin32=0,smax=umax=smax32=umax32=1024, var_off=(0x0; 0x400)) 6: (79) r0 = *(u64 *)(r7 +0) ; R0_w=scalar() 7: (95) exit This prog loads flow_keys to r7, and adds the variable offset r8 to r7, and finally causes out-of-bounds access: BUG: unable to handle page fault for address: ffffc90014c80038 [...] Call Trace: bpf_dispatcher_nop_func include/linux/bpf.h:1231 [inline] __bpf_prog_run include/linux/filter.h:651 [inline] bpf_prog_run include/linux/filter.h:658 [inline] bpf_prog_run_pin_on_cpu include/linux/filter.h:675 [inline] bpf_flow_dissect+0x15f/0x350 net/core/flow_dissector.c:991 bpf_prog_test_run_flow_dissector+0x39d/0x620 net/bpf/test_run.c:1359 bpf_prog_test_run kernel/bpf/syscall.c:4107 [inline] __sys_bpf+0xf8f/0x4560 kernel/bpf/syscall.c:5475 __do_sys_bpf kernel/bpf/syscall.c:5561 [inline] __se_sys_bpf kernel/bpf/syscall.c:5559 [inline] __x64_sys_bpf+0x73/0xb0 kernel/bpf/syscall.c:5559 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0x3f/0x110 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x63/0x6b Fix this by rejecting ptr alu with variable offset on flow_keys. Applying the patch rejects the program with \"R7 pointer arithmetic on flow_keys prohibited\".", "cve_priority": "medium", "cve_public_date": "2024-02-22 17:15:00 UTC" }, { "cve": "CVE-2024-26591", "url": "https://ubuntu.com/security/CVE-2024-26591", "cve_description": "In the Linux kernel, the following vulnerability has been resolved: bpf: Fix re-attachment branch in bpf_tracing_prog_attach The following case can cause a crash due to missing attach_btf: 1) load rawtp program 2) load fentry program with rawtp as target_fd 3) create tracing link for fentry program with target_fd = 0 4) repeat 3 In the end we have: - prog->aux->dst_trampoline == NULL - tgt_prog == NULL (because we did not provide target_fd to link_create) - prog->aux->attach_btf == NULL (the program was loaded with attach_prog_fd=X) - the program was loaded for tgt_prog but we have no way to find out which one BUG: kernel NULL pointer dereference, address: 0000000000000058 Call Trace: ? __die+0x20/0x70 ? page_fault_oops+0x15b/0x430 ? fixup_exception+0x22/0x330 ? exc_page_fault+0x6f/0x170 ? asm_exc_page_fault+0x22/0x30 ? bpf_tracing_prog_attach+0x279/0x560 ? btf_obj_id+0x5/0x10 bpf_tracing_prog_attach+0x439/0x560 __sys_bpf+0x1cf4/0x2de0 __x64_sys_bpf+0x1c/0x30 do_syscall_64+0x41/0xf0 entry_SYSCALL_64_after_hwframe+0x6e/0x76 Return -EINVAL in this situation.", "cve_priority": "medium", "cve_public_date": "2024-02-22 17:15:00 UTC" } ], "log": [ "", " * jammy/linux-riscv-6.5: 6.5.0-28.29.1~22.04.1 -proposed tracker", " (LP: #2059697)", "", " * Packaging resync (LP: #1786013)", " - [Packaging] drop getabis data", "", " [ Ubuntu: 6.5.0-28.29.1 ]", "", " * mantic/linux-riscv: 6.5.0-28.29.1 -proposed tracker (LP: #2059698)", " * Packaging resync (LP: #1786013)", " - [Packaging] drop getabis data", " * mantic/linux: 6.5.0-28.29 -proposed tracker (LP: #2059706)", " * Packaging resync (LP: #1786013)", " - [Packaging] drop getabis data", " * Remove getabis scripts (LP: #2059143)", " - [Packaging] Remove getabis", " * CVE-2023-52600", " - jfs: fix uaf in jfs_evict_inode", " * Mantic update: upstream stable patchset 2024-03-27 (LP: #2059284) //", " CVE-2023-52603", " - UBSAN: array-index-out-of-bounds in dtSplitRoot", " * CVE-2024-26581", " - netfilter: nft_set_rbtree: skip end interval element from gc", " * Mantic update: upstream stable patchset 2024-03-07 (LP: #2056403) //", " CVE-2024-26589", " - bpf: Reject variable offset alu on PTR_TO_FLOW_KEYS", " * Mantic update: upstream stable patchset 2024-03-07 (LP: #2056403) //", " CVE-2024-26591", " - bpf: Fix re-attachment branch in bpf_tracing_prog_attach", " * iwlwifi disconnect and crash - intel wifi7 (LP: #2058808)", " - wifi: iwlwifi: pcie: fix RB status reading", "" ], "package": "linux-riscv-6.5", "version": "6.5.0-28.29.1~22.04.1", "urgency": "medium", "distributions": "jammy", "launchpad_bugs_fixed": [ 2059697, 1786013, 2059698, 1786013, 2059706, 1786013, 2059143, 2059284, 2056403, 2056403, 2058808 ], "author": "Hannah Peuckmann ", "date": "Mon, 08 Apr 2024 08:49:19 +0200" } ], "notes": "linux-headers-6.5.0-28-generic version '6.5.0-28.29.1~22.04.1' (source package linux-riscv-6.5 version '6.5.0-28.29.1~22.04.1') was added. linux-headers-6.5.0-28-generic version '6.5.0-28.29.1~22.04.1' has the same source package name, linux-riscv-6.5, as removed package linux-headers-6.5.0-27-generic. As such we can use the source package version of the removed package, '6.5.0-27.28.1~22.04.1', 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.5.0-28-generic", "from_version": { "source_package_name": "linux-riscv-6.5", "source_package_version": "6.5.0-27.28.1~22.04.1", "version": null }, "to_version": { "source_package_name": "linux-riscv-6.5", "source_package_version": "6.5.0-28.29.1~22.04.1", "version": "6.5.0-28.29.1~22.04.1" }, "cves": [ { "cve": "CVE-2023-52600", "url": "https://ubuntu.com/security/CVE-2023-52600", "cve_description": "In the Linux kernel, the following vulnerability has been resolved: jfs: fix uaf in jfs_evict_inode When the execution of diMount(ipimap) fails, the object ipimap that has been released may be accessed in diFreeSpecial(). Asynchronous ipimap release occurs when rcu_core() calls jfs_free_node(). Therefore, when diMount(ipimap) fails, sbi->ipimap should not be initialized as ipimap.", "cve_priority": "medium", "cve_public_date": "2024-03-06 07:15:00 UTC" }, { "cve": "CVE-2023-52603", "url": "https://ubuntu.com/security/CVE-2023-52603", "cve_description": "In the Linux kernel, the following vulnerability has been resolved: UBSAN: array-index-out-of-bounds in dtSplitRoot Syzkaller reported the following issue: oop0: detected capacity change from 0 to 32768 UBSAN: array-index-out-of-bounds in fs/jfs/jfs_dtree.c:1971:9 index -2 is out of range for type 'struct dtslot [128]' CPU: 0 PID: 3613 Comm: syz-executor270 Not tainted 6.0.0-syzkaller-09423-g493ffd6605b2 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/22/2022 Call Trace: __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0x1b1/0x28e lib/dump_stack.c:106 ubsan_epilogue lib/ubsan.c:151 [inline] __ubsan_handle_out_of_bounds+0xdb/0x130 lib/ubsan.c:283 dtSplitRoot+0x8d8/0x1900 fs/jfs/jfs_dtree.c:1971 dtSplitUp fs/jfs/jfs_dtree.c:985 [inline] dtInsert+0x1189/0x6b80 fs/jfs/jfs_dtree.c:863 jfs_mkdir+0x757/0xb00 fs/jfs/namei.c:270 vfs_mkdir+0x3b3/0x590 fs/namei.c:4013 do_mkdirat+0x279/0x550 fs/namei.c:4038 __do_sys_mkdirat fs/namei.c:4053 [inline] __se_sys_mkdirat fs/namei.c:4051 [inline] __x64_sys_mkdirat+0x85/0x90 fs/namei.c:4051 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x63/0xcd RIP: 0033:0x7fcdc0113fd9 Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 c0 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007ffeb8bc67d8 EFLAGS: 00000246 ORIG_RAX: 0000000000000102 RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007fcdc0113fd9 RDX: 0000000000000000 RSI: 0000000020000340 RDI: 0000000000000003 RBP: 00007fcdc00d37a0 R08: 0000000000000000 R09: 00007fcdc00d37a0 R10: 00005555559a72c0 R11: 0000000000000246 R12: 00000000f8008000 R13: 0000000000000000 R14: 00083878000000f8 R15: 0000000000000000 The issue is caused when the value of fsi becomes less than -1. The check to break the loop when fsi value becomes -1 is present but syzbot was able to produce value less than -1 which cause the error. This patch simply add the change for the values less than 0. The patch is tested via syzbot.", "cve_priority": "medium", "cve_public_date": "2024-03-06 07:15:00 UTC" }, { "cve": "CVE-2024-26581", "url": "https://ubuntu.com/security/CVE-2024-26581", "cve_description": "In the Linux kernel, the following vulnerability has been resolved: netfilter: nft_set_rbtree: skip end interval element from gc rbtree lazy gc on insert might collect an end interval element that has been just added in this transactions, skip end interval elements that are not yet active.", "cve_priority": "medium", "cve_public_date": "2024-02-20 13:15:00 UTC" }, { "cve": "CVE-2024-26589", "url": "https://ubuntu.com/security/CVE-2024-26589", "cve_description": "In the Linux kernel, the following vulnerability has been resolved: bpf: Reject variable offset alu on PTR_TO_FLOW_KEYS For PTR_TO_FLOW_KEYS, check_flow_keys_access() only uses fixed off for validation. However, variable offset ptr alu is not prohibited for this ptr kind. So the variable offset is not checked. The following prog is accepted: func#0 @0 0: R1=ctx() R10=fp0 0: (bf) r6 = r1 ; R1=ctx() R6_w=ctx() 1: (79) r7 = *(u64 *)(r6 +144) ; R6_w=ctx() R7_w=flow_keys() 2: (b7) r8 = 1024 ; R8_w=1024 3: (37) r8 /= 1 ; R8_w=scalar() 4: (57) r8 &= 1024 ; R8_w=scalar(smin=smin32=0, smax=umax=smax32=umax32=1024,var_off=(0x0; 0x400)) 5: (0f) r7 += r8 mark_precise: frame0: last_idx 5 first_idx 0 subseq_idx -1 mark_precise: frame0: regs=r8 stack= before 4: (57) r8 &= 1024 mark_precise: frame0: regs=r8 stack= before 3: (37) r8 /= 1 mark_precise: frame0: regs=r8 stack= before 2: (b7) r8 = 1024 6: R7_w=flow_keys(smin=smin32=0,smax=umax=smax32=umax32=1024,var_off =(0x0; 0x400)) R8_w=scalar(smin=smin32=0,smax=umax=smax32=umax32=1024, var_off=(0x0; 0x400)) 6: (79) r0 = *(u64 *)(r7 +0) ; R0_w=scalar() 7: (95) exit This prog loads flow_keys to r7, and adds the variable offset r8 to r7, and finally causes out-of-bounds access: BUG: unable to handle page fault for address: ffffc90014c80038 [...] Call Trace: bpf_dispatcher_nop_func include/linux/bpf.h:1231 [inline] __bpf_prog_run include/linux/filter.h:651 [inline] bpf_prog_run include/linux/filter.h:658 [inline] bpf_prog_run_pin_on_cpu include/linux/filter.h:675 [inline] bpf_flow_dissect+0x15f/0x350 net/core/flow_dissector.c:991 bpf_prog_test_run_flow_dissector+0x39d/0x620 net/bpf/test_run.c:1359 bpf_prog_test_run kernel/bpf/syscall.c:4107 [inline] __sys_bpf+0xf8f/0x4560 kernel/bpf/syscall.c:5475 __do_sys_bpf kernel/bpf/syscall.c:5561 [inline] __se_sys_bpf kernel/bpf/syscall.c:5559 [inline] __x64_sys_bpf+0x73/0xb0 kernel/bpf/syscall.c:5559 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0x3f/0x110 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x63/0x6b Fix this by rejecting ptr alu with variable offset on flow_keys. Applying the patch rejects the program with \"R7 pointer arithmetic on flow_keys prohibited\".", "cve_priority": "medium", "cve_public_date": "2024-02-22 17:15:00 UTC" }, { "cve": "CVE-2024-26591", "url": "https://ubuntu.com/security/CVE-2024-26591", "cve_description": "In the Linux kernel, the following vulnerability has been resolved: bpf: Fix re-attachment branch in bpf_tracing_prog_attach The following case can cause a crash due to missing attach_btf: 1) load rawtp program 2) load fentry program with rawtp as target_fd 3) create tracing link for fentry program with target_fd = 0 4) repeat 3 In the end we have: - prog->aux->dst_trampoline == NULL - tgt_prog == NULL (because we did not provide target_fd to link_create) - prog->aux->attach_btf == NULL (the program was loaded with attach_prog_fd=X) - the program was loaded for tgt_prog but we have no way to find out which one BUG: kernel NULL pointer dereference, address: 0000000000000058 Call Trace: ? __die+0x20/0x70 ? page_fault_oops+0x15b/0x430 ? fixup_exception+0x22/0x330 ? exc_page_fault+0x6f/0x170 ? asm_exc_page_fault+0x22/0x30 ? bpf_tracing_prog_attach+0x279/0x560 ? btf_obj_id+0x5/0x10 bpf_tracing_prog_attach+0x439/0x560 __sys_bpf+0x1cf4/0x2de0 __x64_sys_bpf+0x1c/0x30 do_syscall_64+0x41/0xf0 entry_SYSCALL_64_after_hwframe+0x6e/0x76 Return -EINVAL in this situation.", "cve_priority": "medium", "cve_public_date": "2024-02-22 17:15:00 UTC" } ], "launchpad_bugs_fixed": [ 2059697, 1786013, 2059698, 1786013, 2059706, 1786013, 2059143, 2059284, 2056403, 2056403, 2058808 ], "changes": [ { "cves": [ { "cve": "CVE-2023-52600", "url": "https://ubuntu.com/security/CVE-2023-52600", "cve_description": "In the Linux kernel, the following vulnerability has been resolved: jfs: fix uaf in jfs_evict_inode When the execution of diMount(ipimap) fails, the object ipimap that has been released may be accessed in diFreeSpecial(). Asynchronous ipimap release occurs when rcu_core() calls jfs_free_node(). Therefore, when diMount(ipimap) fails, sbi->ipimap should not be initialized as ipimap.", "cve_priority": "medium", "cve_public_date": "2024-03-06 07:15:00 UTC" }, { "cve": "CVE-2023-52603", "url": "https://ubuntu.com/security/CVE-2023-52603", "cve_description": "In the Linux kernel, the following vulnerability has been resolved: UBSAN: array-index-out-of-bounds in dtSplitRoot Syzkaller reported the following issue: oop0: detected capacity change from 0 to 32768 UBSAN: array-index-out-of-bounds in fs/jfs/jfs_dtree.c:1971:9 index -2 is out of range for type 'struct dtslot [128]' CPU: 0 PID: 3613 Comm: syz-executor270 Not tainted 6.0.0-syzkaller-09423-g493ffd6605b2 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/22/2022 Call Trace: __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0x1b1/0x28e lib/dump_stack.c:106 ubsan_epilogue lib/ubsan.c:151 [inline] __ubsan_handle_out_of_bounds+0xdb/0x130 lib/ubsan.c:283 dtSplitRoot+0x8d8/0x1900 fs/jfs/jfs_dtree.c:1971 dtSplitUp fs/jfs/jfs_dtree.c:985 [inline] dtInsert+0x1189/0x6b80 fs/jfs/jfs_dtree.c:863 jfs_mkdir+0x757/0xb00 fs/jfs/namei.c:270 vfs_mkdir+0x3b3/0x590 fs/namei.c:4013 do_mkdirat+0x279/0x550 fs/namei.c:4038 __do_sys_mkdirat fs/namei.c:4053 [inline] __se_sys_mkdirat fs/namei.c:4051 [inline] __x64_sys_mkdirat+0x85/0x90 fs/namei.c:4051 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x63/0xcd RIP: 0033:0x7fcdc0113fd9 Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 c0 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007ffeb8bc67d8 EFLAGS: 00000246 ORIG_RAX: 0000000000000102 RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007fcdc0113fd9 RDX: 0000000000000000 RSI: 0000000020000340 RDI: 0000000000000003 RBP: 00007fcdc00d37a0 R08: 0000000000000000 R09: 00007fcdc00d37a0 R10: 00005555559a72c0 R11: 0000000000000246 R12: 00000000f8008000 R13: 0000000000000000 R14: 00083878000000f8 R15: 0000000000000000 The issue is caused when the value of fsi becomes less than -1. The check to break the loop when fsi value becomes -1 is present but syzbot was able to produce value less than -1 which cause the error. This patch simply add the change for the values less than 0. The patch is tested via syzbot.", "cve_priority": "medium", "cve_public_date": "2024-03-06 07:15:00 UTC" }, { "cve": "CVE-2024-26581", "url": "https://ubuntu.com/security/CVE-2024-26581", "cve_description": "In the Linux kernel, the following vulnerability has been resolved: netfilter: nft_set_rbtree: skip end interval element from gc rbtree lazy gc on insert might collect an end interval element that has been just added in this transactions, skip end interval elements that are not yet active.", "cve_priority": "medium", "cve_public_date": "2024-02-20 13:15:00 UTC" }, { "cve": "CVE-2024-26589", "url": "https://ubuntu.com/security/CVE-2024-26589", "cve_description": "In the Linux kernel, the following vulnerability has been resolved: bpf: Reject variable offset alu on PTR_TO_FLOW_KEYS For PTR_TO_FLOW_KEYS, check_flow_keys_access() only uses fixed off for validation. However, variable offset ptr alu is not prohibited for this ptr kind. So the variable offset is not checked. The following prog is accepted: func#0 @0 0: R1=ctx() R10=fp0 0: (bf) r6 = r1 ; R1=ctx() R6_w=ctx() 1: (79) r7 = *(u64 *)(r6 +144) ; R6_w=ctx() R7_w=flow_keys() 2: (b7) r8 = 1024 ; R8_w=1024 3: (37) r8 /= 1 ; R8_w=scalar() 4: (57) r8 &= 1024 ; R8_w=scalar(smin=smin32=0, smax=umax=smax32=umax32=1024,var_off=(0x0; 0x400)) 5: (0f) r7 += r8 mark_precise: frame0: last_idx 5 first_idx 0 subseq_idx -1 mark_precise: frame0: regs=r8 stack= before 4: (57) r8 &= 1024 mark_precise: frame0: regs=r8 stack= before 3: (37) r8 /= 1 mark_precise: frame0: regs=r8 stack= before 2: (b7) r8 = 1024 6: R7_w=flow_keys(smin=smin32=0,smax=umax=smax32=umax32=1024,var_off =(0x0; 0x400)) R8_w=scalar(smin=smin32=0,smax=umax=smax32=umax32=1024, var_off=(0x0; 0x400)) 6: (79) r0 = *(u64 *)(r7 +0) ; R0_w=scalar() 7: (95) exit This prog loads flow_keys to r7, and adds the variable offset r8 to r7, and finally causes out-of-bounds access: BUG: unable to handle page fault for address: ffffc90014c80038 [...] Call Trace: bpf_dispatcher_nop_func include/linux/bpf.h:1231 [inline] __bpf_prog_run include/linux/filter.h:651 [inline] bpf_prog_run include/linux/filter.h:658 [inline] bpf_prog_run_pin_on_cpu include/linux/filter.h:675 [inline] bpf_flow_dissect+0x15f/0x350 net/core/flow_dissector.c:991 bpf_prog_test_run_flow_dissector+0x39d/0x620 net/bpf/test_run.c:1359 bpf_prog_test_run kernel/bpf/syscall.c:4107 [inline] __sys_bpf+0xf8f/0x4560 kernel/bpf/syscall.c:5475 __do_sys_bpf kernel/bpf/syscall.c:5561 [inline] __se_sys_bpf kernel/bpf/syscall.c:5559 [inline] __x64_sys_bpf+0x73/0xb0 kernel/bpf/syscall.c:5559 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0x3f/0x110 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x63/0x6b Fix this by rejecting ptr alu with variable offset on flow_keys. Applying the patch rejects the program with \"R7 pointer arithmetic on flow_keys prohibited\".", "cve_priority": "medium", "cve_public_date": "2024-02-22 17:15:00 UTC" }, { "cve": "CVE-2024-26591", "url": "https://ubuntu.com/security/CVE-2024-26591", "cve_description": "In the Linux kernel, the following vulnerability has been resolved: bpf: Fix re-attachment branch in bpf_tracing_prog_attach The following case can cause a crash due to missing attach_btf: 1) load rawtp program 2) load fentry program with rawtp as target_fd 3) create tracing link for fentry program with target_fd = 0 4) repeat 3 In the end we have: - prog->aux->dst_trampoline == NULL - tgt_prog == NULL (because we did not provide target_fd to link_create) - prog->aux->attach_btf == NULL (the program was loaded with attach_prog_fd=X) - the program was loaded for tgt_prog but we have no way to find out which one BUG: kernel NULL pointer dereference, address: 0000000000000058 Call Trace: ? __die+0x20/0x70 ? page_fault_oops+0x15b/0x430 ? fixup_exception+0x22/0x330 ? exc_page_fault+0x6f/0x170 ? asm_exc_page_fault+0x22/0x30 ? bpf_tracing_prog_attach+0x279/0x560 ? btf_obj_id+0x5/0x10 bpf_tracing_prog_attach+0x439/0x560 __sys_bpf+0x1cf4/0x2de0 __x64_sys_bpf+0x1c/0x30 do_syscall_64+0x41/0xf0 entry_SYSCALL_64_after_hwframe+0x6e/0x76 Return -EINVAL in this situation.", "cve_priority": "medium", "cve_public_date": "2024-02-22 17:15:00 UTC" } ], "log": [ "", " * jammy/linux-riscv-6.5: 6.5.0-28.29.1~22.04.1 -proposed tracker", " (LP: #2059697)", "", " * Packaging resync (LP: #1786013)", " - [Packaging] drop getabis data", "", " [ Ubuntu: 6.5.0-28.29.1 ]", "", " * mantic/linux-riscv: 6.5.0-28.29.1 -proposed tracker (LP: #2059698)", " * Packaging resync (LP: #1786013)", " - [Packaging] drop getabis data", " * mantic/linux: 6.5.0-28.29 -proposed tracker (LP: #2059706)", " * Packaging resync (LP: #1786013)", " - [Packaging] drop getabis data", " * Remove getabis scripts (LP: #2059143)", " - [Packaging] Remove getabis", " * CVE-2023-52600", " - jfs: fix uaf in jfs_evict_inode", " * Mantic update: upstream stable patchset 2024-03-27 (LP: #2059284) //", " CVE-2023-52603", " - UBSAN: array-index-out-of-bounds in dtSplitRoot", " * CVE-2024-26581", " - netfilter: nft_set_rbtree: skip end interval element from gc", " * Mantic update: upstream stable patchset 2024-03-07 (LP: #2056403) //", " CVE-2024-26589", " - bpf: Reject variable offset alu on PTR_TO_FLOW_KEYS", " * Mantic update: upstream stable patchset 2024-03-07 (LP: #2056403) //", " CVE-2024-26591", " - bpf: Fix re-attachment branch in bpf_tracing_prog_attach", " * iwlwifi disconnect and crash - intel wifi7 (LP: #2058808)", " - wifi: iwlwifi: pcie: fix RB status reading", "" ], "package": "linux-riscv-6.5", "version": "6.5.0-28.29.1~22.04.1", "urgency": "medium", "distributions": "jammy", "launchpad_bugs_fixed": [ 2059697, 1786013, 2059698, 1786013, 2059706, 1786013, 2059143, 2059284, 2056403, 2056403, 2058808 ], "author": "Hannah Peuckmann ", "date": "Mon, 08 Apr 2024 08:49:19 +0200" } ], "notes": "linux-image-6.5.0-28-generic version '6.5.0-28.29.1~22.04.1' (source package linux-riscv-6.5 version '6.5.0-28.29.1~22.04.1') was added. linux-image-6.5.0-28-generic version '6.5.0-28.29.1~22.04.1' has the same source package name, linux-riscv-6.5, as removed package linux-headers-6.5.0-27-generic. As such we can use the source package version of the removed package, '6.5.0-27.28.1~22.04.1', 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.5.0-28-generic", "from_version": { "source_package_name": "linux-riscv-6.5", "source_package_version": "6.5.0-27.28.1~22.04.1", "version": null }, "to_version": { "source_package_name": "linux-riscv-6.5", "source_package_version": "6.5.0-28.29.1~22.04.1", "version": "6.5.0-28.29.1~22.04.1" }, "cves": [ { "cve": "CVE-2023-52600", "url": "https://ubuntu.com/security/CVE-2023-52600", "cve_description": "In the Linux kernel, the following vulnerability has been resolved: jfs: fix uaf in jfs_evict_inode When the execution of diMount(ipimap) fails, the object ipimap that has been released may be accessed in diFreeSpecial(). Asynchronous ipimap release occurs when rcu_core() calls jfs_free_node(). Therefore, when diMount(ipimap) fails, sbi->ipimap should not be initialized as ipimap.", "cve_priority": "medium", "cve_public_date": "2024-03-06 07:15:00 UTC" }, { "cve": "CVE-2023-52603", "url": "https://ubuntu.com/security/CVE-2023-52603", "cve_description": "In the Linux kernel, the following vulnerability has been resolved: UBSAN: array-index-out-of-bounds in dtSplitRoot Syzkaller reported the following issue: oop0: detected capacity change from 0 to 32768 UBSAN: array-index-out-of-bounds in fs/jfs/jfs_dtree.c:1971:9 index -2 is out of range for type 'struct dtslot [128]' CPU: 0 PID: 3613 Comm: syz-executor270 Not tainted 6.0.0-syzkaller-09423-g493ffd6605b2 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/22/2022 Call Trace: __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0x1b1/0x28e lib/dump_stack.c:106 ubsan_epilogue lib/ubsan.c:151 [inline] __ubsan_handle_out_of_bounds+0xdb/0x130 lib/ubsan.c:283 dtSplitRoot+0x8d8/0x1900 fs/jfs/jfs_dtree.c:1971 dtSplitUp fs/jfs/jfs_dtree.c:985 [inline] dtInsert+0x1189/0x6b80 fs/jfs/jfs_dtree.c:863 jfs_mkdir+0x757/0xb00 fs/jfs/namei.c:270 vfs_mkdir+0x3b3/0x590 fs/namei.c:4013 do_mkdirat+0x279/0x550 fs/namei.c:4038 __do_sys_mkdirat fs/namei.c:4053 [inline] __se_sys_mkdirat fs/namei.c:4051 [inline] __x64_sys_mkdirat+0x85/0x90 fs/namei.c:4051 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x63/0xcd RIP: 0033:0x7fcdc0113fd9 Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 c0 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007ffeb8bc67d8 EFLAGS: 00000246 ORIG_RAX: 0000000000000102 RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007fcdc0113fd9 RDX: 0000000000000000 RSI: 0000000020000340 RDI: 0000000000000003 RBP: 00007fcdc00d37a0 R08: 0000000000000000 R09: 00007fcdc00d37a0 R10: 00005555559a72c0 R11: 0000000000000246 R12: 00000000f8008000 R13: 0000000000000000 R14: 00083878000000f8 R15: 0000000000000000 The issue is caused when the value of fsi becomes less than -1. The check to break the loop when fsi value becomes -1 is present but syzbot was able to produce value less than -1 which cause the error. This patch simply add the change for the values less than 0. The patch is tested via syzbot.", "cve_priority": "medium", "cve_public_date": "2024-03-06 07:15:00 UTC" }, { "cve": "CVE-2024-26581", "url": "https://ubuntu.com/security/CVE-2024-26581", "cve_description": "In the Linux kernel, the following vulnerability has been resolved: netfilter: nft_set_rbtree: skip end interval element from gc rbtree lazy gc on insert might collect an end interval element that has been just added in this transactions, skip end interval elements that are not yet active.", "cve_priority": "medium", "cve_public_date": "2024-02-20 13:15:00 UTC" }, { "cve": "CVE-2024-26589", "url": "https://ubuntu.com/security/CVE-2024-26589", "cve_description": "In the Linux kernel, the following vulnerability has been resolved: bpf: Reject variable offset alu on PTR_TO_FLOW_KEYS For PTR_TO_FLOW_KEYS, check_flow_keys_access() only uses fixed off for validation. However, variable offset ptr alu is not prohibited for this ptr kind. So the variable offset is not checked. The following prog is accepted: func#0 @0 0: R1=ctx() R10=fp0 0: (bf) r6 = r1 ; R1=ctx() R6_w=ctx() 1: (79) r7 = *(u64 *)(r6 +144) ; R6_w=ctx() R7_w=flow_keys() 2: (b7) r8 = 1024 ; R8_w=1024 3: (37) r8 /= 1 ; R8_w=scalar() 4: (57) r8 &= 1024 ; R8_w=scalar(smin=smin32=0, smax=umax=smax32=umax32=1024,var_off=(0x0; 0x400)) 5: (0f) r7 += r8 mark_precise: frame0: last_idx 5 first_idx 0 subseq_idx -1 mark_precise: frame0: regs=r8 stack= before 4: (57) r8 &= 1024 mark_precise: frame0: regs=r8 stack= before 3: (37) r8 /= 1 mark_precise: frame0: regs=r8 stack= before 2: (b7) r8 = 1024 6: R7_w=flow_keys(smin=smin32=0,smax=umax=smax32=umax32=1024,var_off =(0x0; 0x400)) R8_w=scalar(smin=smin32=0,smax=umax=smax32=umax32=1024, var_off=(0x0; 0x400)) 6: (79) r0 = *(u64 *)(r7 +0) ; R0_w=scalar() 7: (95) exit This prog loads flow_keys to r7, and adds the variable offset r8 to r7, and finally causes out-of-bounds access: BUG: unable to handle page fault for address: ffffc90014c80038 [...] Call Trace: bpf_dispatcher_nop_func include/linux/bpf.h:1231 [inline] __bpf_prog_run include/linux/filter.h:651 [inline] bpf_prog_run include/linux/filter.h:658 [inline] bpf_prog_run_pin_on_cpu include/linux/filter.h:675 [inline] bpf_flow_dissect+0x15f/0x350 net/core/flow_dissector.c:991 bpf_prog_test_run_flow_dissector+0x39d/0x620 net/bpf/test_run.c:1359 bpf_prog_test_run kernel/bpf/syscall.c:4107 [inline] __sys_bpf+0xf8f/0x4560 kernel/bpf/syscall.c:5475 __do_sys_bpf kernel/bpf/syscall.c:5561 [inline] __se_sys_bpf kernel/bpf/syscall.c:5559 [inline] __x64_sys_bpf+0x73/0xb0 kernel/bpf/syscall.c:5559 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0x3f/0x110 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x63/0x6b Fix this by rejecting ptr alu with variable offset on flow_keys. Applying the patch rejects the program with \"R7 pointer arithmetic on flow_keys prohibited\".", "cve_priority": "medium", "cve_public_date": "2024-02-22 17:15:00 UTC" }, { "cve": "CVE-2024-26591", "url": "https://ubuntu.com/security/CVE-2024-26591", "cve_description": "In the Linux kernel, the following vulnerability has been resolved: bpf: Fix re-attachment branch in bpf_tracing_prog_attach The following case can cause a crash due to missing attach_btf: 1) load rawtp program 2) load fentry program with rawtp as target_fd 3) create tracing link for fentry program with target_fd = 0 4) repeat 3 In the end we have: - prog->aux->dst_trampoline == NULL - tgt_prog == NULL (because we did not provide target_fd to link_create) - prog->aux->attach_btf == NULL (the program was loaded with attach_prog_fd=X) - the program was loaded for tgt_prog but we have no way to find out which one BUG: kernel NULL pointer dereference, address: 0000000000000058 Call Trace: ? __die+0x20/0x70 ? page_fault_oops+0x15b/0x430 ? fixup_exception+0x22/0x330 ? exc_page_fault+0x6f/0x170 ? asm_exc_page_fault+0x22/0x30 ? bpf_tracing_prog_attach+0x279/0x560 ? btf_obj_id+0x5/0x10 bpf_tracing_prog_attach+0x439/0x560 __sys_bpf+0x1cf4/0x2de0 __x64_sys_bpf+0x1c/0x30 do_syscall_64+0x41/0xf0 entry_SYSCALL_64_after_hwframe+0x6e/0x76 Return -EINVAL in this situation.", "cve_priority": "medium", "cve_public_date": "2024-02-22 17:15:00 UTC" } ], "launchpad_bugs_fixed": [ 2059697, 1786013, 2059698, 1786013, 2059706, 1786013, 2059143, 2059284, 2056403, 2056403, 2058808 ], "changes": [ { "cves": [ { "cve": "CVE-2023-52600", "url": "https://ubuntu.com/security/CVE-2023-52600", "cve_description": "In the Linux kernel, the following vulnerability has been resolved: jfs: fix uaf in jfs_evict_inode When the execution of diMount(ipimap) fails, the object ipimap that has been released may be accessed in diFreeSpecial(). Asynchronous ipimap release occurs when rcu_core() calls jfs_free_node(). Therefore, when diMount(ipimap) fails, sbi->ipimap should not be initialized as ipimap.", "cve_priority": "medium", "cve_public_date": "2024-03-06 07:15:00 UTC" }, { "cve": "CVE-2023-52603", "url": "https://ubuntu.com/security/CVE-2023-52603", "cve_description": "In the Linux kernel, the following vulnerability has been resolved: UBSAN: array-index-out-of-bounds in dtSplitRoot Syzkaller reported the following issue: oop0: detected capacity change from 0 to 32768 UBSAN: array-index-out-of-bounds in fs/jfs/jfs_dtree.c:1971:9 index -2 is out of range for type 'struct dtslot [128]' CPU: 0 PID: 3613 Comm: syz-executor270 Not tainted 6.0.0-syzkaller-09423-g493ffd6605b2 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/22/2022 Call Trace: __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0x1b1/0x28e lib/dump_stack.c:106 ubsan_epilogue lib/ubsan.c:151 [inline] __ubsan_handle_out_of_bounds+0xdb/0x130 lib/ubsan.c:283 dtSplitRoot+0x8d8/0x1900 fs/jfs/jfs_dtree.c:1971 dtSplitUp fs/jfs/jfs_dtree.c:985 [inline] dtInsert+0x1189/0x6b80 fs/jfs/jfs_dtree.c:863 jfs_mkdir+0x757/0xb00 fs/jfs/namei.c:270 vfs_mkdir+0x3b3/0x590 fs/namei.c:4013 do_mkdirat+0x279/0x550 fs/namei.c:4038 __do_sys_mkdirat fs/namei.c:4053 [inline] __se_sys_mkdirat fs/namei.c:4051 [inline] __x64_sys_mkdirat+0x85/0x90 fs/namei.c:4051 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x63/0xcd RIP: 0033:0x7fcdc0113fd9 Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 c0 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007ffeb8bc67d8 EFLAGS: 00000246 ORIG_RAX: 0000000000000102 RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007fcdc0113fd9 RDX: 0000000000000000 RSI: 0000000020000340 RDI: 0000000000000003 RBP: 00007fcdc00d37a0 R08: 0000000000000000 R09: 00007fcdc00d37a0 R10: 00005555559a72c0 R11: 0000000000000246 R12: 00000000f8008000 R13: 0000000000000000 R14: 00083878000000f8 R15: 0000000000000000 The issue is caused when the value of fsi becomes less than -1. The check to break the loop when fsi value becomes -1 is present but syzbot was able to produce value less than -1 which cause the error. This patch simply add the change for the values less than 0. The patch is tested via syzbot.", "cve_priority": "medium", "cve_public_date": "2024-03-06 07:15:00 UTC" }, { "cve": "CVE-2024-26581", "url": "https://ubuntu.com/security/CVE-2024-26581", "cve_description": "In the Linux kernel, the following vulnerability has been resolved: netfilter: nft_set_rbtree: skip end interval element from gc rbtree lazy gc on insert might collect an end interval element that has been just added in this transactions, skip end interval elements that are not yet active.", "cve_priority": "medium", "cve_public_date": "2024-02-20 13:15:00 UTC" }, { "cve": "CVE-2024-26589", "url": "https://ubuntu.com/security/CVE-2024-26589", "cve_description": "In the Linux kernel, the following vulnerability has been resolved: bpf: Reject variable offset alu on PTR_TO_FLOW_KEYS For PTR_TO_FLOW_KEYS, check_flow_keys_access() only uses fixed off for validation. However, variable offset ptr alu is not prohibited for this ptr kind. So the variable offset is not checked. The following prog is accepted: func#0 @0 0: R1=ctx() R10=fp0 0: (bf) r6 = r1 ; R1=ctx() R6_w=ctx() 1: (79) r7 = *(u64 *)(r6 +144) ; R6_w=ctx() R7_w=flow_keys() 2: (b7) r8 = 1024 ; R8_w=1024 3: (37) r8 /= 1 ; R8_w=scalar() 4: (57) r8 &= 1024 ; R8_w=scalar(smin=smin32=0, smax=umax=smax32=umax32=1024,var_off=(0x0; 0x400)) 5: (0f) r7 += r8 mark_precise: frame0: last_idx 5 first_idx 0 subseq_idx -1 mark_precise: frame0: regs=r8 stack= before 4: (57) r8 &= 1024 mark_precise: frame0: regs=r8 stack= before 3: (37) r8 /= 1 mark_precise: frame0: regs=r8 stack= before 2: (b7) r8 = 1024 6: R7_w=flow_keys(smin=smin32=0,smax=umax=smax32=umax32=1024,var_off =(0x0; 0x400)) R8_w=scalar(smin=smin32=0,smax=umax=smax32=umax32=1024, var_off=(0x0; 0x400)) 6: (79) r0 = *(u64 *)(r7 +0) ; R0_w=scalar() 7: (95) exit This prog loads flow_keys to r7, and adds the variable offset r8 to r7, and finally causes out-of-bounds access: BUG: unable to handle page fault for address: ffffc90014c80038 [...] Call Trace: bpf_dispatcher_nop_func include/linux/bpf.h:1231 [inline] __bpf_prog_run include/linux/filter.h:651 [inline] bpf_prog_run include/linux/filter.h:658 [inline] bpf_prog_run_pin_on_cpu include/linux/filter.h:675 [inline] bpf_flow_dissect+0x15f/0x350 net/core/flow_dissector.c:991 bpf_prog_test_run_flow_dissector+0x39d/0x620 net/bpf/test_run.c:1359 bpf_prog_test_run kernel/bpf/syscall.c:4107 [inline] __sys_bpf+0xf8f/0x4560 kernel/bpf/syscall.c:5475 __do_sys_bpf kernel/bpf/syscall.c:5561 [inline] __se_sys_bpf kernel/bpf/syscall.c:5559 [inline] __x64_sys_bpf+0x73/0xb0 kernel/bpf/syscall.c:5559 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0x3f/0x110 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x63/0x6b Fix this by rejecting ptr alu with variable offset on flow_keys. Applying the patch rejects the program with \"R7 pointer arithmetic on flow_keys prohibited\".", "cve_priority": "medium", "cve_public_date": "2024-02-22 17:15:00 UTC" }, { "cve": "CVE-2024-26591", "url": "https://ubuntu.com/security/CVE-2024-26591", "cve_description": "In the Linux kernel, the following vulnerability has been resolved: bpf: Fix re-attachment branch in bpf_tracing_prog_attach The following case can cause a crash due to missing attach_btf: 1) load rawtp program 2) load fentry program with rawtp as target_fd 3) create tracing link for fentry program with target_fd = 0 4) repeat 3 In the end we have: - prog->aux->dst_trampoline == NULL - tgt_prog == NULL (because we did not provide target_fd to link_create) - prog->aux->attach_btf == NULL (the program was loaded with attach_prog_fd=X) - the program was loaded for tgt_prog but we have no way to find out which one BUG: kernel NULL pointer dereference, address: 0000000000000058 Call Trace: ? __die+0x20/0x70 ? page_fault_oops+0x15b/0x430 ? fixup_exception+0x22/0x330 ? exc_page_fault+0x6f/0x170 ? asm_exc_page_fault+0x22/0x30 ? bpf_tracing_prog_attach+0x279/0x560 ? btf_obj_id+0x5/0x10 bpf_tracing_prog_attach+0x439/0x560 __sys_bpf+0x1cf4/0x2de0 __x64_sys_bpf+0x1c/0x30 do_syscall_64+0x41/0xf0 entry_SYSCALL_64_after_hwframe+0x6e/0x76 Return -EINVAL in this situation.", "cve_priority": "medium", "cve_public_date": "2024-02-22 17:15:00 UTC" } ], "log": [ "", " * jammy/linux-riscv-6.5: 6.5.0-28.29.1~22.04.1 -proposed tracker", " (LP: #2059697)", "", " * Packaging resync (LP: #1786013)", " - [Packaging] drop getabis data", "", " [ Ubuntu: 6.5.0-28.29.1 ]", "", " * mantic/linux-riscv: 6.5.0-28.29.1 -proposed tracker (LP: #2059698)", " * Packaging resync (LP: #1786013)", " - [Packaging] drop getabis data", " * mantic/linux: 6.5.0-28.29 -proposed tracker (LP: #2059706)", " * Packaging resync (LP: #1786013)", " - [Packaging] drop getabis data", " * Remove getabis scripts (LP: #2059143)", " - [Packaging] Remove getabis", " * CVE-2023-52600", " - jfs: fix uaf in jfs_evict_inode", " * Mantic update: upstream stable patchset 2024-03-27 (LP: #2059284) //", " CVE-2023-52603", " - UBSAN: array-index-out-of-bounds in dtSplitRoot", " * CVE-2024-26581", " - netfilter: nft_set_rbtree: skip end interval element from gc", " * Mantic update: upstream stable patchset 2024-03-07 (LP: #2056403) //", " CVE-2024-26589", " - bpf: Reject variable offset alu on PTR_TO_FLOW_KEYS", " * Mantic update: upstream stable patchset 2024-03-07 (LP: #2056403) //", " CVE-2024-26591", " - bpf: Fix re-attachment branch in bpf_tracing_prog_attach", " * iwlwifi disconnect and crash - intel wifi7 (LP: #2058808)", " - wifi: iwlwifi: pcie: fix RB status reading", "" ], "package": "linux-riscv-6.5", "version": "6.5.0-28.29.1~22.04.1", "urgency": "medium", "distributions": "jammy", "launchpad_bugs_fixed": [ 2059697, 1786013, 2059698, 1786013, 2059706, 1786013, 2059143, 2059284, 2056403, 2056403, 2058808 ], "author": "Hannah Peuckmann ", "date": "Mon, 08 Apr 2024 08:49:19 +0200" } ], "notes": "linux-modules-6.5.0-28-generic version '6.5.0-28.29.1~22.04.1' (source package linux-riscv-6.5 version '6.5.0-28.29.1~22.04.1') was added. linux-modules-6.5.0-28-generic version '6.5.0-28.29.1~22.04.1' has the same source package name, linux-riscv-6.5, as removed package linux-headers-6.5.0-27-generic. As such we can use the source package version of the removed package, '6.5.0-27.28.1~22.04.1', 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-riscv-6.5-headers-6.5.0-28", "from_version": { "source_package_name": "linux-riscv-6.5", "source_package_version": "6.5.0-27.28.1~22.04.1", "version": null }, "to_version": { "source_package_name": "linux-riscv-6.5", "source_package_version": "6.5.0-28.29.1~22.04.1", "version": "6.5.0-28.29.1~22.04.1" }, "cves": [ { "cve": "CVE-2023-52600", "url": "https://ubuntu.com/security/CVE-2023-52600", "cve_description": "In the Linux kernel, the following vulnerability has been resolved: jfs: fix uaf in jfs_evict_inode When the execution of diMount(ipimap) fails, the object ipimap that has been released may be accessed in diFreeSpecial(). Asynchronous ipimap release occurs when rcu_core() calls jfs_free_node(). Therefore, when diMount(ipimap) fails, sbi->ipimap should not be initialized as ipimap.", "cve_priority": "medium", "cve_public_date": "2024-03-06 07:15:00 UTC" }, { "cve": "CVE-2023-52603", "url": "https://ubuntu.com/security/CVE-2023-52603", "cve_description": "In the Linux kernel, the following vulnerability has been resolved: UBSAN: array-index-out-of-bounds in dtSplitRoot Syzkaller reported the following issue: oop0: detected capacity change from 0 to 32768 UBSAN: array-index-out-of-bounds in fs/jfs/jfs_dtree.c:1971:9 index -2 is out of range for type 'struct dtslot [128]' CPU: 0 PID: 3613 Comm: syz-executor270 Not tainted 6.0.0-syzkaller-09423-g493ffd6605b2 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/22/2022 Call Trace: __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0x1b1/0x28e lib/dump_stack.c:106 ubsan_epilogue lib/ubsan.c:151 [inline] __ubsan_handle_out_of_bounds+0xdb/0x130 lib/ubsan.c:283 dtSplitRoot+0x8d8/0x1900 fs/jfs/jfs_dtree.c:1971 dtSplitUp fs/jfs/jfs_dtree.c:985 [inline] dtInsert+0x1189/0x6b80 fs/jfs/jfs_dtree.c:863 jfs_mkdir+0x757/0xb00 fs/jfs/namei.c:270 vfs_mkdir+0x3b3/0x590 fs/namei.c:4013 do_mkdirat+0x279/0x550 fs/namei.c:4038 __do_sys_mkdirat fs/namei.c:4053 [inline] __se_sys_mkdirat fs/namei.c:4051 [inline] __x64_sys_mkdirat+0x85/0x90 fs/namei.c:4051 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x63/0xcd RIP: 0033:0x7fcdc0113fd9 Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 c0 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007ffeb8bc67d8 EFLAGS: 00000246 ORIG_RAX: 0000000000000102 RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007fcdc0113fd9 RDX: 0000000000000000 RSI: 0000000020000340 RDI: 0000000000000003 RBP: 00007fcdc00d37a0 R08: 0000000000000000 R09: 00007fcdc00d37a0 R10: 00005555559a72c0 R11: 0000000000000246 R12: 00000000f8008000 R13: 0000000000000000 R14: 00083878000000f8 R15: 0000000000000000 The issue is caused when the value of fsi becomes less than -1. The check to break the loop when fsi value becomes -1 is present but syzbot was able to produce value less than -1 which cause the error. This patch simply add the change for the values less than 0. The patch is tested via syzbot.", "cve_priority": "medium", "cve_public_date": "2024-03-06 07:15:00 UTC" }, { "cve": "CVE-2024-26581", "url": "https://ubuntu.com/security/CVE-2024-26581", "cve_description": "In the Linux kernel, the following vulnerability has been resolved: netfilter: nft_set_rbtree: skip end interval element from gc rbtree lazy gc on insert might collect an end interval element that has been just added in this transactions, skip end interval elements that are not yet active.", "cve_priority": "medium", "cve_public_date": "2024-02-20 13:15:00 UTC" }, { "cve": "CVE-2024-26589", "url": "https://ubuntu.com/security/CVE-2024-26589", "cve_description": "In the Linux kernel, the following vulnerability has been resolved: bpf: Reject variable offset alu on PTR_TO_FLOW_KEYS For PTR_TO_FLOW_KEYS, check_flow_keys_access() only uses fixed off for validation. However, variable offset ptr alu is not prohibited for this ptr kind. So the variable offset is not checked. The following prog is accepted: func#0 @0 0: R1=ctx() R10=fp0 0: (bf) r6 = r1 ; R1=ctx() R6_w=ctx() 1: (79) r7 = *(u64 *)(r6 +144) ; R6_w=ctx() R7_w=flow_keys() 2: (b7) r8 = 1024 ; R8_w=1024 3: (37) r8 /= 1 ; R8_w=scalar() 4: (57) r8 &= 1024 ; R8_w=scalar(smin=smin32=0, smax=umax=smax32=umax32=1024,var_off=(0x0; 0x400)) 5: (0f) r7 += r8 mark_precise: frame0: last_idx 5 first_idx 0 subseq_idx -1 mark_precise: frame0: regs=r8 stack= before 4: (57) r8 &= 1024 mark_precise: frame0: regs=r8 stack= before 3: (37) r8 /= 1 mark_precise: frame0: regs=r8 stack= before 2: (b7) r8 = 1024 6: R7_w=flow_keys(smin=smin32=0,smax=umax=smax32=umax32=1024,var_off =(0x0; 0x400)) R8_w=scalar(smin=smin32=0,smax=umax=smax32=umax32=1024, var_off=(0x0; 0x400)) 6: (79) r0 = *(u64 *)(r7 +0) ; R0_w=scalar() 7: (95) exit This prog loads flow_keys to r7, and adds the variable offset r8 to r7, and finally causes out-of-bounds access: BUG: unable to handle page fault for address: ffffc90014c80038 [...] Call Trace: bpf_dispatcher_nop_func include/linux/bpf.h:1231 [inline] __bpf_prog_run include/linux/filter.h:651 [inline] bpf_prog_run include/linux/filter.h:658 [inline] bpf_prog_run_pin_on_cpu include/linux/filter.h:675 [inline] bpf_flow_dissect+0x15f/0x350 net/core/flow_dissector.c:991 bpf_prog_test_run_flow_dissector+0x39d/0x620 net/bpf/test_run.c:1359 bpf_prog_test_run kernel/bpf/syscall.c:4107 [inline] __sys_bpf+0xf8f/0x4560 kernel/bpf/syscall.c:5475 __do_sys_bpf kernel/bpf/syscall.c:5561 [inline] __se_sys_bpf kernel/bpf/syscall.c:5559 [inline] __x64_sys_bpf+0x73/0xb0 kernel/bpf/syscall.c:5559 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0x3f/0x110 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x63/0x6b Fix this by rejecting ptr alu with variable offset on flow_keys. Applying the patch rejects the program with \"R7 pointer arithmetic on flow_keys prohibited\".", "cve_priority": "medium", "cve_public_date": "2024-02-22 17:15:00 UTC" }, { "cve": "CVE-2024-26591", "url": "https://ubuntu.com/security/CVE-2024-26591", "cve_description": "In the Linux kernel, the following vulnerability has been resolved: bpf: Fix re-attachment branch in bpf_tracing_prog_attach The following case can cause a crash due to missing attach_btf: 1) load rawtp program 2) load fentry program with rawtp as target_fd 3) create tracing link for fentry program with target_fd = 0 4) repeat 3 In the end we have: - prog->aux->dst_trampoline == NULL - tgt_prog == NULL (because we did not provide target_fd to link_create) - prog->aux->attach_btf == NULL (the program was loaded with attach_prog_fd=X) - the program was loaded for tgt_prog but we have no way to find out which one BUG: kernel NULL pointer dereference, address: 0000000000000058 Call Trace: ? __die+0x20/0x70 ? page_fault_oops+0x15b/0x430 ? fixup_exception+0x22/0x330 ? exc_page_fault+0x6f/0x170 ? asm_exc_page_fault+0x22/0x30 ? bpf_tracing_prog_attach+0x279/0x560 ? btf_obj_id+0x5/0x10 bpf_tracing_prog_attach+0x439/0x560 __sys_bpf+0x1cf4/0x2de0 __x64_sys_bpf+0x1c/0x30 do_syscall_64+0x41/0xf0 entry_SYSCALL_64_after_hwframe+0x6e/0x76 Return -EINVAL in this situation.", "cve_priority": "medium", "cve_public_date": "2024-02-22 17:15:00 UTC" } ], "launchpad_bugs_fixed": [ 2059697, 1786013, 2059698, 1786013, 2059706, 1786013, 2059143, 2059284, 2056403, 2056403, 2058808 ], "changes": [ { "cves": [ { "cve": "CVE-2023-52600", "url": "https://ubuntu.com/security/CVE-2023-52600", "cve_description": "In the Linux kernel, the following vulnerability has been resolved: jfs: fix uaf in jfs_evict_inode When the execution of diMount(ipimap) fails, the object ipimap that has been released may be accessed in diFreeSpecial(). Asynchronous ipimap release occurs when rcu_core() calls jfs_free_node(). Therefore, when diMount(ipimap) fails, sbi->ipimap should not be initialized as ipimap.", "cve_priority": "medium", "cve_public_date": "2024-03-06 07:15:00 UTC" }, { "cve": "CVE-2023-52603", "url": "https://ubuntu.com/security/CVE-2023-52603", "cve_description": "In the Linux kernel, the following vulnerability has been resolved: UBSAN: array-index-out-of-bounds in dtSplitRoot Syzkaller reported the following issue: oop0: detected capacity change from 0 to 32768 UBSAN: array-index-out-of-bounds in fs/jfs/jfs_dtree.c:1971:9 index -2 is out of range for type 'struct dtslot [128]' CPU: 0 PID: 3613 Comm: syz-executor270 Not tainted 6.0.0-syzkaller-09423-g493ffd6605b2 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/22/2022 Call Trace: __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0x1b1/0x28e lib/dump_stack.c:106 ubsan_epilogue lib/ubsan.c:151 [inline] __ubsan_handle_out_of_bounds+0xdb/0x130 lib/ubsan.c:283 dtSplitRoot+0x8d8/0x1900 fs/jfs/jfs_dtree.c:1971 dtSplitUp fs/jfs/jfs_dtree.c:985 [inline] dtInsert+0x1189/0x6b80 fs/jfs/jfs_dtree.c:863 jfs_mkdir+0x757/0xb00 fs/jfs/namei.c:270 vfs_mkdir+0x3b3/0x590 fs/namei.c:4013 do_mkdirat+0x279/0x550 fs/namei.c:4038 __do_sys_mkdirat fs/namei.c:4053 [inline] __se_sys_mkdirat fs/namei.c:4051 [inline] __x64_sys_mkdirat+0x85/0x90 fs/namei.c:4051 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x63/0xcd RIP: 0033:0x7fcdc0113fd9 Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 c0 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007ffeb8bc67d8 EFLAGS: 00000246 ORIG_RAX: 0000000000000102 RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007fcdc0113fd9 RDX: 0000000000000000 RSI: 0000000020000340 RDI: 0000000000000003 RBP: 00007fcdc00d37a0 R08: 0000000000000000 R09: 00007fcdc00d37a0 R10: 00005555559a72c0 R11: 0000000000000246 R12: 00000000f8008000 R13: 0000000000000000 R14: 00083878000000f8 R15: 0000000000000000 The issue is caused when the value of fsi becomes less than -1. The check to break the loop when fsi value becomes -1 is present but syzbot was able to produce value less than -1 which cause the error. This patch simply add the change for the values less than 0. The patch is tested via syzbot.", "cve_priority": "medium", "cve_public_date": "2024-03-06 07:15:00 UTC" }, { "cve": "CVE-2024-26581", "url": "https://ubuntu.com/security/CVE-2024-26581", "cve_description": "In the Linux kernel, the following vulnerability has been resolved: netfilter: nft_set_rbtree: skip end interval element from gc rbtree lazy gc on insert might collect an end interval element that has been just added in this transactions, skip end interval elements that are not yet active.", "cve_priority": "medium", "cve_public_date": "2024-02-20 13:15:00 UTC" }, { "cve": "CVE-2024-26589", "url": "https://ubuntu.com/security/CVE-2024-26589", "cve_description": "In the Linux kernel, the following vulnerability has been resolved: bpf: Reject variable offset alu on PTR_TO_FLOW_KEYS For PTR_TO_FLOW_KEYS, check_flow_keys_access() only uses fixed off for validation. However, variable offset ptr alu is not prohibited for this ptr kind. So the variable offset is not checked. The following prog is accepted: func#0 @0 0: R1=ctx() R10=fp0 0: (bf) r6 = r1 ; R1=ctx() R6_w=ctx() 1: (79) r7 = *(u64 *)(r6 +144) ; R6_w=ctx() R7_w=flow_keys() 2: (b7) r8 = 1024 ; R8_w=1024 3: (37) r8 /= 1 ; R8_w=scalar() 4: (57) r8 &= 1024 ; R8_w=scalar(smin=smin32=0, smax=umax=smax32=umax32=1024,var_off=(0x0; 0x400)) 5: (0f) r7 += r8 mark_precise: frame0: last_idx 5 first_idx 0 subseq_idx -1 mark_precise: frame0: regs=r8 stack= before 4: (57) r8 &= 1024 mark_precise: frame0: regs=r8 stack= before 3: (37) r8 /= 1 mark_precise: frame0: regs=r8 stack= before 2: (b7) r8 = 1024 6: R7_w=flow_keys(smin=smin32=0,smax=umax=smax32=umax32=1024,var_off =(0x0; 0x400)) R8_w=scalar(smin=smin32=0,smax=umax=smax32=umax32=1024, var_off=(0x0; 0x400)) 6: (79) r0 = *(u64 *)(r7 +0) ; R0_w=scalar() 7: (95) exit This prog loads flow_keys to r7, and adds the variable offset r8 to r7, and finally causes out-of-bounds access: BUG: unable to handle page fault for address: ffffc90014c80038 [...] Call Trace: bpf_dispatcher_nop_func include/linux/bpf.h:1231 [inline] __bpf_prog_run include/linux/filter.h:651 [inline] bpf_prog_run include/linux/filter.h:658 [inline] bpf_prog_run_pin_on_cpu include/linux/filter.h:675 [inline] bpf_flow_dissect+0x15f/0x350 net/core/flow_dissector.c:991 bpf_prog_test_run_flow_dissector+0x39d/0x620 net/bpf/test_run.c:1359 bpf_prog_test_run kernel/bpf/syscall.c:4107 [inline] __sys_bpf+0xf8f/0x4560 kernel/bpf/syscall.c:5475 __do_sys_bpf kernel/bpf/syscall.c:5561 [inline] __se_sys_bpf kernel/bpf/syscall.c:5559 [inline] __x64_sys_bpf+0x73/0xb0 kernel/bpf/syscall.c:5559 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0x3f/0x110 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x63/0x6b Fix this by rejecting ptr alu with variable offset on flow_keys. Applying the patch rejects the program with \"R7 pointer arithmetic on flow_keys prohibited\".", "cve_priority": "medium", "cve_public_date": "2024-02-22 17:15:00 UTC" }, { "cve": "CVE-2024-26591", "url": "https://ubuntu.com/security/CVE-2024-26591", "cve_description": "In the Linux kernel, the following vulnerability has been resolved: bpf: Fix re-attachment branch in bpf_tracing_prog_attach The following case can cause a crash due to missing attach_btf: 1) load rawtp program 2) load fentry program with rawtp as target_fd 3) create tracing link for fentry program with target_fd = 0 4) repeat 3 In the end we have: - prog->aux->dst_trampoline == NULL - tgt_prog == NULL (because we did not provide target_fd to link_create) - prog->aux->attach_btf == NULL (the program was loaded with attach_prog_fd=X) - the program was loaded for tgt_prog but we have no way to find out which one BUG: kernel NULL pointer dereference, address: 0000000000000058 Call Trace: ? __die+0x20/0x70 ? page_fault_oops+0x15b/0x430 ? fixup_exception+0x22/0x330 ? exc_page_fault+0x6f/0x170 ? asm_exc_page_fault+0x22/0x30 ? bpf_tracing_prog_attach+0x279/0x560 ? btf_obj_id+0x5/0x10 bpf_tracing_prog_attach+0x439/0x560 __sys_bpf+0x1cf4/0x2de0 __x64_sys_bpf+0x1c/0x30 do_syscall_64+0x41/0xf0 entry_SYSCALL_64_after_hwframe+0x6e/0x76 Return -EINVAL in this situation.", "cve_priority": "medium", "cve_public_date": "2024-02-22 17:15:00 UTC" } ], "log": [ "", " * jammy/linux-riscv-6.5: 6.5.0-28.29.1~22.04.1 -proposed tracker", " (LP: #2059697)", "", " * Packaging resync (LP: #1786013)", " - [Packaging] drop getabis data", "", " [ Ubuntu: 6.5.0-28.29.1 ]", "", " * mantic/linux-riscv: 6.5.0-28.29.1 -proposed tracker (LP: #2059698)", " * Packaging resync (LP: #1786013)", " - [Packaging] drop getabis data", " * mantic/linux: 6.5.0-28.29 -proposed tracker (LP: #2059706)", " * Packaging resync (LP: #1786013)", " - [Packaging] drop getabis data", " * Remove getabis scripts (LP: #2059143)", " - [Packaging] Remove getabis", " * CVE-2023-52600", " - jfs: fix uaf in jfs_evict_inode", " * Mantic update: upstream stable patchset 2024-03-27 (LP: #2059284) //", " CVE-2023-52603", " - UBSAN: array-index-out-of-bounds in dtSplitRoot", " * CVE-2024-26581", " - netfilter: nft_set_rbtree: skip end interval element from gc", " * Mantic update: upstream stable patchset 2024-03-07 (LP: #2056403) //", " CVE-2024-26589", " - bpf: Reject variable offset alu on PTR_TO_FLOW_KEYS", " * Mantic update: upstream stable patchset 2024-03-07 (LP: #2056403) //", " CVE-2024-26591", " - bpf: Fix re-attachment branch in bpf_tracing_prog_attach", " * iwlwifi disconnect and crash - intel wifi7 (LP: #2058808)", " - wifi: iwlwifi: pcie: fix RB status reading", "" ], "package": "linux-riscv-6.5", "version": "6.5.0-28.29.1~22.04.1", "urgency": "medium", "distributions": "jammy", "launchpad_bugs_fixed": [ 2059697, 1786013, 2059698, 1786013, 2059706, 1786013, 2059143, 2059284, 2056403, 2056403, 2058808 ], "author": "Hannah Peuckmann ", "date": "Mon, 08 Apr 2024 08:49:19 +0200" } ], "notes": "linux-riscv-6.5-headers-6.5.0-28 version '6.5.0-28.29.1~22.04.1' (source package linux-riscv-6.5 version '6.5.0-28.29.1~22.04.1') was added. linux-riscv-6.5-headers-6.5.0-28 version '6.5.0-28.29.1~22.04.1' has the same source package name, linux-riscv-6.5, as removed package linux-headers-6.5.0-27-generic. As such we can use the source package version of the removed package, '6.5.0-27.28.1~22.04.1', 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.5.0-27-generic", "from_version": { "source_package_name": "linux-riscv-6.5", "source_package_version": "6.5.0-27.28.1~22.04.1", "version": "6.5.0-27.28.1~22.04.1" }, "to_version": { "source_package_name": null, "source_package_version": null, "version": null }, "cves": [], "launchpad_bugs_fixed": [], "changes": [], "notes": null }, { "name": "linux-image-6.5.0-27-generic", "from_version": { "source_package_name": "linux-riscv-6.5", "source_package_version": "6.5.0-27.28.1~22.04.1", "version": "6.5.0-27.28.1~22.04.1" }, "to_version": { "source_package_name": null, "source_package_version": null, "version": null }, "cves": [], "launchpad_bugs_fixed": [], "changes": [], "notes": null }, { "name": "linux-modules-6.5.0-27-generic", "from_version": { "source_package_name": "linux-riscv-6.5", "source_package_version": "6.5.0-27.28.1~22.04.1", "version": "6.5.0-27.28.1~22.04.1" }, "to_version": { "source_package_name": null, "source_package_version": null, "version": null }, "cves": [], "launchpad_bugs_fixed": [], "changes": [], "notes": null }, { "name": "linux-riscv-6.5-headers-6.5.0-27", "from_version": { "source_package_name": "linux-riscv-6.5", "source_package_version": "6.5.0-27.28.1~22.04.1", "version": "6.5.0-27.28.1~22.04.1" }, "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 22.04 jammy image from release image serial 20240416 to 20240426", "from_series": "jammy", "to_series": "jammy", "from_serial": "20240416", "to_serial": "20240426", "from_manifest_filename": "release_manifest.previous", "to_manifest_filename": "manifest.current" }