{ "summary": { "snap": { "added": [], "removed": [], "diff": [] }, "deb": { "added": [ "linux-headers-5.4.0-177", "linux-headers-5.4.0-177-generic", "linux-image-5.4.0-177-generic", "linux-modules-5.4.0-177-generic" ], "removed": [ "linux-headers-5.4.0-176", "linux-headers-5.4.0-176-generic", "linux-image-5.4.0-176-generic", "linux-modules-5.4.0-176-generic" ], "diff": [ "cloud-init", "cpio", "less", "libc-bin", "libc6", "libnghttp2-14", "linux-headers-generic", "linux-headers-virtual", "linux-image-virtual", "linux-virtual", "locales" ] } }, "diff": { "deb": [ { "name": "cloud-init", "from_version": { "source_package_name": "cloud-init", "source_package_version": "23.4.4-0ubuntu0~20.04.1", "version": "23.4.4-0ubuntu0~20.04.1" }, "to_version": { "source_package_name": "cloud-init", "source_package_version": "24.1.3-0ubuntu1~20.04.1", "version": "24.1.3-0ubuntu1~20.04.1" }, "cves": [], "launchpad_bugs_fixed": [ 2056100, 2056100, 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~20.04.1", "urgency": "medium", "distributions": "focal", "launchpad_bugs_fixed": [ 2056100 ], "author": "James Falcon ", "date": "Wed, 27 Mar 2024 08:35:43 -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~20.04.1", "urgency": "medium", "distributions": "focal", "launchpad_bugs_fixed": [ 2056100 ], "author": "Chad Smith ", "date": "Thu, 21 Mar 2024 09:12:50 -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", " * d/p/keep-dhclient-as-priority-client.patch:", " - Upstream switched to dhcpcd, keep isc-dhclient as the 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/netplan99-cannot-use-default.patch", " - d/p/retain-netplan-world-readable.patch", " - 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~20.04.1", "urgency": "medium", "distributions": "focal", "launchpad_bugs_fixed": [ 2056100 ], "author": "Brett Holman ", "date": "Wed, 13 Mar 2024 16:12:22 -0600" } ], "notes": null }, { "name": "cpio", "from_version": { "source_package_name": "cpio", "source_package_version": "2.13+dfsg-2ubuntu0.3", "version": "2.13+dfsg-2ubuntu0.3" }, "to_version": { "source_package_name": "cpio", "source_package_version": "2.13+dfsg-2ubuntu0.4", "version": "2.13+dfsg-2ubuntu0.4" }, "cves": [ { "cve": "CVE-2023-7207", "url": "https://ubuntu.com/security/CVE-2023-7207", "cve_description": "Debian's cpio contains a path traversal vulnerability. This issue was introduced by reverting CVE-2015-1197 patches which had caused a regression in --no-absolute-filenames. Upstream has since provided a proper fix to --no-absolute-filenames.", "cve_priority": "medium", "cve_public_date": "2024-02-29 01:42:00 UTC" }, { "cve": "CVE-2015-1197", "url": "https://ubuntu.com/security/CVE-2015-1197", "cve_description": "cpio 2.11, when using the --no-absolute-filenames option, allows local users to write to arbitrary files via a symlink attack on a file in an archive.", "cve_priority": "low", "cve_public_date": "2015-02-19 15:59:00 UTC" } ], "launchpad_bugs_fixed": [], "changes": [ { "cves": [ { "cve": "CVE-2023-7207", "url": "https://ubuntu.com/security/CVE-2023-7207", "cve_description": "Debian's cpio contains a path traversal vulnerability. This issue was introduced by reverting CVE-2015-1197 patches which had caused a regression in --no-absolute-filenames. Upstream has since provided a proper fix to --no-absolute-filenames.", "cve_priority": "medium", "cve_public_date": "2024-02-29 01:42:00 UTC" }, { "cve": "CVE-2015-1197", "url": "https://ubuntu.com/security/CVE-2015-1197", "cve_description": "cpio 2.11, when using the --no-absolute-filenames option, allows local users to write to arbitrary files via a symlink attack on a file in an archive.", "cve_priority": "low", "cve_public_date": "2015-02-19 15:59:00 UTC" } ], "log": [ "", " * SECURITY UPDATE: Path traversal vulnerability", " - debian/patches/CVE-2023-7207.patch: Create symlink placeholder", " if --no-absolute-filenames was given and replace placeholders", " after extraction.", " - debian/patches/revert-CVE-2015-1197-handling.patch: Removed.", " - CVE-2023-7207", "" ], "package": "cpio", "version": "2.13+dfsg-2ubuntu0.4", "urgency": "medium", "distributions": "focal-security", "launchpad_bugs_fixed": [], "author": "Fabian Toepfer ", "date": "Sun, 28 Apr 2024 14:31:25 +0200" } ], "notes": null }, { "name": "less", "from_version": { "source_package_name": "less", "source_package_version": "551-1ubuntu0.2", "version": "551-1ubuntu0.2" }, "to_version": { "source_package_name": "less", "source_package_version": "551-1ubuntu0.3", "version": "551-1ubuntu0.3" }, "cves": [ { "cve": "CVE-2024-32487", "url": "https://ubuntu.com/security/CVE-2024-32487", "cve_description": "less through 653 allows OS command execution via a newline character in the name of a file, because quoting is mishandled in filename.c. Exploitation typically requires use with attacker-controlled file names, such as the files extracted from an untrusted archive. Exploitation also requires the LESSOPEN environment variable, but this is set by default in many common cases.", "cve_priority": "medium", "cve_public_date": "2024-04-13 15:15:00 UTC" } ], "launchpad_bugs_fixed": [], "changes": [ { "cves": [ { "cve": "CVE-2024-32487", "url": "https://ubuntu.com/security/CVE-2024-32487", "cve_description": "less through 653 allows OS command execution via a newline character in the name of a file, because quoting is mishandled in filename.c. Exploitation typically requires use with attacker-controlled file names, such as the files extracted from an untrusted archive. Exploitation also requires the LESSOPEN environment variable, but this is set by default in many common cases.", "cve_priority": "medium", "cve_public_date": "2024-04-13 15:15:00 UTC" } ], "log": [ "", " * SECURITY UPDATE: Arbitrary command execution", " - debian/patches/CVE-2024-32487.patch: Fix bug when viewing a file", " whose name contains a newline.", " - CVE-2024-32487", "" ], "package": "less", "version": "551-1ubuntu0.3", "urgency": "medium", "distributions": "focal-security", "launchpad_bugs_fixed": [], "author": "Fabian Toepfer ", "date": "Sun, 28 Apr 2024 13:42:44 +0200" } ], "notes": null }, { "name": "libc-bin", "from_version": { "source_package_name": "glibc", "source_package_version": "2.31-0ubuntu9.14", "version": "2.31-0ubuntu9.14" }, "to_version": { "source_package_name": "glibc", "source_package_version": "2.31-0ubuntu9.15", "version": "2.31-0ubuntu9.15" }, "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.31-0ubuntu9.15", "urgency": "medium", "distributions": "focal-security", "launchpad_bugs_fixed": [], "author": "Marc Deslauriers ", "date": "Tue, 16 Apr 2024 09:43:50 -0400" } ], "notes": null }, { "name": "libc6", "from_version": { "source_package_name": "glibc", "source_package_version": "2.31-0ubuntu9.14", "version": "2.31-0ubuntu9.14" }, "to_version": { "source_package_name": "glibc", "source_package_version": "2.31-0ubuntu9.15", "version": "2.31-0ubuntu9.15" }, "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.31-0ubuntu9.15", "urgency": "medium", "distributions": "focal-security", "launchpad_bugs_fixed": [], "author": "Marc Deslauriers ", "date": "Tue, 16 Apr 2024 09:43:50 -0400" } ], "notes": null }, { "name": "libnghttp2-14", "from_version": { "source_package_name": "nghttp2", "source_package_version": "1.40.0-1ubuntu0.2", "version": "1.40.0-1ubuntu0.2" }, "to_version": { "source_package_name": "nghttp2", "source_package_version": "1.40.0-1ubuntu0.3", "version": "1.40.0-1ubuntu0.3" }, "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.40.0-1ubuntu0.3", "urgency": "medium", "distributions": "focal-security", "launchpad_bugs_fixed": [], "author": "Fabian Toepfer ", "date": "Thu, 18 Apr 2024 09:15:36 +0200" } ], "notes": null }, { "name": "linux-headers-generic", "from_version": { "source_package_name": "linux-meta", "source_package_version": "5.4.0.176.174", "version": "5.4.0.176.174" }, "to_version": { "source_package_name": "linux-meta", "source_package_version": "5.4.0.177.175", "version": "5.4.0.177.175" }, "cves": [], "launchpad_bugs_fixed": [], "changes": [ { "cves": [], "log": [ "", " * Bump ABI 5.4.0-177", "" ], "package": "linux-meta", "version": "5.4.0.177.175", "urgency": "medium", "distributions": "focal", "launchpad_bugs_fixed": [], "author": "Manuel Diewald ", "date": "Thu, 28 Mar 2024 17:25:59 +0100" } ], "notes": null }, { "name": "linux-headers-virtual", "from_version": { "source_package_name": "linux-meta", "source_package_version": "5.4.0.176.174", "version": "5.4.0.176.174" }, "to_version": { "source_package_name": "linux-meta", "source_package_version": "5.4.0.177.175", "version": "5.4.0.177.175" }, "cves": [], "launchpad_bugs_fixed": [], "changes": [ { "cves": [], "log": [ "", " * Bump ABI 5.4.0-177", "" ], "package": "linux-meta", "version": "5.4.0.177.175", "urgency": "medium", "distributions": "focal", "launchpad_bugs_fixed": [], "author": "Manuel Diewald ", "date": "Thu, 28 Mar 2024 17:25:59 +0100" } ], "notes": null }, { "name": "linux-image-virtual", "from_version": { "source_package_name": "linux-meta", "source_package_version": "5.4.0.176.174", "version": "5.4.0.176.174" }, "to_version": { "source_package_name": "linux-meta", "source_package_version": "5.4.0.177.175", "version": "5.4.0.177.175" }, "cves": [], "launchpad_bugs_fixed": [], "changes": [ { "cves": [], "log": [ "", " * Bump ABI 5.4.0-177", "" ], "package": "linux-meta", "version": "5.4.0.177.175", "urgency": "medium", "distributions": "focal", "launchpad_bugs_fixed": [], "author": "Manuel Diewald ", "date": "Thu, 28 Mar 2024 17:25:59 +0100" } ], "notes": null }, { "name": "linux-virtual", "from_version": { "source_package_name": "linux-meta", "source_package_version": "5.4.0.176.174", "version": "5.4.0.176.174" }, "to_version": { "source_package_name": "linux-meta", "source_package_version": "5.4.0.177.175", "version": "5.4.0.177.175" }, "cves": [], "launchpad_bugs_fixed": [], "changes": [ { "cves": [], "log": [ "", " * Bump ABI 5.4.0-177", "" ], "package": "linux-meta", "version": "5.4.0.177.175", "urgency": "medium", "distributions": "focal", "launchpad_bugs_fixed": [], "author": "Manuel Diewald ", "date": "Thu, 28 Mar 2024 17:25:59 +0100" } ], "notes": null }, { "name": "locales", "from_version": { "source_package_name": "glibc", "source_package_version": "2.31-0ubuntu9.14", "version": "2.31-0ubuntu9.14" }, "to_version": { "source_package_name": "glibc", "source_package_version": "2.31-0ubuntu9.15", "version": "2.31-0ubuntu9.15" }, "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.31-0ubuntu9.15", "urgency": "medium", "distributions": "focal-security", "launchpad_bugs_fixed": [], "author": "Marc Deslauriers ", "date": "Tue, 16 Apr 2024 09:43:50 -0400" } ], "notes": null } ], "snap": [] }, "added": { "deb": [ { "name": "linux-headers-5.4.0-177", "from_version": { "source_package_name": "linux", "source_package_version": "5.4.0-176.196", "version": null }, "to_version": { "source_package_name": "linux", "source_package_version": "5.4.0-177.197", "version": "5.4.0-177.197" }, "cves": [ { "cve": "CVE-2023-24023", "url": "https://ubuntu.com/security/CVE-2023-24023", "cve_description": "Bluetooth BR/EDR devices with Secure Simple Pairing and Secure Connections pairing in Bluetooth Core Specification 4.2 through 5.4 allow certain man-in-the-middle attacks that force a short key length, and might lead to discovery of the encryption key and live injection, aka BLUFFS.", "cve_priority": "medium", "cve_public_date": "2023-11-28 07:15:00 UTC" }, { "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" } ], "launchpad_bugs_fixed": [ 2059633, 1786013, 2059143, 2058948 ], "changes": [ { "cves": [ { "cve": "CVE-2023-24023", "url": "https://ubuntu.com/security/CVE-2023-24023", "cve_description": "Bluetooth BR/EDR devices with Secure Simple Pairing and Secure Connections pairing in Bluetooth Core Specification 4.2 through 5.4 allow certain man-in-the-middle attacks that force a short key length, and might lead to discovery of the encryption key and live injection, aka BLUFFS.", "cve_priority": "medium", "cve_public_date": "2023-11-28 07:15:00 UTC" }, { "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" } ], "log": [ "", " * focal/linux: 5.4.0-177.197 -proposed tracker (LP: #2059633)", "", " * Packaging resync (LP: #1786013)", " - [Packaging] drop getabis data", "", " * Remove getabis scripts (LP: #2059143)", " - [Packaging] Remove getabis", "", " * CVE-2023-24023", " - Bluetooth: Add more enc key size check", "", " * CVE-2023-52600", " - jfs: fix uaf in jfs_evict_inode", "", " * Focal update: v5.4.269 upstream stable release (LP: #2058948) //", " CVE-2023-52603", " - UBSAN: array-index-out-of-bounds in dtSplitRoot", "", " * CVE-2024-26581", " - netfilter: nf_tables: nft_set_rbtree: fix spurious insertion failure", " - netfilter: nft_set_rbtree: skip end interval element from gc", "", " * CVE-2024-26589", " - bpf: Reject variable offset alu on PTR_TO_FLOW_KEYS", "" ], "package": "linux", "version": "5.4.0-177.197", "urgency": "medium", "distributions": "focal", "launchpad_bugs_fixed": [ 2059633, 1786013, 2059143, 2058948 ], "author": "Manuel Diewald ", "date": "Thu, 28 Mar 2024 19:08:48 +0100" } ], "notes": "linux-headers-5.4.0-177 version '5.4.0-177.197' (source package linux version '5.4.0-177.197') was added. linux-headers-5.4.0-177 version '5.4.0-177.197' has the same source package name, linux, as removed package linux-headers-5.4.0-176. As such we can use the source package version of the removed package, '5.4.0-176.196', as the starting point in our changelog diff. Kernel packages are an example of where the binary package name changes for the same source package. Using the removed package source package version as our starting point means we can still get meaningful changelog diffs even for what appears to be a new package." }, { "name": "linux-headers-5.4.0-177-generic", "from_version": { "source_package_name": "linux", "source_package_version": "5.4.0-176.196", "version": null }, "to_version": { "source_package_name": "linux", "source_package_version": "5.4.0-177.197", "version": "5.4.0-177.197" }, "cves": [ { "cve": "CVE-2023-24023", "url": "https://ubuntu.com/security/CVE-2023-24023", "cve_description": "Bluetooth BR/EDR devices with Secure Simple Pairing and Secure Connections pairing in Bluetooth Core Specification 4.2 through 5.4 allow certain man-in-the-middle attacks that force a short key length, and might lead to discovery of the encryption key and live injection, aka BLUFFS.", "cve_priority": "medium", "cve_public_date": "2023-11-28 07:15:00 UTC" }, { "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" } ], "launchpad_bugs_fixed": [ 2059633, 1786013, 2059143, 2058948 ], "changes": [ { "cves": [ { "cve": "CVE-2023-24023", "url": "https://ubuntu.com/security/CVE-2023-24023", "cve_description": "Bluetooth BR/EDR devices with Secure Simple Pairing and Secure Connections pairing in Bluetooth Core Specification 4.2 through 5.4 allow certain man-in-the-middle attacks that force a short key length, and might lead to discovery of the encryption key and live injection, aka BLUFFS.", "cve_priority": "medium", "cve_public_date": "2023-11-28 07:15:00 UTC" }, { "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" } ], "log": [ "", " * focal/linux: 5.4.0-177.197 -proposed tracker (LP: #2059633)", "", " * Packaging resync (LP: #1786013)", " - [Packaging] drop getabis data", "", " * Remove getabis scripts (LP: #2059143)", " - [Packaging] Remove getabis", "", " * CVE-2023-24023", " - Bluetooth: Add more enc key size check", "", " * CVE-2023-52600", " - jfs: fix uaf in jfs_evict_inode", "", " * Focal update: v5.4.269 upstream stable release (LP: #2058948) //", " CVE-2023-52603", " - UBSAN: array-index-out-of-bounds in dtSplitRoot", "", " * CVE-2024-26581", " - netfilter: nf_tables: nft_set_rbtree: fix spurious insertion failure", " - netfilter: nft_set_rbtree: skip end interval element from gc", "", " * CVE-2024-26589", " - bpf: Reject variable offset alu on PTR_TO_FLOW_KEYS", "" ], "package": "linux", "version": "5.4.0-177.197", "urgency": "medium", "distributions": "focal", "launchpad_bugs_fixed": [ 2059633, 1786013, 2059143, 2058948 ], "author": "Manuel Diewald ", "date": "Thu, 28 Mar 2024 19:08:48 +0100" } ], "notes": "linux-headers-5.4.0-177-generic version '5.4.0-177.197' (source package linux version '5.4.0-177.197') was added. linux-headers-5.4.0-177-generic version '5.4.0-177.197' has the same source package name, linux, as removed package linux-headers-5.4.0-176. As such we can use the source package version of the removed package, '5.4.0-176.196', 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-5.4.0-177-generic", "from_version": { "source_package_name": "linux-signed", "source_package_version": "5.4.0-176.196", "version": null }, "to_version": { "source_package_name": "linux-signed", "source_package_version": "5.4.0-177.197", "version": "5.4.0-177.197" }, "cves": [], "launchpad_bugs_fixed": [ 1786013 ], "changes": [ { "cves": [], "log": [ "", " * Main version: 5.4.0-177.197", "", " * Packaging resync (LP: #1786013)", " - [Packaging] debian/tracking-bug -- resync from main package", "" ], "package": "linux-signed", "version": "5.4.0-177.197", "urgency": "medium", "distributions": "focal", "launchpad_bugs_fixed": [ 1786013 ], "author": "Manuel Diewald ", "date": "Thu, 28 Mar 2024 17:26:14 +0100" } ], "notes": "linux-image-5.4.0-177-generic version '5.4.0-177.197' (source package linux-signed version '5.4.0-177.197') was added. linux-image-5.4.0-177-generic version '5.4.0-177.197' has the same source package name, linux-signed, as removed package linux-image-5.4.0-176-generic. As such we can use the source package version of the removed package, '5.4.0-176.196', 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-5.4.0-177-generic", "from_version": { "source_package_name": "linux", "source_package_version": "5.4.0-176.196", "version": null }, "to_version": { "source_package_name": "linux", "source_package_version": "5.4.0-177.197", "version": "5.4.0-177.197" }, "cves": [ { "cve": "CVE-2023-24023", "url": "https://ubuntu.com/security/CVE-2023-24023", "cve_description": "Bluetooth BR/EDR devices with Secure Simple Pairing and Secure Connections pairing in Bluetooth Core Specification 4.2 through 5.4 allow certain man-in-the-middle attacks that force a short key length, and might lead to discovery of the encryption key and live injection, aka BLUFFS.", "cve_priority": "medium", "cve_public_date": "2023-11-28 07:15:00 UTC" }, { "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" } ], "launchpad_bugs_fixed": [ 2059633, 1786013, 2059143, 2058948 ], "changes": [ { "cves": [ { "cve": "CVE-2023-24023", "url": "https://ubuntu.com/security/CVE-2023-24023", "cve_description": "Bluetooth BR/EDR devices with Secure Simple Pairing and Secure Connections pairing in Bluetooth Core Specification 4.2 through 5.4 allow certain man-in-the-middle attacks that force a short key length, and might lead to discovery of the encryption key and live injection, aka BLUFFS.", "cve_priority": "medium", "cve_public_date": "2023-11-28 07:15:00 UTC" }, { "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" } ], "log": [ "", " * focal/linux: 5.4.0-177.197 -proposed tracker (LP: #2059633)", "", " * Packaging resync (LP: #1786013)", " - [Packaging] drop getabis data", "", " * Remove getabis scripts (LP: #2059143)", " - [Packaging] Remove getabis", "", " * CVE-2023-24023", " - Bluetooth: Add more enc key size check", "", " * CVE-2023-52600", " - jfs: fix uaf in jfs_evict_inode", "", " * Focal update: v5.4.269 upstream stable release (LP: #2058948) //", " CVE-2023-52603", " - UBSAN: array-index-out-of-bounds in dtSplitRoot", "", " * CVE-2024-26581", " - netfilter: nf_tables: nft_set_rbtree: fix spurious insertion failure", " - netfilter: nft_set_rbtree: skip end interval element from gc", "", " * CVE-2024-26589", " - bpf: Reject variable offset alu on PTR_TO_FLOW_KEYS", "" ], "package": "linux", "version": "5.4.0-177.197", "urgency": "medium", "distributions": "focal", "launchpad_bugs_fixed": [ 2059633, 1786013, 2059143, 2058948 ], "author": "Manuel Diewald ", "date": "Thu, 28 Mar 2024 19:08:48 +0100" } ], "notes": "linux-modules-5.4.0-177-generic version '5.4.0-177.197' (source package linux version '5.4.0-177.197') was added. linux-modules-5.4.0-177-generic version '5.4.0-177.197' has the same source package name, linux, as removed package linux-headers-5.4.0-176. As such we can use the source package version of the removed package, '5.4.0-176.196', 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-5.4.0-176", "from_version": { "source_package_name": "linux", "source_package_version": "5.4.0-176.196", "version": "5.4.0-176.196" }, "to_version": { "source_package_name": null, "source_package_version": null, "version": null }, "cves": [], "launchpad_bugs_fixed": [], "changes": [], "notes": null }, { "name": "linux-headers-5.4.0-176-generic", "from_version": { "source_package_name": "linux", "source_package_version": "5.4.0-176.196", "version": "5.4.0-176.196" }, "to_version": { "source_package_name": null, "source_package_version": null, "version": null }, "cves": [], "launchpad_bugs_fixed": [], "changes": [], "notes": null }, { "name": "linux-image-5.4.0-176-generic", "from_version": { "source_package_name": "linux-signed", "source_package_version": "5.4.0-176.196", "version": "5.4.0-176.196" }, "to_version": { "source_package_name": null, "source_package_version": null, "version": null }, "cves": [], "launchpad_bugs_fixed": [], "changes": [], "notes": null }, { "name": "linux-modules-5.4.0-176-generic", "from_version": { "source_package_name": "linux", "source_package_version": "5.4.0-176.196", "version": "5.4.0-176.196" }, "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 20.04 focal image from daily image serial 20240416 to 20240430", "from_series": "focal", "to_series": "focal", "from_serial": "20240416", "to_serial": "20240430", "from_manifest_filename": "daily_manifest.previous", "to_manifest_filename": "manifest.current" }