{ "summary": { "snap": { "added": [], "removed": [], "diff": [] }, "deb": { "added": [ "linux-image-7.3.0-8-generic", "linux-main-modules-v4l2loopback-7.3.0-8-generic", "linux-main-modules-zfs-7.3.0-8-generic", "linux-modules-7.3.0-8-generic" ], "removed": [ "linux-image-7.3.0-5-generic", "linux-main-modules-zfs-7.3.0-5-generic", "linux-modules-7.3.0-5-generic" ], "diff": [ "apparmor", "bsdutils", "curl", "dhcpcd-base", "distro-info", "fdisk", "gcc-16-base", "iproute2", "libacl1", "libapparmor1", "libatomic1", "libblkid1", "libcap-ng0", "libcurl4t64", "libexpat1", "libfdisk1", "libgcc-s1", "libjs-sphinxdoc", "libmount1", "libnetplan1", "libpam-systemd", "libparted2t64", "libpng16-16t64", "libpython3.14-minimal", "libpython3.14-stdlib", "libselinux1", "libsmartcols1", "libssh2-1t64", "libssl4", "libstdc++6", "libsystemd-shared", "libsystemd0", "libudev1", "libuuid1", "linux-image-virtual", "login", "login.defs", "mount", "netplan-generator", "netplan.io", "openssl", "openssl-provider-legacy", "parted", "passwd", "python3-distro-info", "python3-launchpadlib", "python3-netplan", "python3-requests", "python3-urllib3", "python3.14", "python3.14-minimal", "rust-coreutils", "systemd", "systemd-resolved", "systemd-sysv", "tar", "tzdata", "ubuntu-drivers-common", "udev", "util-linux" ] } }, "diff": { "deb": [ { "name": "apparmor", "from_version": { "source_package_name": "apparmor", "source_package_version": "6.0.0~alpha1-0ubuntu2", "version": "6.0.0~alpha1-0ubuntu2" }, "to_version": { "source_package_name": "apparmor", "source_package_version": "6.0.0~alpha1-0ubuntu3", "version": "6.0.0~alpha1-0ubuntu3" }, "cves": [], "launchpad_bugs_fixed": [ 2163559, 2168731 ], "changes": [ { "cves": [], "log": [ "", " * Add patch to fix who username lookups (LP: #2163559)", " - d/p/u/profiles-who-add-rules-Rust-coreutils-username-lookup.patch", " * Update patch to fix loupe opening in more directories (LP: #2168731)", " - d/p/u/0004-rewrite-the-loupe-profile.patch", "" ], "package": "apparmor", "version": "6.0.0~alpha1-0ubuntu3", "urgency": "medium", "distributions": "stonking", "launchpad_bugs_fixed": [ 2163559, 2168731 ], "author": "Ryan Lee ", "date": "Thu, 24 Sep 2026 09:57:27 -0700" } ], "notes": null, "is_version_downgrade": false }, { "name": "bsdutils", "from_version": { "source_package_name": "util-linux", "source_package_version": "2.41.3-3ubuntu2", "version": "1:2.41.3-3ubuntu2" }, "to_version": { "source_package_name": "util-linux", "source_package_version": "2.42.2-1ubuntu2", "version": "1:2.42.2-1ubuntu2" }, "cves": [ { "cve": "CVE-2026-53612", "url": "https://ubuntu.com/security/CVE-2026-53612", "cve_description": "[Local Privilege Escalation via TOCTOU in mount(8) hook_owner.c chmod/chown]", "cve_priority": "medium", "cve_public_date": "2026-06-18" }, { "cve": "CVE-2026-53613", "url": "https://ubuntu.com/security/CVE-2026-53613", "cve_description": "[Local Privilege Escalation via TOCTOU in mount(8) - Target Path Redirection]", "cve_priority": "medium", "cve_public_date": "2026-06-18" }, { "cve": "CVE-2026-53614", "url": "https://ubuntu.com/security/CVE-2026-53614", "cve_description": "[Local Privilege Escalation via LIBMOUNT_FORCE_MOUNT2 Environment Variable - nosuid/noexec Bypass in SUID mount(8)]", "cve_priority": "medium", "cve_public_date": "2026-06-18" }, { "cve": "CVE-2026-27456", "url": "https://ubuntu.com/security/CVE-2026-27456", "cve_description": "util-linux is a random collection of Linux utilities. Prior to version 2.41.4, a TOCTOU (Time-of-Check-Time-of-Use) vulnerability has been identified in the SUID binary /usr/bin/mount from util-linux. The mount binary, when setting up loop devices, validates the source file path with user privileges via fork() + setuid() + realpath(), but subsequently re-canonicalizes and opens it with root privileges (euid=0) without verifying that the path has not been replaced between both operations. Neither O_NOFOLLOW, nor inode comparison, nor post-open fstat() are employed. This allows a local unprivileged user to replace the source file with a symlink pointing to any root-owned file or device during the race window, causing the SUID binary to open and mount it as root. Exploitation requires an /etc/fstab entry with user,loop options whose path points to a directory where the attacker has write permission, and that /usr/bin/mount has the SUID bit set (the default configuration on virtually all Linux distributions). The impact is unauthorized read access to root-protected files and block devices, including backup images, disk volumes, and any file containing a valid filesystem. This issue has been patched in version 2.41.4.", "cve_priority": "medium", "cve_public_date": "2026-04-03 22:16:00 UTC" }, { "cve": "CVE-2026-3184", "url": "https://ubuntu.com/security/CVE-2026-3184", "cve_description": "A flaw was found in util-linux. Improper hostname canonicalization in the `login(1)` utility, when invoked with the `-h` option, can modify the supplied remote hostname before setting `PAM_RHOST`. A remote attacker could exploit this by providing a specially crafted hostname, potentially bypassing host-based Pluggable Authentication Modules (PAM) access control rules that rely on fully qualified domain names. This could lead to unauthorized access.", "cve_priority": "medium", "cve_public_date": "2026-04-03 19:17:00 UTC" } ], "launchpad_bugs_fixed": [ 2166882, 2153369, 2125968 ], "changes": [ { "cves": [], "log": [ "", " * d/p/ubuntu/libmount-restricted-live-creds.patch: restore live-credential", " check for libmount restricted mode (LP: #2166882)", "" ], "package": "util-linux", "version": "2.42.2-1ubuntu2", "urgency": "medium", "distributions": "stonking", "launchpad_bugs_fixed": [ 2166882 ], "author": "Nadzeya Hutsko ", "date": "Wed, 16 Sep 2026 19:36:33 +0200" }, { "cves": [], "log": [ "", " * Merge with Debian unstable (LP: #2153369).", " Added changes:", " - tests/fincore: force the use of GNU dd over uutils (LP: #2125968)", " Remaining changes:", " - Add sulogin-fallback-static-sh.patch", " Add support for /bin/static-sh as fallback if the regular shell fails to", " execute. Patch ported from sysvinit. (see LP #505887)", " - Add sulogin-lockedpwd.patch", " Make sure file systems can be fixed on machines with locked root", " accounts (as Ubuntu does by default). Don't require --force for sulogin.", " - d/rules: disable libmount mountfs support", " Disable brand new feature with --disable-libmount-mountfd-support that", " causes inability to deploy MAAS LP #2037417.", " - d/p/ubuntu/su-pty-drop-caps.patch: harden 'su --pty' to temporarily lower", " capabilities while proxying between stdin/stdout and the pty master. This", " is to avoid su from being used to exploit kernel vulnerabilities.", "" ], "package": "util-linux", "version": "2.42.2-1ubuntu1", "urgency": "medium", "distributions": "stonking", "launchpad_bugs_fixed": [ 2153369, 2125968 ], "author": "Florent 'Skia' Jacquet ", "date": "Fri, 26 Jun 2026 12:03:00 +0200" }, { "cves": [ { "cve": "CVE-2026-53612", "url": "https://ubuntu.com/security/CVE-2026-53612", "cve_description": "[Local Privilege Escalation via TOCTOU in mount(8) hook_owner.c chmod/chown]", "cve_priority": "medium", "cve_public_date": "2026-06-18" }, { "cve": "CVE-2026-53613", "url": "https://ubuntu.com/security/CVE-2026-53613", "cve_description": "[Local Privilege Escalation via TOCTOU in mount(8) - Target Path Redirection]", "cve_priority": "medium", "cve_public_date": "2026-06-18" }, { "cve": "CVE-2026-53614", "url": "https://ubuntu.com/security/CVE-2026-53614", "cve_description": "[Local Privilege Escalation via LIBMOUNT_FORCE_MOUNT2 Environment Variable - nosuid/noexec Bypass in SUID mount(8)]", "cve_priority": "medium", "cve_public_date": "2026-06-18" } ], "log": [ "", " * New upstream version, fixing security issues", " CVE-2026-53612, CVE-2026-53613, CVE-2026-53614 (Closes: #1140194,", " #1140195, #1140196)", " * Drop upstream-applied patch.", "" ], "package": "util-linux", "version": "2.42.2-1", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Wed, 17 Jun 2026 11:20:49 +0200" }, { "cves": [], "log": [ "", " * Follow debhelper 14.1, thus putting PAM files back into /etc/pam.d.", " Note that include=login is still undesirable, and packages should", " include common-* instead.", "" ], "package": "util-linux", "version": "2.42.1-6", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Tue, 16 Jun 2026 22:26:25 +0200" }, { "cves": [], "log": [ "", " * PAM config: stop using include.", " Avoid including our own PAM config files, as a workaround until PAM can", " include files from /usr/lib/pam.d.", " Should make su -(l) and runuser -l work again. See #1140029.", "" ], "package": "util-linux", "version": "2.42.1-5", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Mon, 15 Jun 2026 19:34:54 +0200" }, { "cves": [], "log": [ "", " * Update debhelper-compat to v14.", " Remove dh-sequence-installsysusers, remove ${misc:Pre-Depends} from", " Pre-Depends. PAM /etc/pam.d files are replaced by files in", " /usr/lib/pam.d.", "" ], "package": "util-linux", "version": "2.42.1-4", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Sun, 14 Jun 2026 17:28:35 +0200" }, { "cves": [], "log": [ "", " * Use upstream patch to fix FTBFS on systems with non-4K pagesizes", " (Closes: #1138789)", "" ], "package": "util-linux", "version": "2.42.1-3", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Mon, 08 Jun 2026 15:05:17 +0200" }, { "cves": [], "log": [ "", " * Fix FTBFS on systems with non-4K pagesizes (Closes: #1138789)", "" ], "package": "util-linux", "version": "2.42.1-2", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Thu, 04 Jun 2026 13:31:17 +0200" }, { "cves": [], "log": [ "", " * New upstream version", " * Refresh/drop upstream applied patches", "", " [ Karel Zak ]", " * script: fix backward compatibility for options after non-option args", " * script: fix \"--\" separator when used as option argument", " (Closes: #1132887)", "" ], "package": "util-linux", "version": "2.42.1-1", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Wed, 03 Jun 2026 20:12:19 +0200" }, { "cves": [], "log": [ "", " * Stop using Linux crypto API in hardlink(1)", "" ], "package": "util-linux", "version": "2.42-6", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Wed, 06 May 2026 20:41:22 +0200" }, { "cves": [], "log": [ "", " * Remove leftover /etc/init.d/uuidd conffile", "" ], "package": "util-linux", "version": "2.42-5", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Sun, 26 Apr 2026 14:49:42 +0200" }, { "cves": [], "log": [ "", " * Apply upstream revert of su breakage", " (Closes: #1133379, #1132588, #1132610)", "" ], "package": "util-linux", "version": "2.42-4", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Sun, 19 Apr 2026 17:36:56 +0200" }, { "cves": [], "log": [ "", " * Stop pulling deb_systemdsystemunitdir from pkg-config", " * Stop installing uuidd init script", " * Clarify /bin/login situation on Hurd", " * Install bash-completions using normal dh_install mechanism", " * Install more localized man pages", " * Simplify installing into udebs", " * Install lintian overrides into udebs", " * Run a second build without libsystemd for d-i.", " This is not great, but I see no other option at this time.", " Let's hope a libsystemd0-udeb will appear. (Closes: #1132561)", " * util-linux-extra: install copyfilerange, getino", " * Update lintian overrides", " * Update dependency libselinux1-dev to libselinux-dev", "" ], "package": "util-linux", "version": "2.42-3", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Sun, 12 Apr 2026 00:03:33 +0200" }, { "cves": [], "log": [ "", " * Add upstream patches addressing #1132887", "" ], "package": "util-linux", "version": "2.42-2", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Wed, 08 Apr 2026 18:28:21 +0200" }, { "cves": [ { "cve": "CVE-2026-27456", "url": "https://ubuntu.com/security/CVE-2026-27456", "cve_description": "util-linux is a random collection of Linux utilities. Prior to version 2.41.4, a TOCTOU (Time-of-Check-Time-of-Use) vulnerability has been identified in the SUID binary /usr/bin/mount from util-linux. The mount binary, when setting up loop devices, validates the source file path with user privileges via fork() + setuid() + realpath(), but subsequently re-canonicalizes and opens it with root privileges (euid=0) without verifying that the path has not been replaced between both operations. Neither O_NOFOLLOW, nor inode comparison, nor post-open fstat() are employed. This allows a local unprivileged user to replace the source file with a symlink pointing to any root-owned file or device during the race window, causing the SUID binary to open and mount it as root. Exploitation requires an /etc/fstab entry with user,loop options whose path points to a directory where the attacker has write permission, and that /usr/bin/mount has the SUID bit set (the default configuration on virtually all Linux distributions). The impact is unauthorized read access to root-protected files and block devices, including backup images, disk volumes, and any file containing a valid filesystem. This issue has been patched in version 2.41.4.", "cve_priority": "medium", "cve_public_date": "2026-04-03 22:16:00 UTC" } ], "log": [ "", " * New upstream release, fixing CVE-2026-27456 and a CWE-190.", " * Upload to unstable.", "" ], "package": "util-linux", "version": "2.42-1", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Thu, 02 Apr 2026 15:19:42 +0200" }, { "cves": [], "log": [ "", " * New upstream release candidate.", " * Refresh patches", "" ], "package": "util-linux", "version": "2.42~rc2-1", "urgency": "medium", "distributions": "experimental", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Thu, 26 Mar 2026 15:05:59 +0100" }, { "cves": [], "log": [ "", " * Apply upstream patches", " * Fixes unshare issue", " * Use Hurd patches directly from upstream", "" ], "package": "util-linux", "version": "2.42~rc1-3", "urgency": "medium", "distributions": "experimental", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Sun, 22 Mar 2026 15:20:19 +0100" }, { "cves": [], "log": [ "", " * Fix lsmem tests on loong64.", " Using patch from https://github.com/util-linux/util-linux/pull/4090", " * autopkgtests: switch to pkgconf", "", " [ Samuel Thibault ]", " * Fix build on Hurd", "" ], "package": "util-linux", "version": "2.42~rc1-2", "urgency": "medium", "distributions": "experimental", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Tue, 03 Mar 2026 12:43:24 +0100" }, { "cves": [ { "cve": "CVE-2026-3184", "url": "https://ubuntu.com/security/CVE-2026-3184", "cve_description": "A flaw was found in util-linux. Improper hostname canonicalization in the `login(1)` utility, when invoked with the `-h` option, can modify the supplied remote hostname before setting `PAM_RHOST`. A remote attacker could exploit this by providing a specially crafted hostname, potentially bypassing host-based Pluggable Authentication Modules (PAM) access control rules that rely on fully qualified domain names. This could lead to unauthorized access.", "cve_priority": "medium", "cve_public_date": "2026-04-03 19:17:00 UTC" } ], "log": [ "", " * New upstream release candidate.", " * includes fix for CVE-2026-3184:", " * login: use original FQDN for PAM_RHOST", " * libuuid: reset initial cont-clock time on service start (Closes:", " #1126894)", " * Symbols: use (symver) and update lists", " * Stop installing untranslated man pages", "" ], "package": "util-linux", "version": "2.42~rc1-1", "urgency": "medium", "distributions": "experimental", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Sat, 28 Feb 2026 20:37:48 +0100" }, { "cves": [], "log": [ "", " [ Chris Hofstaedtler ]", " * Follow libselinux1-dev to libselinux-dev rename (Closes: #1124751)", " * uuid-runtime: stop removing /var/run/uuidd on purge", " /run is a tmpfs, it will be cleaned up anyway. Lets us drop the postrm", " maintscript.", "", " [ Luca Boccassi ]", " * uuid-runtime: drop manual scripting in postinst and rely on sysusers.d", "" ], "package": "util-linux", "version": "2.41.3-4", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Sat, 21 Feb 2026 17:15:50 +0100" } ], "notes": null, "is_version_downgrade": false }, { "name": "curl", "from_version": { "source_package_name": "curl", "source_package_version": "8.20.0-2ubuntu10", "version": "8.20.0-2ubuntu10" }, "to_version": { "source_package_name": "curl", "source_package_version": "8.20.0-2ubuntu11", "version": "8.20.0-2ubuntu11" }, "cves": [ { "cve": "CVE-2026-13608", "url": "https://ubuntu.com/security/CVE-2026-13608", "cve_description": "A flaw in the libcurl SASL negotiation for LDAP authentication allows an incomplete handshake sequence to be misinterpreted as a successful cryptographic verification. An attacker executing a Man-in-the-Middle (MITM) attack can inject a premature or shortcut response that bypasses complete peer validation.", "cve_priority": "medium", "cve_public_date": "2026-09-06 18:17:00 UTC" }, { "cve": "CVE-2026-18924", "url": "https://ubuntu.com/security/CVE-2026-18924", "cve_description": "A flaw in libcurl's handling of HTTP/2 Server Push streams, when the parent handle is set to share connections with other handles, can lead to use-after-free in the cleanup process.", "cve_priority": "medium", "cve_public_date": "2026-09-06 18:17:00 UTC" }, { "cve": "CVE-2026-80229", "url": "https://ubuntu.com/security/CVE-2026-80229", "cve_description": "When performing transfers via libcurl’s multi interface, pooled TLS connections can outlive their originating easy handles. In OpenSSL 3 provider configurations, libcurl attaches an allocated library context to the easy handle's state and passes it to OpenSSL without acquiring an ownership reference; destroying the easy handle prematurely frees this context while the active connection retains a dangling pointer, leading to a heap-use-after-free upon subsequent I/O or post-handshake operations.", "cve_priority": "medium", "cve_public_date": "2026-09-06 18:17:00 UTC" }, { "cve": "CVE-2026-80230", "url": "https://ubuntu.com/security/CVE-2026-80230", "cve_description": "When `CURLOPT_PINNEDPUBLICKEY` is configured alongside options that disable standard peer verification (`CURLOPT_SSL_VERIFYPEER = 0` and `CURLOPT_SSL_VERIFYHOST = 0`), libcurl fails to enforce public key pinning on connections established without a presented server certificate. Bypassing the pinning check under these disabled-verification conditions allows unauthenticated connections to succeed when they should be rejected.", "cve_priority": "medium", "cve_public_date": "2026-09-06 18:17:00 UTC" }, { "cve": "CVE-2026-80255", "url": "https://ubuntu.com/security/CVE-2026-80255", "cve_description": "A `Set-Cookie:` header using tab (horizontal tab, ASCII code 9) instead of space (ascii code 32) immediately before the `Secure` attribute causes curl to store the cookie without its Secure flag. The cookie might then wrongfully be sent over plaintext HTTP on subsequent requests to the same host.", "cve_priority": "medium", "cve_public_date": "2026-09-06 18:17:00 UTC" }, { "cve": "CVE-2026-82209", "url": "https://ubuntu.com/security/CVE-2026-82209", "cve_description": "When libpsl support is enabled, libcurl fails to enforce the Public Suffix List boundary check when processing a `Set-Cookie` header where the `Domain` attribute explicitly matches an origin host that is itself a public suffix (e.g., `Domain=co.uk` set by `co.uk`). Instead of coercing it into a strict host-only cookie, libcurl saves the cookie with wildcard domain scope (`.co.uk`). Consequently, the cookie is inappropriately included in subsequent outbound requests or HTTP redirects to arbitrary sibling subdomains under the same public suffix (e.g., `attacker.co.uk`).", "cve_priority": "medium", "cve_public_date": "2026-09-06 18:17:00 UTC" }, { "cve": "CVE-2026-10536", "url": "https://ubuntu.com/security/CVE-2026-10536", "cve_description": "A use-after-free vulnerability exists in libcurl when an application configures an HTTP/2 stream-dependency tree via `CURLOPT_STREAM_DEPENDS` or `CURLOPT_STREAM_DEPENDS_E`, subsequently invokes `curl_easy_reset()`, and finally terminates the handle with `curl_easy_cleanup()`. During this final cleanup phase, libcurl attempts to access and modify an internal structure that was already freed during the reset operation.", "cve_priority": "low", "cve_public_date": "2026-07-03 07:16:00 UTC" }, { "cve": "CVE-2026-11352", "url": "https://ubuntu.com/security/CVE-2026-11352", "cve_description": "An issue in curl’s QUIC UDP receive function allows a malicious HTTP/3 server to trigger a remote denial of service against a curl or libcurl client. Because the helper function discards zero-length UDP datagrams before counting them toward the per-call packet budget, a connected QUIC peer can continuously stream empty datagrams to indefinitely stall the client.", "cve_priority": "low", "cve_public_date": "2026-07-03 07:16:00 UTC" }, { "cve": "CVE-2026-11564", "url": "https://ubuntu.com/security/CVE-2026-11564", "cve_description": "libcurl keeps previously used connections in a connection pool for subsequent transfers to reuse if one of them matches the setup. An easy handle that first uses default native CA trust can continue trusting the native platform store after the application switches that same handle to custom CA material for a later transfer.", "cve_priority": "low", "cve_public_date": "2026-07-03 07:16:00 UTC" }, { "cve": "CVE-2026-11586", "url": "https://ubuntu.com/security/CVE-2026-11586", "cve_description": "By default, curl automatically responds to WebSocket PING frames. Because curl lacks an upper bound on memory allocation for unacknowledged frames, a malicious server can exhaust all available memory by flooding curl with rapid, sequential PING messages.", "cve_priority": "low", "cve_public_date": "2026-07-03 07:16:00 UTC" }, { "cve": "CVE-2026-11856", "url": "https://ubuntu.com/security/CVE-2026-11856", "cve_description": "Successfully using libcurl to do a transfer to a specific HTTP origin (`hostA`) with **Digest** authentication and then changing the origin to a different one (`hostB`) for a second transfer, reusing the same handle, makes libcurl wrongly pass on the `Authorization:` header field meant for `hostA`, to `hostB`.", "cve_priority": "medium", "cve_public_date": "2026-07-03 07:16:00 UTC" }, { "cve": "CVE-2026-12064", "url": "https://ubuntu.com/security/CVE-2026-12064", "cve_description": "When a user invokes curl using a schemeless URL combined with `--proto-default` sftp (or scp), a disconnect occurs between the tool layer and libcurl. The tool layer incorrectly infers the URL scheme, which erroneously bypasses the initialization of critical SSH security options like CURLOPT_SSH_HOST_PUBLIC_KEY_SHA256 and CURLOPT_SSH_KNOWNHOSTS. Conversely, the libcurl runtime successfully honors CURLOPT_DEFAULT_PROTOCOL and establishes the connection via SFTP/SCP as specified. Because the tool layer skipped the security configuration, these SSH host verification options are silently omitted, causing curl to connect to an unverified SSH remote host without throwing an error.", "cve_priority": "low", "cve_public_date": "2026-07-03 07:16:00 UTC" }, { "cve": "CVE-2026-8286", "url": "https://ubuntu.com/security/CVE-2026-8286", "cve_description": "A vulnerability exists where a new transfer that uses STARTTLS to upgrade the connection might reuse an existing live connection even though the TLS configuration mismatches so it should not.", "cve_priority": "low", "cve_public_date": "2026-07-03 07:16:00 UTC" }, { "cve": "CVE-2026-8458", "url": "https://ubuntu.com/security/CVE-2026-8458", "cve_description": "libcurl might in some circumstances reuse the wrong connection when asked to do Negotiate-authenticated ones, even when they are set to use different \"services\". libcurl features a pool of recent connections so that subsequent requests can reuse an existing connection to avoid overhead. When reusing a connection a range of criteria must be met. Due to a logical error in the code, a request that was issued by an application could wrongfully reuse an existing connection to the same server that was authenticated using different services.", "cve_priority": "low", "cve_public_date": "2026-07-03 07:16:00 UTC" }, { "cve": "CVE-2026-8924", "url": "https://ubuntu.com/security/CVE-2026-8924", "cve_description": "A flaw in curl’s cookie parsing logic allows a malicious HTTP server to set \"super cookies\" that bypass the Public Suffix List check. This enables an attacker-controlled origin to inject cookies that curl subsequently scopes and transmits to unrelated third-party domains.", "cve_priority": "low", "cve_public_date": "2026-07-03 07:16:00 UTC" }, { "cve": "CVE-2026-8925", "url": "https://ubuntu.com/security/CVE-2026-8925", "cve_description": "The curl logic that works with SASL authentication could end up cleaning up the GSASL context *twice* without clearing the pointer in between, making it `free()` the same pointer twice.", "cve_priority": "medium", "cve_public_date": "2026-07-03 07:16:00 UTC" }, { "cve": "CVE-2026-8926", "url": "https://ubuntu.com/security/CVE-2026-8926", "cve_description": "When asking curl to use a `.netrc` file to find credentials and at the same time specifying a URL with a username (without a password), like `https://user@example.com/`, curl could wrongly get and use the password for *another* user set in the `.netrc` file for that host if such a one exists and there is no match for the specified user.", "cve_priority": "low", "cve_public_date": "2026-07-03 07:16:00 UTC" }, { "cve": "CVE-2026-8927", "url": "https://ubuntu.com/security/CVE-2026-8927", "cve_description": "When reusing a libcurl handle for sequential transfers driven by environment-variable proxy configuration, libcurl fails to clear the proxy authentication state between requests. Specifically, if the initial transfer authenticates against `proxyA` using Digest auth, a subsequent transfer routed through `proxyB` erroneously leaks the `Proxy-Authorization:` header intended solely for `proxyA`.", "cve_priority": "medium", "cve_public_date": "2026-07-03 07:16:00 UTC" }, { "cve": "CVE-2026-9079", "url": "https://ubuntu.com/security/CVE-2026-9079", "cve_description": "libcurl had a flaw that when instructed to clear proxy authentication credentials which made it not do so, leaving the old credentials around to get used for subsequent transfers that should not know nor use them.", "cve_priority": "medium", "cve_public_date": "2026-07-03 07:16:00 UTC" }, { "cve": "CVE-2026-9545", "url": "https://ubuntu.com/security/CVE-2026-9545", "cve_description": "In this scenario, libcurl first uses a proper HTTP/3 server for the initial transfers, and when it makes a second transfer to the same site it has been replaced by the attacker's impostor machine - without a valid certificate. When libcurl returns to the hostname the second time with a cached SSL session (`CURLOPT_SSL_SESSIONID_CACHE` is not disabled) and early data enabled (the `CURLSSLOPT_EARLYDATA` bit is set in `CURLOPT_SSL_OPTIONS`), libcurl might send off the second request's bytes on that new connection *before* enforcing the certificate verification failure. Potentially leaking sensitive information.", "cve_priority": "low", "cve_public_date": "2026-07-03 07:16:00 UTC" }, { "cve": "CVE-2026-9080", "url": "https://ubuntu.com/security/CVE-2026-9080", "cve_description": "Calling `curl_easy_pause()` within the event-based `CURLMOPT_SOCKETFUNCTION` callback triggers a use-after-free vulnerability, where libcurl attempts to store a flag using a dangling struct pointer immediately after that pointer's memory has been freed.", "cve_priority": "low", "cve_public_date": "2026-07-03 07:16:00 UTC" }, { "cve": "CVE-2026-9546", "url": "https://ubuntu.com/security/CVE-2026-9546", "cve_description": "A vulnerability in libcurl caused the HTTP `Referer:` header to persist even when explicitly cleared. While the documentation states that passing NULL to `CURLOPT_REFERER` suppresses the header, the option failed to clear the internal state. As a result, the previous referrer string was erroneously reused and sent in subsequent requests, potentially leaking sensitive information to unintended servers.", "cve_priority": "low", "cve_public_date": "2026-07-03 07:16:00 UTC" }, { "cve": "CVE-2026-9547", "url": "https://ubuntu.com/security/CVE-2026-9547", "cve_description": "When a libcurl-based application performs transfers via `SCP://` or `SFTP://` and utilizes the `CURLOPT_SSH_KEYFUNCTION` callback, it may silently accept an untrusted server. This vulnerability occurs when a server presents a host key type that does not match the specific key type already recorded for that host in the `known_hosts` file. Instead of rejecting the mismatch, the callback mechanism fails to properly enforce the restriction, allowing the connection to succeed without warning and risking a potential man-in-the-middle attack.", "cve_priority": "low", "cve_public_date": "2026-07-03 07:16:00 UTC" } ], "launchpad_bugs_fixed": [], "changes": [ { "cves": [ { "cve": "CVE-2026-13608", "url": "https://ubuntu.com/security/CVE-2026-13608", "cve_description": "A flaw in the libcurl SASL negotiation for LDAP authentication allows an incomplete handshake sequence to be misinterpreted as a successful cryptographic verification. An attacker executing a Man-in-the-Middle (MITM) attack can inject a premature or shortcut response that bypasses complete peer validation.", "cve_priority": "medium", "cve_public_date": "2026-09-06 18:17:00 UTC" }, { "cve": "CVE-2026-18924", "url": "https://ubuntu.com/security/CVE-2026-18924", "cve_description": "A flaw in libcurl's handling of HTTP/2 Server Push streams, when the parent handle is set to share connections with other handles, can lead to use-after-free in the cleanup process.", "cve_priority": "medium", "cve_public_date": "2026-09-06 18:17:00 UTC" }, { "cve": "CVE-2026-80229", "url": "https://ubuntu.com/security/CVE-2026-80229", "cve_description": "When performing transfers via libcurl’s multi interface, pooled TLS connections can outlive their originating easy handles. In OpenSSL 3 provider configurations, libcurl attaches an allocated library context to the easy handle's state and passes it to OpenSSL without acquiring an ownership reference; destroying the easy handle prematurely frees this context while the active connection retains a dangling pointer, leading to a heap-use-after-free upon subsequent I/O or post-handshake operations.", "cve_priority": "medium", "cve_public_date": "2026-09-06 18:17:00 UTC" }, { "cve": "CVE-2026-80230", "url": "https://ubuntu.com/security/CVE-2026-80230", "cve_description": "When `CURLOPT_PINNEDPUBLICKEY` is configured alongside options that disable standard peer verification (`CURLOPT_SSL_VERIFYPEER = 0` and `CURLOPT_SSL_VERIFYHOST = 0`), libcurl fails to enforce public key pinning on connections established without a presented server certificate. Bypassing the pinning check under these disabled-verification conditions allows unauthenticated connections to succeed when they should be rejected.", "cve_priority": "medium", "cve_public_date": "2026-09-06 18:17:00 UTC" }, { "cve": "CVE-2026-80255", "url": "https://ubuntu.com/security/CVE-2026-80255", "cve_description": "A `Set-Cookie:` header using tab (horizontal tab, ASCII code 9) instead of space (ascii code 32) immediately before the `Secure` attribute causes curl to store the cookie without its Secure flag. The cookie might then wrongfully be sent over plaintext HTTP on subsequent requests to the same host.", "cve_priority": "medium", "cve_public_date": "2026-09-06 18:17:00 UTC" }, { "cve": "CVE-2026-82209", "url": "https://ubuntu.com/security/CVE-2026-82209", "cve_description": "When libpsl support is enabled, libcurl fails to enforce the Public Suffix List boundary check when processing a `Set-Cookie` header where the `Domain` attribute explicitly matches an origin host that is itself a public suffix (e.g., `Domain=co.uk` set by `co.uk`). Instead of coercing it into a strict host-only cookie, libcurl saves the cookie with wildcard domain scope (`.co.uk`). Consequently, the cookie is inappropriately included in subsequent outbound requests or HTTP redirects to arbitrary sibling subdomains under the same public suffix (e.g., `attacker.co.uk`).", "cve_priority": "medium", "cve_public_date": "2026-09-06 18:17:00 UTC" }, { "cve": "CVE-2026-10536", "url": "https://ubuntu.com/security/CVE-2026-10536", "cve_description": "A use-after-free vulnerability exists in libcurl when an application configures an HTTP/2 stream-dependency tree via `CURLOPT_STREAM_DEPENDS` or `CURLOPT_STREAM_DEPENDS_E`, subsequently invokes `curl_easy_reset()`, and finally terminates the handle with `curl_easy_cleanup()`. During this final cleanup phase, libcurl attempts to access and modify an internal structure that was already freed during the reset operation.", "cve_priority": "low", "cve_public_date": "2026-07-03 07:16:00 UTC" }, { "cve": "CVE-2026-11352", "url": "https://ubuntu.com/security/CVE-2026-11352", "cve_description": "An issue in curl’s QUIC UDP receive function allows a malicious HTTP/3 server to trigger a remote denial of service against a curl or libcurl client. Because the helper function discards zero-length UDP datagrams before counting them toward the per-call packet budget, a connected QUIC peer can continuously stream empty datagrams to indefinitely stall the client.", "cve_priority": "low", "cve_public_date": "2026-07-03 07:16:00 UTC" }, { "cve": "CVE-2026-11564", "url": "https://ubuntu.com/security/CVE-2026-11564", "cve_description": "libcurl keeps previously used connections in a connection pool for subsequent transfers to reuse if one of them matches the setup. An easy handle that first uses default native CA trust can continue trusting the native platform store after the application switches that same handle to custom CA material for a later transfer.", "cve_priority": "low", "cve_public_date": "2026-07-03 07:16:00 UTC" }, { "cve": "CVE-2026-11586", "url": "https://ubuntu.com/security/CVE-2026-11586", "cve_description": "By default, curl automatically responds to WebSocket PING frames. Because curl lacks an upper bound on memory allocation for unacknowledged frames, a malicious server can exhaust all available memory by flooding curl with rapid, sequential PING messages.", "cve_priority": "low", "cve_public_date": "2026-07-03 07:16:00 UTC" }, { "cve": "CVE-2026-11856", "url": "https://ubuntu.com/security/CVE-2026-11856", "cve_description": "Successfully using libcurl to do a transfer to a specific HTTP origin (`hostA`) with **Digest** authentication and then changing the origin to a different one (`hostB`) for a second transfer, reusing the same handle, makes libcurl wrongly pass on the `Authorization:` header field meant for `hostA`, to `hostB`.", "cve_priority": "medium", "cve_public_date": "2026-07-03 07:16:00 UTC" }, { "cve": "CVE-2026-12064", "url": "https://ubuntu.com/security/CVE-2026-12064", "cve_description": "When a user invokes curl using a schemeless URL combined with `--proto-default` sftp (or scp), a disconnect occurs between the tool layer and libcurl. The tool layer incorrectly infers the URL scheme, which erroneously bypasses the initialization of critical SSH security options like CURLOPT_SSH_HOST_PUBLIC_KEY_SHA256 and CURLOPT_SSH_KNOWNHOSTS. Conversely, the libcurl runtime successfully honors CURLOPT_DEFAULT_PROTOCOL and establishes the connection via SFTP/SCP as specified. Because the tool layer skipped the security configuration, these SSH host verification options are silently omitted, causing curl to connect to an unverified SSH remote host without throwing an error.", "cve_priority": "low", "cve_public_date": "2026-07-03 07:16:00 UTC" }, { "cve": "CVE-2026-8286", "url": "https://ubuntu.com/security/CVE-2026-8286", "cve_description": "A vulnerability exists where a new transfer that uses STARTTLS to upgrade the connection might reuse an existing live connection even though the TLS configuration mismatches so it should not.", "cve_priority": "low", "cve_public_date": "2026-07-03 07:16:00 UTC" }, { "cve": "CVE-2026-8458", "url": "https://ubuntu.com/security/CVE-2026-8458", "cve_description": "libcurl might in some circumstances reuse the wrong connection when asked to do Negotiate-authenticated ones, even when they are set to use different \"services\". libcurl features a pool of recent connections so that subsequent requests can reuse an existing connection to avoid overhead. When reusing a connection a range of criteria must be met. Due to a logical error in the code, a request that was issued by an application could wrongfully reuse an existing connection to the same server that was authenticated using different services.", "cve_priority": "low", "cve_public_date": "2026-07-03 07:16:00 UTC" }, { "cve": "CVE-2026-8924", "url": "https://ubuntu.com/security/CVE-2026-8924", "cve_description": "A flaw in curl’s cookie parsing logic allows a malicious HTTP server to set \"super cookies\" that bypass the Public Suffix List check. This enables an attacker-controlled origin to inject cookies that curl subsequently scopes and transmits to unrelated third-party domains.", "cve_priority": "low", "cve_public_date": "2026-07-03 07:16:00 UTC" }, { "cve": "CVE-2026-8925", "url": "https://ubuntu.com/security/CVE-2026-8925", "cve_description": "The curl logic that works with SASL authentication could end up cleaning up the GSASL context *twice* without clearing the pointer in between, making it `free()` the same pointer twice.", "cve_priority": "medium", "cve_public_date": "2026-07-03 07:16:00 UTC" }, { "cve": "CVE-2026-8926", "url": "https://ubuntu.com/security/CVE-2026-8926", "cve_description": "When asking curl to use a `.netrc` file to find credentials and at the same time specifying a URL with a username (without a password), like `https://user@example.com/`, curl could wrongly get and use the password for *another* user set in the `.netrc` file for that host if such a one exists and there is no match for the specified user.", "cve_priority": "low", "cve_public_date": "2026-07-03 07:16:00 UTC" }, { "cve": "CVE-2026-8927", "url": "https://ubuntu.com/security/CVE-2026-8927", "cve_description": "When reusing a libcurl handle for sequential transfers driven by environment-variable proxy configuration, libcurl fails to clear the proxy authentication state between requests. Specifically, if the initial transfer authenticates against `proxyA` using Digest auth, a subsequent transfer routed through `proxyB` erroneously leaks the `Proxy-Authorization:` header intended solely for `proxyA`.", "cve_priority": "medium", "cve_public_date": "2026-07-03 07:16:00 UTC" }, { "cve": "CVE-2026-9079", "url": "https://ubuntu.com/security/CVE-2026-9079", "cve_description": "libcurl had a flaw that when instructed to clear proxy authentication credentials which made it not do so, leaving the old credentials around to get used for subsequent transfers that should not know nor use them.", "cve_priority": "medium", "cve_public_date": "2026-07-03 07:16:00 UTC" }, { "cve": "CVE-2026-9545", "url": "https://ubuntu.com/security/CVE-2026-9545", "cve_description": "In this scenario, libcurl first uses a proper HTTP/3 server for the initial transfers, and when it makes a second transfer to the same site it has been replaced by the attacker's impostor machine - without a valid certificate. When libcurl returns to the hostname the second time with a cached SSL session (`CURLOPT_SSL_SESSIONID_CACHE` is not disabled) and early data enabled (the `CURLSSLOPT_EARLYDATA` bit is set in `CURLOPT_SSL_OPTIONS`), libcurl might send off the second request's bytes on that new connection *before* enforcing the certificate verification failure. Potentially leaking sensitive information.", "cve_priority": "low", "cve_public_date": "2026-07-03 07:16:00 UTC" }, { "cve": "CVE-2026-9080", "url": "https://ubuntu.com/security/CVE-2026-9080", "cve_description": "Calling `curl_easy_pause()` within the event-based `CURLMOPT_SOCKETFUNCTION` callback triggers a use-after-free vulnerability, where libcurl attempts to store a flag using a dangling struct pointer immediately after that pointer's memory has been freed.", "cve_priority": "low", "cve_public_date": "2026-07-03 07:16:00 UTC" }, { "cve": "CVE-2026-9546", "url": "https://ubuntu.com/security/CVE-2026-9546", "cve_description": "A vulnerability in libcurl caused the HTTP `Referer:` header to persist even when explicitly cleared. While the documentation states that passing NULL to `CURLOPT_REFERER` suppresses the header, the option failed to clear the internal state. As a result, the previous referrer string was erroneously reused and sent in subsequent requests, potentially leaking sensitive information to unintended servers.", "cve_priority": "low", "cve_public_date": "2026-07-03 07:16:00 UTC" }, { "cve": "CVE-2026-9547", "url": "https://ubuntu.com/security/CVE-2026-9547", "cve_description": "When a libcurl-based application performs transfers via `SCP://` or `SFTP://` and utilizes the `CURLOPT_SSH_KEYFUNCTION` callback, it may silently accept an untrusted server. This vulnerability occurs when a server presents a host key type that does not match the specific key type already recorded for that host in the `known_hosts` file. Instead of rejecting the mismatch, the callback mechanism fails to properly enforce the restriction, allowing the connection to succeed without warning and risking a potential man-in-the-middle attack.", "cve_priority": "low", "cve_public_date": "2026-07-03 07:16:00 UTC" } ], "log": [ "", " [ Charles Cochran ]", " * SECURITY UPDATE: Authentication bypass in LDAP SASL negotiation.", " - debian/patches/CVE-2026-13608.patch: openldap: handle", " Curl_sasl_continue() returns better in lib/openldap.c.", " - CVE-2026-13608", " * SECURITY UPDATE: Use after free in HTTP/2 server push.", " - debian/patches/CVE-2026-18924.patch: make server push transfers", " inherit share from parent in lib/http2.c.", " - CVE-2026-18924", " * SECURITY UPDATE: Use after free in OpenSSL library context.", " - debian/patches/CVE-2026-80229.patch: avoid conn reuse if provider is", " used in lib/vtls/openssl.c.", " - CVE-2026-80229", " * SECURITY UPDATE: Public key pinning bypass.", " - debian/patches/CVE-2026-80230.patch: require server cert if public", " key pinned in lib/vtls/openssl.c.", " - CVE-2026-80230", " * SECURITY UPDATE: Cookie Secure attribute bypass in Set-Cookie.", " - debian/patches/CVE-2026-80255.patch: improve TAB handling in", " lib/cookie.c, tests/data/Makefile.am, tests/data/test2885.", " - CVE-2026-80255", " * SECURITY UPDATE: Cookie injection for public suffix domains.", " - debian/patches/CVE-2026-82209.patch: ensure cookies set for an exact", " PSL domain are host-only in lib/cookie.c, tests/data/Makefile.am,", " tests/data/test1136, tests/data/test2318, tests/data/test798.", " - CVE-2026-82209", "", " [ Kyle Kernick ]", " * SECURITY UPDATE: Use after free in curl_easy_reset.", " - debian/patches/CVE-2026-10536.patch: Deprecate CURLOPT_* in", " include/curl/curl.h, lib/http2.c,", " lib/setopt.c, lib/url.c, and lib/urldata.h", " - CVE-2026-10536", " * SECURITY UPDATE: Denial of service in QUIC UDP.", " - debian/patches/CVE-2026-11352.patch: Count zero-length UDP packets", " and enforce an upper bound in", " lib/vquic/vquic.c", " - CVE-2026-11352", " * SECURITY UPDATE: Improper certificate validation in native_ca_store.", " - debian/patches/CVE-2026-11564.patch: Add bit native_ca_store_opt to", " keep the setting of CURLOPT_(PROXY_)SSL_OPTIONS and use that to", " calculate every easy transfer if a native CA store shall be used or", " not in lib/doh.c, lib/setopt.c, and lib/vtls/vtls.c", " - CVE-2026-11564", " * SECURITY UPDATE: Memory exhaustion in ws.c", " - debian/patches/CVE-2026-11586.patch: Do not send PONG frames unless", " there is sufficient space left in the websocket send buffer in", " lib/ws.c.", " - CVE-2026-11586", " * SECURITY UPDATE: Authentication Bypass by Capture-replay", " - debian/patches/CVE-2026-11856.patch: Flush state on origin or credential", " change in lib/http_digest.c, lib/urldata.h, lib/vauth/digest.c, and", " lib/vauth/digest_sspi.c.", " - CVE-2026-11856", " * SECURITY UPDATE: Improper validation in config2setopts.", " - debian/patches/CVE-2026-12064.patch: Use default protocol properly in", " src/config2setopts.c.", " - CVE-2026-12064", " * SECURITY UPDATE: Connection reuse for starttls protocols.", " - debian/patches/CVE-2026-8286.patch: When a connection is tested for", " reuse in a transfer that may upgrade to TLS (commonly via STARTTLS),", " the SSL configuration must match the existing connection in lib/url.c", " - CVE-2026-8286", " * SECURITY UPDATE: Connection reuse in SASL.", " - debian/patches/CVE-2026-8458.patch: Fix erroneous connection reuse in", " lib/curl_sasl.c, lib/http_negotiate.c, and lib/http_ntlm.c.", " - CVE-2026-8458", " * SECURITY UPDATE: Cookie injection in is_public_suffix.", " - debian/patches/CVE-2026-8924.patch: Trim trailing dots when checking", " PSL in lib/cookie.c.", " - CVE-2026-8924", " * SECURITY UPDATE: Double-free in gsasl.", " - debian/patches/CVE-2026-8925.patch: Require libgsasl 1.6.0 to handle", " NULL argument in lib/vauth/gsasl.c.", " - CVE-2026-8925", " * SECURITY UPDATE: Information disclosure in netrc.", " - debian/patches/CVE-2026-8926.patch: Do not return a password from", " parsenetrc() when the requested login did not match the credentials", " found for the matched machine in lib/netrc.c.", " - CVE-2026-8926", " * SECURITY UPDATE: Information disclosure in libcurl", " - debian/patches/CVE-2026-8927.patch: Detect if proxy is not the same as", " previous and flush state in lib/url.c and lib/urldata.h.", " - debian/patches/CVE-2026-9079.patch: Verify NULLed proxy credentials", " in lib/setopt.c.", " - debian/patches/CVE-2026-9545.patch: Hard fail when certificate", " verification fails in lib/vquic/curl_ngtcp2.c.", " - CVE-2026-8927", " - CVE-2026-9079", " - CVE-2026-9545", " * SECURITY UPDATE: Use-after-free in curl_easy_pause", " - debian/patches/CVE-2026-9080.patch: Introduce magic struct field to", " assert against NULL pointers in lib/multi_ev.c", " - debian/patches/CVE-2026-9080-post1.patch: Refresh sock entry after", " remove callback in lib/multi_ev.c", " - CVE-2026-9080", " * SECURITY UPDATE: Information disclosure in libcurl", " - debian/patches/CVE-2026-9546.patch: clear referer in lib/transfer.c", " - CVE-2026-9546", " * SECURITY UPDATE: Man-in-the-middle in libcurl.", " - debian/patches/CVE-2026-9547.patch: Reject host key mismatches in", " lib/vssh/libssh.c.", " - CVE-2026-9547", "" ], "package": "curl", "version": "8.20.0-2ubuntu11", "urgency": "medium", "distributions": "stonking", "launchpad_bugs_fixed": [], "author": "Kyle Kernick ", "date": "Wed, 23 Sep 2026 15:00:22 -0600" } ], "notes": null, "is_version_downgrade": false }, { "name": "dhcpcd-base", "from_version": { "source_package_name": "dhcpcd", "source_package_version": "1:10.3.2-6", "version": "1:10.3.2-6" }, "to_version": { "source_package_name": "dhcpcd", "source_package_version": "1:10.5.2-6", "version": "1:10.5.2-6" }, "cves": [], "launchpad_bugs_fixed": [], "changes": [ { "cves": [], "log": [ "", " * [patches]", " + 0002: Fix stdout/stderr not closed when daemonising (Closes: #1149297).", "" ], "package": "dhcpcd", "version": "1:10.5.2-6", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Martin-Éric Racine ", "date": "Wed, 30 Sep 2026 07:48:01 +0300" }, { "cves": [], "log": [ "", " * [autopkgtest]", " = timesyncd: use active verbs for output text.", "" ], "package": "dhcpcd", "version": "1:10.5.2-5", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Martin-Éric Racine ", "date": "Tue, 22 Sep 2026 14:24:31 +0300" }, { "cves": [], "log": [ "", " * [rules]", " + Add --no-start back to dh_install[init|systemd] to fix autopkgtest.", " * [autopkgtest]", " - Remove superfluous ethtool call and Depends.", "" ], "package": "dhcpcd", "version": "1:10.5.2-4", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Martin-Éric Racine ", "date": "Mon, 07 Sep 2026 20:41:16 +0300" }, { "cves": [], "log": [ "", " * [autopkgtest]", " + Echo mileposts: veth addr, dnsmasq status, timedatectl show-timesync.", "" ], "package": "dhcpcd", "version": "1:10.5.2-3", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Martin-Éric Racine ", "date": "Mon, 07 Sep 2026 10:20:52 +0300" }, { "cves": [], "log": [ "", " * [systemd]", " - Remove After/Before references to networking.service (Closes: #1146692).", " * [rules]", " - Ensure that monitor mode restarts after an upgrade (Closes: #1146835).", "" ], "package": "dhcpcd", "version": "1:10.5.2-2", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Martin-Éric Racine ", "date": "Sun, 06 Sep 2026 12:05:01 +0300" }, { "cves": [], "log": [ "", " * New upstream version.", "" ], "package": "dhcpcd", "version": "1:10.5.2-1", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Martin-Éric Racine ", "date": "Mon, 17 Aug 2026 19:13:55 +0300" }, { "cves": [], "log": [ "", " * New upstream version.", " This version brings extensive code refactoring and some intrusive changes.", " Cautiously uploading to unstable. Please report all regressions upstream.", " * [patches]", " - Drop all recent upstream cherry-picks. They're included in this release.", "" ], "package": "dhcpcd", "version": "1:10.5.1-1", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Martin-Éric Racine ", "date": "Mon, 17 Aug 2026 14:51:17 +0300" }, { "cves": [], "log": [ "", " * [patches]", " Cherry-pick upstream fixes for regressions:", " + 42307ab3c8aee9dfb99b80ae2086750adb465989.patch", " * [autopkgtest]", " - timesyncd-ntp-servers-from-dhcp: no longer flaky.", "" ], "package": "dhcpcd", "version": "1:10.5.0-4", "urgency": "medium", "distributions": "experimental", "launchpad_bugs_fixed": [], "author": "Martin-Éric Racine ", "date": "Thu, 13 Aug 2026 20:08:28 +0300" }, { "cves": [], "log": [ "", " * [patches]", " Cherry-pick upstream fixes for regressions:", " + 78429f5f4dff60ed56de56ae8524e6f50acee96a.patch", "" ], "package": "dhcpcd", "version": "1:10.5.0-3", "urgency": "medium", "distributions": "experimental", "launchpad_bugs_fixed": [], "author": "Martin-Éric Racine ", "date": "Wed, 12 Aug 2026 10:48:17 +0000" }, { "cves": [], "log": [ "", " * [patches]", " Cherry-pick upstream fixes for regressions:", " + 0406dd87753049f54b9beb7ab66f333a1d2709d2.patch", " + 9151877f4954f13df3afec25e5d677927a2b8b72.patch", "" ], "package": "dhcpcd", "version": "1:10.5.0-2", "urgency": "medium", "distributions": "experimental", "launchpad_bugs_fixed": [], "author": "Martin-Éric Racine ", "date": "Tue, 11 Aug 2026 19:06:11 +0300" }, { "cves": [], "log": [ "", " * New upstream version.", " This version brings extensive code refactoring and some intrusive changes,", " hence the upload via experimental. Please report all regressions upstream.", " * [patches]", " - Drop all CVE fixes (merged upstream).", " * [control]", " - Build-Depends: openntpd [hurd-any]. Try building Hurd without NTP hooks.", "" ], "package": "dhcpcd", "version": "1:10.5.0-1", "urgency": "medium", "distributions": "experimental", "launchpad_bugs_fixed": [], "author": "Martin-Éric Racine ", "date": "Wed, 05 Aug 2026 16:04:53 +0300" } ], "notes": null, "is_version_downgrade": false }, { "name": "distro-info", "from_version": { "source_package_name": "distro-info", "source_package_version": "1.17", "version": "1.17" }, "to_version": { "source_package_name": "distro-info", "source_package_version": "1.19", "version": "1.19" }, "cves": [], "launchpad_bugs_fixed": [ 2131678 ], "changes": [ { "cves": [], "log": [ "", " * Makefile: remove python/.mypy_cache on clean", "" ], "package": "distro-info", "version": "1.19", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Benjamin Drung ", "date": "Tue, 29 Sep 2026 12:41:41 +0200" }, { "cves": [], "log": [ "", " * Support Ubuntu Pro with Legacy add-on (LP: #2131678):", " - ubuntu-distro-info: add --supported-legacy", " - python: add UbuntuDistroInfo.supported_legacy", " - perl: add UbuntuDistroInfo.supported_legacy", " * Add test cases for ubuntu-distro-info --supported-esm", "" ], "package": "distro-info", "version": "1.18", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [ 2131678 ], "author": "Benjamin Drung ", "date": "Mon, 28 Sep 2026 16:01:16 +0200" } ], "notes": null, "is_version_downgrade": false }, { "name": "fdisk", "from_version": { "source_package_name": "util-linux", "source_package_version": "2.41.3-3ubuntu2", "version": "2.41.3-3ubuntu2" }, "to_version": { "source_package_name": "util-linux", "source_package_version": "2.42.2-1ubuntu2", "version": "2.42.2-1ubuntu2" }, "cves": [ { "cve": "CVE-2026-53612", "url": "https://ubuntu.com/security/CVE-2026-53612", "cve_description": "[Local Privilege Escalation via TOCTOU in mount(8) hook_owner.c chmod/chown]", "cve_priority": "medium", "cve_public_date": "2026-06-18" }, { "cve": "CVE-2026-53613", "url": "https://ubuntu.com/security/CVE-2026-53613", "cve_description": "[Local Privilege Escalation via TOCTOU in mount(8) - Target Path Redirection]", "cve_priority": "medium", "cve_public_date": "2026-06-18" }, { "cve": "CVE-2026-53614", "url": "https://ubuntu.com/security/CVE-2026-53614", "cve_description": "[Local Privilege Escalation via LIBMOUNT_FORCE_MOUNT2 Environment Variable - nosuid/noexec Bypass in SUID mount(8)]", "cve_priority": "medium", "cve_public_date": "2026-06-18" }, { "cve": "CVE-2026-27456", "url": "https://ubuntu.com/security/CVE-2026-27456", "cve_description": "util-linux is a random collection of Linux utilities. Prior to version 2.41.4, a TOCTOU (Time-of-Check-Time-of-Use) vulnerability has been identified in the SUID binary /usr/bin/mount from util-linux. The mount binary, when setting up loop devices, validates the source file path with user privileges via fork() + setuid() + realpath(), but subsequently re-canonicalizes and opens it with root privileges (euid=0) without verifying that the path has not been replaced between both operations. Neither O_NOFOLLOW, nor inode comparison, nor post-open fstat() are employed. This allows a local unprivileged user to replace the source file with a symlink pointing to any root-owned file or device during the race window, causing the SUID binary to open and mount it as root. Exploitation requires an /etc/fstab entry with user,loop options whose path points to a directory where the attacker has write permission, and that /usr/bin/mount has the SUID bit set (the default configuration on virtually all Linux distributions). The impact is unauthorized read access to root-protected files and block devices, including backup images, disk volumes, and any file containing a valid filesystem. This issue has been patched in version 2.41.4.", "cve_priority": "medium", "cve_public_date": "2026-04-03 22:16:00 UTC" }, { "cve": "CVE-2026-3184", "url": "https://ubuntu.com/security/CVE-2026-3184", "cve_description": "A flaw was found in util-linux. Improper hostname canonicalization in the `login(1)` utility, when invoked with the `-h` option, can modify the supplied remote hostname before setting `PAM_RHOST`. A remote attacker could exploit this by providing a specially crafted hostname, potentially bypassing host-based Pluggable Authentication Modules (PAM) access control rules that rely on fully qualified domain names. This could lead to unauthorized access.", "cve_priority": "medium", "cve_public_date": "2026-04-03 19:17:00 UTC" } ], "launchpad_bugs_fixed": [ 2166882, 2153369, 2125968 ], "changes": [ { "cves": [], "log": [ "", " * d/p/ubuntu/libmount-restricted-live-creds.patch: restore live-credential", " check for libmount restricted mode (LP: #2166882)", "" ], "package": "util-linux", "version": "2.42.2-1ubuntu2", "urgency": "medium", "distributions": "stonking", "launchpad_bugs_fixed": [ 2166882 ], "author": "Nadzeya Hutsko ", "date": "Wed, 16 Sep 2026 19:36:33 +0200" }, { "cves": [], "log": [ "", " * Merge with Debian unstable (LP: #2153369).", " Added changes:", " - tests/fincore: force the use of GNU dd over uutils (LP: #2125968)", " Remaining changes:", " - Add sulogin-fallback-static-sh.patch", " Add support for /bin/static-sh as fallback if the regular shell fails to", " execute. Patch ported from sysvinit. (see LP #505887)", " - Add sulogin-lockedpwd.patch", " Make sure file systems can be fixed on machines with locked root", " accounts (as Ubuntu does by default). Don't require --force for sulogin.", " - d/rules: disable libmount mountfs support", " Disable brand new feature with --disable-libmount-mountfd-support that", " causes inability to deploy MAAS LP #2037417.", " - d/p/ubuntu/su-pty-drop-caps.patch: harden 'su --pty' to temporarily lower", " capabilities while proxying between stdin/stdout and the pty master. This", " is to avoid su from being used to exploit kernel vulnerabilities.", "" ], "package": "util-linux", "version": "2.42.2-1ubuntu1", "urgency": "medium", "distributions": "stonking", "launchpad_bugs_fixed": [ 2153369, 2125968 ], "author": "Florent 'Skia' Jacquet ", "date": "Fri, 26 Jun 2026 12:03:00 +0200" }, { "cves": [ { "cve": "CVE-2026-53612", "url": "https://ubuntu.com/security/CVE-2026-53612", "cve_description": "[Local Privilege Escalation via TOCTOU in mount(8) hook_owner.c chmod/chown]", "cve_priority": "medium", "cve_public_date": "2026-06-18" }, { "cve": "CVE-2026-53613", "url": "https://ubuntu.com/security/CVE-2026-53613", "cve_description": "[Local Privilege Escalation via TOCTOU in mount(8) - Target Path Redirection]", "cve_priority": "medium", "cve_public_date": "2026-06-18" }, { "cve": "CVE-2026-53614", "url": "https://ubuntu.com/security/CVE-2026-53614", "cve_description": "[Local Privilege Escalation via LIBMOUNT_FORCE_MOUNT2 Environment Variable - nosuid/noexec Bypass in SUID mount(8)]", "cve_priority": "medium", "cve_public_date": "2026-06-18" } ], "log": [ "", " * New upstream version, fixing security issues", " CVE-2026-53612, CVE-2026-53613, CVE-2026-53614 (Closes: #1140194,", " #1140195, #1140196)", " * Drop upstream-applied patch.", "" ], "package": "util-linux", "version": "2.42.2-1", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Wed, 17 Jun 2026 11:20:49 +0200" }, { "cves": [], "log": [ "", " * Follow debhelper 14.1, thus putting PAM files back into /etc/pam.d.", " Note that include=login is still undesirable, and packages should", " include common-* instead.", "" ], "package": "util-linux", "version": "2.42.1-6", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Tue, 16 Jun 2026 22:26:25 +0200" }, { "cves": [], "log": [ "", " * PAM config: stop using include.", " Avoid including our own PAM config files, as a workaround until PAM can", " include files from /usr/lib/pam.d.", " Should make su -(l) and runuser -l work again. See #1140029.", "" ], "package": "util-linux", "version": "2.42.1-5", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Mon, 15 Jun 2026 19:34:54 +0200" }, { "cves": [], "log": [ "", " * Update debhelper-compat to v14.", " Remove dh-sequence-installsysusers, remove ${misc:Pre-Depends} from", " Pre-Depends. PAM /etc/pam.d files are replaced by files in", " /usr/lib/pam.d.", "" ], "package": "util-linux", "version": "2.42.1-4", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Sun, 14 Jun 2026 17:28:35 +0200" }, { "cves": [], "log": [ "", " * Use upstream patch to fix FTBFS on systems with non-4K pagesizes", " (Closes: #1138789)", "" ], "package": "util-linux", "version": "2.42.1-3", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Mon, 08 Jun 2026 15:05:17 +0200" }, { "cves": [], "log": [ "", " * Fix FTBFS on systems with non-4K pagesizes (Closes: #1138789)", "" ], "package": "util-linux", "version": "2.42.1-2", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Thu, 04 Jun 2026 13:31:17 +0200" }, { "cves": [], "log": [ "", " * New upstream version", " * Refresh/drop upstream applied patches", "", " [ Karel Zak ]", " * script: fix backward compatibility for options after non-option args", " * script: fix \"--\" separator when used as option argument", " (Closes: #1132887)", "" ], "package": "util-linux", "version": "2.42.1-1", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Wed, 03 Jun 2026 20:12:19 +0200" }, { "cves": [], "log": [ "", " * Stop using Linux crypto API in hardlink(1)", "" ], "package": "util-linux", "version": "2.42-6", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Wed, 06 May 2026 20:41:22 +0200" }, { "cves": [], "log": [ "", " * Remove leftover /etc/init.d/uuidd conffile", "" ], "package": "util-linux", "version": "2.42-5", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Sun, 26 Apr 2026 14:49:42 +0200" }, { "cves": [], "log": [ "", " * Apply upstream revert of su breakage", " (Closes: #1133379, #1132588, #1132610)", "" ], "package": "util-linux", "version": "2.42-4", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Sun, 19 Apr 2026 17:36:56 +0200" }, { "cves": [], "log": [ "", " * Stop pulling deb_systemdsystemunitdir from pkg-config", " * Stop installing uuidd init script", " * Clarify /bin/login situation on Hurd", " * Install bash-completions using normal dh_install mechanism", " * Install more localized man pages", " * Simplify installing into udebs", " * Install lintian overrides into udebs", " * Run a second build without libsystemd for d-i.", " This is not great, but I see no other option at this time.", " Let's hope a libsystemd0-udeb will appear. (Closes: #1132561)", " * util-linux-extra: install copyfilerange, getino", " * Update lintian overrides", " * Update dependency libselinux1-dev to libselinux-dev", "" ], "package": "util-linux", "version": "2.42-3", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Sun, 12 Apr 2026 00:03:33 +0200" }, { "cves": [], "log": [ "", " * Add upstream patches addressing #1132887", "" ], "package": "util-linux", "version": "2.42-2", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Wed, 08 Apr 2026 18:28:21 +0200" }, { "cves": [ { "cve": "CVE-2026-27456", "url": "https://ubuntu.com/security/CVE-2026-27456", "cve_description": "util-linux is a random collection of Linux utilities. Prior to version 2.41.4, a TOCTOU (Time-of-Check-Time-of-Use) vulnerability has been identified in the SUID binary /usr/bin/mount from util-linux. The mount binary, when setting up loop devices, validates the source file path with user privileges via fork() + setuid() + realpath(), but subsequently re-canonicalizes and opens it with root privileges (euid=0) without verifying that the path has not been replaced between both operations. Neither O_NOFOLLOW, nor inode comparison, nor post-open fstat() are employed. This allows a local unprivileged user to replace the source file with a symlink pointing to any root-owned file or device during the race window, causing the SUID binary to open and mount it as root. Exploitation requires an /etc/fstab entry with user,loop options whose path points to a directory where the attacker has write permission, and that /usr/bin/mount has the SUID bit set (the default configuration on virtually all Linux distributions). The impact is unauthorized read access to root-protected files and block devices, including backup images, disk volumes, and any file containing a valid filesystem. This issue has been patched in version 2.41.4.", "cve_priority": "medium", "cve_public_date": "2026-04-03 22:16:00 UTC" } ], "log": [ "", " * New upstream release, fixing CVE-2026-27456 and a CWE-190.", " * Upload to unstable.", "" ], "package": "util-linux", "version": "2.42-1", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Thu, 02 Apr 2026 15:19:42 +0200" }, { "cves": [], "log": [ "", " * New upstream release candidate.", " * Refresh patches", "" ], "package": "util-linux", "version": "2.42~rc2-1", "urgency": "medium", "distributions": "experimental", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Thu, 26 Mar 2026 15:05:59 +0100" }, { "cves": [], "log": [ "", " * Apply upstream patches", " * Fixes unshare issue", " * Use Hurd patches directly from upstream", "" ], "package": "util-linux", "version": "2.42~rc1-3", "urgency": "medium", "distributions": "experimental", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Sun, 22 Mar 2026 15:20:19 +0100" }, { "cves": [], "log": [ "", " * Fix lsmem tests on loong64.", " Using patch from https://github.com/util-linux/util-linux/pull/4090", " * autopkgtests: switch to pkgconf", "", " [ Samuel Thibault ]", " * Fix build on Hurd", "" ], "package": "util-linux", "version": "2.42~rc1-2", "urgency": "medium", "distributions": "experimental", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Tue, 03 Mar 2026 12:43:24 +0100" }, { "cves": [ { "cve": "CVE-2026-3184", "url": "https://ubuntu.com/security/CVE-2026-3184", "cve_description": "A flaw was found in util-linux. Improper hostname canonicalization in the `login(1)` utility, when invoked with the `-h` option, can modify the supplied remote hostname before setting `PAM_RHOST`. A remote attacker could exploit this by providing a specially crafted hostname, potentially bypassing host-based Pluggable Authentication Modules (PAM) access control rules that rely on fully qualified domain names. This could lead to unauthorized access.", "cve_priority": "medium", "cve_public_date": "2026-04-03 19:17:00 UTC" } ], "log": [ "", " * New upstream release candidate.", " * includes fix for CVE-2026-3184:", " * login: use original FQDN for PAM_RHOST", " * libuuid: reset initial cont-clock time on service start (Closes:", " #1126894)", " * Symbols: use (symver) and update lists", " * Stop installing untranslated man pages", "" ], "package": "util-linux", "version": "2.42~rc1-1", "urgency": "medium", "distributions": "experimental", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Sat, 28 Feb 2026 20:37:48 +0100" }, { "cves": [], "log": [ "", " [ Chris Hofstaedtler ]", " * Follow libselinux1-dev to libselinux-dev rename (Closes: #1124751)", " * uuid-runtime: stop removing /var/run/uuidd on purge", " /run is a tmpfs, it will be cleaned up anyway. Lets us drop the postrm", " maintscript.", "", " [ Luca Boccassi ]", " * uuid-runtime: drop manual scripting in postinst and rely on sysusers.d", "" ], "package": "util-linux", "version": "2.41.3-4", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Sat, 21 Feb 2026 17:15:50 +0100" } ], "notes": null, "is_version_downgrade": false }, { "name": "gcc-16-base", "from_version": { "source_package_name": "gcc-16", "source_package_version": "16.2.0-2ubuntu1", "version": "16.2.0-2ubuntu1" }, "to_version": { "source_package_name": "gcc-16", "source_package_version": "16.2.0-3ubuntu1", "version": "16.2.0-3ubuntu1" }, "cves": [], "launchpad_bugs_fixed": [], "changes": [ { "cves": [], "log": [ "", " * Merge with Debian; remaining changes:", " - Build from upstream sources.", "" ], "package": "gcc-16", "version": "16.2.0-3ubuntu1", "urgency": "medium", "distributions": "stonking", "launchpad_bugs_fixed": [], "author": "Matthias Klose ", "date": "Fri, 18 Sep 2026 09:36:18 +0200" }, { "cves": [], "log": [ "", " * Update to git 20260918 from the gcc-16 branch.", " - Fix PR target/127306 (RISCV), PR target/127318 (RISCV),", " PR target/127153 (loongarch), PR target/126932 (RISCV),", " PR middle-end/127256, PR target/126463 (AArch64),", " PR target/126196 (RISCV), PR rtl-optimization/125683, PR debug/125421,", " PR target/127188 (RISCV), PR c++/125642, PR c++/127207, PR c++/123495,", " PR c++/126860, PR c++/124983, PR fortran/127128, PR libstdc++/124121,", " PR libstdc++/127220, PR libstdc++/127219, PR libstdc++/126949,", " PR libstdc++/127325, PR libstdc++/126800, PR target/122535 (PPC),", " PR tree-optimization/127390, PR tree-optimization/127377,", " PR tree-optimization/127262, PR tree-optimization/127130,", " PR tree-optimization/127049, PR tree-optimization/127000,", " PR tree-optimization/127000, PR tree-optimization/126760,", " PR tree-optimization/127391, PR tree-optimization/126658, PR ipa/126153,", " PR tree-optimization/126153, PR ipa/126153, PR libstdc++/127430.", " * Strip compiler executables for release builds. Closes: #1147241.", " * Bootstrap using gnat-14, to be able to remove GCC 15.", " * Add comment why libstdc++.so in the gcc_lib_dir needs to be copy", " of the library, not a symlink.", " * Apply PR target/120165 (m68k only), taken from the trunk.", "" ], "package": "gcc-16", "version": "16.2.0-3", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Matthias Klose ", "date": "Fri, 18 Sep 2026 09:35:21 +0200" } ], "notes": null, "is_version_downgrade": false }, { "name": "iproute2", "from_version": { "source_package_name": "iproute2", "source_package_version": "6.19.0-1ubuntu2", "version": "6.19.0-1ubuntu2" }, "to_version": { "source_package_name": "iproute2", "source_package_version": "7.2.0-1ubuntu1", "version": "7.2.0-1ubuntu1" }, "cves": [], "launchpad_bugs_fixed": [], "changes": [ { "cves": [], "log": [ "", " * Merge from debian, remaining changes:", " - Ubuntu FAN support", " * patches: Dropped patches that got upstreamed", "" ], "package": "iproute2", "version": "7.2.0-1ubuntu1", "urgency": "medium", "distributions": "stonking", "launchpad_bugs_fixed": [], "author": "Timo Aaltonen ", "date": "Wed, 30 Sep 2026 16:15:03 +0300" }, { "cves": [], "log": [ "", " * Update upstream source from tag 'upstream/7.2.0'", "" ], "package": "iproute2", "version": "7.2.0-1", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Luca Boccassi ", "date": "Thu, 03 Sep 2026 13:08:27 +0100" }, { "cves": [], "log": [ "", " * d/watch: ignore leading 'v' in version", " * Update upstream source from tag 'upstream/7.1.0'", " * Bump dh compat to 14", " * Drop conffile workaround for pre-Trixie version", "" ], "package": "iproute2", "version": "7.1.0-1", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Luca Boccassi ", "date": "Fri, 19 Jun 2026 14:35:55 +0100" }, { "cves": [], "log": [ "", " * Update upstream source from tag 'upstream/7.0.0'", " * Bump Standards-version to 4.7.4, no changes", " * Switch from libselinux1-dev to libselinux-dev", "" ], "package": "iproute2", "version": "7.0.0-1", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Luca Boccassi ", "date": "Thu, 16 Apr 2026 14:22:55 +0100" } ], "notes": null, "is_version_downgrade": false }, { "name": "libacl1", "from_version": { "source_package_name": "acl", "source_package_version": "2.3.2-2", "version": "2.3.2-2" }, "to_version": { "source_package_name": "acl", "source_package_version": "2.4.0-1", "version": "2.4.0-1" }, "cves": [ { "cve": "CVE-2026-54369", "url": "https://ubuntu.com/security/CVE-2026-54369", "cve_description": "acl before version 2.4.0 contains a symlink traversal vulnerability in the libacl pathname-based functions acl_get_file(), acl_set_file(), acl_extended_file(), and acl_delete_def_file() that allows local attackers to escalate privileges by replacing any pathname component with a symbolic link. Attackers who control any component of a pathname processed by a privileged caller can redirect ACL read or write operations to arbitrary files or directories, enabling unauthorized manipulation of access control lists and local privilege escalation.", "cve_priority": "medium", "cve_public_date": "2026-06-29 14:16:00 UTC" }, { "cve": "CVE-2026-54370", "url": "https://ubuntu.com/security/CVE-2026-54370", "cve_description": "acl before version 2.4.0 contains a time-of-check to time-of-use (TOCTOU) race condition vulnerability that allows local attackers to escalate privileges by replacing a pathname component with a symbolic link between an lstat() check and subsequent symlink-following operations such as stat(), chown(), chmod(), acl_get_file(), and acl_set_file(). Attackers who control a pathname component can redirect file access control list operations to arbitrary files when getfacl, setfacl, or chacl is invoked by a privileged process over an attacker-controlled path, resulting in local privilege escalation.", "cve_priority": "medium", "cve_public_date": "2026-06-29 14:16:00 UTC" } ], "launchpad_bugs_fixed": [], "changes": [ { "cves": [ { "cve": "CVE-2026-54369", "url": "https://ubuntu.com/security/CVE-2026-54369", "cve_description": "acl before version 2.4.0 contains a symlink traversal vulnerability in the libacl pathname-based functions acl_get_file(), acl_set_file(), acl_extended_file(), and acl_delete_def_file() that allows local attackers to escalate privileges by replacing any pathname component with a symbolic link. Attackers who control any component of a pathname processed by a privileged caller can redirect ACL read or write operations to arbitrary files or directories, enabling unauthorized manipulation of access control lists and local privilege escalation.", "cve_priority": "medium", "cve_public_date": "2026-06-29 14:16:00 UTC" }, { "cve": "CVE-2026-54370", "url": "https://ubuntu.com/security/CVE-2026-54370", "cve_description": "acl before version 2.4.0 contains a time-of-check to time-of-use (TOCTOU) race condition vulnerability that allows local attackers to escalate privileges by replacing a pathname component with a symbolic link between an lstat() check and subsequent symlink-following operations such as stat(), chown(), chmod(), acl_get_file(), and acl_set_file(). Attackers who control a pathname component can redirect file access control list operations to arbitrary files when getfacl, setfacl, or chacl is invoked by a privileged process over an attacker-controlled path, resulting in local privilege escalation.", "cve_priority": "medium", "cve_public_date": "2026-06-29 14:16:00 UTC" } ], "log": [ "", " * New upstream release.", " - Refresh local patches.", " - Remove upstream patches included in this release.", " - Update upstream OpenPGP signing certificates.", " - Update symbols file for new upstream release.", " - Fix symlink traversal vulnerability [CVE-2026-54369].", " - Fix time-of-check to time-of-use (TOCTOU) race condition vulnerability", " [CVE-2026-54370].", " Closes: #1141110", " * Remove build dependency on debhelper (>= 13.10) implied by", " debhelper-compat (= 13) since Debian bookworm.", " * Remove build dependencies on automake, autoconf and libtool implied", " by debhelper-compat (>= 10) since Debian stretch.", " * Switch to Standards-Version 4.7.4 (no changes needed).", " * Refactor common synopsis into a source stanza Description field.", " * Switch debian/watch URL to use the one not affected by mirroring,", " as that has delays of up to a day.", "" ], "package": "acl", "version": "2.4.0-1", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Guillem Jover ", "date": "Mon, 29 Jun 2026 23:53:15 +0200" }, { "cves": [], "log": [ "", " * Remove «Rules-Requires-Root: no», which is the current default.", " * Remove «Priority: optional», which is the current default.", " * Switch to debian/watch version 5.", " * Add spaces around make assignment operators to distinguish from shell ones.", " * Remove unused lintian overrides for hardening-no-fortify-functions.", " * Switch to Standards-Version 4.7.3 (no changes needed).", " * Reorganize patches by upstream and local provenance.", " * Fix examples build instructions and Makefile to make them work.", " * Install examples in libacl1-dev.", "" ], "package": "acl", "version": "2.3.2-3", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Guillem Jover ", "date": "Sun, 15 Feb 2026 13:55:25 +0100" } ], "notes": null, "is_version_downgrade": false }, { "name": "libapparmor1", "from_version": { "source_package_name": "apparmor", "source_package_version": "6.0.0~alpha1-0ubuntu2", "version": "6.0.0~alpha1-0ubuntu2" }, "to_version": { "source_package_name": "apparmor", "source_package_version": "6.0.0~alpha1-0ubuntu3", "version": "6.0.0~alpha1-0ubuntu3" }, "cves": [], "launchpad_bugs_fixed": [ 2163559, 2168731 ], "changes": [ { "cves": [], "log": [ "", " * Add patch to fix who username lookups (LP: #2163559)", " - d/p/u/profiles-who-add-rules-Rust-coreutils-username-lookup.patch", " * Update patch to fix loupe opening in more directories (LP: #2168731)", " - d/p/u/0004-rewrite-the-loupe-profile.patch", "" ], "package": "apparmor", "version": "6.0.0~alpha1-0ubuntu3", "urgency": "medium", "distributions": "stonking", "launchpad_bugs_fixed": [ 2163559, 2168731 ], "author": "Ryan Lee ", "date": "Thu, 24 Sep 2026 09:57:27 -0700" } ], "notes": null, "is_version_downgrade": false }, { "name": "libatomic1", "from_version": { "source_package_name": "gcc-16", "source_package_version": "16.2.0-2ubuntu1", "version": "16.2.0-2ubuntu1" }, "to_version": { "source_package_name": "gcc-16", "source_package_version": "16.2.0-3ubuntu1", "version": "16.2.0-3ubuntu1" }, "cves": [], "launchpad_bugs_fixed": [], "changes": [ { "cves": [], "log": [ "", " * Merge with Debian; remaining changes:", " - Build from upstream sources.", "" ], "package": "gcc-16", "version": "16.2.0-3ubuntu1", "urgency": "medium", "distributions": "stonking", "launchpad_bugs_fixed": [], "author": "Matthias Klose ", "date": "Fri, 18 Sep 2026 09:36:18 +0200" }, { "cves": [], "log": [ "", " * Update to git 20260918 from the gcc-16 branch.", " - Fix PR target/127306 (RISCV), PR target/127318 (RISCV),", " PR target/127153 (loongarch), PR target/126932 (RISCV),", " PR middle-end/127256, PR target/126463 (AArch64),", " PR target/126196 (RISCV), PR rtl-optimization/125683, PR debug/125421,", " PR target/127188 (RISCV), PR c++/125642, PR c++/127207, PR c++/123495,", " PR c++/126860, PR c++/124983, PR fortran/127128, PR libstdc++/124121,", " PR libstdc++/127220, PR libstdc++/127219, PR libstdc++/126949,", " PR libstdc++/127325, PR libstdc++/126800, PR target/122535 (PPC),", " PR tree-optimization/127390, PR tree-optimization/127377,", " PR tree-optimization/127262, PR tree-optimization/127130,", " PR tree-optimization/127049, PR tree-optimization/127000,", " PR tree-optimization/127000, PR tree-optimization/126760,", " PR tree-optimization/127391, PR tree-optimization/126658, PR ipa/126153,", " PR tree-optimization/126153, PR ipa/126153, PR libstdc++/127430.", " * Strip compiler executables for release builds. Closes: #1147241.", " * Bootstrap using gnat-14, to be able to remove GCC 15.", " * Add comment why libstdc++.so in the gcc_lib_dir needs to be copy", " of the library, not a symlink.", " * Apply PR target/120165 (m68k only), taken from the trunk.", "" ], "package": "gcc-16", "version": "16.2.0-3", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Matthias Klose ", "date": "Fri, 18 Sep 2026 09:35:21 +0200" } ], "notes": null, "is_version_downgrade": false }, { "name": "libblkid1", "from_version": { "source_package_name": "util-linux", "source_package_version": "2.41.3-3ubuntu2", "version": "2.41.3-3ubuntu2" }, "to_version": { "source_package_name": "util-linux", "source_package_version": "2.42.2-1ubuntu2", "version": "2.42.2-1ubuntu2" }, "cves": [ { "cve": "CVE-2026-53612", "url": "https://ubuntu.com/security/CVE-2026-53612", "cve_description": "[Local Privilege Escalation via TOCTOU in mount(8) hook_owner.c chmod/chown]", "cve_priority": "medium", "cve_public_date": "2026-06-18" }, { "cve": "CVE-2026-53613", "url": "https://ubuntu.com/security/CVE-2026-53613", "cve_description": "[Local Privilege Escalation via TOCTOU in mount(8) - Target Path Redirection]", "cve_priority": "medium", "cve_public_date": "2026-06-18" }, { "cve": "CVE-2026-53614", "url": "https://ubuntu.com/security/CVE-2026-53614", "cve_description": "[Local Privilege Escalation via LIBMOUNT_FORCE_MOUNT2 Environment Variable - nosuid/noexec Bypass in SUID mount(8)]", "cve_priority": "medium", "cve_public_date": "2026-06-18" }, { "cve": "CVE-2026-27456", "url": "https://ubuntu.com/security/CVE-2026-27456", "cve_description": "util-linux is a random collection of Linux utilities. Prior to version 2.41.4, a TOCTOU (Time-of-Check-Time-of-Use) vulnerability has been identified in the SUID binary /usr/bin/mount from util-linux. The mount binary, when setting up loop devices, validates the source file path with user privileges via fork() + setuid() + realpath(), but subsequently re-canonicalizes and opens it with root privileges (euid=0) without verifying that the path has not been replaced between both operations. Neither O_NOFOLLOW, nor inode comparison, nor post-open fstat() are employed. This allows a local unprivileged user to replace the source file with a symlink pointing to any root-owned file or device during the race window, causing the SUID binary to open and mount it as root. Exploitation requires an /etc/fstab entry with user,loop options whose path points to a directory where the attacker has write permission, and that /usr/bin/mount has the SUID bit set (the default configuration on virtually all Linux distributions). The impact is unauthorized read access to root-protected files and block devices, including backup images, disk volumes, and any file containing a valid filesystem. This issue has been patched in version 2.41.4.", "cve_priority": "medium", "cve_public_date": "2026-04-03 22:16:00 UTC" }, { "cve": "CVE-2026-3184", "url": "https://ubuntu.com/security/CVE-2026-3184", "cve_description": "A flaw was found in util-linux. Improper hostname canonicalization in the `login(1)` utility, when invoked with the `-h` option, can modify the supplied remote hostname before setting `PAM_RHOST`. A remote attacker could exploit this by providing a specially crafted hostname, potentially bypassing host-based Pluggable Authentication Modules (PAM) access control rules that rely on fully qualified domain names. This could lead to unauthorized access.", "cve_priority": "medium", "cve_public_date": "2026-04-03 19:17:00 UTC" } ], "launchpad_bugs_fixed": [ 2166882, 2153369, 2125968 ], "changes": [ { "cves": [], "log": [ "", " * d/p/ubuntu/libmount-restricted-live-creds.patch: restore live-credential", " check for libmount restricted mode (LP: #2166882)", "" ], "package": "util-linux", "version": "2.42.2-1ubuntu2", "urgency": "medium", "distributions": "stonking", "launchpad_bugs_fixed": [ 2166882 ], "author": "Nadzeya Hutsko ", "date": "Wed, 16 Sep 2026 19:36:33 +0200" }, { "cves": [], "log": [ "", " * Merge with Debian unstable (LP: #2153369).", " Added changes:", " - tests/fincore: force the use of GNU dd over uutils (LP: #2125968)", " Remaining changes:", " - Add sulogin-fallback-static-sh.patch", " Add support for /bin/static-sh as fallback if the regular shell fails to", " execute. Patch ported from sysvinit. (see LP #505887)", " - Add sulogin-lockedpwd.patch", " Make sure file systems can be fixed on machines with locked root", " accounts (as Ubuntu does by default). Don't require --force for sulogin.", " - d/rules: disable libmount mountfs support", " Disable brand new feature with --disable-libmount-mountfd-support that", " causes inability to deploy MAAS LP #2037417.", " - d/p/ubuntu/su-pty-drop-caps.patch: harden 'su --pty' to temporarily lower", " capabilities while proxying between stdin/stdout and the pty master. This", " is to avoid su from being used to exploit kernel vulnerabilities.", "" ], "package": "util-linux", "version": "2.42.2-1ubuntu1", "urgency": "medium", "distributions": "stonking", "launchpad_bugs_fixed": [ 2153369, 2125968 ], "author": "Florent 'Skia' Jacquet ", "date": "Fri, 26 Jun 2026 12:03:00 +0200" }, { "cves": [ { "cve": "CVE-2026-53612", "url": "https://ubuntu.com/security/CVE-2026-53612", "cve_description": "[Local Privilege Escalation via TOCTOU in mount(8) hook_owner.c chmod/chown]", "cve_priority": "medium", "cve_public_date": "2026-06-18" }, { "cve": "CVE-2026-53613", "url": "https://ubuntu.com/security/CVE-2026-53613", "cve_description": "[Local Privilege Escalation via TOCTOU in mount(8) - Target Path Redirection]", "cve_priority": "medium", "cve_public_date": "2026-06-18" }, { "cve": "CVE-2026-53614", "url": "https://ubuntu.com/security/CVE-2026-53614", "cve_description": "[Local Privilege Escalation via LIBMOUNT_FORCE_MOUNT2 Environment Variable - nosuid/noexec Bypass in SUID mount(8)]", "cve_priority": "medium", "cve_public_date": "2026-06-18" } ], "log": [ "", " * New upstream version, fixing security issues", " CVE-2026-53612, CVE-2026-53613, CVE-2026-53614 (Closes: #1140194,", " #1140195, #1140196)", " * Drop upstream-applied patch.", "" ], "package": "util-linux", "version": "2.42.2-1", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Wed, 17 Jun 2026 11:20:49 +0200" }, { "cves": [], "log": [ "", " * Follow debhelper 14.1, thus putting PAM files back into /etc/pam.d.", " Note that include=login is still undesirable, and packages should", " include common-* instead.", "" ], "package": "util-linux", "version": "2.42.1-6", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Tue, 16 Jun 2026 22:26:25 +0200" }, { "cves": [], "log": [ "", " * PAM config: stop using include.", " Avoid including our own PAM config files, as a workaround until PAM can", " include files from /usr/lib/pam.d.", " Should make su -(l) and runuser -l work again. See #1140029.", "" ], "package": "util-linux", "version": "2.42.1-5", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Mon, 15 Jun 2026 19:34:54 +0200" }, { "cves": [], "log": [ "", " * Update debhelper-compat to v14.", " Remove dh-sequence-installsysusers, remove ${misc:Pre-Depends} from", " Pre-Depends. PAM /etc/pam.d files are replaced by files in", " /usr/lib/pam.d.", "" ], "package": "util-linux", "version": "2.42.1-4", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Sun, 14 Jun 2026 17:28:35 +0200" }, { "cves": [], "log": [ "", " * Use upstream patch to fix FTBFS on systems with non-4K pagesizes", " (Closes: #1138789)", "" ], "package": "util-linux", "version": "2.42.1-3", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Mon, 08 Jun 2026 15:05:17 +0200" }, { "cves": [], "log": [ "", " * Fix FTBFS on systems with non-4K pagesizes (Closes: #1138789)", "" ], "package": "util-linux", "version": "2.42.1-2", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Thu, 04 Jun 2026 13:31:17 +0200" }, { "cves": [], "log": [ "", " * New upstream version", " * Refresh/drop upstream applied patches", "", " [ Karel Zak ]", " * script: fix backward compatibility for options after non-option args", " * script: fix \"--\" separator when used as option argument", " (Closes: #1132887)", "" ], "package": "util-linux", "version": "2.42.1-1", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Wed, 03 Jun 2026 20:12:19 +0200" }, { "cves": [], "log": [ "", " * Stop using Linux crypto API in hardlink(1)", "" ], "package": "util-linux", "version": "2.42-6", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Wed, 06 May 2026 20:41:22 +0200" }, { "cves": [], "log": [ "", " * Remove leftover /etc/init.d/uuidd conffile", "" ], "package": "util-linux", "version": "2.42-5", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Sun, 26 Apr 2026 14:49:42 +0200" }, { "cves": [], "log": [ "", " * Apply upstream revert of su breakage", " (Closes: #1133379, #1132588, #1132610)", "" ], "package": "util-linux", "version": "2.42-4", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Sun, 19 Apr 2026 17:36:56 +0200" }, { "cves": [], "log": [ "", " * Stop pulling deb_systemdsystemunitdir from pkg-config", " * Stop installing uuidd init script", " * Clarify /bin/login situation on Hurd", " * Install bash-completions using normal dh_install mechanism", " * Install more localized man pages", " * Simplify installing into udebs", " * Install lintian overrides into udebs", " * Run a second build without libsystemd for d-i.", " This is not great, but I see no other option at this time.", " Let's hope a libsystemd0-udeb will appear. (Closes: #1132561)", " * util-linux-extra: install copyfilerange, getino", " * Update lintian overrides", " * Update dependency libselinux1-dev to libselinux-dev", "" ], "package": "util-linux", "version": "2.42-3", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Sun, 12 Apr 2026 00:03:33 +0200" }, { "cves": [], "log": [ "", " * Add upstream patches addressing #1132887", "" ], "package": "util-linux", "version": "2.42-2", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Wed, 08 Apr 2026 18:28:21 +0200" }, { "cves": [ { "cve": "CVE-2026-27456", "url": "https://ubuntu.com/security/CVE-2026-27456", "cve_description": "util-linux is a random collection of Linux utilities. Prior to version 2.41.4, a TOCTOU (Time-of-Check-Time-of-Use) vulnerability has been identified in the SUID binary /usr/bin/mount from util-linux. The mount binary, when setting up loop devices, validates the source file path with user privileges via fork() + setuid() + realpath(), but subsequently re-canonicalizes and opens it with root privileges (euid=0) without verifying that the path has not been replaced between both operations. Neither O_NOFOLLOW, nor inode comparison, nor post-open fstat() are employed. This allows a local unprivileged user to replace the source file with a symlink pointing to any root-owned file or device during the race window, causing the SUID binary to open and mount it as root. Exploitation requires an /etc/fstab entry with user,loop options whose path points to a directory where the attacker has write permission, and that /usr/bin/mount has the SUID bit set (the default configuration on virtually all Linux distributions). The impact is unauthorized read access to root-protected files and block devices, including backup images, disk volumes, and any file containing a valid filesystem. This issue has been patched in version 2.41.4.", "cve_priority": "medium", "cve_public_date": "2026-04-03 22:16:00 UTC" } ], "log": [ "", " * New upstream release, fixing CVE-2026-27456 and a CWE-190.", " * Upload to unstable.", "" ], "package": "util-linux", "version": "2.42-1", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Thu, 02 Apr 2026 15:19:42 +0200" }, { "cves": [], "log": [ "", " * New upstream release candidate.", " * Refresh patches", "" ], "package": "util-linux", "version": "2.42~rc2-1", "urgency": "medium", "distributions": "experimental", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Thu, 26 Mar 2026 15:05:59 +0100" }, { "cves": [], "log": [ "", " * Apply upstream patches", " * Fixes unshare issue", " * Use Hurd patches directly from upstream", "" ], "package": "util-linux", "version": "2.42~rc1-3", "urgency": "medium", "distributions": "experimental", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Sun, 22 Mar 2026 15:20:19 +0100" }, { "cves": [], "log": [ "", " * Fix lsmem tests on loong64.", " Using patch from https://github.com/util-linux/util-linux/pull/4090", " * autopkgtests: switch to pkgconf", "", " [ Samuel Thibault ]", " * Fix build on Hurd", "" ], "package": "util-linux", "version": "2.42~rc1-2", "urgency": "medium", "distributions": "experimental", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Tue, 03 Mar 2026 12:43:24 +0100" }, { "cves": [ { "cve": "CVE-2026-3184", "url": "https://ubuntu.com/security/CVE-2026-3184", "cve_description": "A flaw was found in util-linux. Improper hostname canonicalization in the `login(1)` utility, when invoked with the `-h` option, can modify the supplied remote hostname before setting `PAM_RHOST`. A remote attacker could exploit this by providing a specially crafted hostname, potentially bypassing host-based Pluggable Authentication Modules (PAM) access control rules that rely on fully qualified domain names. This could lead to unauthorized access.", "cve_priority": "medium", "cve_public_date": "2026-04-03 19:17:00 UTC" } ], "log": [ "", " * New upstream release candidate.", " * includes fix for CVE-2026-3184:", " * login: use original FQDN for PAM_RHOST", " * libuuid: reset initial cont-clock time on service start (Closes:", " #1126894)", " * Symbols: use (symver) and update lists", " * Stop installing untranslated man pages", "" ], "package": "util-linux", "version": "2.42~rc1-1", "urgency": "medium", "distributions": "experimental", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Sat, 28 Feb 2026 20:37:48 +0100" }, { "cves": [], "log": [ "", " [ Chris Hofstaedtler ]", " * Follow libselinux1-dev to libselinux-dev rename (Closes: #1124751)", " * uuid-runtime: stop removing /var/run/uuidd on purge", " /run is a tmpfs, it will be cleaned up anyway. Lets us drop the postrm", " maintscript.", "", " [ Luca Boccassi ]", " * uuid-runtime: drop manual scripting in postinst and rely on sysusers.d", "" ], "package": "util-linux", "version": "2.41.3-4", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Sat, 21 Feb 2026 17:15:50 +0100" } ], "notes": null, "is_version_downgrade": false }, { "name": "libcap-ng0", "from_version": { "source_package_name": "libcap-ng", "source_package_version": "0.9.3-1", "version": "0.9.3-1" }, "to_version": { "source_package_name": "libcap-ng", "source_package_version": "0.9.6-1", "version": "0.9.6-1" }, "cves": [], "launchpad_bugs_fixed": [], "changes": [ { "cves": [], "log": [ "", " * New upstream release.", "" ], "package": "libcap-ng", "version": "0.9.6-1", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Håvard F. Aasen ", "date": "Mon, 14 Sep 2026 20:18:16 +0200" }, { "cves": [], "log": [ "", " [ Helmut Grohne ]", " * Make bluetooth build dependency optional. Closes: #1146424", "" ], "package": "libcap-ng", "version": "0.9.5-2", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Håvard F. Aasen ", "date": "Wed, 02 Sep 2026 21:59:53 +0200" }, { "cves": [], "log": [ "", " * New upstream release.", " * Fix duplicated file entry in d/copyright.", " * Replace patch by using variable in d/rules.", " * Update years in d/copyright.", " * Update symbols file.", " * Bump to debhelper version 14:", " - Remove all unneeded substvars.", " * Remove unnecessary 'Provides' in Python binary.", " * Add libbluetooth-dev to BD.", "" ], "package": "libcap-ng", "version": "0.9.5-1", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Håvard F. Aasen ", "date": "Wed, 26 Aug 2026 21:32:42 +0200" } ], "notes": null, "is_version_downgrade": false }, { "name": "libcurl4t64", "from_version": { "source_package_name": "curl", "source_package_version": "8.20.0-2ubuntu10", "version": "8.20.0-2ubuntu10" }, "to_version": { "source_package_name": "curl", "source_package_version": "8.20.0-2ubuntu11", "version": "8.20.0-2ubuntu11" }, "cves": [ { "cve": "CVE-2026-13608", "url": "https://ubuntu.com/security/CVE-2026-13608", "cve_description": "A flaw in the libcurl SASL negotiation for LDAP authentication allows an incomplete handshake sequence to be misinterpreted as a successful cryptographic verification. An attacker executing a Man-in-the-Middle (MITM) attack can inject a premature or shortcut response that bypasses complete peer validation.", "cve_priority": "medium", "cve_public_date": "2026-09-06 18:17:00 UTC" }, { "cve": "CVE-2026-18924", "url": "https://ubuntu.com/security/CVE-2026-18924", "cve_description": "A flaw in libcurl's handling of HTTP/2 Server Push streams, when the parent handle is set to share connections with other handles, can lead to use-after-free in the cleanup process.", "cve_priority": "medium", "cve_public_date": "2026-09-06 18:17:00 UTC" }, { "cve": "CVE-2026-80229", "url": "https://ubuntu.com/security/CVE-2026-80229", "cve_description": "When performing transfers via libcurl’s multi interface, pooled TLS connections can outlive their originating easy handles. In OpenSSL 3 provider configurations, libcurl attaches an allocated library context to the easy handle's state and passes it to OpenSSL without acquiring an ownership reference; destroying the easy handle prematurely frees this context while the active connection retains a dangling pointer, leading to a heap-use-after-free upon subsequent I/O or post-handshake operations.", "cve_priority": "medium", "cve_public_date": "2026-09-06 18:17:00 UTC" }, { "cve": "CVE-2026-80230", "url": "https://ubuntu.com/security/CVE-2026-80230", "cve_description": "When `CURLOPT_PINNEDPUBLICKEY` is configured alongside options that disable standard peer verification (`CURLOPT_SSL_VERIFYPEER = 0` and `CURLOPT_SSL_VERIFYHOST = 0`), libcurl fails to enforce public key pinning on connections established without a presented server certificate. Bypassing the pinning check under these disabled-verification conditions allows unauthenticated connections to succeed when they should be rejected.", "cve_priority": "medium", "cve_public_date": "2026-09-06 18:17:00 UTC" }, { "cve": "CVE-2026-80255", "url": "https://ubuntu.com/security/CVE-2026-80255", "cve_description": "A `Set-Cookie:` header using tab (horizontal tab, ASCII code 9) instead of space (ascii code 32) immediately before the `Secure` attribute causes curl to store the cookie without its Secure flag. The cookie might then wrongfully be sent over plaintext HTTP on subsequent requests to the same host.", "cve_priority": "medium", "cve_public_date": "2026-09-06 18:17:00 UTC" }, { "cve": "CVE-2026-82209", "url": "https://ubuntu.com/security/CVE-2026-82209", "cve_description": "When libpsl support is enabled, libcurl fails to enforce the Public Suffix List boundary check when processing a `Set-Cookie` header where the `Domain` attribute explicitly matches an origin host that is itself a public suffix (e.g., `Domain=co.uk` set by `co.uk`). Instead of coercing it into a strict host-only cookie, libcurl saves the cookie with wildcard domain scope (`.co.uk`). Consequently, the cookie is inappropriately included in subsequent outbound requests or HTTP redirects to arbitrary sibling subdomains under the same public suffix (e.g., `attacker.co.uk`).", "cve_priority": "medium", "cve_public_date": "2026-09-06 18:17:00 UTC" }, { "cve": "CVE-2026-10536", "url": "https://ubuntu.com/security/CVE-2026-10536", "cve_description": "A use-after-free vulnerability exists in libcurl when an application configures an HTTP/2 stream-dependency tree via `CURLOPT_STREAM_DEPENDS` or `CURLOPT_STREAM_DEPENDS_E`, subsequently invokes `curl_easy_reset()`, and finally terminates the handle with `curl_easy_cleanup()`. During this final cleanup phase, libcurl attempts to access and modify an internal structure that was already freed during the reset operation.", "cve_priority": "low", "cve_public_date": "2026-07-03 07:16:00 UTC" }, { "cve": "CVE-2026-11352", "url": "https://ubuntu.com/security/CVE-2026-11352", "cve_description": "An issue in curl’s QUIC UDP receive function allows a malicious HTTP/3 server to trigger a remote denial of service against a curl or libcurl client. Because the helper function discards zero-length UDP datagrams before counting them toward the per-call packet budget, a connected QUIC peer can continuously stream empty datagrams to indefinitely stall the client.", "cve_priority": "low", "cve_public_date": "2026-07-03 07:16:00 UTC" }, { "cve": "CVE-2026-11564", "url": "https://ubuntu.com/security/CVE-2026-11564", "cve_description": "libcurl keeps previously used connections in a connection pool for subsequent transfers to reuse if one of them matches the setup. An easy handle that first uses default native CA trust can continue trusting the native platform store after the application switches that same handle to custom CA material for a later transfer.", "cve_priority": "low", "cve_public_date": "2026-07-03 07:16:00 UTC" }, { "cve": "CVE-2026-11586", "url": "https://ubuntu.com/security/CVE-2026-11586", "cve_description": "By default, curl automatically responds to WebSocket PING frames. Because curl lacks an upper bound on memory allocation for unacknowledged frames, a malicious server can exhaust all available memory by flooding curl with rapid, sequential PING messages.", "cve_priority": "low", "cve_public_date": "2026-07-03 07:16:00 UTC" }, { "cve": "CVE-2026-11856", "url": "https://ubuntu.com/security/CVE-2026-11856", "cve_description": "Successfully using libcurl to do a transfer to a specific HTTP origin (`hostA`) with **Digest** authentication and then changing the origin to a different one (`hostB`) for a second transfer, reusing the same handle, makes libcurl wrongly pass on the `Authorization:` header field meant for `hostA`, to `hostB`.", "cve_priority": "medium", "cve_public_date": "2026-07-03 07:16:00 UTC" }, { "cve": "CVE-2026-12064", "url": "https://ubuntu.com/security/CVE-2026-12064", "cve_description": "When a user invokes curl using a schemeless URL combined with `--proto-default` sftp (or scp), a disconnect occurs between the tool layer and libcurl. The tool layer incorrectly infers the URL scheme, which erroneously bypasses the initialization of critical SSH security options like CURLOPT_SSH_HOST_PUBLIC_KEY_SHA256 and CURLOPT_SSH_KNOWNHOSTS. Conversely, the libcurl runtime successfully honors CURLOPT_DEFAULT_PROTOCOL and establishes the connection via SFTP/SCP as specified. Because the tool layer skipped the security configuration, these SSH host verification options are silently omitted, causing curl to connect to an unverified SSH remote host without throwing an error.", "cve_priority": "low", "cve_public_date": "2026-07-03 07:16:00 UTC" }, { "cve": "CVE-2026-8286", "url": "https://ubuntu.com/security/CVE-2026-8286", "cve_description": "A vulnerability exists where a new transfer that uses STARTTLS to upgrade the connection might reuse an existing live connection even though the TLS configuration mismatches so it should not.", "cve_priority": "low", "cve_public_date": "2026-07-03 07:16:00 UTC" }, { "cve": "CVE-2026-8458", "url": "https://ubuntu.com/security/CVE-2026-8458", "cve_description": "libcurl might in some circumstances reuse the wrong connection when asked to do Negotiate-authenticated ones, even when they are set to use different \"services\". libcurl features a pool of recent connections so that subsequent requests can reuse an existing connection to avoid overhead. When reusing a connection a range of criteria must be met. Due to a logical error in the code, a request that was issued by an application could wrongfully reuse an existing connection to the same server that was authenticated using different services.", "cve_priority": "low", "cve_public_date": "2026-07-03 07:16:00 UTC" }, { "cve": "CVE-2026-8924", "url": "https://ubuntu.com/security/CVE-2026-8924", "cve_description": "A flaw in curl’s cookie parsing logic allows a malicious HTTP server to set \"super cookies\" that bypass the Public Suffix List check. This enables an attacker-controlled origin to inject cookies that curl subsequently scopes and transmits to unrelated third-party domains.", "cve_priority": "low", "cve_public_date": "2026-07-03 07:16:00 UTC" }, { "cve": "CVE-2026-8925", "url": "https://ubuntu.com/security/CVE-2026-8925", "cve_description": "The curl logic that works with SASL authentication could end up cleaning up the GSASL context *twice* without clearing the pointer in between, making it `free()` the same pointer twice.", "cve_priority": "medium", "cve_public_date": "2026-07-03 07:16:00 UTC" }, { "cve": "CVE-2026-8926", "url": "https://ubuntu.com/security/CVE-2026-8926", "cve_description": "When asking curl to use a `.netrc` file to find credentials and at the same time specifying a URL with a username (without a password), like `https://user@example.com/`, curl could wrongly get and use the password for *another* user set in the `.netrc` file for that host if such a one exists and there is no match for the specified user.", "cve_priority": "low", "cve_public_date": "2026-07-03 07:16:00 UTC" }, { "cve": "CVE-2026-8927", "url": "https://ubuntu.com/security/CVE-2026-8927", "cve_description": "When reusing a libcurl handle for sequential transfers driven by environment-variable proxy configuration, libcurl fails to clear the proxy authentication state between requests. Specifically, if the initial transfer authenticates against `proxyA` using Digest auth, a subsequent transfer routed through `proxyB` erroneously leaks the `Proxy-Authorization:` header intended solely for `proxyA`.", "cve_priority": "medium", "cve_public_date": "2026-07-03 07:16:00 UTC" }, { "cve": "CVE-2026-9079", "url": "https://ubuntu.com/security/CVE-2026-9079", "cve_description": "libcurl had a flaw that when instructed to clear proxy authentication credentials which made it not do so, leaving the old credentials around to get used for subsequent transfers that should not know nor use them.", "cve_priority": "medium", "cve_public_date": "2026-07-03 07:16:00 UTC" }, { "cve": "CVE-2026-9545", "url": "https://ubuntu.com/security/CVE-2026-9545", "cve_description": "In this scenario, libcurl first uses a proper HTTP/3 server for the initial transfers, and when it makes a second transfer to the same site it has been replaced by the attacker's impostor machine - without a valid certificate. When libcurl returns to the hostname the second time with a cached SSL session (`CURLOPT_SSL_SESSIONID_CACHE` is not disabled) and early data enabled (the `CURLSSLOPT_EARLYDATA` bit is set in `CURLOPT_SSL_OPTIONS`), libcurl might send off the second request's bytes on that new connection *before* enforcing the certificate verification failure. Potentially leaking sensitive information.", "cve_priority": "low", "cve_public_date": "2026-07-03 07:16:00 UTC" }, { "cve": "CVE-2026-9080", "url": "https://ubuntu.com/security/CVE-2026-9080", "cve_description": "Calling `curl_easy_pause()` within the event-based `CURLMOPT_SOCKETFUNCTION` callback triggers a use-after-free vulnerability, where libcurl attempts to store a flag using a dangling struct pointer immediately after that pointer's memory has been freed.", "cve_priority": "low", "cve_public_date": "2026-07-03 07:16:00 UTC" }, { "cve": "CVE-2026-9546", "url": "https://ubuntu.com/security/CVE-2026-9546", "cve_description": "A vulnerability in libcurl caused the HTTP `Referer:` header to persist even when explicitly cleared. While the documentation states that passing NULL to `CURLOPT_REFERER` suppresses the header, the option failed to clear the internal state. As a result, the previous referrer string was erroneously reused and sent in subsequent requests, potentially leaking sensitive information to unintended servers.", "cve_priority": "low", "cve_public_date": "2026-07-03 07:16:00 UTC" }, { "cve": "CVE-2026-9547", "url": "https://ubuntu.com/security/CVE-2026-9547", "cve_description": "When a libcurl-based application performs transfers via `SCP://` or `SFTP://` and utilizes the `CURLOPT_SSH_KEYFUNCTION` callback, it may silently accept an untrusted server. This vulnerability occurs when a server presents a host key type that does not match the specific key type already recorded for that host in the `known_hosts` file. Instead of rejecting the mismatch, the callback mechanism fails to properly enforce the restriction, allowing the connection to succeed without warning and risking a potential man-in-the-middle attack.", "cve_priority": "low", "cve_public_date": "2026-07-03 07:16:00 UTC" } ], "launchpad_bugs_fixed": [], "changes": [ { "cves": [ { "cve": "CVE-2026-13608", "url": "https://ubuntu.com/security/CVE-2026-13608", "cve_description": "A flaw in the libcurl SASL negotiation for LDAP authentication allows an incomplete handshake sequence to be misinterpreted as a successful cryptographic verification. An attacker executing a Man-in-the-Middle (MITM) attack can inject a premature or shortcut response that bypasses complete peer validation.", "cve_priority": "medium", "cve_public_date": "2026-09-06 18:17:00 UTC" }, { "cve": "CVE-2026-18924", "url": "https://ubuntu.com/security/CVE-2026-18924", "cve_description": "A flaw in libcurl's handling of HTTP/2 Server Push streams, when the parent handle is set to share connections with other handles, can lead to use-after-free in the cleanup process.", "cve_priority": "medium", "cve_public_date": "2026-09-06 18:17:00 UTC" }, { "cve": "CVE-2026-80229", "url": "https://ubuntu.com/security/CVE-2026-80229", "cve_description": "When performing transfers via libcurl’s multi interface, pooled TLS connections can outlive their originating easy handles. In OpenSSL 3 provider configurations, libcurl attaches an allocated library context to the easy handle's state and passes it to OpenSSL without acquiring an ownership reference; destroying the easy handle prematurely frees this context while the active connection retains a dangling pointer, leading to a heap-use-after-free upon subsequent I/O or post-handshake operations.", "cve_priority": "medium", "cve_public_date": "2026-09-06 18:17:00 UTC" }, { "cve": "CVE-2026-80230", "url": "https://ubuntu.com/security/CVE-2026-80230", "cve_description": "When `CURLOPT_PINNEDPUBLICKEY` is configured alongside options that disable standard peer verification (`CURLOPT_SSL_VERIFYPEER = 0` and `CURLOPT_SSL_VERIFYHOST = 0`), libcurl fails to enforce public key pinning on connections established without a presented server certificate. Bypassing the pinning check under these disabled-verification conditions allows unauthenticated connections to succeed when they should be rejected.", "cve_priority": "medium", "cve_public_date": "2026-09-06 18:17:00 UTC" }, { "cve": "CVE-2026-80255", "url": "https://ubuntu.com/security/CVE-2026-80255", "cve_description": "A `Set-Cookie:` header using tab (horizontal tab, ASCII code 9) instead of space (ascii code 32) immediately before the `Secure` attribute causes curl to store the cookie without its Secure flag. The cookie might then wrongfully be sent over plaintext HTTP on subsequent requests to the same host.", "cve_priority": "medium", "cve_public_date": "2026-09-06 18:17:00 UTC" }, { "cve": "CVE-2026-82209", "url": "https://ubuntu.com/security/CVE-2026-82209", "cve_description": "When libpsl support is enabled, libcurl fails to enforce the Public Suffix List boundary check when processing a `Set-Cookie` header where the `Domain` attribute explicitly matches an origin host that is itself a public suffix (e.g., `Domain=co.uk` set by `co.uk`). Instead of coercing it into a strict host-only cookie, libcurl saves the cookie with wildcard domain scope (`.co.uk`). Consequently, the cookie is inappropriately included in subsequent outbound requests or HTTP redirects to arbitrary sibling subdomains under the same public suffix (e.g., `attacker.co.uk`).", "cve_priority": "medium", "cve_public_date": "2026-09-06 18:17:00 UTC" }, { "cve": "CVE-2026-10536", "url": "https://ubuntu.com/security/CVE-2026-10536", "cve_description": "A use-after-free vulnerability exists in libcurl when an application configures an HTTP/2 stream-dependency tree via `CURLOPT_STREAM_DEPENDS` or `CURLOPT_STREAM_DEPENDS_E`, subsequently invokes `curl_easy_reset()`, and finally terminates the handle with `curl_easy_cleanup()`. During this final cleanup phase, libcurl attempts to access and modify an internal structure that was already freed during the reset operation.", "cve_priority": "low", "cve_public_date": "2026-07-03 07:16:00 UTC" }, { "cve": "CVE-2026-11352", "url": "https://ubuntu.com/security/CVE-2026-11352", "cve_description": "An issue in curl’s QUIC UDP receive function allows a malicious HTTP/3 server to trigger a remote denial of service against a curl or libcurl client. Because the helper function discards zero-length UDP datagrams before counting them toward the per-call packet budget, a connected QUIC peer can continuously stream empty datagrams to indefinitely stall the client.", "cve_priority": "low", "cve_public_date": "2026-07-03 07:16:00 UTC" }, { "cve": "CVE-2026-11564", "url": "https://ubuntu.com/security/CVE-2026-11564", "cve_description": "libcurl keeps previously used connections in a connection pool for subsequent transfers to reuse if one of them matches the setup. An easy handle that first uses default native CA trust can continue trusting the native platform store after the application switches that same handle to custom CA material for a later transfer.", "cve_priority": "low", "cve_public_date": "2026-07-03 07:16:00 UTC" }, { "cve": "CVE-2026-11586", "url": "https://ubuntu.com/security/CVE-2026-11586", "cve_description": "By default, curl automatically responds to WebSocket PING frames. Because curl lacks an upper bound on memory allocation for unacknowledged frames, a malicious server can exhaust all available memory by flooding curl with rapid, sequential PING messages.", "cve_priority": "low", "cve_public_date": "2026-07-03 07:16:00 UTC" }, { "cve": "CVE-2026-11856", "url": "https://ubuntu.com/security/CVE-2026-11856", "cve_description": "Successfully using libcurl to do a transfer to a specific HTTP origin (`hostA`) with **Digest** authentication and then changing the origin to a different one (`hostB`) for a second transfer, reusing the same handle, makes libcurl wrongly pass on the `Authorization:` header field meant for `hostA`, to `hostB`.", "cve_priority": "medium", "cve_public_date": "2026-07-03 07:16:00 UTC" }, { "cve": "CVE-2026-12064", "url": "https://ubuntu.com/security/CVE-2026-12064", "cve_description": "When a user invokes curl using a schemeless URL combined with `--proto-default` sftp (or scp), a disconnect occurs between the tool layer and libcurl. The tool layer incorrectly infers the URL scheme, which erroneously bypasses the initialization of critical SSH security options like CURLOPT_SSH_HOST_PUBLIC_KEY_SHA256 and CURLOPT_SSH_KNOWNHOSTS. Conversely, the libcurl runtime successfully honors CURLOPT_DEFAULT_PROTOCOL and establishes the connection via SFTP/SCP as specified. Because the tool layer skipped the security configuration, these SSH host verification options are silently omitted, causing curl to connect to an unverified SSH remote host without throwing an error.", "cve_priority": "low", "cve_public_date": "2026-07-03 07:16:00 UTC" }, { "cve": "CVE-2026-8286", "url": "https://ubuntu.com/security/CVE-2026-8286", "cve_description": "A vulnerability exists where a new transfer that uses STARTTLS to upgrade the connection might reuse an existing live connection even though the TLS configuration mismatches so it should not.", "cve_priority": "low", "cve_public_date": "2026-07-03 07:16:00 UTC" }, { "cve": "CVE-2026-8458", "url": "https://ubuntu.com/security/CVE-2026-8458", "cve_description": "libcurl might in some circumstances reuse the wrong connection when asked to do Negotiate-authenticated ones, even when they are set to use different \"services\". libcurl features a pool of recent connections so that subsequent requests can reuse an existing connection to avoid overhead. When reusing a connection a range of criteria must be met. Due to a logical error in the code, a request that was issued by an application could wrongfully reuse an existing connection to the same server that was authenticated using different services.", "cve_priority": "low", "cve_public_date": "2026-07-03 07:16:00 UTC" }, { "cve": "CVE-2026-8924", "url": "https://ubuntu.com/security/CVE-2026-8924", "cve_description": "A flaw in curl’s cookie parsing logic allows a malicious HTTP server to set \"super cookies\" that bypass the Public Suffix List check. This enables an attacker-controlled origin to inject cookies that curl subsequently scopes and transmits to unrelated third-party domains.", "cve_priority": "low", "cve_public_date": "2026-07-03 07:16:00 UTC" }, { "cve": "CVE-2026-8925", "url": "https://ubuntu.com/security/CVE-2026-8925", "cve_description": "The curl logic that works with SASL authentication could end up cleaning up the GSASL context *twice* without clearing the pointer in between, making it `free()` the same pointer twice.", "cve_priority": "medium", "cve_public_date": "2026-07-03 07:16:00 UTC" }, { "cve": "CVE-2026-8926", "url": "https://ubuntu.com/security/CVE-2026-8926", "cve_description": "When asking curl to use a `.netrc` file to find credentials and at the same time specifying a URL with a username (without a password), like `https://user@example.com/`, curl could wrongly get and use the password for *another* user set in the `.netrc` file for that host if such a one exists and there is no match for the specified user.", "cve_priority": "low", "cve_public_date": "2026-07-03 07:16:00 UTC" }, { "cve": "CVE-2026-8927", "url": "https://ubuntu.com/security/CVE-2026-8927", "cve_description": "When reusing a libcurl handle for sequential transfers driven by environment-variable proxy configuration, libcurl fails to clear the proxy authentication state between requests. Specifically, if the initial transfer authenticates against `proxyA` using Digest auth, a subsequent transfer routed through `proxyB` erroneously leaks the `Proxy-Authorization:` header intended solely for `proxyA`.", "cve_priority": "medium", "cve_public_date": "2026-07-03 07:16:00 UTC" }, { "cve": "CVE-2026-9079", "url": "https://ubuntu.com/security/CVE-2026-9079", "cve_description": "libcurl had a flaw that when instructed to clear proxy authentication credentials which made it not do so, leaving the old credentials around to get used for subsequent transfers that should not know nor use them.", "cve_priority": "medium", "cve_public_date": "2026-07-03 07:16:00 UTC" }, { "cve": "CVE-2026-9545", "url": "https://ubuntu.com/security/CVE-2026-9545", "cve_description": "In this scenario, libcurl first uses a proper HTTP/3 server for the initial transfers, and when it makes a second transfer to the same site it has been replaced by the attacker's impostor machine - without a valid certificate. When libcurl returns to the hostname the second time with a cached SSL session (`CURLOPT_SSL_SESSIONID_CACHE` is not disabled) and early data enabled (the `CURLSSLOPT_EARLYDATA` bit is set in `CURLOPT_SSL_OPTIONS`), libcurl might send off the second request's bytes on that new connection *before* enforcing the certificate verification failure. Potentially leaking sensitive information.", "cve_priority": "low", "cve_public_date": "2026-07-03 07:16:00 UTC" }, { "cve": "CVE-2026-9080", "url": "https://ubuntu.com/security/CVE-2026-9080", "cve_description": "Calling `curl_easy_pause()` within the event-based `CURLMOPT_SOCKETFUNCTION` callback triggers a use-after-free vulnerability, where libcurl attempts to store a flag using a dangling struct pointer immediately after that pointer's memory has been freed.", "cve_priority": "low", "cve_public_date": "2026-07-03 07:16:00 UTC" }, { "cve": "CVE-2026-9546", "url": "https://ubuntu.com/security/CVE-2026-9546", "cve_description": "A vulnerability in libcurl caused the HTTP `Referer:` header to persist even when explicitly cleared. While the documentation states that passing NULL to `CURLOPT_REFERER` suppresses the header, the option failed to clear the internal state. As a result, the previous referrer string was erroneously reused and sent in subsequent requests, potentially leaking sensitive information to unintended servers.", "cve_priority": "low", "cve_public_date": "2026-07-03 07:16:00 UTC" }, { "cve": "CVE-2026-9547", "url": "https://ubuntu.com/security/CVE-2026-9547", "cve_description": "When a libcurl-based application performs transfers via `SCP://` or `SFTP://` and utilizes the `CURLOPT_SSH_KEYFUNCTION` callback, it may silently accept an untrusted server. This vulnerability occurs when a server presents a host key type that does not match the specific key type already recorded for that host in the `known_hosts` file. Instead of rejecting the mismatch, the callback mechanism fails to properly enforce the restriction, allowing the connection to succeed without warning and risking a potential man-in-the-middle attack.", "cve_priority": "low", "cve_public_date": "2026-07-03 07:16:00 UTC" } ], "log": [ "", " [ Charles Cochran ]", " * SECURITY UPDATE: Authentication bypass in LDAP SASL negotiation.", " - debian/patches/CVE-2026-13608.patch: openldap: handle", " Curl_sasl_continue() returns better in lib/openldap.c.", " - CVE-2026-13608", " * SECURITY UPDATE: Use after free in HTTP/2 server push.", " - debian/patches/CVE-2026-18924.patch: make server push transfers", " inherit share from parent in lib/http2.c.", " - CVE-2026-18924", " * SECURITY UPDATE: Use after free in OpenSSL library context.", " - debian/patches/CVE-2026-80229.patch: avoid conn reuse if provider is", " used in lib/vtls/openssl.c.", " - CVE-2026-80229", " * SECURITY UPDATE: Public key pinning bypass.", " - debian/patches/CVE-2026-80230.patch: require server cert if public", " key pinned in lib/vtls/openssl.c.", " - CVE-2026-80230", " * SECURITY UPDATE: Cookie Secure attribute bypass in Set-Cookie.", " - debian/patches/CVE-2026-80255.patch: improve TAB handling in", " lib/cookie.c, tests/data/Makefile.am, tests/data/test2885.", " - CVE-2026-80255", " * SECURITY UPDATE: Cookie injection for public suffix domains.", " - debian/patches/CVE-2026-82209.patch: ensure cookies set for an exact", " PSL domain are host-only in lib/cookie.c, tests/data/Makefile.am,", " tests/data/test1136, tests/data/test2318, tests/data/test798.", " - CVE-2026-82209", "", " [ Kyle Kernick ]", " * SECURITY UPDATE: Use after free in curl_easy_reset.", " - debian/patches/CVE-2026-10536.patch: Deprecate CURLOPT_* in", " include/curl/curl.h, lib/http2.c,", " lib/setopt.c, lib/url.c, and lib/urldata.h", " - CVE-2026-10536", " * SECURITY UPDATE: Denial of service in QUIC UDP.", " - debian/patches/CVE-2026-11352.patch: Count zero-length UDP packets", " and enforce an upper bound in", " lib/vquic/vquic.c", " - CVE-2026-11352", " * SECURITY UPDATE: Improper certificate validation in native_ca_store.", " - debian/patches/CVE-2026-11564.patch: Add bit native_ca_store_opt to", " keep the setting of CURLOPT_(PROXY_)SSL_OPTIONS and use that to", " calculate every easy transfer if a native CA store shall be used or", " not in lib/doh.c, lib/setopt.c, and lib/vtls/vtls.c", " - CVE-2026-11564", " * SECURITY UPDATE: Memory exhaustion in ws.c", " - debian/patches/CVE-2026-11586.patch: Do not send PONG frames unless", " there is sufficient space left in the websocket send buffer in", " lib/ws.c.", " - CVE-2026-11586", " * SECURITY UPDATE: Authentication Bypass by Capture-replay", " - debian/patches/CVE-2026-11856.patch: Flush state on origin or credential", " change in lib/http_digest.c, lib/urldata.h, lib/vauth/digest.c, and", " lib/vauth/digest_sspi.c.", " - CVE-2026-11856", " * SECURITY UPDATE: Improper validation in config2setopts.", " - debian/patches/CVE-2026-12064.patch: Use default protocol properly in", " src/config2setopts.c.", " - CVE-2026-12064", " * SECURITY UPDATE: Connection reuse for starttls protocols.", " - debian/patches/CVE-2026-8286.patch: When a connection is tested for", " reuse in a transfer that may upgrade to TLS (commonly via STARTTLS),", " the SSL configuration must match the existing connection in lib/url.c", " - CVE-2026-8286", " * SECURITY UPDATE: Connection reuse in SASL.", " - debian/patches/CVE-2026-8458.patch: Fix erroneous connection reuse in", " lib/curl_sasl.c, lib/http_negotiate.c, and lib/http_ntlm.c.", " - CVE-2026-8458", " * SECURITY UPDATE: Cookie injection in is_public_suffix.", " - debian/patches/CVE-2026-8924.patch: Trim trailing dots when checking", " PSL in lib/cookie.c.", " - CVE-2026-8924", " * SECURITY UPDATE: Double-free in gsasl.", " - debian/patches/CVE-2026-8925.patch: Require libgsasl 1.6.0 to handle", " NULL argument in lib/vauth/gsasl.c.", " - CVE-2026-8925", " * SECURITY UPDATE: Information disclosure in netrc.", " - debian/patches/CVE-2026-8926.patch: Do not return a password from", " parsenetrc() when the requested login did not match the credentials", " found for the matched machine in lib/netrc.c.", " - CVE-2026-8926", " * SECURITY UPDATE: Information disclosure in libcurl", " - debian/patches/CVE-2026-8927.patch: Detect if proxy is not the same as", " previous and flush state in lib/url.c and lib/urldata.h.", " - debian/patches/CVE-2026-9079.patch: Verify NULLed proxy credentials", " in lib/setopt.c.", " - debian/patches/CVE-2026-9545.patch: Hard fail when certificate", " verification fails in lib/vquic/curl_ngtcp2.c.", " - CVE-2026-8927", " - CVE-2026-9079", " - CVE-2026-9545", " * SECURITY UPDATE: Use-after-free in curl_easy_pause", " - debian/patches/CVE-2026-9080.patch: Introduce magic struct field to", " assert against NULL pointers in lib/multi_ev.c", " - debian/patches/CVE-2026-9080-post1.patch: Refresh sock entry after", " remove callback in lib/multi_ev.c", " - CVE-2026-9080", " * SECURITY UPDATE: Information disclosure in libcurl", " - debian/patches/CVE-2026-9546.patch: clear referer in lib/transfer.c", " - CVE-2026-9546", " * SECURITY UPDATE: Man-in-the-middle in libcurl.", " - debian/patches/CVE-2026-9547.patch: Reject host key mismatches in", " lib/vssh/libssh.c.", " - CVE-2026-9547", "" ], "package": "curl", "version": "8.20.0-2ubuntu11", "urgency": "medium", "distributions": "stonking", "launchpad_bugs_fixed": [], "author": "Kyle Kernick ", "date": "Wed, 23 Sep 2026 15:00:22 -0600" } ], "notes": null, "is_version_downgrade": false }, { "name": "libexpat1", "from_version": { "source_package_name": "expat", "source_package_version": "2.8.3-1", "version": "2.8.3-1" }, "to_version": { "source_package_name": "expat", "source_package_version": "2.8.3-1ubuntu1", "version": "2.8.3-1ubuntu1" }, "cves": [ { "cve": "CVE-2026-66046", "url": "https://ubuntu.com/security/CVE-2026-66046", "cve_description": "Expat through 2.8.3 contains a denial of service vulnerability caused by quadratic algorithmic complexity in the storeAtts() function in xmlparse.c, where processing N specified attributes with non-normalized values triggers an O(N^2) linear scan of elementType->defaultAtts to determine CDATA status. A remote unauthenticated attacker can supply a single well-formed XML document of a few megabytes to an application parsing untrusted XML to cause excessive CPU consumption, resulting in denial of service without requiring authentication, external entity resolution, or non-default parser options.", "cve_priority": "medium", "cve_public_date": "2026-08-18 15:16:00 UTC" }, { "cve": "CVE-2026-76641", "url": "https://ubuntu.com/security/CVE-2026-76641", "cve_description": "Expat through 2.8.3 contains an out-of-bounds read vulnerability that allows attackers to trigger memory corruption by processing XML with external entity parsers created via XML_ExternalEntityParserCreate. A struct size mismatch between ELEMENT_TYPE members causes storeAtts to read the attIndex member past allocated memory boundaries, resulting in failure to normalize whitespace in non-CDATA attributes or a wild pointer dereference causing a segfault. This vulnerability was introduced by the fix for CVE-2026-66046.", "cve_priority": "medium", "cve_public_date": "2026-08-20 18:16:00 UTC" }, { "cve": "CVE-2026-76956", "url": "https://ubuntu.com/security/CVE-2026-76956", "cve_description": "In libexpat 2.8.2 and 2.8.3 before 2.8.4, misinterpretation of getentropy's return code leads to insufficient entropy, which results in being vulnerable to hash flooding attacks, causing a denial of service via crafted XML content.", "cve_priority": "medium", "cve_public_date": "2026-08-20 05:16:00 UTC" }, { "cve": "CVE-2026-76957", "url": "https://ubuntu.com/security/CVE-2026-76957", "cve_description": "libexpat before 2.8.4 lacks handler call depth tracking with custom encoding callbacks. Thus, a use-after-free can occur. NOTE: this is similar to CVE-2026-50219, CVE-2026-56131 and CVE-2026-56412.", "cve_priority": "medium", "cve_public_date": "2026-08-20 05:16:00 UTC" } ], "launchpad_bugs_fixed": [], "changes": [ { "cves": [ { "cve": "CVE-2026-66046", "url": "https://ubuntu.com/security/CVE-2026-66046", "cve_description": "Expat through 2.8.3 contains a denial of service vulnerability caused by quadratic algorithmic complexity in the storeAtts() function in xmlparse.c, where processing N specified attributes with non-normalized values triggers an O(N^2) linear scan of elementType->defaultAtts to determine CDATA status. A remote unauthenticated attacker can supply a single well-formed XML document of a few megabytes to an application parsing untrusted XML to cause excessive CPU consumption, resulting in denial of service without requiring authentication, external entity resolution, or non-default parser options.", "cve_priority": "medium", "cve_public_date": "2026-08-18 15:16:00 UTC" }, { "cve": "CVE-2026-76641", "url": "https://ubuntu.com/security/CVE-2026-76641", "cve_description": "Expat through 2.8.3 contains an out-of-bounds read vulnerability that allows attackers to trigger memory corruption by processing XML with external entity parsers created via XML_ExternalEntityParserCreate. A struct size mismatch between ELEMENT_TYPE members causes storeAtts to read the attIndex member past allocated memory boundaries, resulting in failure to normalize whitespace in non-CDATA attributes or a wild pointer dereference causing a segfault. This vulnerability was introduced by the fix for CVE-2026-66046.", "cve_priority": "medium", "cve_public_date": "2026-08-20 18:16:00 UTC" }, { "cve": "CVE-2026-76956", "url": "https://ubuntu.com/security/CVE-2026-76956", "cve_description": "In libexpat 2.8.2 and 2.8.3 before 2.8.4, misinterpretation of getentropy's return code leads to insufficient entropy, which results in being vulnerable to hash flooding attacks, causing a denial of service via crafted XML content.", "cve_priority": "medium", "cve_public_date": "2026-08-20 05:16:00 UTC" }, { "cve": "CVE-2026-76957", "url": "https://ubuntu.com/security/CVE-2026-76957", "cve_description": "libexpat before 2.8.4 lacks handler call depth tracking with custom encoding callbacks. Thus, a use-after-free can occur. NOTE: this is similar to CVE-2026-50219, CVE-2026-56131 and CVE-2026-56412.", "cve_priority": "medium", "cve_public_date": "2026-08-20 05:16:00 UTC" } ], "log": [ "", " * SECURITY UPDATE: denial of service (algorithmic complexity of storeAtts())", " - debian/patches/CVE-2026-66046-1.patch: lib: Rename hash table", " `defaultAttsNames` to `defaultAttForName` in expat/lib/xmlparse.c.", " - debian/patches/CVE-2026-66046-2.patch: lib: Migrate .isCdata lookup from a", " linear loop to a hash table lookup in expat/lib/xmlparse.c.", " - CVE-2026-66046", " * SECURITY UPDATE: out-of-bounds read", " - debian/patches/CVE-2026-76641.patch: lib: Fix out-of-bounds read from hash", " table entries created by dtdCopy in expat/lib/xmlparse.c,", " expat/tests/basic_tests.c.", " - CVE-2026-76641", " * SECURITY UPDATE: hash flooding vulnerability (possibly causing denial of service)", " - debian/patches/CVE-2026-76956.patch: lib: Fix inverted getentropy() return", " in writeRandomBytes_getentropy in expat/lib/random_getentropy.c.", " - CVE-2026-76956", " * SECURITY UPDATE: use after free", " - debian/patches/CVE-2026-76957-1.patch: Protect custom encoding callbacks", " from parser reentry in expat/lib/xmlparse.c.", " - debian/patches/CVE-2026-76957-2.patch: Test custom encoding callback", " reentry protection in expat/tests/misc_tests.c.", " - CVE-2026-76957", "" ], "package": "expat", "version": "2.8.3-1ubuntu1", "urgency": "medium", "distributions": "stonking", "launchpad_bugs_fixed": [], "author": "Isabel Garcia Contreras ", "date": "Mon, 21 Sep 2026 15:29:35 -0400" } ], "notes": null, "is_version_downgrade": false }, { "name": "libfdisk1", "from_version": { "source_package_name": "util-linux", "source_package_version": "2.41.3-3ubuntu2", "version": "2.41.3-3ubuntu2" }, "to_version": { "source_package_name": "util-linux", "source_package_version": "2.42.2-1ubuntu2", "version": "2.42.2-1ubuntu2" }, "cves": [ { "cve": "CVE-2026-53612", "url": "https://ubuntu.com/security/CVE-2026-53612", "cve_description": "[Local Privilege Escalation via TOCTOU in mount(8) hook_owner.c chmod/chown]", "cve_priority": "medium", "cve_public_date": "2026-06-18" }, { "cve": "CVE-2026-53613", "url": "https://ubuntu.com/security/CVE-2026-53613", "cve_description": "[Local Privilege Escalation via TOCTOU in mount(8) - Target Path Redirection]", "cve_priority": "medium", "cve_public_date": "2026-06-18" }, { "cve": "CVE-2026-53614", "url": "https://ubuntu.com/security/CVE-2026-53614", "cve_description": "[Local Privilege Escalation via LIBMOUNT_FORCE_MOUNT2 Environment Variable - nosuid/noexec Bypass in SUID mount(8)]", "cve_priority": "medium", "cve_public_date": "2026-06-18" }, { "cve": "CVE-2026-27456", "url": "https://ubuntu.com/security/CVE-2026-27456", "cve_description": "util-linux is a random collection of Linux utilities. Prior to version 2.41.4, a TOCTOU (Time-of-Check-Time-of-Use) vulnerability has been identified in the SUID binary /usr/bin/mount from util-linux. The mount binary, when setting up loop devices, validates the source file path with user privileges via fork() + setuid() + realpath(), but subsequently re-canonicalizes and opens it with root privileges (euid=0) without verifying that the path has not been replaced between both operations. Neither O_NOFOLLOW, nor inode comparison, nor post-open fstat() are employed. This allows a local unprivileged user to replace the source file with a symlink pointing to any root-owned file or device during the race window, causing the SUID binary to open and mount it as root. Exploitation requires an /etc/fstab entry with user,loop options whose path points to a directory where the attacker has write permission, and that /usr/bin/mount has the SUID bit set (the default configuration on virtually all Linux distributions). The impact is unauthorized read access to root-protected files and block devices, including backup images, disk volumes, and any file containing a valid filesystem. This issue has been patched in version 2.41.4.", "cve_priority": "medium", "cve_public_date": "2026-04-03 22:16:00 UTC" }, { "cve": "CVE-2026-3184", "url": "https://ubuntu.com/security/CVE-2026-3184", "cve_description": "A flaw was found in util-linux. Improper hostname canonicalization in the `login(1)` utility, when invoked with the `-h` option, can modify the supplied remote hostname before setting `PAM_RHOST`. A remote attacker could exploit this by providing a specially crafted hostname, potentially bypassing host-based Pluggable Authentication Modules (PAM) access control rules that rely on fully qualified domain names. This could lead to unauthorized access.", "cve_priority": "medium", "cve_public_date": "2026-04-03 19:17:00 UTC" } ], "launchpad_bugs_fixed": [ 2166882, 2153369, 2125968 ], "changes": [ { "cves": [], "log": [ "", " * d/p/ubuntu/libmount-restricted-live-creds.patch: restore live-credential", " check for libmount restricted mode (LP: #2166882)", "" ], "package": "util-linux", "version": "2.42.2-1ubuntu2", "urgency": "medium", "distributions": "stonking", "launchpad_bugs_fixed": [ 2166882 ], "author": "Nadzeya Hutsko ", "date": "Wed, 16 Sep 2026 19:36:33 +0200" }, { "cves": [], "log": [ "", " * Merge with Debian unstable (LP: #2153369).", " Added changes:", " - tests/fincore: force the use of GNU dd over uutils (LP: #2125968)", " Remaining changes:", " - Add sulogin-fallback-static-sh.patch", " Add support for /bin/static-sh as fallback if the regular shell fails to", " execute. Patch ported from sysvinit. (see LP #505887)", " - Add sulogin-lockedpwd.patch", " Make sure file systems can be fixed on machines with locked root", " accounts (as Ubuntu does by default). Don't require --force for sulogin.", " - d/rules: disable libmount mountfs support", " Disable brand new feature with --disable-libmount-mountfd-support that", " causes inability to deploy MAAS LP #2037417.", " - d/p/ubuntu/su-pty-drop-caps.patch: harden 'su --pty' to temporarily lower", " capabilities while proxying between stdin/stdout and the pty master. This", " is to avoid su from being used to exploit kernel vulnerabilities.", "" ], "package": "util-linux", "version": "2.42.2-1ubuntu1", "urgency": "medium", "distributions": "stonking", "launchpad_bugs_fixed": [ 2153369, 2125968 ], "author": "Florent 'Skia' Jacquet ", "date": "Fri, 26 Jun 2026 12:03:00 +0200" }, { "cves": [ { "cve": "CVE-2026-53612", "url": "https://ubuntu.com/security/CVE-2026-53612", "cve_description": "[Local Privilege Escalation via TOCTOU in mount(8) hook_owner.c chmod/chown]", "cve_priority": "medium", "cve_public_date": "2026-06-18" }, { "cve": "CVE-2026-53613", "url": "https://ubuntu.com/security/CVE-2026-53613", "cve_description": "[Local Privilege Escalation via TOCTOU in mount(8) - Target Path Redirection]", "cve_priority": "medium", "cve_public_date": "2026-06-18" }, { "cve": "CVE-2026-53614", "url": "https://ubuntu.com/security/CVE-2026-53614", "cve_description": "[Local Privilege Escalation via LIBMOUNT_FORCE_MOUNT2 Environment Variable - nosuid/noexec Bypass in SUID mount(8)]", "cve_priority": "medium", "cve_public_date": "2026-06-18" } ], "log": [ "", " * New upstream version, fixing security issues", " CVE-2026-53612, CVE-2026-53613, CVE-2026-53614 (Closes: #1140194,", " #1140195, #1140196)", " * Drop upstream-applied patch.", "" ], "package": "util-linux", "version": "2.42.2-1", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Wed, 17 Jun 2026 11:20:49 +0200" }, { "cves": [], "log": [ "", " * Follow debhelper 14.1, thus putting PAM files back into /etc/pam.d.", " Note that include=login is still undesirable, and packages should", " include common-* instead.", "" ], "package": "util-linux", "version": "2.42.1-6", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Tue, 16 Jun 2026 22:26:25 +0200" }, { "cves": [], "log": [ "", " * PAM config: stop using include.", " Avoid including our own PAM config files, as a workaround until PAM can", " include files from /usr/lib/pam.d.", " Should make su -(l) and runuser -l work again. See #1140029.", "" ], "package": "util-linux", "version": "2.42.1-5", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Mon, 15 Jun 2026 19:34:54 +0200" }, { "cves": [], "log": [ "", " * Update debhelper-compat to v14.", " Remove dh-sequence-installsysusers, remove ${misc:Pre-Depends} from", " Pre-Depends. PAM /etc/pam.d files are replaced by files in", " /usr/lib/pam.d.", "" ], "package": "util-linux", "version": "2.42.1-4", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Sun, 14 Jun 2026 17:28:35 +0200" }, { "cves": [], "log": [ "", " * Use upstream patch to fix FTBFS on systems with non-4K pagesizes", " (Closes: #1138789)", "" ], "package": "util-linux", "version": "2.42.1-3", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Mon, 08 Jun 2026 15:05:17 +0200" }, { "cves": [], "log": [ "", " * Fix FTBFS on systems with non-4K pagesizes (Closes: #1138789)", "" ], "package": "util-linux", "version": "2.42.1-2", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Thu, 04 Jun 2026 13:31:17 +0200" }, { "cves": [], "log": [ "", " * New upstream version", " * Refresh/drop upstream applied patches", "", " [ Karel Zak ]", " * script: fix backward compatibility for options after non-option args", " * script: fix \"--\" separator when used as option argument", " (Closes: #1132887)", "" ], "package": "util-linux", "version": "2.42.1-1", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Wed, 03 Jun 2026 20:12:19 +0200" }, { "cves": [], "log": [ "", " * Stop using Linux crypto API in hardlink(1)", "" ], "package": "util-linux", "version": "2.42-6", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Wed, 06 May 2026 20:41:22 +0200" }, { "cves": [], "log": [ "", " * Remove leftover /etc/init.d/uuidd conffile", "" ], "package": "util-linux", "version": "2.42-5", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Sun, 26 Apr 2026 14:49:42 +0200" }, { "cves": [], "log": [ "", " * Apply upstream revert of su breakage", " (Closes: #1133379, #1132588, #1132610)", "" ], "package": "util-linux", "version": "2.42-4", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Sun, 19 Apr 2026 17:36:56 +0200" }, { "cves": [], "log": [ "", " * Stop pulling deb_systemdsystemunitdir from pkg-config", " * Stop installing uuidd init script", " * Clarify /bin/login situation on Hurd", " * Install bash-completions using normal dh_install mechanism", " * Install more localized man pages", " * Simplify installing into udebs", " * Install lintian overrides into udebs", " * Run a second build without libsystemd for d-i.", " This is not great, but I see no other option at this time.", " Let's hope a libsystemd0-udeb will appear. (Closes: #1132561)", " * util-linux-extra: install copyfilerange, getino", " * Update lintian overrides", " * Update dependency libselinux1-dev to libselinux-dev", "" ], "package": "util-linux", "version": "2.42-3", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Sun, 12 Apr 2026 00:03:33 +0200" }, { "cves": [], "log": [ "", " * Add upstream patches addressing #1132887", "" ], "package": "util-linux", "version": "2.42-2", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Wed, 08 Apr 2026 18:28:21 +0200" }, { "cves": [ { "cve": "CVE-2026-27456", "url": "https://ubuntu.com/security/CVE-2026-27456", "cve_description": "util-linux is a random collection of Linux utilities. Prior to version 2.41.4, a TOCTOU (Time-of-Check-Time-of-Use) vulnerability has been identified in the SUID binary /usr/bin/mount from util-linux. The mount binary, when setting up loop devices, validates the source file path with user privileges via fork() + setuid() + realpath(), but subsequently re-canonicalizes and opens it with root privileges (euid=0) without verifying that the path has not been replaced between both operations. Neither O_NOFOLLOW, nor inode comparison, nor post-open fstat() are employed. This allows a local unprivileged user to replace the source file with a symlink pointing to any root-owned file or device during the race window, causing the SUID binary to open and mount it as root. Exploitation requires an /etc/fstab entry with user,loop options whose path points to a directory where the attacker has write permission, and that /usr/bin/mount has the SUID bit set (the default configuration on virtually all Linux distributions). The impact is unauthorized read access to root-protected files and block devices, including backup images, disk volumes, and any file containing a valid filesystem. This issue has been patched in version 2.41.4.", "cve_priority": "medium", "cve_public_date": "2026-04-03 22:16:00 UTC" } ], "log": [ "", " * New upstream release, fixing CVE-2026-27456 and a CWE-190.", " * Upload to unstable.", "" ], "package": "util-linux", "version": "2.42-1", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Thu, 02 Apr 2026 15:19:42 +0200" }, { "cves": [], "log": [ "", " * New upstream release candidate.", " * Refresh patches", "" ], "package": "util-linux", "version": "2.42~rc2-1", "urgency": "medium", "distributions": "experimental", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Thu, 26 Mar 2026 15:05:59 +0100" }, { "cves": [], "log": [ "", " * Apply upstream patches", " * Fixes unshare issue", " * Use Hurd patches directly from upstream", "" ], "package": "util-linux", "version": "2.42~rc1-3", "urgency": "medium", "distributions": "experimental", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Sun, 22 Mar 2026 15:20:19 +0100" }, { "cves": [], "log": [ "", " * Fix lsmem tests on loong64.", " Using patch from https://github.com/util-linux/util-linux/pull/4090", " * autopkgtests: switch to pkgconf", "", " [ Samuel Thibault ]", " * Fix build on Hurd", "" ], "package": "util-linux", "version": "2.42~rc1-2", "urgency": "medium", "distributions": "experimental", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Tue, 03 Mar 2026 12:43:24 +0100" }, { "cves": [ { "cve": "CVE-2026-3184", "url": "https://ubuntu.com/security/CVE-2026-3184", "cve_description": "A flaw was found in util-linux. Improper hostname canonicalization in the `login(1)` utility, when invoked with the `-h` option, can modify the supplied remote hostname before setting `PAM_RHOST`. A remote attacker could exploit this by providing a specially crafted hostname, potentially bypassing host-based Pluggable Authentication Modules (PAM) access control rules that rely on fully qualified domain names. This could lead to unauthorized access.", "cve_priority": "medium", "cve_public_date": "2026-04-03 19:17:00 UTC" } ], "log": [ "", " * New upstream release candidate.", " * includes fix for CVE-2026-3184:", " * login: use original FQDN for PAM_RHOST", " * libuuid: reset initial cont-clock time on service start (Closes:", " #1126894)", " * Symbols: use (symver) and update lists", " * Stop installing untranslated man pages", "" ], "package": "util-linux", "version": "2.42~rc1-1", "urgency": "medium", "distributions": "experimental", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Sat, 28 Feb 2026 20:37:48 +0100" }, { "cves": [], "log": [ "", " [ Chris Hofstaedtler ]", " * Follow libselinux1-dev to libselinux-dev rename (Closes: #1124751)", " * uuid-runtime: stop removing /var/run/uuidd on purge", " /run is a tmpfs, it will be cleaned up anyway. Lets us drop the postrm", " maintscript.", "", " [ Luca Boccassi ]", " * uuid-runtime: drop manual scripting in postinst and rely on sysusers.d", "" ], "package": "util-linux", "version": "2.41.3-4", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Sat, 21 Feb 2026 17:15:50 +0100" } ], "notes": null, "is_version_downgrade": false }, { "name": "libgcc-s1", "from_version": { "source_package_name": "gcc-16", "source_package_version": "16.2.0-2ubuntu1", "version": "16.2.0-2ubuntu1" }, "to_version": { "source_package_name": "gcc-16", "source_package_version": "16.2.0-3ubuntu1", "version": "16.2.0-3ubuntu1" }, "cves": [], "launchpad_bugs_fixed": [], "changes": [ { "cves": [], "log": [ "", " * Merge with Debian; remaining changes:", " - Build from upstream sources.", "" ], "package": "gcc-16", "version": "16.2.0-3ubuntu1", "urgency": "medium", "distributions": "stonking", "launchpad_bugs_fixed": [], "author": "Matthias Klose ", "date": "Fri, 18 Sep 2026 09:36:18 +0200" }, { "cves": [], "log": [ "", " * Update to git 20260918 from the gcc-16 branch.", " - Fix PR target/127306 (RISCV), PR target/127318 (RISCV),", " PR target/127153 (loongarch), PR target/126932 (RISCV),", " PR middle-end/127256, PR target/126463 (AArch64),", " PR target/126196 (RISCV), PR rtl-optimization/125683, PR debug/125421,", " PR target/127188 (RISCV), PR c++/125642, PR c++/127207, PR c++/123495,", " PR c++/126860, PR c++/124983, PR fortran/127128, PR libstdc++/124121,", " PR libstdc++/127220, PR libstdc++/127219, PR libstdc++/126949,", " PR libstdc++/127325, PR libstdc++/126800, PR target/122535 (PPC),", " PR tree-optimization/127390, PR tree-optimization/127377,", " PR tree-optimization/127262, PR tree-optimization/127130,", " PR tree-optimization/127049, PR tree-optimization/127000,", " PR tree-optimization/127000, PR tree-optimization/126760,", " PR tree-optimization/127391, PR tree-optimization/126658, PR ipa/126153,", " PR tree-optimization/126153, PR ipa/126153, PR libstdc++/127430.", " * Strip compiler executables for release builds. Closes: #1147241.", " * Bootstrap using gnat-14, to be able to remove GCC 15.", " * Add comment why libstdc++.so in the gcc_lib_dir needs to be copy", " of the library, not a symlink.", " * Apply PR target/120165 (m68k only), taken from the trunk.", "" ], "package": "gcc-16", "version": "16.2.0-3", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Matthias Klose ", "date": "Fri, 18 Sep 2026 09:35:21 +0200" } ], "notes": null, "is_version_downgrade": false }, { "name": "libjs-sphinxdoc", "from_version": { "source_package_name": "sphinx", "source_package_version": "9.1.0-6", "version": "9.1.0-6" }, "to_version": { "source_package_name": "sphinx", "source_package_version": "9.1.0-8", "version": "9.1.0-8" }, "cves": [], "launchpad_bugs_fixed": [], "changes": [ { "cves": [], "log": [ "", " [ Alexandre Detiste ]", " * Drop python3-setuptools from debian/tests/control.", " * Drop build-dependency on python3-html5lib.", "", " [ Dmitry Shachnev ]", " * Add a patch to fix test failure in test_cfunction (closes: #1147737).", "" ], "package": "sphinx", "version": "9.1.0-8", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Dmitry Shachnev ", "date": "Tue, 15 Sep 2026 14:39:13 +0300" }, { "cves": [], "log": [ "", " * Team upload.", " * Drop build-dependency on python3-setuptools", "" ], "package": "sphinx", "version": "9.1.0-7", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Alexandre Detiste ", "date": "Thu, 27 Aug 2026 18:15:50 +0200" } ], "notes": null, "is_version_downgrade": false }, { "name": "libmount1", "from_version": { "source_package_name": "util-linux", "source_package_version": "2.41.3-3ubuntu2", "version": "2.41.3-3ubuntu2" }, "to_version": { "source_package_name": "util-linux", "source_package_version": "2.42.2-1ubuntu2", "version": "2.42.2-1ubuntu2" }, "cves": [ { "cve": "CVE-2026-53612", "url": "https://ubuntu.com/security/CVE-2026-53612", "cve_description": "[Local Privilege Escalation via TOCTOU in mount(8) hook_owner.c chmod/chown]", "cve_priority": "medium", "cve_public_date": "2026-06-18" }, { "cve": "CVE-2026-53613", "url": "https://ubuntu.com/security/CVE-2026-53613", "cve_description": "[Local Privilege Escalation via TOCTOU in mount(8) - Target Path Redirection]", "cve_priority": "medium", "cve_public_date": "2026-06-18" }, { "cve": "CVE-2026-53614", "url": "https://ubuntu.com/security/CVE-2026-53614", "cve_description": "[Local Privilege Escalation via LIBMOUNT_FORCE_MOUNT2 Environment Variable - nosuid/noexec Bypass in SUID mount(8)]", "cve_priority": "medium", "cve_public_date": "2026-06-18" }, { "cve": "CVE-2026-27456", "url": "https://ubuntu.com/security/CVE-2026-27456", "cve_description": "util-linux is a random collection of Linux utilities. Prior to version 2.41.4, a TOCTOU (Time-of-Check-Time-of-Use) vulnerability has been identified in the SUID binary /usr/bin/mount from util-linux. The mount binary, when setting up loop devices, validates the source file path with user privileges via fork() + setuid() + realpath(), but subsequently re-canonicalizes and opens it with root privileges (euid=0) without verifying that the path has not been replaced between both operations. Neither O_NOFOLLOW, nor inode comparison, nor post-open fstat() are employed. This allows a local unprivileged user to replace the source file with a symlink pointing to any root-owned file or device during the race window, causing the SUID binary to open and mount it as root. Exploitation requires an /etc/fstab entry with user,loop options whose path points to a directory where the attacker has write permission, and that /usr/bin/mount has the SUID bit set (the default configuration on virtually all Linux distributions). The impact is unauthorized read access to root-protected files and block devices, including backup images, disk volumes, and any file containing a valid filesystem. This issue has been patched in version 2.41.4.", "cve_priority": "medium", "cve_public_date": "2026-04-03 22:16:00 UTC" }, { "cve": "CVE-2026-3184", "url": "https://ubuntu.com/security/CVE-2026-3184", "cve_description": "A flaw was found in util-linux. Improper hostname canonicalization in the `login(1)` utility, when invoked with the `-h` option, can modify the supplied remote hostname before setting `PAM_RHOST`. A remote attacker could exploit this by providing a specially crafted hostname, potentially bypassing host-based Pluggable Authentication Modules (PAM) access control rules that rely on fully qualified domain names. This could lead to unauthorized access.", "cve_priority": "medium", "cve_public_date": "2026-04-03 19:17:00 UTC" } ], "launchpad_bugs_fixed": [ 2166882, 2153369, 2125968 ], "changes": [ { "cves": [], "log": [ "", " * d/p/ubuntu/libmount-restricted-live-creds.patch: restore live-credential", " check for libmount restricted mode (LP: #2166882)", "" ], "package": "util-linux", "version": "2.42.2-1ubuntu2", "urgency": "medium", "distributions": "stonking", "launchpad_bugs_fixed": [ 2166882 ], "author": "Nadzeya Hutsko ", "date": "Wed, 16 Sep 2026 19:36:33 +0200" }, { "cves": [], "log": [ "", " * Merge with Debian unstable (LP: #2153369).", " Added changes:", " - tests/fincore: force the use of GNU dd over uutils (LP: #2125968)", " Remaining changes:", " - Add sulogin-fallback-static-sh.patch", " Add support for /bin/static-sh as fallback if the regular shell fails to", " execute. Patch ported from sysvinit. (see LP #505887)", " - Add sulogin-lockedpwd.patch", " Make sure file systems can be fixed on machines with locked root", " accounts (as Ubuntu does by default). Don't require --force for sulogin.", " - d/rules: disable libmount mountfs support", " Disable brand new feature with --disable-libmount-mountfd-support that", " causes inability to deploy MAAS LP #2037417.", " - d/p/ubuntu/su-pty-drop-caps.patch: harden 'su --pty' to temporarily lower", " capabilities while proxying between stdin/stdout and the pty master. This", " is to avoid su from being used to exploit kernel vulnerabilities.", "" ], "package": "util-linux", "version": "2.42.2-1ubuntu1", "urgency": "medium", "distributions": "stonking", "launchpad_bugs_fixed": [ 2153369, 2125968 ], "author": "Florent 'Skia' Jacquet ", "date": "Fri, 26 Jun 2026 12:03:00 +0200" }, { "cves": [ { "cve": "CVE-2026-53612", "url": "https://ubuntu.com/security/CVE-2026-53612", "cve_description": "[Local Privilege Escalation via TOCTOU in mount(8) hook_owner.c chmod/chown]", "cve_priority": "medium", "cve_public_date": "2026-06-18" }, { "cve": "CVE-2026-53613", "url": "https://ubuntu.com/security/CVE-2026-53613", "cve_description": "[Local Privilege Escalation via TOCTOU in mount(8) - Target Path Redirection]", "cve_priority": "medium", "cve_public_date": "2026-06-18" }, { "cve": "CVE-2026-53614", "url": "https://ubuntu.com/security/CVE-2026-53614", "cve_description": "[Local Privilege Escalation via LIBMOUNT_FORCE_MOUNT2 Environment Variable - nosuid/noexec Bypass in SUID mount(8)]", "cve_priority": "medium", "cve_public_date": "2026-06-18" } ], "log": [ "", " * New upstream version, fixing security issues", " CVE-2026-53612, CVE-2026-53613, CVE-2026-53614 (Closes: #1140194,", " #1140195, #1140196)", " * Drop upstream-applied patch.", "" ], "package": "util-linux", "version": "2.42.2-1", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Wed, 17 Jun 2026 11:20:49 +0200" }, { "cves": [], "log": [ "", " * Follow debhelper 14.1, thus putting PAM files back into /etc/pam.d.", " Note that include=login is still undesirable, and packages should", " include common-* instead.", "" ], "package": "util-linux", "version": "2.42.1-6", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Tue, 16 Jun 2026 22:26:25 +0200" }, { "cves": [], "log": [ "", " * PAM config: stop using include.", " Avoid including our own PAM config files, as a workaround until PAM can", " include files from /usr/lib/pam.d.", " Should make su -(l) and runuser -l work again. See #1140029.", "" ], "package": "util-linux", "version": "2.42.1-5", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Mon, 15 Jun 2026 19:34:54 +0200" }, { "cves": [], "log": [ "", " * Update debhelper-compat to v14.", " Remove dh-sequence-installsysusers, remove ${misc:Pre-Depends} from", " Pre-Depends. PAM /etc/pam.d files are replaced by files in", " /usr/lib/pam.d.", "" ], "package": "util-linux", "version": "2.42.1-4", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Sun, 14 Jun 2026 17:28:35 +0200" }, { "cves": [], "log": [ "", " * Use upstream patch to fix FTBFS on systems with non-4K pagesizes", " (Closes: #1138789)", "" ], "package": "util-linux", "version": "2.42.1-3", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Mon, 08 Jun 2026 15:05:17 +0200" }, { "cves": [], "log": [ "", " * Fix FTBFS on systems with non-4K pagesizes (Closes: #1138789)", "" ], "package": "util-linux", "version": "2.42.1-2", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Thu, 04 Jun 2026 13:31:17 +0200" }, { "cves": [], "log": [ "", " * New upstream version", " * Refresh/drop upstream applied patches", "", " [ Karel Zak ]", " * script: fix backward compatibility for options after non-option args", " * script: fix \"--\" separator when used as option argument", " (Closes: #1132887)", "" ], "package": "util-linux", "version": "2.42.1-1", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Wed, 03 Jun 2026 20:12:19 +0200" }, { "cves": [], "log": [ "", " * Stop using Linux crypto API in hardlink(1)", "" ], "package": "util-linux", "version": "2.42-6", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Wed, 06 May 2026 20:41:22 +0200" }, { "cves": [], "log": [ "", " * Remove leftover /etc/init.d/uuidd conffile", "" ], "package": "util-linux", "version": "2.42-5", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Sun, 26 Apr 2026 14:49:42 +0200" }, { "cves": [], "log": [ "", " * Apply upstream revert of su breakage", " (Closes: #1133379, #1132588, #1132610)", "" ], "package": "util-linux", "version": "2.42-4", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Sun, 19 Apr 2026 17:36:56 +0200" }, { "cves": [], "log": [ "", " * Stop pulling deb_systemdsystemunitdir from pkg-config", " * Stop installing uuidd init script", " * Clarify /bin/login situation on Hurd", " * Install bash-completions using normal dh_install mechanism", " * Install more localized man pages", " * Simplify installing into udebs", " * Install lintian overrides into udebs", " * Run a second build without libsystemd for d-i.", " This is not great, but I see no other option at this time.", " Let's hope a libsystemd0-udeb will appear. (Closes: #1132561)", " * util-linux-extra: install copyfilerange, getino", " * Update lintian overrides", " * Update dependency libselinux1-dev to libselinux-dev", "" ], "package": "util-linux", "version": "2.42-3", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Sun, 12 Apr 2026 00:03:33 +0200" }, { "cves": [], "log": [ "", " * Add upstream patches addressing #1132887", "" ], "package": "util-linux", "version": "2.42-2", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Wed, 08 Apr 2026 18:28:21 +0200" }, { "cves": [ { "cve": "CVE-2026-27456", "url": "https://ubuntu.com/security/CVE-2026-27456", "cve_description": "util-linux is a random collection of Linux utilities. Prior to version 2.41.4, a TOCTOU (Time-of-Check-Time-of-Use) vulnerability has been identified in the SUID binary /usr/bin/mount from util-linux. The mount binary, when setting up loop devices, validates the source file path with user privileges via fork() + setuid() + realpath(), but subsequently re-canonicalizes and opens it with root privileges (euid=0) without verifying that the path has not been replaced between both operations. Neither O_NOFOLLOW, nor inode comparison, nor post-open fstat() are employed. This allows a local unprivileged user to replace the source file with a symlink pointing to any root-owned file or device during the race window, causing the SUID binary to open and mount it as root. Exploitation requires an /etc/fstab entry with user,loop options whose path points to a directory where the attacker has write permission, and that /usr/bin/mount has the SUID bit set (the default configuration on virtually all Linux distributions). The impact is unauthorized read access to root-protected files and block devices, including backup images, disk volumes, and any file containing a valid filesystem. This issue has been patched in version 2.41.4.", "cve_priority": "medium", "cve_public_date": "2026-04-03 22:16:00 UTC" } ], "log": [ "", " * New upstream release, fixing CVE-2026-27456 and a CWE-190.", " * Upload to unstable.", "" ], "package": "util-linux", "version": "2.42-1", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Thu, 02 Apr 2026 15:19:42 +0200" }, { "cves": [], "log": [ "", " * New upstream release candidate.", " * Refresh patches", "" ], "package": "util-linux", "version": "2.42~rc2-1", "urgency": "medium", "distributions": "experimental", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Thu, 26 Mar 2026 15:05:59 +0100" }, { "cves": [], "log": [ "", " * Apply upstream patches", " * Fixes unshare issue", " * Use Hurd patches directly from upstream", "" ], "package": "util-linux", "version": "2.42~rc1-3", "urgency": "medium", "distributions": "experimental", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Sun, 22 Mar 2026 15:20:19 +0100" }, { "cves": [], "log": [ "", " * Fix lsmem tests on loong64.", " Using patch from https://github.com/util-linux/util-linux/pull/4090", " * autopkgtests: switch to pkgconf", "", " [ Samuel Thibault ]", " * Fix build on Hurd", "" ], "package": "util-linux", "version": "2.42~rc1-2", "urgency": "medium", "distributions": "experimental", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Tue, 03 Mar 2026 12:43:24 +0100" }, { "cves": [ { "cve": "CVE-2026-3184", "url": "https://ubuntu.com/security/CVE-2026-3184", "cve_description": "A flaw was found in util-linux. Improper hostname canonicalization in the `login(1)` utility, when invoked with the `-h` option, can modify the supplied remote hostname before setting `PAM_RHOST`. A remote attacker could exploit this by providing a specially crafted hostname, potentially bypassing host-based Pluggable Authentication Modules (PAM) access control rules that rely on fully qualified domain names. This could lead to unauthorized access.", "cve_priority": "medium", "cve_public_date": "2026-04-03 19:17:00 UTC" } ], "log": [ "", " * New upstream release candidate.", " * includes fix for CVE-2026-3184:", " * login: use original FQDN for PAM_RHOST", " * libuuid: reset initial cont-clock time on service start (Closes:", " #1126894)", " * Symbols: use (symver) and update lists", " * Stop installing untranslated man pages", "" ], "package": "util-linux", "version": "2.42~rc1-1", "urgency": "medium", "distributions": "experimental", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Sat, 28 Feb 2026 20:37:48 +0100" }, { "cves": [], "log": [ "", " [ Chris Hofstaedtler ]", " * Follow libselinux1-dev to libselinux-dev rename (Closes: #1124751)", " * uuid-runtime: stop removing /var/run/uuidd on purge", " /run is a tmpfs, it will be cleaned up anyway. Lets us drop the postrm", " maintscript.", "", " [ Luca Boccassi ]", " * uuid-runtime: drop manual scripting in postinst and rely on sysusers.d", "" ], "package": "util-linux", "version": "2.41.3-4", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Sat, 21 Feb 2026 17:15:50 +0100" } ], "notes": null, "is_version_downgrade": false }, { "name": "libnetplan1", "from_version": { "source_package_name": "netplan.io", "source_package_version": "1.2.2-1", "version": "1.2.2-1" }, "to_version": { "source_package_name": "netplan.io", "source_package_version": "1.2.2-3", "version": "1.2.2-3" }, "cves": [], "launchpad_bugs_fixed": [], "changes": [ { "cves": [], "log": [ "", " [ Grayson Wolf ]", " * d/p/lp2168838-ovs-test.patch: Fix autopkgtests on ovs 4 (Closes: #1149299)", "" ], "package": "netplan.io", "version": "1.2.2-3", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Lukas Märdian ", "date": "Wed, 30 Sep 2026 20:59:16 +0200" }, { "cves": [], "log": [ "", " * d/t/prep-testbed: Remove LXC quirks (Closes: #1144818)", " which are not needed for incus-lxc anymore.", "" ], "package": "netplan.io", "version": "1.2.2-2", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Lukas Märdian ", "date": "Thu, 27 Aug 2026 18:12:25 +0200" } ], "notes": null, "is_version_downgrade": false }, { "name": "libpam-systemd", "from_version": { "source_package_name": "systemd", "source_package_version": "261.2-1ubuntu2", "version": "261.2-1ubuntu2" }, "to_version": { "source_package_name": "systemd", "source_package_version": "261.3-0ubuntu3", "version": "261.3-0ubuntu3" }, "cves": [], "launchpad_bugs_fixed": [ 2169316 ], "changes": [ { "cves": [], "log": [ "", " * d/rules: remove libssl3t64 Depends (LP: #2169316)", "" ], "package": "systemd", "version": "261.3-0ubuntu3", "urgency": "medium", "distributions": "stonking", "launchpad_bugs_fixed": [ 2169316 ], "author": "Nick Rosbrook ", "date": "Fri, 02 Oct 2026 13:35:38 -0400" }, { "cves": [], "log": [ "", " * d/udev.install: do not install tpm2 rules on i386", "" ], "package": "systemd", "version": "261.3-0ubuntu2", "urgency": "medium", "distributions": "stonking", "launchpad_bugs_fixed": [], "author": "Nick Rosbrook ", "date": "Wed, 23 Sep 2026 08:39:15 -0400" }, { "cves": [], "log": [ "", " * New upstream stable version 261.3", " - d/gbp.conf: set upstream branch to 261.x stable", " - d/watch: track 261.x stable", " - Update upstream source from tag 'upstream/261.3'", " Update to upstream version '261.3'", " with Debian dir 3857375784a9bdd0b319a0e09222392a5d485461", " - Bug fixes", " * mkosi: remove systemd from minimal-base on ubuntu", " * d/systemd.links: stop creating hwclock.service mask", "" ], "package": "systemd", "version": "261.3-0ubuntu1", "urgency": "medium", "distributions": "stonking", "launchpad_bugs_fixed": [], "author": "Nick Rosbrook ", "date": "Mon, 21 Sep 2026 17:15:49 -0400" } ], "notes": null, "is_version_downgrade": false }, { "name": "libparted2t64", "from_version": { "source_package_name": "parted", "source_package_version": "3.7-1", "version": "3.7-1" }, "to_version": { "source_package_name": "parted", "source_package_version": "3.8-2", "version": "3.8-2" }, "cves": [ { "cve": "CVE-2026-89085", "url": "https://ubuntu.com/security/CVE-2026-89085", "cve_description": "[heap buffer overflow in _init_fats / fat_table_read]", "cve_priority": "medium", "cve_public_date": "2026-09-17" }, { "cve": "CVE-2026-89088", "url": "https://ubuntu.com/security/CVE-2026-89088", "cve_description": "[heap buffer overflow in duplicate_legacy_root_dir]", "cve_priority": "medium", "cve_public_date": "2026-09-17" } ], "launchpad_bugs_fixed": [], "changes": [ { "cves": [], "log": [ "", " * Reupload pointing dgit to the correct upstream tag.", "" ], "package": "parted", "version": "3.8-2", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Colin Watson ", "date": "Fri, 25 Sep 2026 10:10:23 +0100" }, { "cves": [ { "cve": "CVE-2026-89085", "url": "https://ubuntu.com/security/CVE-2026-89085", "cve_description": "[heap buffer overflow in _init_fats / fat_table_read]", "cve_priority": "medium", "cve_public_date": "2026-09-17" }, { "cve": "CVE-2026-89088", "url": "https://ubuntu.com/security/CVE-2026-89088", "cve_description": "[heap buffer overflow in duplicate_legacy_root_dir]", "cve_priority": "medium", "cve_public_date": "2026-09-17" } ], "log": [ "", " * New upstream release:", " - CVE-2026-89085, CVE-2026-89088: Catch errors triggered by bad FAT", " metadata (closes: #1148169).", "" ], "package": "parted", "version": "3.8-1", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Colin Watson ", "date": "Fri, 25 Sep 2026 09:31:05 +0100" } ], "notes": null, "is_version_downgrade": false }, { "name": "libpng16-16t64", "from_version": { "source_package_name": "libpng1.6", "source_package_version": "1.6.58-1", "version": "1.6.58-1" }, "to_version": { "source_package_name": "libpng1.6", "source_package_version": "1.6.59-1", "version": "1.6.59-1" }, "cves": [], "launchpad_bugs_fixed": [], "changes": [ { "cves": [], "log": [ "", " * New upstream version 1.6.59", "" ], "package": "libpng1.6", "version": "1.6.59-1", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Gianfranco Costamagna ", "date": "Fri, 02 Oct 2026 08:04:23 +0200" } ], "notes": null, "is_version_downgrade": false }, { "name": "libpython3.14-minimal", "from_version": { "source_package_name": "python3.14", "source_package_version": "3.14.7-4ubuntu2", "version": "3.14.7-4ubuntu2" }, "to_version": { "source_package_name": "python3.14", "source_package_version": "3.14.8-1ubuntu1", "version": "3.14.8-1ubuntu1" }, "cves": [], "launchpad_bugs_fixed": [], "changes": [ { "cves": [], "log": [ "", " * Merge with Debian; remaining changes:", " - Revert the module-install-* autopkg tests to run with setuptools v78.", "" ], "package": "python3.14", "version": "3.14.8-1ubuntu1", "urgency": "medium", "distributions": "stonking", "launchpad_bugs_fixed": [], "author": "Matthias Klose ", "date": "Thu, 01 Oct 2026 22:09:47 +0200" }, { "cves": [], "log": [ "", " * Python 3.14.8 release.", " * Refresh patches.", "" ], "package": "python3.14", "version": "3.14.8-1", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Matthias Klose ", "date": "Thu, 01 Oct 2026 21:55:55 +0200" }, { "cves": [], "log": [ "", " * Merge with Debian; remaining changes:", " - Revert the module-install-* autopkg tests to run with setuptools v78.", "" ], "package": "python3.14", "version": "3.14.7-5ubuntu1", "urgency": "medium", "distributions": "stonking", "launchpad_bugs_fixed": [], "author": "Matthias Klose ", "date": "Sun, 27 Sep 2026 09:49:39 +0200" }, { "cves": [], "log": [ "", " * Update to the 3.14 branch 2026-09-27.", " * Update devhelp documentation for devhelp format v2 (Simon McVittie).", " Addresses: #1147626.", "" ], "package": "python3.14", "version": "3.14.7-5", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Matthias Klose ", "date": "Sun, 27 Sep 2026 09:22:20 +0200" } ], "notes": null, "is_version_downgrade": false }, { "name": "libpython3.14-stdlib", "from_version": { "source_package_name": "python3.14", "source_package_version": "3.14.7-4ubuntu2", "version": "3.14.7-4ubuntu2" }, "to_version": { "source_package_name": "python3.14", "source_package_version": "3.14.8-1ubuntu1", "version": "3.14.8-1ubuntu1" }, "cves": [], "launchpad_bugs_fixed": [], "changes": [ { "cves": [], "log": [ "", " * Merge with Debian; remaining changes:", " - Revert the module-install-* autopkg tests to run with setuptools v78.", "" ], "package": "python3.14", "version": "3.14.8-1ubuntu1", "urgency": "medium", "distributions": "stonking", "launchpad_bugs_fixed": [], "author": "Matthias Klose ", "date": "Thu, 01 Oct 2026 22:09:47 +0200" }, { "cves": [], "log": [ "", " * Python 3.14.8 release.", " * Refresh patches.", "" ], "package": "python3.14", "version": "3.14.8-1", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Matthias Klose ", "date": "Thu, 01 Oct 2026 21:55:55 +0200" }, { "cves": [], "log": [ "", " * Merge with Debian; remaining changes:", " - Revert the module-install-* autopkg tests to run with setuptools v78.", "" ], "package": "python3.14", "version": "3.14.7-5ubuntu1", "urgency": "medium", "distributions": "stonking", "launchpad_bugs_fixed": [], "author": "Matthias Klose ", "date": "Sun, 27 Sep 2026 09:49:39 +0200" }, { "cves": [], "log": [ "", " * Update to the 3.14 branch 2026-09-27.", " * Update devhelp documentation for devhelp format v2 (Simon McVittie).", " Addresses: #1147626.", "" ], "package": "python3.14", "version": "3.14.7-5", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Matthias Klose ", "date": "Sun, 27 Sep 2026 09:22:20 +0200" } ], "notes": null, "is_version_downgrade": false }, { "name": "libselinux1", "from_version": { "source_package_name": "libselinux", "source_package_version": "3.11-2", "version": "3.11-2" }, "to_version": { "source_package_name": "libselinux", "source_package_version": "3.11-2.1", "version": "3.11-2.1" }, "cves": [], "launchpad_bugs_fixed": [], "changes": [ { "cves": [], "log": [ "", " * Non-maintainer upload.", "", " [ Maximiliano Curia ]", " * Fix ftbfs with swig 4.5.0. Closes: #1145457.", "" ], "package": "libselinux", "version": "3.11-2.1", "urgency": "medium", "distributions": "sid", "launchpad_bugs_fixed": [], "author": "Matthias Klose ", "date": "Thu, 24 Sep 2026 15:37:09 +0200" } ], "notes": null, "is_version_downgrade": false }, { "name": "libsmartcols1", "from_version": { "source_package_name": "util-linux", "source_package_version": "2.41.3-3ubuntu2", "version": "2.41.3-3ubuntu2" }, "to_version": { "source_package_name": "util-linux", "source_package_version": "2.42.2-1ubuntu2", "version": "2.42.2-1ubuntu2" }, "cves": [ { "cve": "CVE-2026-53612", "url": "https://ubuntu.com/security/CVE-2026-53612", "cve_description": "[Local Privilege Escalation via TOCTOU in mount(8) hook_owner.c chmod/chown]", "cve_priority": "medium", "cve_public_date": "2026-06-18" }, { "cve": "CVE-2026-53613", "url": "https://ubuntu.com/security/CVE-2026-53613", "cve_description": "[Local Privilege Escalation via TOCTOU in mount(8) - Target Path Redirection]", "cve_priority": "medium", "cve_public_date": "2026-06-18" }, { "cve": "CVE-2026-53614", "url": "https://ubuntu.com/security/CVE-2026-53614", "cve_description": "[Local Privilege Escalation via LIBMOUNT_FORCE_MOUNT2 Environment Variable - nosuid/noexec Bypass in SUID mount(8)]", "cve_priority": "medium", "cve_public_date": "2026-06-18" }, { "cve": "CVE-2026-27456", "url": "https://ubuntu.com/security/CVE-2026-27456", "cve_description": "util-linux is a random collection of Linux utilities. Prior to version 2.41.4, a TOCTOU (Time-of-Check-Time-of-Use) vulnerability has been identified in the SUID binary /usr/bin/mount from util-linux. The mount binary, when setting up loop devices, validates the source file path with user privileges via fork() + setuid() + realpath(), but subsequently re-canonicalizes and opens it with root privileges (euid=0) without verifying that the path has not been replaced between both operations. Neither O_NOFOLLOW, nor inode comparison, nor post-open fstat() are employed. This allows a local unprivileged user to replace the source file with a symlink pointing to any root-owned file or device during the race window, causing the SUID binary to open and mount it as root. Exploitation requires an /etc/fstab entry with user,loop options whose path points to a directory where the attacker has write permission, and that /usr/bin/mount has the SUID bit set (the default configuration on virtually all Linux distributions). The impact is unauthorized read access to root-protected files and block devices, including backup images, disk volumes, and any file containing a valid filesystem. This issue has been patched in version 2.41.4.", "cve_priority": "medium", "cve_public_date": "2026-04-03 22:16:00 UTC" }, { "cve": "CVE-2026-3184", "url": "https://ubuntu.com/security/CVE-2026-3184", "cve_description": "A flaw was found in util-linux. Improper hostname canonicalization in the `login(1)` utility, when invoked with the `-h` option, can modify the supplied remote hostname before setting `PAM_RHOST`. A remote attacker could exploit this by providing a specially crafted hostname, potentially bypassing host-based Pluggable Authentication Modules (PAM) access control rules that rely on fully qualified domain names. This could lead to unauthorized access.", "cve_priority": "medium", "cve_public_date": "2026-04-03 19:17:00 UTC" } ], "launchpad_bugs_fixed": [ 2166882, 2153369, 2125968 ], "changes": [ { "cves": [], "log": [ "", " * d/p/ubuntu/libmount-restricted-live-creds.patch: restore live-credential", " check for libmount restricted mode (LP: #2166882)", "" ], "package": "util-linux", "version": "2.42.2-1ubuntu2", "urgency": "medium", "distributions": "stonking", "launchpad_bugs_fixed": [ 2166882 ], "author": "Nadzeya Hutsko ", "date": "Wed, 16 Sep 2026 19:36:33 +0200" }, { "cves": [], "log": [ "", " * Merge with Debian unstable (LP: #2153369).", " Added changes:", " - tests/fincore: force the use of GNU dd over uutils (LP: #2125968)", " Remaining changes:", " - Add sulogin-fallback-static-sh.patch", " Add support for /bin/static-sh as fallback if the regular shell fails to", " execute. Patch ported from sysvinit. (see LP #505887)", " - Add sulogin-lockedpwd.patch", " Make sure file systems can be fixed on machines with locked root", " accounts (as Ubuntu does by default). Don't require --force for sulogin.", " - d/rules: disable libmount mountfs support", " Disable brand new feature with --disable-libmount-mountfd-support that", " causes inability to deploy MAAS LP #2037417.", " - d/p/ubuntu/su-pty-drop-caps.patch: harden 'su --pty' to temporarily lower", " capabilities while proxying between stdin/stdout and the pty master. This", " is to avoid su from being used to exploit kernel vulnerabilities.", "" ], "package": "util-linux", "version": "2.42.2-1ubuntu1", "urgency": "medium", "distributions": "stonking", "launchpad_bugs_fixed": [ 2153369, 2125968 ], "author": "Florent 'Skia' Jacquet ", "date": "Fri, 26 Jun 2026 12:03:00 +0200" }, { "cves": [ { "cve": "CVE-2026-53612", "url": "https://ubuntu.com/security/CVE-2026-53612", "cve_description": "[Local Privilege Escalation via TOCTOU in mount(8) hook_owner.c chmod/chown]", "cve_priority": "medium", "cve_public_date": "2026-06-18" }, { "cve": "CVE-2026-53613", "url": "https://ubuntu.com/security/CVE-2026-53613", "cve_description": "[Local Privilege Escalation via TOCTOU in mount(8) - Target Path Redirection]", "cve_priority": "medium", "cve_public_date": "2026-06-18" }, { "cve": "CVE-2026-53614", "url": "https://ubuntu.com/security/CVE-2026-53614", "cve_description": "[Local Privilege Escalation via LIBMOUNT_FORCE_MOUNT2 Environment Variable - nosuid/noexec Bypass in SUID mount(8)]", "cve_priority": "medium", "cve_public_date": "2026-06-18" } ], "log": [ "", " * New upstream version, fixing security issues", " CVE-2026-53612, CVE-2026-53613, CVE-2026-53614 (Closes: #1140194,", " #1140195, #1140196)", " * Drop upstream-applied patch.", "" ], "package": "util-linux", "version": "2.42.2-1", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Wed, 17 Jun 2026 11:20:49 +0200" }, { "cves": [], "log": [ "", " * Follow debhelper 14.1, thus putting PAM files back into /etc/pam.d.", " Note that include=login is still undesirable, and packages should", " include common-* instead.", "" ], "package": "util-linux", "version": "2.42.1-6", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Tue, 16 Jun 2026 22:26:25 +0200" }, { "cves": [], "log": [ "", " * PAM config: stop using include.", " Avoid including our own PAM config files, as a workaround until PAM can", " include files from /usr/lib/pam.d.", " Should make su -(l) and runuser -l work again. See #1140029.", "" ], "package": "util-linux", "version": "2.42.1-5", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Mon, 15 Jun 2026 19:34:54 +0200" }, { "cves": [], "log": [ "", " * Update debhelper-compat to v14.", " Remove dh-sequence-installsysusers, remove ${misc:Pre-Depends} from", " Pre-Depends. PAM /etc/pam.d files are replaced by files in", " /usr/lib/pam.d.", "" ], "package": "util-linux", "version": "2.42.1-4", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Sun, 14 Jun 2026 17:28:35 +0200" }, { "cves": [], "log": [ "", " * Use upstream patch to fix FTBFS on systems with non-4K pagesizes", " (Closes: #1138789)", "" ], "package": "util-linux", "version": "2.42.1-3", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Mon, 08 Jun 2026 15:05:17 +0200" }, { "cves": [], "log": [ "", " * Fix FTBFS on systems with non-4K pagesizes (Closes: #1138789)", "" ], "package": "util-linux", "version": "2.42.1-2", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Thu, 04 Jun 2026 13:31:17 +0200" }, { "cves": [], "log": [ "", " * New upstream version", " * Refresh/drop upstream applied patches", "", " [ Karel Zak ]", " * script: fix backward compatibility for options after non-option args", " * script: fix \"--\" separator when used as option argument", " (Closes: #1132887)", "" ], "package": "util-linux", "version": "2.42.1-1", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Wed, 03 Jun 2026 20:12:19 +0200" }, { "cves": [], "log": [ "", " * Stop using Linux crypto API in hardlink(1)", "" ], "package": "util-linux", "version": "2.42-6", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Wed, 06 May 2026 20:41:22 +0200" }, { "cves": [], "log": [ "", " * Remove leftover /etc/init.d/uuidd conffile", "" ], "package": "util-linux", "version": "2.42-5", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Sun, 26 Apr 2026 14:49:42 +0200" }, { "cves": [], "log": [ "", " * Apply upstream revert of su breakage", " (Closes: #1133379, #1132588, #1132610)", "" ], "package": "util-linux", "version": "2.42-4", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Sun, 19 Apr 2026 17:36:56 +0200" }, { "cves": [], "log": [ "", " * Stop pulling deb_systemdsystemunitdir from pkg-config", " * Stop installing uuidd init script", " * Clarify /bin/login situation on Hurd", " * Install bash-completions using normal dh_install mechanism", " * Install more localized man pages", " * Simplify installing into udebs", " * Install lintian overrides into udebs", " * Run a second build without libsystemd for d-i.", " This is not great, but I see no other option at this time.", " Let's hope a libsystemd0-udeb will appear. (Closes: #1132561)", " * util-linux-extra: install copyfilerange, getino", " * Update lintian overrides", " * Update dependency libselinux1-dev to libselinux-dev", "" ], "package": "util-linux", "version": "2.42-3", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Sun, 12 Apr 2026 00:03:33 +0200" }, { "cves": [], "log": [ "", " * Add upstream patches addressing #1132887", "" ], "package": "util-linux", "version": "2.42-2", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Wed, 08 Apr 2026 18:28:21 +0200" }, { "cves": [ { "cve": "CVE-2026-27456", "url": "https://ubuntu.com/security/CVE-2026-27456", "cve_description": "util-linux is a random collection of Linux utilities. Prior to version 2.41.4, a TOCTOU (Time-of-Check-Time-of-Use) vulnerability has been identified in the SUID binary /usr/bin/mount from util-linux. The mount binary, when setting up loop devices, validates the source file path with user privileges via fork() + setuid() + realpath(), but subsequently re-canonicalizes and opens it with root privileges (euid=0) without verifying that the path has not been replaced between both operations. Neither O_NOFOLLOW, nor inode comparison, nor post-open fstat() are employed. This allows a local unprivileged user to replace the source file with a symlink pointing to any root-owned file or device during the race window, causing the SUID binary to open and mount it as root. Exploitation requires an /etc/fstab entry with user,loop options whose path points to a directory where the attacker has write permission, and that /usr/bin/mount has the SUID bit set (the default configuration on virtually all Linux distributions). The impact is unauthorized read access to root-protected files and block devices, including backup images, disk volumes, and any file containing a valid filesystem. This issue has been patched in version 2.41.4.", "cve_priority": "medium", "cve_public_date": "2026-04-03 22:16:00 UTC" } ], "log": [ "", " * New upstream release, fixing CVE-2026-27456 and a CWE-190.", " * Upload to unstable.", "" ], "package": "util-linux", "version": "2.42-1", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Thu, 02 Apr 2026 15:19:42 +0200" }, { "cves": [], "log": [ "", " * New upstream release candidate.", " * Refresh patches", "" ], "package": "util-linux", "version": "2.42~rc2-1", "urgency": "medium", "distributions": "experimental", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Thu, 26 Mar 2026 15:05:59 +0100" }, { "cves": [], "log": [ "", " * Apply upstream patches", " * Fixes unshare issue", " * Use Hurd patches directly from upstream", "" ], "package": "util-linux", "version": "2.42~rc1-3", "urgency": "medium", "distributions": "experimental", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Sun, 22 Mar 2026 15:20:19 +0100" }, { "cves": [], "log": [ "", " * Fix lsmem tests on loong64.", " Using patch from https://github.com/util-linux/util-linux/pull/4090", " * autopkgtests: switch to pkgconf", "", " [ Samuel Thibault ]", " * Fix build on Hurd", "" ], "package": "util-linux", "version": "2.42~rc1-2", "urgency": "medium", "distributions": "experimental", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Tue, 03 Mar 2026 12:43:24 +0100" }, { "cves": [ { "cve": "CVE-2026-3184", "url": "https://ubuntu.com/security/CVE-2026-3184", "cve_description": "A flaw was found in util-linux. Improper hostname canonicalization in the `login(1)` utility, when invoked with the `-h` option, can modify the supplied remote hostname before setting `PAM_RHOST`. A remote attacker could exploit this by providing a specially crafted hostname, potentially bypassing host-based Pluggable Authentication Modules (PAM) access control rules that rely on fully qualified domain names. This could lead to unauthorized access.", "cve_priority": "medium", "cve_public_date": "2026-04-03 19:17:00 UTC" } ], "log": [ "", " * New upstream release candidate.", " * includes fix for CVE-2026-3184:", " * login: use original FQDN for PAM_RHOST", " * libuuid: reset initial cont-clock time on service start (Closes:", " #1126894)", " * Symbols: use (symver) and update lists", " * Stop installing untranslated man pages", "" ], "package": "util-linux", "version": "2.42~rc1-1", "urgency": "medium", "distributions": "experimental", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Sat, 28 Feb 2026 20:37:48 +0100" }, { "cves": [], "log": [ "", " [ Chris Hofstaedtler ]", " * Follow libselinux1-dev to libselinux-dev rename (Closes: #1124751)", " * uuid-runtime: stop removing /var/run/uuidd on purge", " /run is a tmpfs, it will be cleaned up anyway. Lets us drop the postrm", " maintscript.", "", " [ Luca Boccassi ]", " * uuid-runtime: drop manual scripting in postinst and rely on sysusers.d", "" ], "package": "util-linux", "version": "2.41.3-4", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Sat, 21 Feb 2026 17:15:50 +0100" } ], "notes": null, "is_version_downgrade": false }, { "name": "libssh2-1t64", "from_version": { "source_package_name": "libssh2", "source_package_version": "1.11.1-4ubuntu3", "version": "1.11.1-4ubuntu3" }, "to_version": { "source_package_name": "libssh2", "source_package_version": "1.11.1-6", "version": "1.11.1-6" }, "cves": [ { "cve": "CVE-2026-66032", "url": "https://ubuntu.com/security/CVE-2026-66032", "cve_description": "libssh2 through 1.11.1, fixed in commit 5e47761, contains a double-free vulnerability in the sftp_open() function in src/sftp.c that allows a malicious SSH server to corrupt the heap of any authenticated client opening an SFTP session. When a server responds to SSH_FXP_OPEN with SSH_FXP_STATUS containing FX_OK, the response data buffer is freed, and if a subsequent sftp_packet_require() call returns a specific error such as LIBSSH2_ERROR_CHANNEL_PACKET_EXCEEDED, the same pointer is freed a second time, enabling tcache dup conditions on glibc systems that allow overlapping allocations and function pointer overwrites.", "cve_priority": "medium", "cve_public_date": "2026-07-24 17:17:00 UTC" }, { "cve": "CVE-2026-66033", "url": "https://ubuntu.com/security/CVE-2026-66033", "cve_description": "libssh2 through 1.11.1, fixed in commit a2ed82d, contains a pre-authentication integer underflow vulnerability in the ssh2_cipher_crypt() function in src/openssl.c that allows a malicious SSH server to crash any connecting client by negotiating AES-GCM ciphers during handshake. Attackers can exploit the underflow in the expression computing blocksize minus aadlen minus authentication tag length to trigger an out-of-bounds read and a memcpy call with a near-SIZE_MAX length argument, causing immediate process crash before any authentication occurs.", "cve_priority": "medium", "cve_public_date": "2026-07-24 17:17:00 UTC" }, { "cve": "CVE-2026-66035", "url": "https://ubuntu.com/security/CVE-2026-66035", "cve_description": "libssh2 through 1.11.1, fixed in commit 42e33d8, contains a pre-authentication heap buffer overflow vulnerability that allows a malicious SSH server to corrupt heap metadata in any connecting client by sending a packet with a packet_length smaller than the cipher's block size during Encrypt-then-MAC cipher negotiation. In the fullpacket() function in src/transport.c, the ETM path allocates a buffer of packet_length bytes but copies blocksize minus one bytes via memcpy, causing an overflow that on 32-bit glibc writes attacker-controlled bytes into an adjacent chunk's SIZE field, enabling tcache bin confusion, overlapping live objects, and function pointer overwrite during the session handshake before authentication.", "cve_priority": "medium", "cve_public_date": "2026-07-24 17:17:00 UTC" }, { "cve": "CVE-2026-5805", "url": "https://ubuntu.com/security/CVE-2026-5805", "cve_description": "", "cve_priority": "n/a", "cve_public_date": "" }, { "cve": "CVE-2026-58051", "url": "https://ubuntu.com/security/CVE-2026-58051", "cve_description": "libssh2 through 1.11.1 grows its publickey list with SSH2_REALLOC but does not zero-initialize new entries before parsing populates them, so a parse failure reaching the cleanup path leaves libssh2_publickey_list_free operating on an uninitialized entry. A malicious SSH server offering the publickey subsystem can use a malformed response to make cleanup free an uninitialized, attacker-influenceable attrs pointer in a connecting libssh2 client.", "cve_priority": "medium", "cve_public_date": "2026-06-28 02:16:00 UTC" }, { "cve": "CVE-2026-58050", "url": "https://ubuntu.com/security/CVE-2026-58050", "cve_description": "libssh2 through 1.11.1 reads an attacker-controlled 32-bit attribute count from a publickey-subsystem response and uses it in the allocation num_attrs * sizeof(libssh2_publickey_attribute) without bounds checking, so on 32-bit platforms the multiplication overflows to an undersized buffer. A malicious SSH server can then drive the attribute-parsing loop to write past the allocation, causing a heap buffer overflow in a connecting libssh2 client.", "cve_priority": "medium", "cve_public_date": "2026-06-28 02:16:00 UTC" } ], "launchpad_bugs_fixed": [], "changes": [ { "cves": [ { "cve": "CVE-2026-66032", "url": "https://ubuntu.com/security/CVE-2026-66032", "cve_description": "libssh2 through 1.11.1, fixed in commit 5e47761, contains a double-free vulnerability in the sftp_open() function in src/sftp.c that allows a malicious SSH server to corrupt the heap of any authenticated client opening an SFTP session. When a server responds to SSH_FXP_OPEN with SSH_FXP_STATUS containing FX_OK, the response data buffer is freed, and if a subsequent sftp_packet_require() call returns a specific error such as LIBSSH2_ERROR_CHANNEL_PACKET_EXCEEDED, the same pointer is freed a second time, enabling tcache dup conditions on glibc systems that allow overlapping allocations and function pointer overwrites.", "cve_priority": "medium", "cve_public_date": "2026-07-24 17:17:00 UTC" }, { "cve": "CVE-2026-66033", "url": "https://ubuntu.com/security/CVE-2026-66033", "cve_description": "libssh2 through 1.11.1, fixed in commit a2ed82d, contains a pre-authentication integer underflow vulnerability in the ssh2_cipher_crypt() function in src/openssl.c that allows a malicious SSH server to crash any connecting client by negotiating AES-GCM ciphers during handshake. Attackers can exploit the underflow in the expression computing blocksize minus aadlen minus authentication tag length to trigger an out-of-bounds read and a memcpy call with a near-SIZE_MAX length argument, causing immediate process crash before any authentication occurs.", "cve_priority": "medium", "cve_public_date": "2026-07-24 17:17:00 UTC" }, { "cve": "CVE-2026-66035", "url": "https://ubuntu.com/security/CVE-2026-66035", "cve_description": "libssh2 through 1.11.1, fixed in commit 42e33d8, contains a pre-authentication heap buffer overflow vulnerability that allows a malicious SSH server to corrupt heap metadata in any connecting client by sending a packet with a packet_length smaller than the cipher's block size during Encrypt-then-MAC cipher negotiation. In the fullpacket() function in src/transport.c, the ETM path allocates a buffer of packet_length bytes but copies blocksize minus one bytes via memcpy, causing an overflow that on 32-bit glibc writes attacker-controlled bytes into an adjacent chunk's SIZE field, enabling tcache bin confusion, overlapping live objects, and function pointer overwrite during the session handshake before authentication.", "cve_priority": "medium", "cve_public_date": "2026-07-24 17:17:00 UTC" } ], "log": [ "", " * SECURITY UPDATE: double-free vulnerability in sftp_open()", " - debian/patches/CVE-2026-66032.patch: Prevent dangling pointer by", " nullifying data in src/sftp.c.", " - CVE-2026-66032", " * SECURITY UPDATE: pre-authentication integer underflow vulnerability", " - debian/patches/CVE-2026-66033.patch: fix potential OOB read/write with", " AES-GCM in `ssh2_cipher_crypt()` in src/openssl.c.", " - CVE-2026-66033", " * SECURITY UPDATE: pre-authentication heap buffer overflow vulnerability", " - debian/patches/CVE-2026-66035.patch: transport: fix potential heap", " overflow on ETM decrypt in src/transport.c.", " - CVE-2026-66035", "" ], "package": "libssh2", "version": "1.11.1-4ubuntu3", "urgency": "medium", "distributions": "stonking", "launchpad_bugs_fixed": [], "author": "Marc Deslauriers ", "date": "Wed, 02 Sep 2026 07:45:31 -0400" }, { "cves": [], "log": [ "", " * No-change rebuild against libssl4", "" ], "package": "libssh2", "version": "1.11.1-4ubuntu2", "urgency": "medium", "distributions": "stonking", "launchpad_bugs_fixed": [], "author": "Ravi Kant Sharma ", "date": "Fri, 24 Jul 2026 07:50:24 +0000" }, { "cves": [ { "cve": "CVE-2026-5805", "url": "https://ubuntu.com/security/CVE-2026-5805", "cve_description": "", "cve_priority": "n/a", "cve_public_date": "" }, { "cve": "CVE-2026-58051", "url": "https://ubuntu.com/security/CVE-2026-58051", "cve_description": "libssh2 through 1.11.1 grows its publickey list with SSH2_REALLOC but does not zero-initialize new entries before parsing populates them, so a parse failure reaching the cleanup path leaves libssh2_publickey_list_free operating on an uninitialized entry. A malicious SSH server offering the publickey subsystem can use a malformed response to make cleanup free an uninitialized, attacker-influenceable attrs pointer in a connecting libssh2 client.", "cve_priority": "medium", "cve_public_date": "2026-06-28 02:16:00 UTC" }, { "cve": "CVE-2026-58050", "url": "https://ubuntu.com/security/CVE-2026-58050", "cve_description": "libssh2 through 1.11.1 reads an attacker-controlled 32-bit attribute count from a publickey-subsystem response and uses it in the allocation num_attrs * sizeof(libssh2_publickey_attribute) without bounds checking, so on 32-bit platforms the multiplication overflows to an undersized buffer. A malicious SSH server can then drive the attribute-parsing loop to write past the allocation, causing a heap buffer overflow in a connecting libssh2 client.", "cve_priority": "medium", "cve_public_date": "2026-06-28 02:16:00 UTC" } ], "log": [ "", " * SECURITY UPDATE: Multiple security issues in publickey", " - debian/patches/CVE-2026-5805x-pre1.patch: fix potential arbitrary free", " in libssh2_publickey_list_fetch().", " - debian/patches/CVE-2026-5805x-pre2.patch: fix potential multiplication", " overflow in 32-bit libssh2_publickey_list_fetch().", " - debian/patches/CVE-2026-5805x-pre3.patch: cap packet size in", " publickey_packet_receive().", " - debian/patches/CVE-2026-5805x-pre4.patch: fix leaks when", " publickey_response_success() received <8 bytes.", " - debian/patches/CVE-2026-5805x-pre5.patch: fix potential OOB read in", " publickey_response_success().", " - debian/patches/CVE-2026-58051.patch: fix potential OOB read in", " libssh2_publickey_list_fetch().", " - debian/patches/CVE-2026-5805x-pre6.patch: fix potential OOB read.", " - debian/patches/CVE-2026-5805x-pre7.patch: flatten bounds check if blocks", " (tidy-up).", " - debian/patches/CVE-2026-5805x-pre8.patch: rework bounds checks to avoid", " pointer comparisons.", " - debian/patches/CVE-2026-58050.patch: cap variable-length packet element", " sizes.", " - CVE-2026-58050", " - CVE-2026-58051", "" ], "package": "libssh2", "version": "1.11.1-4ubuntu1", "urgency": "medium", "distributions": "stonking", "launchpad_bugs_fixed": [], "author": "Marc Deslauriers ", "date": "Tue, 07 Jul 2026 14:23:05 -0400" } ], "notes": null, "is_version_downgrade": true }, { "name": "libssl4", "from_version": { "source_package_name": "openssl", "source_package_version": "4.0.1-1ubuntu4", "version": "4.0.1-1ubuntu4" }, "to_version": { "source_package_name": "openssl", "source_package_version": "4.0.3-1ubuntu1", "version": "4.0.3-1ubuntu1" }, "cves": [ { "cve": "CVE-2026-84782", "url": "https://ubuntu.com/security/CVE-2026-84782", "cve_description": "Issue summary: The DTLS retransmission logic does not correctly handle a handshake message write that is suspended part-way through. The retransmitted message can be read past the message buffer and the retransmission overwrites the internal state the suspended write needs to resume correctly. Impact summary: The retransmitted message can disclose a heap memory to the peer as plaintext handshake data or cause a crash and a Denial of Service when the read reaches an unmapped memory region. CWE: CWE-125: Out-of-bounds Read Description: DTLS handshake messages can be written out in multiple fragments, and a write can suspend mid-message (returning WANT_WRITE) if the underlying transport temporarily cannot accept more data. While such a write is suspended, the DTLS retransmission timer may independently fire and ask the retransmission logic to resend an earlier, already-acknowledged-as-sent message from its retransmit queue. The retransmission logic reused the same internal buffer and position tracking as the message that was still being written, without resetting the position back to the start of the message being retransmitted. As a result the retransmission was read starting from wherever the suspended write had left off, producing a mislabelled message whose body was leftover bytes from the other, larger message still in flight - content that was never meant to be sent at that point, and which could run past the end of the allocated buffer. Separately, even when the retransmission is positioned correctly, allowing it to run to completion while another write is suspended overwrites the same shared bookkeeping that the suspended write depends on to resume. When the application later resumes the suspended write (via a subsequent SSL_read(), SSL_write(), SSL_accept(), or SSL_connect() call), it finds that bookkeeping in a state inconsistent with the message and aborts the process in a debugging build. The fix resets the retransmission's read position to the start of the message before resending, and skips retransmission entirely whenever a handshake write is still suspended, deferring to the next call that resumes it instead. FIPS impact: no The affected code is outside the FIPS module boundary.", "cve_priority": "high", "cve_public_date": "2026-09-29 16:17:00 UTC" }, { "cve": "CVE-2026-35189", "url": "https://ubuntu.com/security/CVE-2026-35189", "cve_description": "Issue summary: A certificate with many nameRelativeToCRLIssuer CRL distribution points causes disproportionate heap growth when OpenSSL caches X.509 extensions. Impact summary: Receiving a crafted certificate from a malicious peer can lead to significant memory pressure and possible Denial of Service in clients or in servers that solicit client certificates. CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: A certificate or a set of certificates that fits under the limit for size of certificates accepted from the peer (~100 KiB) can result in allocation of several hundred MiB of resident memory on the receiving side during a normal TLS handshake. This may be enough to crash the client or server, if multiple concurrent connections lead to similarly large memory allocations. The fix postpones processing of the CRL distribution points extensions in certificates to the time when the processed value is required for CRL processing. This avoids keeping large memory allocations for a long time when such certificates are received. FIPS impact: no The affected code is outside the FIPS module boundary.", "cve_priority": "low", "cve_public_date": "2026-09-29 16:17:00 UTC" }, { "cve": "CVE-2026-35191", "url": "https://ubuntu.com/security/CVE-2026-35191", "cve_description": "Issue summary: The OpenSSL QUIC server, when configured to not preform address validation, can be forced to count incoming packets multiple times in its unvalidated credit computation, leading to a violation of the RFC 9000 unvalidated connection amplification limit of 3 times the amount of data received. Impact summary: A remote attacker able to spoof packets to a server using the OpenSSL QUIC implementation might use the server for an amplification of a DDoS attack. CWE: CWE-440: Expected Behavior Violation Description: OpenSSL's QUIC stack, when operating as a server, enforces client address validation (RFC 9000, Section 8), to confirm the peer address is not used for a traffic amplification attack. If this feature is disabled on the server, the QUIC stack limits the amount of server data that can be sent to 3 times the amount of data received from the peer address, until such time as the TLS handshake is completed. The OpenSSL QUIC server, when operating in non-validation mode, adds the length of the whole datagram received to the unvalidated credit limit when processing each QUIC packet in the datagram. A remote peer may, after establishing a connection with an initial client hello frame, send a subsequent datagram containing multiple QUIC packets, leading the server to account the entire datagram length for each packet in the datagram, resulting in the server believing that the peer has sent more data than it actually has, thereby violating the 3x amplification limit mandated by the RFC. FIPS impact: no As the QUIC stack lives outside the FIPS module boundary, no FIPS modules are affected by this CVE.", "cve_priority": "low", "cve_public_date": "2026-09-29 16:17:00 UTC" }, { "cve": "CVE-2026-42772", "url": "https://ubuntu.com/security/CVE-2026-42772", "cve_description": "Issue summary: The QUIC stream reassembly algorithm performance deteriorates progressively as packets are arriving out of order. The worst case has a quadratic complexity proportional to the number of stream frames kept in the buffer for the received stream data. Impact summary: A remote QUIC peer that completes the handshake can create a connection-scoped CPU pressure and potentially a Denial of Service using compliant STREAM frames inside the advertised receive window, with low attacker bandwidth. CWE: CWE-407: Inefficient Algorithmic Complexity Description: OpenSSL manages received QUIC stream fragments using a doubly-linked list. While it optimizes for append operations (at the end of the list), it falls back to a head-to-tail linear search for any fragment that does not immediately follow the current `tail`. By manipulating the sequence of offsets, an attacker can force the server to perform O(n^2) operations, consuming excessive CPU time for the QUIC process. FIPS impact: no The FIPS module is not affected as the QUIC implementation is outside of the OpenSSL FIPS module boundary.", "cve_priority": "low", "cve_public_date": "2026-09-29 16:17:00 UTC" }, { "cve": "CVE-2026-54872", "url": "https://ubuntu.com/security/CVE-2026-54872", "cve_description": "Issue summary: The generic elliptic-curve scalar multiplication used for ECDSA and SM2 signature operations with curves that do not have a dedicated implementation leaks information about the secret nonce through timing. Impact summary: An attacker able to measure signing times may learn information about the per-signature secret nonce, which over many signatures can, via a lattice / Hidden Number Problem attack, lead to recovery of the private key. CWE: CWE-208: Observable Timing Discrepancy Description: The generic elliptic-curve scalar multiplication used for curves that do not have a dedicated constant-time implementation pads the secret scalar with non-constant-time BIGNUM operations, so the time taken depends on the value of the secret scalar derived from the ECDSA and SM2 nonce. The leak is very small; observing it requires a large number of measurements. The effect is largest for curves whose group order lies on a machine-word boundary, such as brainpoolP384r1. Applications using ECDSA signing over the Brainpool and other generic prime curves, and SM2 signing on platforms that use the generic implementation, are vulnerable to this issue. The NIST curves P-256, P-384 and P-521 use dedicated constant-time implementations and are not affected. FIPS Impact: no The FIPS modules are not affected: the approved NIST curves used in the FIPS provider have dedicated constant-time implementations and do not use the affected code path.", "cve_priority": "low", "cve_public_date": "2026-09-29 16:17:00 UTC" }, { "cve": "CVE-2026-54873", "url": "https://ubuntu.com/security/CVE-2026-54873", "cve_description": "Issue summary: QUIC process may keep memory for QUIC packet buffer for much longer period than necessary. Impact summary: Remote peer can exploit this vulnerability by sending maliciously crafted packets, making the local QUIC stack to keep the memory for packet buffers allocated. The time for which the memory remains allocated is entirely under the control of the potentially malicious remote peer. CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: To save copy operation from the packet buffer to the stream reassemble buffer the QUIC stack leaves the stream data on the packet buffer waiting to be copied to a buffer provided by the local receiving application. The QUIC stack releases a reference to the packet buffer only after the data are copied to the application buffer. This design is more efficient for legitimate data transfers but enables an attacker to allocate a lot more memory than actually required by the data kept in the receiving stream buffer. To mitigate the vulnerability, the QUIC stack now calculates and monitors memory overhead for every stream. The memory overhead for a single stream frame is calculated as a difference between the size of the whole packet that carries the stream frame and the size of the stream frame itself. The memory overhead for a single stream frame is added to the total (cumulative) memory overhead QUIC stack keeps for each stream. Once the cumulative memory overhead exceeds 64kB, the QUIC stack moves the stream frame data from the packet buffer to the stream buffer, starting with the next packet received. FIPS impact: no The FIPS module is not affected as the QUIC implementation is outside of the OpenSSL FIPS module boundary.", "cve_priority": "low", "cve_public_date": "2026-09-29 16:17:00 UTC" }, { "cve": "CVE-2026-54875", "url": "https://ubuntu.com/security/CVE-2026-54875", "cve_description": "Issue summary: A non-constant-time optimized implementation of scalar point multiplication is used for SM2 private key operations on ARM64 and RISC-V platforms. Impact summary: An attacker able to measure the time taken by, or to observe the cache-line access pattern of SM2 signing or decryption on an affected platform can learn information about the secret scalar. CWE: CWE-208: Observable Timing Discrepancy Description: On ARM64 and RISC-V processors, the SM2 curve uses an optimized scalar multiplication implementation whose conditional branches and table look ups are chosen according to the bits of the secret scalar. The execution time and the cache-access pattern therefore depend on the long-term private key (during SM2 decryption) or the per-signature nonce (during SM2 signature generation), forming a timing and cache side-channel. FIPS Impact: no SM2 is not a FIPS algorithm and the optimized SM2 implementation is not part of the FIPS module. OpenSSL 4.0, 3.6, 3.5 and 3.4 are vulnerable to this issue on AArch64 and RISC-V. OpenSSL 3.0, 1.1.1 and 1.0.2 are not affected by this issue. OpenSSL 4.0 users should upgrade to OpenSSL 4.0.3. OpenSSL 3.6 users should upgrade to OpenSSL 3.6.5. OpenSSL 3.5 users should upgrade to OpenSSL 3.5.9. OpenSSL 3.4 users should upgrade to OpenSSL 3.4.8. This issue was reported on 2 May 2026 by Abhinav Agarwal. It was independently reported on 6 June 2026 by Feng Xue. The fix was developed by Igor Ustinov. -- cut (non-publishing metadata for internal use) -- Reported by: Abhinav Agarwal, Feng Xue Fixed by: Igor Ustinov", "cve_priority": "low", "cve_public_date": "2026-09-29 16:17:00 UTC" }, { "cve": "CVE-2026-72897", "url": "https://ubuntu.com/security/CVE-2026-72897", "cve_description": "Issue summary: A TLS server that calls SSL_set_SSL_CTX() to switch a connection to a different SSL_CTX part way through a handshake may access memory beyond the end of an internal array if the replacement context knows about more provider signature algorithms than the context the connection was created from. Applications which never call SSL_set_SSL_CTX() are not affected. Impact summary: A remote peer may be able to cause a small out-of-bounds read, and in some circumstances a fixed-value out-of-bounds write, on the server heap. This may lead to a Denial of Service. CWE: CWE-787: Out-of-bounds Write Description: A TLS connection records how many certificate slots it has when it is created, taken from the SSL_CTX that created it: the built-in certificate types plus one slot for each provider TLS-SIGALG entry that context was aware of. That count sizes an internal array of per-slot certificate validity flags. An application may replace a connection's SSL_CTX part way through the handshake by calling SSL_set_SSL_CTX(), most commonly from a servername callback in order to serve a different virtual host. Doing so did not refresh the recorded count. A provider signature algorithm's slot index is its position in the list of whichever context resolves it, so if the replacement context is aware of more of them than the original, an algorithm offered by the peer can resolve to an index beyond the end of the array. Processing the peer's signature algorithms then reads one four byte word past the end for each such algorithm and, where the word read is zero, writes a fixed value over it. A peer offering many of them can corrupt heap metadata and abort the process. Only provider signature algorithms which occupy one of the excess slots, and which the server also has configured, have this effect. Codepoints the replacement context does not recognise are discarded without being resolved to a slot, and provider signature algorithms are usable only from TLS 1.3. The two contexts must therefore be aware of different numbers of provider signature algorithms, which requires separate library contexts, a provider loaded between the two being created, or providers which differ in what they advertise - in 4.0, for example, the default provider advertises SM2 where the FIPS provider does not. A deployment meeting the condition is also unable to negotiate the affected algorithms with legitimate clients, since the same stale count hides the corresponding certificates, so the misconfiguration is likely to be noticed. For that reason, and because the configuration is not the default, this issue has been assessed as Low severity. FIPS impact: no No FIPS modules are affected by this issue as the affected code is outside the OpenSSL FIPS module boundary.", "cve_priority": "low", "cve_public_date": "2026-09-29 16:17:00 UTC" }, { "cve": "CVE-2026-75804", "url": "https://ubuntu.com/security/CVE-2026-75804", "cve_description": "Issue summary: OpenSSL QUIC stack does not enforce connection level flow control for streams. Remote peers may send more bytes as long as they fit within the stream flow control limits. Impact summary: A malicious remote peer may exploit the lack of connection flow control for streams to make the QUIC stack receive ~100MB of memory instead of 768 KiB (default flow control window size). CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: The local QUIC stack advertises two flow control limits to its remote peer: stream flow control limit and connection flow control limit. The remote peer must follow both limits when transmitting stream data. Whenever the local QUIC stack receives a stream frame, it validates that the size of the received stream frame stays within flow control limits. If either limit is exceeded (stream level or connection level), then the QUIC stack must close the connection with a flow control error. The vulnerable OpenSSL QUIC stack enforces the stream-level but not the connection-level limit. To exploit the issue, three conditions must be met: - the remote peer opens several streams - each stream must stay within the stream-level flow control limit - there must be no zero-offset byte sent on any of the streams (to prevent the vulnerable QUIC stack from consuming data). By meeting the conditions above, the remote peer may make the local stack allocate 2 x MAX_STREAMS x (stream flow control limit) bytes of memory. MAX_STREAMS defaults to 100, and the limit applies to both bidirectional and unidirectional streams, making it 200 in total. The default flow control window for a stream is 512kB. The remote peer may force the vulnerable QUIC stack to allocate 100MB of heap per connection. FIPS impact: no The FIPS module is not affected as the QUIC implementation is outside of the OpenSSL FIPS module boundary.", "cve_priority": "low", "cve_public_date": "2026-09-29 16:17:00 UTC" }, { "cve": "CVE-2026-75805", "url": "https://ubuntu.com/security/CVE-2026-75805", "cve_description": "Issue summary: A CMP client that requests certificate revocation on the basis of a PKCS#10 CSR may dereference a NULL pointer and terminate abnormally when processing a crafted revocation response. Impact summary: The NULL pointer dereference happens on a read which leads to a crash and a Denial of Service for the affected client application. CWE: CWE-476: NULL-pointer dereference Description: A CMP client revoking a certificate has to tell the server which certificate to revoke, and may do so by supplying a PKCS#10 CSR instead of the certificate itself or its issuer name and serial number. This is 'openssl cmp -cmd rr -csr ' on the command line, or OSSL_CMP_exec_RR_ses() with the certificate supplied via OSSL_CMP_CTX_set1_p10CSR() through the API. A CSR does not contain the issuer name and serial number of the certificate, so the client does not send them. A server may optionally name the certificate it revoked in its response, and the client then compares that name against what it sent. Having sent neither an issuer name nor a serial number, it has nothing to compare against, and a server returning a specially crafted name causes the client to read from a NULL pointer and crash. The revocation response is checked for valid message protection before the affected code is reached, so an attacker must be a malicious or compromised CMP server, or a man-in-the-middle in possession of the secret used for message protection. Clients that identify the certificate to be revoked by a certificate or by issuer and serial number rather than by a PKCS#10 CSR are not affected. FIPS impact: no No FIPS modules are affected by this issue, as the CMP protocol implementation is outside the OpenSSL FIPS module boundary.", "cve_priority": "low", "cve_public_date": "2026-09-29 16:17:00 UTC" }, { "cve": "CVE-2026-75806", "url": "https://ubuntu.com/security/CVE-2026-75806", "cve_description": "Issue summary: An established DTLS 1.2 association using an AEAD cipher suite can be terminated by a single unauthenticated datagram whose encrypted fragment is shorter than the mandatory explicit IV and authentication tag overhead. Impact summary: An attacker who can send a datagram that is routed to an existing DTLS 1.2 association can tear that association down without knowing any key material. This is a Denial of Service limited to the targeted association. There is no memory safety or confidentiality impact. CWE: CWE-1284: Improper Validation of Specified Quantity in Input Description: In TLS 1.2 and DTLS 1.2 every record protected by an AEAD cipher suite carries an explicit IV followed by the ciphertext and an authentication tag. When decrypting such a record the record layer passed the record length to the cipher implementation before checking that the record was long enough to contain the explicit IV and the tag. For a record shorter than that overhead the cipher implementation rejected the impossible length, and the record layer treated this as an internal failure and raised a fatal internal_error alert instead of treating the record as one that failed authentication. In TLS 1.2 the same record causes a fatal internal_error alert instead of the expected bad_record_mac alert. Since any undecryptable record already terminates a TLS connection, this is a protocol conformance issue rather than a security issue in TLS. The fix validates the record length against the explicit IV and tag length before any AEAD processing, so that TLS reports bad_record_mac and DTLS silently discards the record. FIPS impact: no The affected code is outside the FIPS module boundary.", "cve_priority": "low", "cve_public_date": "2026-09-29 16:17:00 UTC" }, { "cve": "CVE-2026-77696", "url": "https://ubuntu.com/security/CVE-2026-77696", "cve_description": "Issue summary: SM2 signature generation uses non-constant-time arithmetic on secret values, forming a timing side-channel. Impact summary: An attacker able to measure SM2 signing times may learn information about the per-signature secret nonce, which over many signatures can, via a lattice / Hidden Number Problem attack, lead to recovery of the private key. CWE: CWE-208: Observable Timing Discrepancy Description: SM2 signature generation computes the signature value using variable-time BIGNUM operations on the secret nonce and the private key, so the time taken to produce an SM2 signature depends on these secret values, forming a timing side-channel. Applications performing SM2 signature generation are affected on all platforms. FIPS Impact: no SM2 is not a FIPS algorithm.", "cve_priority": "low", "cve_public_date": "2026-09-29 16:17:00 UTC" }, { "cve": "CVE-2026-84783", "url": "https://ubuntu.com/security/CVE-2026-84783", "cve_description": "Issue summary: The first concurrent use of the same X.509 certificate by several threads may cause its cached extension data to be freed while another thread is still using it. Impact summary: A remote, unauthenticated peer could crash a multi-threaded TLS client, or a multi-threaded TLS server that requests client certificates, if the first certificate chains built to the same trusted CA certificate are built by several connections at the same time. This is a use-after-free read, which is likely to crash the process, resulting in a Denial of Service. CWE: CWE-416: Use After Free Description: OpenSSL caches the decoded values of a certificate's X.509v3 extensions inside the X509 object the first time they are needed. In OpenSSL 4.0 this cache is built in two phases: the extension values are computed while holding a read lock on the certificate, and the results are then installed into the certificate under a write lock. Because a read lock does not exclude other readers, several threads can compute the cache for the same certificate at the same time. Each thread that subsequently acquires the write lock installs its own results and frees the values installed by the thread before it, even though that earlier thread has already marked the cache as complete and may have returned pointers into it to its caller. A caller still using those pointers then reads freed memory. Any certificate shared between threads is exposed the first time its extensions are decoded. In TLS the certificates at risk are the trusted CA certificates supplied for chain verification, by whatever means, since these are shared by every connection and their extensions are decoded and cached the first time a chain is built to them. Certificates sent by the peer are decoded separately for each connection and are not shared, so they are not affected. In a TLS client verifying server certificates, or a TLS server that requests and verifies client certificates, the use-after-free could only occur if the first chains built to the same trusted CA are built by several connections at the same time. FIPS impact: no The FIPS module is not affected as X.509 certificate handling is outside of the OpenSSL FIPS module boundary. OpenSSL 4.0 is vulnerable to this issue. OpenSSL 3.6, 3.5, 3.4, 3.0, 1.1.1 and 1.0.2 are not affected by this issue. OpenSSL 4.0 users should upgrade to OpenSSL 4.0.3. This issue was reported on 27 August 2026 by Tim Becker (Xint.io) and independently in a public report on 31 August 2026 by aydinmercan. The fix has been developed by Bob Beck. -- cut (non-publishing metadata for internal use) -- Reported by: Tim Becker (Xint.io), aydinmercan Fixed by: Bob Beck", "cve_priority": "medium", "cve_public_date": "2026-09-29 16:17:00 UTC" }, { "cve": "CVE-2026-84784", "url": "https://ubuntu.com/security/CVE-2026-84784", "cve_description": "Issue summary: A malicious remote peer may flood the local QUIC stack with NEW_CONNECTION_ID frames by avoiding a limit check on how many connection IDs the remote QUIC stack can use. Impact summary: The local QUIC stack sends a RETIRE_CONN_ID frame for every NEW_CONNECTION_ID frame it receives. The RETIRE_CONN_ID frame is dispatched via the Control Frame Queue (CFQ). If the remote peer also withholds ACKs, then it can force the local stack to allocate ~400MB (depending on ACK delay). CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: RFC 9000 sections 5.1.1 and 5.1.2 [1] describe the mechanism by which a remote peer can notify the local QUIC stack to change the destination connection ID (a.k.a. CID) the local stack uses to identify the connection at the remote peer. Each CID is associated with a sequence number. The sequence number is transmitted in NEW_CONNECTION_ID and RETIRE_CONNECTION_ID frames to identify the CID which is being either associated with a connection or retired. The remote peer sends a NEW_CONNECTION_ID frame to let the local stack know a new CID is being associated with an existing connection. The NEW_CONNECTION_ID frame carries the new CID, its sequence number, and the retire-prior-to number. The retire-prior-to identifies existing CIDs that are to be retired. The local QUIC stack must send a RETIRE_CONNECTION_ID for every destination CID whose sequence number is less than retire-prior-to. The CID becomes retired after the local stack receives an ACK for its RETIRE_CONNECTION_ID frame. Although the OpenSSL QUIC stack supports at most one destination CID for every connection, it can be tricked into processing more than one RETIRE_CONNECTION_ID frame per connection. The OpenSSL QUIC stack currently retires the destination CID as soon as it receives the NEW_CONNECTION_ID, while in fact the destination CID must be retired after an ACK for the RETIRE_CONNECTION_ID frame is received. Correcting the flawed logic also fixes the backlog growth. [1] https://datatracker.ietf.org/doc/html/rfc9000#name-issuing-connection-ids FIPS impact: no The FIPS module is not affected as the QUIC implementation is outside of the OpenSSL FIPS module boundary.", "cve_priority": "low", "cve_public_date": "2026-09-29 16:17:00 UTC" }, { "cve": "CVE-2026-18798", "url": "https://ubuntu.com/security/CVE-2026-18798", "cve_description": "Issue summary: QUIC server may double free QRX (QUIC record layer RX) object when channel creation fails for initial packet. Impact summary: Double free leads to heap corruption, which typically results in termination of QUIC server process, leading to Denial of Service. There is so far no evidence that this double free is exploitable for remote code execution, thus it is considered highly improbable. CWE: CWE-415: Double Free Description: In order to validate initial packet, OpenSSL QUIC stack default packet handler (port_default_packet_handler()) creates a so-called QRX object. If the initial packet validates successfully with QRX object, the default packet handler proceeds to channel (connection object) creation. The QRX object used for packet validation is passed to port_bind_channel(), so it becomes part of the newly created connection. If port_bind_channel() fails, then it also frees the QRX object. Once port_bind_channel() returns, the port_default_packet_handler() detects the failure and proceeds to the error branch, where the same QRX object is freed for the second time. The failure in port_bind_channel() function can be induced with a relatively low effort by a malformed (non RFC 9000 compliant) INITIAL packet. If the packet carries DCID (destination connection ID) which is shorter than 8 bytes, then port_bind_channel() jumps to the error path after ossl_quic_lcidm_enrol_odcid() detects that the DCID has invalid length. FIPS impact: no The FIPS module is not affected, as the QUIC implementation is outside of the OpenSSL FIPS module boundary.", "cve_priority": "medium", "cve_public_date": "2026-08-25 13:17:00 UTC" }, { "cve": "CVE-2026-63072", "url": "https://ubuntu.com/security/CVE-2026-63072", "cve_description": "Issue summary: OpenSSL CMS decryption sizes the key-unwrap output buffer based on querying the unwrapped key size, but the AES-WRAP-PAD unwrap primitive can write and cleanse more bytes than that query reports, causing an 8-byte out-of-bounds heap write. Impact summary: An attacker who supplies a crafted CMS message can trigger a deterministic 8-byte out-of-bounds heap write when the victim decrypts it with CMS_decrypt(), corrupting the heap and typically resulting in a Denial of Service. CWE: CWE-787: Out-of-bounds Write Description: The key-wrap OID is potentially attacker-controlled on the wire. CMS unwrapping allows both id-aesNNN-wrap-pad and id-aesNNN-wrap ciphers. An attacker can take a legitimate message and change a single OID byte to select the padded variant while leaving the message otherwise valid. Since the unwrap key is derived from the recipient's private operation (ECDH key agreement or ML-KEM decapsulation), the RFC 5649 integrity check cannot pass, and the decryption fails with integrity failure. The write is a fixed-size (8-byte), fixed-value (zero) heap overflow immediately past the allocation, requires no special configuration, and is reachable from the public CMS_decrypt() function. The consequence is a heap corruption leading to a Denial of Service. The fix in the CMS code sizes the unwrap output buffer for the worst case so a failed unwrap cannot write past the allocation. FIPS impact: no As the CMS code lives outside the FIPS module boundary, no FIPS modules are affected by this CVE.", "cve_priority": "medium", "cve_public_date": "2026-08-25 13:19:00 UTC" }, { "cve": "CVE-2026-63076", "url": "https://ubuntu.com/security/CVE-2026-63076", "cve_description": "Issue summary: OpenSSL CMP password based protection verification only checks whether the protectionAlg parameter was not NULL and not its ASN.1 type, before treating it as a PBMParameter. A crafted message can contain a parameter of a different type, which is then dereferenced as an invalid pointer. Impact summary: A remote, unauthenticated attacker can crash an application acting as a CMP server that accepts PBM-protected messages, or a CMP client talking to a malicious or intercepted CMP server, resulting in a Denial of Service. CWE: CWE-476: NULL Pointer Dereference Description: When verifying the password-based MAC protection of a CMP message, OpenSSL library reads the protectionAlg algorithm parameter with X509_ALGOR_get0(), which returns both the parameter type and its value pointer. The value is then cast to an ASN1_STRING and treated as the expected PBMParameter after only checking that pointer is not NULL. The parameter type returned by X509_ALGOR_get0() was never consulted. This happens during protection verification, before any MAC is computed, so no knowledge of the PBM shared secret is required; the only precondition is that PBM verification is reachable. On the server side this is reached from OSSL_CMP_SRV_process_request() for any application that stands up a CMP server accepting PBM-protected messages, and on the client side from CMP response validation against a malicious or on-path (MITM) server. The reliable consequence is a denial of service; there is no memory disclosure, no controlled memory write, and no path to code execution. CMP is a specialized feature that an application must explicitly enable. FIPS impact: no As the CMP code lives outside the FIPS module boundary, no FIPS modules are affected by this CVE.", "cve_priority": "medium", "cve_public_date": "2026-08-25 13:19:00 UTC" }, { "cve": "CVE-2026-14457", "url": "https://ubuntu.com/security/CVE-2026-14457", "cve_description": "Issue summary: In a server or client configuration with RFC7250 Raw Public Keys (RPKs) enabled, and only the private key (with no associated certificate) configured locally, a NULL pointer dereference may occur when the remote peer solicits raw public keys and also sends the typically omitted \"signature_algorithms_cert\" TLS extension. Impact summary: The impact is limited to a possible Denial of Service as a result of an application abort, no data disclosure or remote command execution are possible. CWE: CWE-476: NULL Pointer Dereference Description: While a passing comment in sample code in the documentation suggests that key-only RPK configurations are supported, the best-practice RPK configuration is to always configure a corresponding certificate (possibly self-signed or signed by any convenient CA). When the private key is configured along with a matching certificate, the \"signature_algorithms_cert\" extension is handled reliably even without the fix, and peer clients or servers that don't support raw public keys may be able to complete a TLS connection by pinning or verifying the corresponding certificate or its public key. Deployments that prefer to configure just a private key with no certificate need to upgrade to an updated release as noted below. FIPS impact: no No FIPS modules are affected by this issue, as the SSL protocol implementation is outside the OpenSSL FIPS module boundary.", "cve_priority": "low", "cve_public_date": "2026-08-25 13:17:00 UTC" }, { "cve": "CVE-2026-54874", "url": "https://ubuntu.com/security/CVE-2026-54874", "cve_description": "Issue summary: Receiving a DTLS record for a future epoch while a handshake is in progress causes OpenSSL to buffer far more memory than the record itself requires. Impact summary: A peer can use a small amount of network traffic to make an OpenSSL DTLS endpoint retain a disproportionately large amount of memory, which may lead to a Denial of Service. CWE: CWE-405: Asymmetric Resource Consumption (Amplification) Description: While a DTLS handshake is in progress, a peer may legitimately have already moved on to the next epoch (for example, having sent its ChangeCipherSpec and Finished messages) before the local endpoint has processed the same transition, typically because of reordering on the underlying UDP transport. OpenSSL buffers such early records so that they can be processed once the local endpoint catches up. Buffering a record currently retains the entire read buffer it arrived in, which is sized to hold the largest possible DTLS record (around 16 kilobytes), rather than just the bytes that make up the record itself. Up to 100 such records may be buffered per connection. As a result, a peer that sends a stream of small forged records claiming to belong to the next epoch can cause an OpenSSL DTLS endpoint to retain around 1.7 megabytes of memory, despite sending only a small fraction of that amount of data over the network. An attacker therefore gains a memory amplification factor of around 1200, and can multiply the effect across as many associations as it is able to open, making this a remote memory exhaustion Denial of Service risk for DTLS servers. Since the memory retained per connection remains bounded, and any limit an application already places on the number of concurrent associations also bounds the total exposure, this issue has been assessed as Low severity. FIPS impact: no No FIPS modules are affected by this issue as the affected code is outside the OpenSSL FIPS module boundary. OpenSSL 4.0, 3.6, 3.5, 3.4, 3.0, 1.1.1 and 1.0.2 are vulnerable to this issue. OpenSSL 4.0 users should upgrade to OpenSSL 4.0.2. OpenSSL 3.6 users should upgrade to OpenSSL 3.6.4. OpenSSL 3.5 users should upgrade to OpenSSL 3.5.8. OpenSSL 3.4 users should upgrade to OpenSSL 3.4.7. OpenSSL 3.0 users should upgrade to OpenSSL 3.0.22. Premium support customers only: OpenSSL 1.1.1 users should upgrade to OpenSSL 1.1.1zi OpenSSL 1.0.2 users should upgrade to OpenSSL 1.0.2zr This issue was reported on 18 May 2026 by Amazon Web Services. The fix has been developed by Matt Caswell. -- cut (non-publishing metadata for internal use) -- Reported by: Amazon Web Services Fixed by: Matt Caswell", "cve_priority": "low", "cve_public_date": "2026-08-25 13:19:00 UTC" }, { "cve": "CVE-2026-63073", "url": "https://ubuntu.com/security/CVE-2026-63073", "cve_description": "Issue summary: OpenSSL CMP response validation passed an unexpected response sender distinguished name directly as the format string to `ERR_raise_data()`. Impact summary: A malicious or intercepted CMP endpoint can crash a CMP client that enforces an expected sender or uses a pinned server certificate whose subject becomes the default expected sender. CWE: CWE-134 (Use of Externally-Controlled Format String) Description: When validating a received CMP message, ossl_cmp_msg_check_update() converts the peer-supplied sender distinguished name with X509_NAME_oneline() and passes it directly as the format argument to ERR_raise_data(). Percent characters survive the conversion, so a sender DN such as \"CN=%s%n\" reaches BIO_vsnprintf() as an attacker-controlled format string with no matching variadic arguments. This path is only reached when the caller configures an expected sender or pins a server certificate, which is the normal configuration for a CMP client validating server responses. Since the attacker controls the format string but none of the variadic arguments, such specifiers as %s and %n dereference or write through unrelated stack contents and crash the client. The reliable consequence is a denial of service, when the response comes from a malicious or intercepted CMP endpoint. There is no controlled memory write, arbitrary-address read, or reliable path to remote code execution. FIPS impact: no No FIPS modules are affected by this issue, as the CMP protocol implementation is outside the OpenSSL FIPS module boundary.", "cve_priority": "low", "cve_public_date": "2026-08-25 13:19:00 UTC" }, { "cve": "CVE-2026-63074", "url": "https://ubuntu.com/security/CVE-2026-63074", "cve_description": "Issue summary: The OpenSSL Certificate Management Protocol (CMP) caches additional certificates (extraCerts) sent in a CMP message, but never expunges them (for instance if they are invalid). If a server reuses an OSSL_CMP_CTX frequently, this cache of extraCerts may grow unboundedly, and a malicious client may flood a CMP server with requests driving this growth. Impact summary: Users utilizing a CMP server that reuses a single OSSL_CMP_CTX for the lifetime of a server process may observe unbounded memory growth in the event a malicious client repeatedly sends requests containing unique extra certificates, which may lead to OOM conditions. CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: If a remote user sends CMP messages to a server with a list of extraCerts and the message is rejected, the extraCerts from the message remains in the server contexts untrusted certificate stack. This exposes servers with long lived ctx objects to Denial of Service attacks in which an attacker sends messages intending to be rejected with a large list of additional certificates repeatedly, forcing the server to store them indefinitely. The issue was fixed by removing the added extra certs if the message is rejected, using the same method as when the context is configured to not do caching at all. FIPS impact: no As the CMP code lives outside the FIPS module boundary, no FIPS modules are affected by this CVE.", "cve_priority": "low", "cve_public_date": "2026-08-25 13:19:00 UTC" }, { "cve": "CVE-2026-63075", "url": "https://ubuntu.com/security/CVE-2026-63075", "cve_description": "Issue summary: When OpenSSL processes QUIC traffic from a peer that repeatedly sends ack-eliciting packets while not acknowledging ACK-only responses, the QUIC stack can retain ACK-only packet metadata for the lifetime of the connection. Impact summary: A remote peer that can complete a QUIC handshake can cause connection-scoped memory growth which may lead to Denial of Service through memory exhaustion, especially with sustained traffic or many concurrent QUIC connections. CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: When the OpenSSL QUIC stack sends an ACK-only packet, there is no requirement by the QUIC protocol that the peer will acknowledge that ACK-only packet (i.e. it is itself not ack-eliciting). However, the OpenSSL implementation stores the metadata about the ACK frames regardless. In and of itself that's ok, but if a malicious peer establishes a connection, and then drives the connection such that ACK-only packets are forced from the OpenSSL implementation peer (i.e., by sending numerous PING frames), and then withholding any subsequent acks for ack-eliciting data, like legitimate data, said malicious peer can force inappropriate memory growth on the OpenSSL peer, potentially leading to a Denial of Service. The fix is to ensure that we account for the transmission of the ACK-only packet in the packet histories high and low watermark without actually storing the ACK-only packet metadata itself. FIPS impact: no The OpenSSL FIPS module is not affected as the QUIC code is outside the FIPS module boundary.", "cve_priority": "low", "cve_public_date": "2026-08-25 13:19:00 UTC" }, { "cve": "CVE-2026-75803", "url": "https://ubuntu.com/security/CVE-2026-75803", "cve_description": "Issue summary: ChaCha20-Poly1305 and AES-OCB decryption with an empty ciphertext can report success without verifying the supplied authentication tag when the operation is finalized by calling the EVP_Cipher() function. Impact summary: Applications calling EVP_Cipher() on an empty ciphertext and expecting the call to check the AEAD tag may accept forged messages. CWE: CWE-354 (Improper Validation of Integrity Check Value) Description: The EVP_Cipher() API call for AEAD ciphers behaves like a one shot encryption and decryption call. It also verifies the AEAD tag after the decryption operation. However for AES-OCB and ChaCha20-Poly1305 ciphers it skipped the AEAD tag verification when an empty ciphertext was passed to the function. The callers of this function might believe that a successful return indicates a valid AEAD tag for these ciphers, even when that has not truly been validated in this case. FIPS impact: no The FIPS modules in 4.0, 3.6, 3.5, 3.4, and 3.0 are not affected by this CVE as the affected algorithms are not FIPS approved and thus not implemented in the FIPS module.", "cve_priority": "low", "cve_public_date": "2026-08-25 13:19:00 UTC" }, { "cve": "CVE-2026-14456", "url": "https://ubuntu.com/security/CVE-2026-14456", "cve_description": "Issue summary: When an OpenSSL QUIC server (Listener SSL object) processes valid QUIC Initial packets for unknown destination connection IDs, it can allocate and queue new incoming channels without enforcing any limit. Impact summary: A remote peer that can make many Initial packets reach the server listener faster than the application accepts connections, can cause the memory allocated to store the per-channel state to grow without any limits, potentially making the QUIC listener unavailable and causing Denial of Service. CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: The function that handles inbound QUIC packets uses Connection-Id from the packet header to find an existing connection (QUIC channel). If no existing connection is found and the packet type is INITIAL, the function treats the packet as a new connection. It allocates a new channel object and inserts it into a queue where it waits to be accepted by the local application with SSL_accept(3ossl). The memory occupied by these initial channel objects may grow without bounds if the application is not able to call SSL_accept() frequently enough to serve these inbound connection requests. The issue is present since OpenSSL 3.5 when the QUIC server implementation was added. The fix introduces a limit for pending connections. The default limit is set to 256 pending connections (waiting to be accepted by the local application). Applications may change the default by calling SSL_set_value_uint(3ossl). FIPS impact: no The FIPS module is not affected as the QUIC implementation is outside of the OpenSSL FIPS module boundary.", "cve_priority": "medium", "cve_public_date": "2026-08-13 15:19:00 UTC" }, { "cve": "CVE-2026-54876", "url": "https://ubuntu.com/security/CVE-2026-54876", "cve_description": "Issue summary: A malicious TLS server can cause a memory leak in a TLS client that has enabled OCSP response checking by sending an OCSP response that contains no single response entries. Impact summary: An attacker can leak an attacker-tunable amount of memory per TLS handshake in a victim client application. A long-running client that repeatedly connects to a malicious server can have its memory exhausted, resulting in a Denial of Service. CWE: CWE-401: Missing Release of Memory after Effective Lifetime Description: The affected function is called during X.509 certificate chain verification when OCSP response checking is enabled with the X509_V_FLAG_OCSP_RESP_CHECK or X509_V_FLAG_OCSP_RESP_CHECK_ALL verification flags, for example when a TLS client verifies an OCSP response stapled into the TLS handshake by the server. When the received BasicOCSPResponse contains an empty SEQUENCE OF SingleResponse, which is permitted on the wire and accepted by the OpenSSL decoder, the OCSP_BASICRESP structure allocated by OCSP_response_get1_basic() was not freed because an early return bypassed the cleanup code at the end of the function. The amount of memory leaked per handshake can be amplified by the attacker by padding the certs field of the BasicOCSPResponse with bogus certificates, which are parsed and stored in the leaked structure before the empty response check triggers the early return. A long-running TLS client that repeatedly connects to a malicious server can have its memory exhausted over time. OCSP response checking is not enabled by default. Only client applications that explicitly enable the OCSP response check verification flags are affected. FIPS impact: no The FIPS modules in 4.0 and 3.6 are not affected by this issue as the affected code is outside the OpenSSL FIPS module boundary.", "cve_priority": "medium", "cve_public_date": "2026-08-05 15:16:00 UTC" } ], "launchpad_bugs_fixed": [ 2167826 ], "changes": [ { "cves": [], "log": [ "", " * Merge with Debian experimental (LP: #2167826). Remaining changes:", " - Use perl:native in the autopkgtest for installability on i386.", " - Symlink copyright/changelog.Debian.gz in libssl3* to libssl-dev/openssl", " - Disable LTO with which the codebase is generally incompatible", " (LP #2058017)", " - Default config reads crypto-config and /etc/ssl/openssl.cnf.d dropins", " - Don't enable or package anything FIPS (LP #2087955)", " - Match last filename for output in ecp_nistp521-ppc64.pl (LP #2137464)", " - Enable CPU jitter fluctuations", " - fips patches (debian/patches/fips):", " - crypto: Add kernel FIPS mode detection", " - crypto: Automatically use the FIPS provider...", " - apps/speed: Omit unavailable algorithms in FIPS mode", " - apps: pass -propquery arg to the libctx DRBG fetches", " - test: Ensure encoding runs with the correct context...", " - Add Ubuntu-specific defines to help FIPS certification (LP #2073991)", " + UBUNTU_OSSL_SELF_TEST_DESC_PCT_DH", " + UBUNTU_OSSL_PROV_FIPS_PARAM_UNAPPROVED_USAGE", " - Detect FIPS jitterentropy mode and load jitterentropy enabled FIPS", " provider", " - Fallback to default provider when FIPS provider is missing.", "" ], "package": "openssl", "version": "4.0.3-1ubuntu1", "urgency": "medium", "distributions": "stonking", "launchpad_bugs_fixed": [ 2167826 ], "author": "Ravi Kant Sharma ", "date": "Fri, 02 Oct 2026 12:25:40 +0200" }, { "cves": [ { "cve": "CVE-2026-84782", "url": "https://ubuntu.com/security/CVE-2026-84782", "cve_description": "Issue summary: The DTLS retransmission logic does not correctly handle a handshake message write that is suspended part-way through. The retransmitted message can be read past the message buffer and the retransmission overwrites the internal state the suspended write needs to resume correctly. Impact summary: The retransmitted message can disclose a heap memory to the peer as plaintext handshake data or cause a crash and a Denial of Service when the read reaches an unmapped memory region. CWE: CWE-125: Out-of-bounds Read Description: DTLS handshake messages can be written out in multiple fragments, and a write can suspend mid-message (returning WANT_WRITE) if the underlying transport temporarily cannot accept more data. While such a write is suspended, the DTLS retransmission timer may independently fire and ask the retransmission logic to resend an earlier, already-acknowledged-as-sent message from its retransmit queue. The retransmission logic reused the same internal buffer and position tracking as the message that was still being written, without resetting the position back to the start of the message being retransmitted. As a result the retransmission was read starting from wherever the suspended write had left off, producing a mislabelled message whose body was leftover bytes from the other, larger message still in flight - content that was never meant to be sent at that point, and which could run past the end of the allocated buffer. Separately, even when the retransmission is positioned correctly, allowing it to run to completion while another write is suspended overwrites the same shared bookkeeping that the suspended write depends on to resume. When the application later resumes the suspended write (via a subsequent SSL_read(), SSL_write(), SSL_accept(), or SSL_connect() call), it finds that bookkeeping in a state inconsistent with the message and aborts the process in a debugging build. The fix resets the retransmission's read position to the start of the message before resending, and skips retransmission entirely whenever a handshake write is still suspended, deferring to the next call that resumes it instead. FIPS impact: no The affected code is outside the FIPS module boundary.", "cve_priority": "high", "cve_public_date": "2026-09-29 16:17:00 UTC" }, { "cve": "CVE-2026-35189", "url": "https://ubuntu.com/security/CVE-2026-35189", "cve_description": "Issue summary: A certificate with many nameRelativeToCRLIssuer CRL distribution points causes disproportionate heap growth when OpenSSL caches X.509 extensions. Impact summary: Receiving a crafted certificate from a malicious peer can lead to significant memory pressure and possible Denial of Service in clients or in servers that solicit client certificates. CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: A certificate or a set of certificates that fits under the limit for size of certificates accepted from the peer (~100 KiB) can result in allocation of several hundred MiB of resident memory on the receiving side during a normal TLS handshake. This may be enough to crash the client or server, if multiple concurrent connections lead to similarly large memory allocations. The fix postpones processing of the CRL distribution points extensions in certificates to the time when the processed value is required for CRL processing. This avoids keeping large memory allocations for a long time when such certificates are received. FIPS impact: no The affected code is outside the FIPS module boundary.", "cve_priority": "low", "cve_public_date": "2026-09-29 16:17:00 UTC" }, { "cve": "CVE-2026-35191", "url": "https://ubuntu.com/security/CVE-2026-35191", "cve_description": "Issue summary: The OpenSSL QUIC server, when configured to not preform address validation, can be forced to count incoming packets multiple times in its unvalidated credit computation, leading to a violation of the RFC 9000 unvalidated connection amplification limit of 3 times the amount of data received. Impact summary: A remote attacker able to spoof packets to a server using the OpenSSL QUIC implementation might use the server for an amplification of a DDoS attack. CWE: CWE-440: Expected Behavior Violation Description: OpenSSL's QUIC stack, when operating as a server, enforces client address validation (RFC 9000, Section 8), to confirm the peer address is not used for a traffic amplification attack. If this feature is disabled on the server, the QUIC stack limits the amount of server data that can be sent to 3 times the amount of data received from the peer address, until such time as the TLS handshake is completed. The OpenSSL QUIC server, when operating in non-validation mode, adds the length of the whole datagram received to the unvalidated credit limit when processing each QUIC packet in the datagram. A remote peer may, after establishing a connection with an initial client hello frame, send a subsequent datagram containing multiple QUIC packets, leading the server to account the entire datagram length for each packet in the datagram, resulting in the server believing that the peer has sent more data than it actually has, thereby violating the 3x amplification limit mandated by the RFC. FIPS impact: no As the QUIC stack lives outside the FIPS module boundary, no FIPS modules are affected by this CVE.", "cve_priority": "low", "cve_public_date": "2026-09-29 16:17:00 UTC" }, { "cve": "CVE-2026-42772", "url": "https://ubuntu.com/security/CVE-2026-42772", "cve_description": "Issue summary: The QUIC stream reassembly algorithm performance deteriorates progressively as packets are arriving out of order. The worst case has a quadratic complexity proportional to the number of stream frames kept in the buffer for the received stream data. Impact summary: A remote QUIC peer that completes the handshake can create a connection-scoped CPU pressure and potentially a Denial of Service using compliant STREAM frames inside the advertised receive window, with low attacker bandwidth. CWE: CWE-407: Inefficient Algorithmic Complexity Description: OpenSSL manages received QUIC stream fragments using a doubly-linked list. While it optimizes for append operations (at the end of the list), it falls back to a head-to-tail linear search for any fragment that does not immediately follow the current `tail`. By manipulating the sequence of offsets, an attacker can force the server to perform O(n^2) operations, consuming excessive CPU time for the QUIC process. FIPS impact: no The FIPS module is not affected as the QUIC implementation is outside of the OpenSSL FIPS module boundary.", "cve_priority": "low", "cve_public_date": "2026-09-29 16:17:00 UTC" }, { "cve": "CVE-2026-54872", "url": "https://ubuntu.com/security/CVE-2026-54872", "cve_description": "Issue summary: The generic elliptic-curve scalar multiplication used for ECDSA and SM2 signature operations with curves that do not have a dedicated implementation leaks information about the secret nonce through timing. Impact summary: An attacker able to measure signing times may learn information about the per-signature secret nonce, which over many signatures can, via a lattice / Hidden Number Problem attack, lead to recovery of the private key. CWE: CWE-208: Observable Timing Discrepancy Description: The generic elliptic-curve scalar multiplication used for curves that do not have a dedicated constant-time implementation pads the secret scalar with non-constant-time BIGNUM operations, so the time taken depends on the value of the secret scalar derived from the ECDSA and SM2 nonce. The leak is very small; observing it requires a large number of measurements. The effect is largest for curves whose group order lies on a machine-word boundary, such as brainpoolP384r1. Applications using ECDSA signing over the Brainpool and other generic prime curves, and SM2 signing on platforms that use the generic implementation, are vulnerable to this issue. The NIST curves P-256, P-384 and P-521 use dedicated constant-time implementations and are not affected. FIPS Impact: no The FIPS modules are not affected: the approved NIST curves used in the FIPS provider have dedicated constant-time implementations and do not use the affected code path.", "cve_priority": "low", "cve_public_date": "2026-09-29 16:17:00 UTC" }, { "cve": "CVE-2026-54873", "url": "https://ubuntu.com/security/CVE-2026-54873", "cve_description": "Issue summary: QUIC process may keep memory for QUIC packet buffer for much longer period than necessary. Impact summary: Remote peer can exploit this vulnerability by sending maliciously crafted packets, making the local QUIC stack to keep the memory for packet buffers allocated. The time for which the memory remains allocated is entirely under the control of the potentially malicious remote peer. CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: To save copy operation from the packet buffer to the stream reassemble buffer the QUIC stack leaves the stream data on the packet buffer waiting to be copied to a buffer provided by the local receiving application. The QUIC stack releases a reference to the packet buffer only after the data are copied to the application buffer. This design is more efficient for legitimate data transfers but enables an attacker to allocate a lot more memory than actually required by the data kept in the receiving stream buffer. To mitigate the vulnerability, the QUIC stack now calculates and monitors memory overhead for every stream. The memory overhead for a single stream frame is calculated as a difference between the size of the whole packet that carries the stream frame and the size of the stream frame itself. The memory overhead for a single stream frame is added to the total (cumulative) memory overhead QUIC stack keeps for each stream. Once the cumulative memory overhead exceeds 64kB, the QUIC stack moves the stream frame data from the packet buffer to the stream buffer, starting with the next packet received. FIPS impact: no The FIPS module is not affected as the QUIC implementation is outside of the OpenSSL FIPS module boundary.", "cve_priority": "low", "cve_public_date": "2026-09-29 16:17:00 UTC" }, { "cve": "CVE-2026-54875", "url": "https://ubuntu.com/security/CVE-2026-54875", "cve_description": "Issue summary: A non-constant-time optimized implementation of scalar point multiplication is used for SM2 private key operations on ARM64 and RISC-V platforms. Impact summary: An attacker able to measure the time taken by, or to observe the cache-line access pattern of SM2 signing or decryption on an affected platform can learn information about the secret scalar. CWE: CWE-208: Observable Timing Discrepancy Description: On ARM64 and RISC-V processors, the SM2 curve uses an optimized scalar multiplication implementation whose conditional branches and table look ups are chosen according to the bits of the secret scalar. The execution time and the cache-access pattern therefore depend on the long-term private key (during SM2 decryption) or the per-signature nonce (during SM2 signature generation), forming a timing and cache side-channel. FIPS Impact: no SM2 is not a FIPS algorithm and the optimized SM2 implementation is not part of the FIPS module. OpenSSL 4.0, 3.6, 3.5 and 3.4 are vulnerable to this issue on AArch64 and RISC-V. OpenSSL 3.0, 1.1.1 and 1.0.2 are not affected by this issue. OpenSSL 4.0 users should upgrade to OpenSSL 4.0.3. OpenSSL 3.6 users should upgrade to OpenSSL 3.6.5. OpenSSL 3.5 users should upgrade to OpenSSL 3.5.9. OpenSSL 3.4 users should upgrade to OpenSSL 3.4.8. This issue was reported on 2 May 2026 by Abhinav Agarwal. It was independently reported on 6 June 2026 by Feng Xue. The fix was developed by Igor Ustinov. -- cut (non-publishing metadata for internal use) -- Reported by: Abhinav Agarwal, Feng Xue Fixed by: Igor Ustinov", "cve_priority": "low", "cve_public_date": "2026-09-29 16:17:00 UTC" }, { "cve": "CVE-2026-72897", "url": "https://ubuntu.com/security/CVE-2026-72897", "cve_description": "Issue summary: A TLS server that calls SSL_set_SSL_CTX() to switch a connection to a different SSL_CTX part way through a handshake may access memory beyond the end of an internal array if the replacement context knows about more provider signature algorithms than the context the connection was created from. Applications which never call SSL_set_SSL_CTX() are not affected. Impact summary: A remote peer may be able to cause a small out-of-bounds read, and in some circumstances a fixed-value out-of-bounds write, on the server heap. This may lead to a Denial of Service. CWE: CWE-787: Out-of-bounds Write Description: A TLS connection records how many certificate slots it has when it is created, taken from the SSL_CTX that created it: the built-in certificate types plus one slot for each provider TLS-SIGALG entry that context was aware of. That count sizes an internal array of per-slot certificate validity flags. An application may replace a connection's SSL_CTX part way through the handshake by calling SSL_set_SSL_CTX(), most commonly from a servername callback in order to serve a different virtual host. Doing so did not refresh the recorded count. A provider signature algorithm's slot index is its position in the list of whichever context resolves it, so if the replacement context is aware of more of them than the original, an algorithm offered by the peer can resolve to an index beyond the end of the array. Processing the peer's signature algorithms then reads one four byte word past the end for each such algorithm and, where the word read is zero, writes a fixed value over it. A peer offering many of them can corrupt heap metadata and abort the process. Only provider signature algorithms which occupy one of the excess slots, and which the server also has configured, have this effect. Codepoints the replacement context does not recognise are discarded without being resolved to a slot, and provider signature algorithms are usable only from TLS 1.3. The two contexts must therefore be aware of different numbers of provider signature algorithms, which requires separate library contexts, a provider loaded between the two being created, or providers which differ in what they advertise - in 4.0, for example, the default provider advertises SM2 where the FIPS provider does not. A deployment meeting the condition is also unable to negotiate the affected algorithms with legitimate clients, since the same stale count hides the corresponding certificates, so the misconfiguration is likely to be noticed. For that reason, and because the configuration is not the default, this issue has been assessed as Low severity. FIPS impact: no No FIPS modules are affected by this issue as the affected code is outside the OpenSSL FIPS module boundary.", "cve_priority": "low", "cve_public_date": "2026-09-29 16:17:00 UTC" }, { "cve": "CVE-2026-75804", "url": "https://ubuntu.com/security/CVE-2026-75804", "cve_description": "Issue summary: OpenSSL QUIC stack does not enforce connection level flow control for streams. Remote peers may send more bytes as long as they fit within the stream flow control limits. Impact summary: A malicious remote peer may exploit the lack of connection flow control for streams to make the QUIC stack receive ~100MB of memory instead of 768 KiB (default flow control window size). CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: The local QUIC stack advertises two flow control limits to its remote peer: stream flow control limit and connection flow control limit. The remote peer must follow both limits when transmitting stream data. Whenever the local QUIC stack receives a stream frame, it validates that the size of the received stream frame stays within flow control limits. If either limit is exceeded (stream level or connection level), then the QUIC stack must close the connection with a flow control error. The vulnerable OpenSSL QUIC stack enforces the stream-level but not the connection-level limit. To exploit the issue, three conditions must be met: - the remote peer opens several streams - each stream must stay within the stream-level flow control limit - there must be no zero-offset byte sent on any of the streams (to prevent the vulnerable QUIC stack from consuming data). By meeting the conditions above, the remote peer may make the local stack allocate 2 x MAX_STREAMS x (stream flow control limit) bytes of memory. MAX_STREAMS defaults to 100, and the limit applies to both bidirectional and unidirectional streams, making it 200 in total. The default flow control window for a stream is 512kB. The remote peer may force the vulnerable QUIC stack to allocate 100MB of heap per connection. FIPS impact: no The FIPS module is not affected as the QUIC implementation is outside of the OpenSSL FIPS module boundary.", "cve_priority": "low", "cve_public_date": "2026-09-29 16:17:00 UTC" }, { "cve": "CVE-2026-75805", "url": "https://ubuntu.com/security/CVE-2026-75805", "cve_description": "Issue summary: A CMP client that requests certificate revocation on the basis of a PKCS#10 CSR may dereference a NULL pointer and terminate abnormally when processing a crafted revocation response. Impact summary: The NULL pointer dereference happens on a read which leads to a crash and a Denial of Service for the affected client application. CWE: CWE-476: NULL-pointer dereference Description: A CMP client revoking a certificate has to tell the server which certificate to revoke, and may do so by supplying a PKCS#10 CSR instead of the certificate itself or its issuer name and serial number. This is 'openssl cmp -cmd rr -csr ' on the command line, or OSSL_CMP_exec_RR_ses() with the certificate supplied via OSSL_CMP_CTX_set1_p10CSR() through the API. A CSR does not contain the issuer name and serial number of the certificate, so the client does not send them. A server may optionally name the certificate it revoked in its response, and the client then compares that name against what it sent. Having sent neither an issuer name nor a serial number, it has nothing to compare against, and a server returning a specially crafted name causes the client to read from a NULL pointer and crash. The revocation response is checked for valid message protection before the affected code is reached, so an attacker must be a malicious or compromised CMP server, or a man-in-the-middle in possession of the secret used for message protection. Clients that identify the certificate to be revoked by a certificate or by issuer and serial number rather than by a PKCS#10 CSR are not affected. FIPS impact: no No FIPS modules are affected by this issue, as the CMP protocol implementation is outside the OpenSSL FIPS module boundary.", "cve_priority": "low", "cve_public_date": "2026-09-29 16:17:00 UTC" }, { "cve": "CVE-2026-75806", "url": "https://ubuntu.com/security/CVE-2026-75806", "cve_description": "Issue summary: An established DTLS 1.2 association using an AEAD cipher suite can be terminated by a single unauthenticated datagram whose encrypted fragment is shorter than the mandatory explicit IV and authentication tag overhead. Impact summary: An attacker who can send a datagram that is routed to an existing DTLS 1.2 association can tear that association down without knowing any key material. This is a Denial of Service limited to the targeted association. There is no memory safety or confidentiality impact. CWE: CWE-1284: Improper Validation of Specified Quantity in Input Description: In TLS 1.2 and DTLS 1.2 every record protected by an AEAD cipher suite carries an explicit IV followed by the ciphertext and an authentication tag. When decrypting such a record the record layer passed the record length to the cipher implementation before checking that the record was long enough to contain the explicit IV and the tag. For a record shorter than that overhead the cipher implementation rejected the impossible length, and the record layer treated this as an internal failure and raised a fatal internal_error alert instead of treating the record as one that failed authentication. In TLS 1.2 the same record causes a fatal internal_error alert instead of the expected bad_record_mac alert. Since any undecryptable record already terminates a TLS connection, this is a protocol conformance issue rather than a security issue in TLS. The fix validates the record length against the explicit IV and tag length before any AEAD processing, so that TLS reports bad_record_mac and DTLS silently discards the record. FIPS impact: no The affected code is outside the FIPS module boundary.", "cve_priority": "low", "cve_public_date": "2026-09-29 16:17:00 UTC" }, { "cve": "CVE-2026-77696", "url": "https://ubuntu.com/security/CVE-2026-77696", "cve_description": "Issue summary: SM2 signature generation uses non-constant-time arithmetic on secret values, forming a timing side-channel. Impact summary: An attacker able to measure SM2 signing times may learn information about the per-signature secret nonce, which over many signatures can, via a lattice / Hidden Number Problem attack, lead to recovery of the private key. CWE: CWE-208: Observable Timing Discrepancy Description: SM2 signature generation computes the signature value using variable-time BIGNUM operations on the secret nonce and the private key, so the time taken to produce an SM2 signature depends on these secret values, forming a timing side-channel. Applications performing SM2 signature generation are affected on all platforms. FIPS Impact: no SM2 is not a FIPS algorithm.", "cve_priority": "low", "cve_public_date": "2026-09-29 16:17:00 UTC" }, { "cve": "CVE-2026-84783", "url": "https://ubuntu.com/security/CVE-2026-84783", "cve_description": "Issue summary: The first concurrent use of the same X.509 certificate by several threads may cause its cached extension data to be freed while another thread is still using it. Impact summary: A remote, unauthenticated peer could crash a multi-threaded TLS client, or a multi-threaded TLS server that requests client certificates, if the first certificate chains built to the same trusted CA certificate are built by several connections at the same time. This is a use-after-free read, which is likely to crash the process, resulting in a Denial of Service. CWE: CWE-416: Use After Free Description: OpenSSL caches the decoded values of a certificate's X.509v3 extensions inside the X509 object the first time they are needed. In OpenSSL 4.0 this cache is built in two phases: the extension values are computed while holding a read lock on the certificate, and the results are then installed into the certificate under a write lock. Because a read lock does not exclude other readers, several threads can compute the cache for the same certificate at the same time. Each thread that subsequently acquires the write lock installs its own results and frees the values installed by the thread before it, even though that earlier thread has already marked the cache as complete and may have returned pointers into it to its caller. A caller still using those pointers then reads freed memory. Any certificate shared between threads is exposed the first time its extensions are decoded. In TLS the certificates at risk are the trusted CA certificates supplied for chain verification, by whatever means, since these are shared by every connection and their extensions are decoded and cached the first time a chain is built to them. Certificates sent by the peer are decoded separately for each connection and are not shared, so they are not affected. In a TLS client verifying server certificates, or a TLS server that requests and verifies client certificates, the use-after-free could only occur if the first chains built to the same trusted CA are built by several connections at the same time. FIPS impact: no The FIPS module is not affected as X.509 certificate handling is outside of the OpenSSL FIPS module boundary. OpenSSL 4.0 is vulnerable to this issue. OpenSSL 3.6, 3.5, 3.4, 3.0, 1.1.1 and 1.0.2 are not affected by this issue. OpenSSL 4.0 users should upgrade to OpenSSL 4.0.3. This issue was reported on 27 August 2026 by Tim Becker (Xint.io) and independently in a public report on 31 August 2026 by aydinmercan. The fix has been developed by Bob Beck. -- cut (non-publishing metadata for internal use) -- Reported by: Tim Becker (Xint.io), aydinmercan Fixed by: Bob Beck", "cve_priority": "medium", "cve_public_date": "2026-09-29 16:17:00 UTC" }, { "cve": "CVE-2026-84784", "url": "https://ubuntu.com/security/CVE-2026-84784", "cve_description": "Issue summary: A malicious remote peer may flood the local QUIC stack with NEW_CONNECTION_ID frames by avoiding a limit check on how many connection IDs the remote QUIC stack can use. Impact summary: The local QUIC stack sends a RETIRE_CONN_ID frame for every NEW_CONNECTION_ID frame it receives. The RETIRE_CONN_ID frame is dispatched via the Control Frame Queue (CFQ). If the remote peer also withholds ACKs, then it can force the local stack to allocate ~400MB (depending on ACK delay). CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: RFC 9000 sections 5.1.1 and 5.1.2 [1] describe the mechanism by which a remote peer can notify the local QUIC stack to change the destination connection ID (a.k.a. CID) the local stack uses to identify the connection at the remote peer. Each CID is associated with a sequence number. The sequence number is transmitted in NEW_CONNECTION_ID and RETIRE_CONNECTION_ID frames to identify the CID which is being either associated with a connection or retired. The remote peer sends a NEW_CONNECTION_ID frame to let the local stack know a new CID is being associated with an existing connection. The NEW_CONNECTION_ID frame carries the new CID, its sequence number, and the retire-prior-to number. The retire-prior-to identifies existing CIDs that are to be retired. The local QUIC stack must send a RETIRE_CONNECTION_ID for every destination CID whose sequence number is less than retire-prior-to. The CID becomes retired after the local stack receives an ACK for its RETIRE_CONNECTION_ID frame. Although the OpenSSL QUIC stack supports at most one destination CID for every connection, it can be tricked into processing more than one RETIRE_CONNECTION_ID frame per connection. The OpenSSL QUIC stack currently retires the destination CID as soon as it receives the NEW_CONNECTION_ID, while in fact the destination CID must be retired after an ACK for the RETIRE_CONNECTION_ID frame is received. Correcting the flawed logic also fixes the backlog growth. [1] https://datatracker.ietf.org/doc/html/rfc9000#name-issuing-connection-ids FIPS impact: no The FIPS module is not affected as the QUIC implementation is outside of the OpenSSL FIPS module boundary.", "cve_priority": "low", "cve_public_date": "2026-09-29 16:17:00 UTC" } ], "log": [ "", " * Import 4.0.3", " - CVE-2026-84782 (\"DTLS Retransmits Handshake Messages From a Stale Buffer", " Offset\")", " - CVE-2026-35189 (\"Memory Allocation in Relative CRLDP Processing\")", " - CVE-2026-35191 (\"QUIC Unvalidated Amplification Credit may be Over", " Accounted\")", " - CVE-2026-42772 (\"Potential CPU DoS via O(n^2) Fragment Reassembly in QUIC\")", " - CVE-2026-54872 (\"Timing Side-Channel in Scalar Multiplication for Non-NIST", " EC Curves\")", " - CVE-2026-54873 (\"QUIC STREAM Fragment Metadata DoS\")", " - CVE-2026-54875 (\"Non-Constant-Time SM2 Scalar Multiplication on ARM64 and", " RISC-V\")", " - CVE-2026-72897 (\"Out-of-Bounds Access After SSL_set_SSL_CTX() During a", " Handshake\")", " - CVE-2026-75804 (\"QUIC Connection-Level Flow Control is Not Enforced for", " Streams\")", " - CVE-2026-75805 (\"NULL Pointer Dereference in CMP Client Revocation", " Response Handling\")", " - CVE-2026-75806 (\"Unauthenticated and Undersized DTLS 1.2 AEAD Record", " Causes DoS\")", " - CVE-2026-77696 (\"Timing Side-Channel in SM2 Signature Generation\")", " - CVE-2026-84783 (\"Use-After-Free in X.509 Extension Cache Under Concurrent Use\")", " - CVE-2026-84784 (\"QUIC: Unbounded RETIRE_CONNECTION_ID Backlog\")", "" ], "package": "openssl", "version": "4.0.3-1", "urgency": "medium", "distributions": "experimental", "launchpad_bugs_fixed": [], "author": "Sebastian Andrzej Siewior ", "date": "Tue, 29 Sep 2026 21:40:01 +0200" }, { "cves": [ { "cve": "CVE-2026-18798", "url": "https://ubuntu.com/security/CVE-2026-18798", "cve_description": "Issue summary: QUIC server may double free QRX (QUIC record layer RX) object when channel creation fails for initial packet. Impact summary: Double free leads to heap corruption, which typically results in termination of QUIC server process, leading to Denial of Service. There is so far no evidence that this double free is exploitable for remote code execution, thus it is considered highly improbable. CWE: CWE-415: Double Free Description: In order to validate initial packet, OpenSSL QUIC stack default packet handler (port_default_packet_handler()) creates a so-called QRX object. If the initial packet validates successfully with QRX object, the default packet handler proceeds to channel (connection object) creation. The QRX object used for packet validation is passed to port_bind_channel(), so it becomes part of the newly created connection. If port_bind_channel() fails, then it also frees the QRX object. Once port_bind_channel() returns, the port_default_packet_handler() detects the failure and proceeds to the error branch, where the same QRX object is freed for the second time. The failure in port_bind_channel() function can be induced with a relatively low effort by a malformed (non RFC 9000 compliant) INITIAL packet. If the packet carries DCID (destination connection ID) which is shorter than 8 bytes, then port_bind_channel() jumps to the error path after ossl_quic_lcidm_enrol_odcid() detects that the DCID has invalid length. FIPS impact: no The FIPS module is not affected, as the QUIC implementation is outside of the OpenSSL FIPS module boundary.", "cve_priority": "medium", "cve_public_date": "2026-08-25 13:17:00 UTC" }, { "cve": "CVE-2026-63072", "url": "https://ubuntu.com/security/CVE-2026-63072", "cve_description": "Issue summary: OpenSSL CMS decryption sizes the key-unwrap output buffer based on querying the unwrapped key size, but the AES-WRAP-PAD unwrap primitive can write and cleanse more bytes than that query reports, causing an 8-byte out-of-bounds heap write. Impact summary: An attacker who supplies a crafted CMS message can trigger a deterministic 8-byte out-of-bounds heap write when the victim decrypts it with CMS_decrypt(), corrupting the heap and typically resulting in a Denial of Service. CWE: CWE-787: Out-of-bounds Write Description: The key-wrap OID is potentially attacker-controlled on the wire. CMS unwrapping allows both id-aesNNN-wrap-pad and id-aesNNN-wrap ciphers. An attacker can take a legitimate message and change a single OID byte to select the padded variant while leaving the message otherwise valid. Since the unwrap key is derived from the recipient's private operation (ECDH key agreement or ML-KEM decapsulation), the RFC 5649 integrity check cannot pass, and the decryption fails with integrity failure. The write is a fixed-size (8-byte), fixed-value (zero) heap overflow immediately past the allocation, requires no special configuration, and is reachable from the public CMS_decrypt() function. The consequence is a heap corruption leading to a Denial of Service. The fix in the CMS code sizes the unwrap output buffer for the worst case so a failed unwrap cannot write past the allocation. FIPS impact: no As the CMS code lives outside the FIPS module boundary, no FIPS modules are affected by this CVE.", "cve_priority": "medium", "cve_public_date": "2026-08-25 13:19:00 UTC" }, { "cve": "CVE-2026-63076", "url": "https://ubuntu.com/security/CVE-2026-63076", "cve_description": "Issue summary: OpenSSL CMP password based protection verification only checks whether the protectionAlg parameter was not NULL and not its ASN.1 type, before treating it as a PBMParameter. A crafted message can contain a parameter of a different type, which is then dereferenced as an invalid pointer. Impact summary: A remote, unauthenticated attacker can crash an application acting as a CMP server that accepts PBM-protected messages, or a CMP client talking to a malicious or intercepted CMP server, resulting in a Denial of Service. CWE: CWE-476: NULL Pointer Dereference Description: When verifying the password-based MAC protection of a CMP message, OpenSSL library reads the protectionAlg algorithm parameter with X509_ALGOR_get0(), which returns both the parameter type and its value pointer. The value is then cast to an ASN1_STRING and treated as the expected PBMParameter after only checking that pointer is not NULL. The parameter type returned by X509_ALGOR_get0() was never consulted. This happens during protection verification, before any MAC is computed, so no knowledge of the PBM shared secret is required; the only precondition is that PBM verification is reachable. On the server side this is reached from OSSL_CMP_SRV_process_request() for any application that stands up a CMP server accepting PBM-protected messages, and on the client side from CMP response validation against a malicious or on-path (MITM) server. The reliable consequence is a denial of service; there is no memory disclosure, no controlled memory write, and no path to code execution. CMP is a specialized feature that an application must explicitly enable. FIPS impact: no As the CMP code lives outside the FIPS module boundary, no FIPS modules are affected by this CVE.", "cve_priority": "medium", "cve_public_date": "2026-08-25 13:19:00 UTC" }, { "cve": "CVE-2026-14457", "url": "https://ubuntu.com/security/CVE-2026-14457", "cve_description": "Issue summary: In a server or client configuration with RFC7250 Raw Public Keys (RPKs) enabled, and only the private key (with no associated certificate) configured locally, a NULL pointer dereference may occur when the remote peer solicits raw public keys and also sends the typically omitted \"signature_algorithms_cert\" TLS extension. Impact summary: The impact is limited to a possible Denial of Service as a result of an application abort, no data disclosure or remote command execution are possible. CWE: CWE-476: NULL Pointer Dereference Description: While a passing comment in sample code in the documentation suggests that key-only RPK configurations are supported, the best-practice RPK configuration is to always configure a corresponding certificate (possibly self-signed or signed by any convenient CA). When the private key is configured along with a matching certificate, the \"signature_algorithms_cert\" extension is handled reliably even without the fix, and peer clients or servers that don't support raw public keys may be able to complete a TLS connection by pinning or verifying the corresponding certificate or its public key. Deployments that prefer to configure just a private key with no certificate need to upgrade to an updated release as noted below. FIPS impact: no No FIPS modules are affected by this issue, as the SSL protocol implementation is outside the OpenSSL FIPS module boundary.", "cve_priority": "low", "cve_public_date": "2026-08-25 13:17:00 UTC" }, { "cve": "CVE-2026-54874", "url": "https://ubuntu.com/security/CVE-2026-54874", "cve_description": "Issue summary: Receiving a DTLS record for a future epoch while a handshake is in progress causes OpenSSL to buffer far more memory than the record itself requires. Impact summary: A peer can use a small amount of network traffic to make an OpenSSL DTLS endpoint retain a disproportionately large amount of memory, which may lead to a Denial of Service. CWE: CWE-405: Asymmetric Resource Consumption (Amplification) Description: While a DTLS handshake is in progress, a peer may legitimately have already moved on to the next epoch (for example, having sent its ChangeCipherSpec and Finished messages) before the local endpoint has processed the same transition, typically because of reordering on the underlying UDP transport. OpenSSL buffers such early records so that they can be processed once the local endpoint catches up. Buffering a record currently retains the entire read buffer it arrived in, which is sized to hold the largest possible DTLS record (around 16 kilobytes), rather than just the bytes that make up the record itself. Up to 100 such records may be buffered per connection. As a result, a peer that sends a stream of small forged records claiming to belong to the next epoch can cause an OpenSSL DTLS endpoint to retain around 1.7 megabytes of memory, despite sending only a small fraction of that amount of data over the network. An attacker therefore gains a memory amplification factor of around 1200, and can multiply the effect across as many associations as it is able to open, making this a remote memory exhaustion Denial of Service risk for DTLS servers. Since the memory retained per connection remains bounded, and any limit an application already places on the number of concurrent associations also bounds the total exposure, this issue has been assessed as Low severity. FIPS impact: no No FIPS modules are affected by this issue as the affected code is outside the OpenSSL FIPS module boundary. OpenSSL 4.0, 3.6, 3.5, 3.4, 3.0, 1.1.1 and 1.0.2 are vulnerable to this issue. OpenSSL 4.0 users should upgrade to OpenSSL 4.0.2. OpenSSL 3.6 users should upgrade to OpenSSL 3.6.4. OpenSSL 3.5 users should upgrade to OpenSSL 3.5.8. OpenSSL 3.4 users should upgrade to OpenSSL 3.4.7. OpenSSL 3.0 users should upgrade to OpenSSL 3.0.22. Premium support customers only: OpenSSL 1.1.1 users should upgrade to OpenSSL 1.1.1zi OpenSSL 1.0.2 users should upgrade to OpenSSL 1.0.2zr This issue was reported on 18 May 2026 by Amazon Web Services. The fix has been developed by Matt Caswell. -- cut (non-publishing metadata for internal use) -- Reported by: Amazon Web Services Fixed by: Matt Caswell", "cve_priority": "low", "cve_public_date": "2026-08-25 13:19:00 UTC" }, { "cve": "CVE-2026-63073", "url": "https://ubuntu.com/security/CVE-2026-63073", "cve_description": "Issue summary: OpenSSL CMP response validation passed an unexpected response sender distinguished name directly as the format string to `ERR_raise_data()`. Impact summary: A malicious or intercepted CMP endpoint can crash a CMP client that enforces an expected sender or uses a pinned server certificate whose subject becomes the default expected sender. CWE: CWE-134 (Use of Externally-Controlled Format String) Description: When validating a received CMP message, ossl_cmp_msg_check_update() converts the peer-supplied sender distinguished name with X509_NAME_oneline() and passes it directly as the format argument to ERR_raise_data(). Percent characters survive the conversion, so a sender DN such as \"CN=%s%n\" reaches BIO_vsnprintf() as an attacker-controlled format string with no matching variadic arguments. This path is only reached when the caller configures an expected sender or pins a server certificate, which is the normal configuration for a CMP client validating server responses. Since the attacker controls the format string but none of the variadic arguments, such specifiers as %s and %n dereference or write through unrelated stack contents and crash the client. The reliable consequence is a denial of service, when the response comes from a malicious or intercepted CMP endpoint. There is no controlled memory write, arbitrary-address read, or reliable path to remote code execution. FIPS impact: no No FIPS modules are affected by this issue, as the CMP protocol implementation is outside the OpenSSL FIPS module boundary.", "cve_priority": "low", "cve_public_date": "2026-08-25 13:19:00 UTC" }, { "cve": "CVE-2026-63074", "url": "https://ubuntu.com/security/CVE-2026-63074", "cve_description": "Issue summary: The OpenSSL Certificate Management Protocol (CMP) caches additional certificates (extraCerts) sent in a CMP message, but never expunges them (for instance if they are invalid). If a server reuses an OSSL_CMP_CTX frequently, this cache of extraCerts may grow unboundedly, and a malicious client may flood a CMP server with requests driving this growth. Impact summary: Users utilizing a CMP server that reuses a single OSSL_CMP_CTX for the lifetime of a server process may observe unbounded memory growth in the event a malicious client repeatedly sends requests containing unique extra certificates, which may lead to OOM conditions. CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: If a remote user sends CMP messages to a server with a list of extraCerts and the message is rejected, the extraCerts from the message remains in the server contexts untrusted certificate stack. This exposes servers with long lived ctx objects to Denial of Service attacks in which an attacker sends messages intending to be rejected with a large list of additional certificates repeatedly, forcing the server to store them indefinitely. The issue was fixed by removing the added extra certs if the message is rejected, using the same method as when the context is configured to not do caching at all. FIPS impact: no As the CMP code lives outside the FIPS module boundary, no FIPS modules are affected by this CVE.", "cve_priority": "low", "cve_public_date": "2026-08-25 13:19:00 UTC" }, { "cve": "CVE-2026-63075", "url": "https://ubuntu.com/security/CVE-2026-63075", "cve_description": "Issue summary: When OpenSSL processes QUIC traffic from a peer that repeatedly sends ack-eliciting packets while not acknowledging ACK-only responses, the QUIC stack can retain ACK-only packet metadata for the lifetime of the connection. Impact summary: A remote peer that can complete a QUIC handshake can cause connection-scoped memory growth which may lead to Denial of Service through memory exhaustion, especially with sustained traffic or many concurrent QUIC connections. CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: When the OpenSSL QUIC stack sends an ACK-only packet, there is no requirement by the QUIC protocol that the peer will acknowledge that ACK-only packet (i.e. it is itself not ack-eliciting). However, the OpenSSL implementation stores the metadata about the ACK frames regardless. In and of itself that's ok, but if a malicious peer establishes a connection, and then drives the connection such that ACK-only packets are forced from the OpenSSL implementation peer (i.e., by sending numerous PING frames), and then withholding any subsequent acks for ack-eliciting data, like legitimate data, said malicious peer can force inappropriate memory growth on the OpenSSL peer, potentially leading to a Denial of Service. The fix is to ensure that we account for the transmission of the ACK-only packet in the packet histories high and low watermark without actually storing the ACK-only packet metadata itself. FIPS impact: no The OpenSSL FIPS module is not affected as the QUIC code is outside the FIPS module boundary.", "cve_priority": "low", "cve_public_date": "2026-08-25 13:19:00 UTC" }, { "cve": "CVE-2026-75803", "url": "https://ubuntu.com/security/CVE-2026-75803", "cve_description": "Issue summary: ChaCha20-Poly1305 and AES-OCB decryption with an empty ciphertext can report success without verifying the supplied authentication tag when the operation is finalized by calling the EVP_Cipher() function. Impact summary: Applications calling EVP_Cipher() on an empty ciphertext and expecting the call to check the AEAD tag may accept forged messages. CWE: CWE-354 (Improper Validation of Integrity Check Value) Description: The EVP_Cipher() API call for AEAD ciphers behaves like a one shot encryption and decryption call. It also verifies the AEAD tag after the decryption operation. However for AES-OCB and ChaCha20-Poly1305 ciphers it skipped the AEAD tag verification when an empty ciphertext was passed to the function. The callers of this function might believe that a successful return indicates a valid AEAD tag for these ciphers, even when that has not truly been validated in this case. FIPS impact: no The FIPS modules in 4.0, 3.6, 3.5, 3.4, and 3.0 are not affected by this CVE as the affected algorithms are not FIPS approved and thus not implemented in the FIPS module.", "cve_priority": "low", "cve_public_date": "2026-08-25 13:19:00 UTC" }, { "cve": "CVE-2026-14456", "url": "https://ubuntu.com/security/CVE-2026-14456", "cve_description": "Issue summary: When an OpenSSL QUIC server (Listener SSL object) processes valid QUIC Initial packets for unknown destination connection IDs, it can allocate and queue new incoming channels without enforcing any limit. Impact summary: A remote peer that can make many Initial packets reach the server listener faster than the application accepts connections, can cause the memory allocated to store the per-channel state to grow without any limits, potentially making the QUIC listener unavailable and causing Denial of Service. CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: The function that handles inbound QUIC packets uses Connection-Id from the packet header to find an existing connection (QUIC channel). If no existing connection is found and the packet type is INITIAL, the function treats the packet as a new connection. It allocates a new channel object and inserts it into a queue where it waits to be accepted by the local application with SSL_accept(3ossl). The memory occupied by these initial channel objects may grow without bounds if the application is not able to call SSL_accept() frequently enough to serve these inbound connection requests. The issue is present since OpenSSL 3.5 when the QUIC server implementation was added. The fix introduces a limit for pending connections. The default limit is set to 256 pending connections (waiting to be accepted by the local application). Applications may change the default by calling SSL_set_value_uint(3ossl). FIPS impact: no The FIPS module is not affected as the QUIC implementation is outside of the OpenSSL FIPS module boundary.", "cve_priority": "medium", "cve_public_date": "2026-08-13 15:19:00 UTC" }, { "cve": "CVE-2026-54876", "url": "https://ubuntu.com/security/CVE-2026-54876", "cve_description": "Issue summary: A malicious TLS server can cause a memory leak in a TLS client that has enabled OCSP response checking by sending an OCSP response that contains no single response entries. Impact summary: An attacker can leak an attacker-tunable amount of memory per TLS handshake in a victim client application. A long-running client that repeatedly connects to a malicious server can have its memory exhausted, resulting in a Denial of Service. CWE: CWE-401: Missing Release of Memory after Effective Lifetime Description: The affected function is called during X.509 certificate chain verification when OCSP response checking is enabled with the X509_V_FLAG_OCSP_RESP_CHECK or X509_V_FLAG_OCSP_RESP_CHECK_ALL verification flags, for example when a TLS client verifies an OCSP response stapled into the TLS handshake by the server. When the received BasicOCSPResponse contains an empty SEQUENCE OF SingleResponse, which is permitted on the wire and accepted by the OpenSSL decoder, the OCSP_BASICRESP structure allocated by OCSP_response_get1_basic() was not freed because an early return bypassed the cleanup code at the end of the function. The amount of memory leaked per handshake can be amplified by the attacker by padding the certs field of the BasicOCSPResponse with bogus certificates, which are parsed and stored in the leaked structure before the empty response check triggers the early return. A long-running TLS client that repeatedly connects to a malicious server can have its memory exhausted over time. OCSP response checking is not enabled by default. Only client applications that explicitly enable the OCSP response check verification flags are affected. FIPS impact: no The FIPS modules in 4.0 and 3.6 are not affected by this issue as the affected code is outside the OpenSSL FIPS module boundary.", "cve_priority": "medium", "cve_public_date": "2026-08-05 15:16:00 UTC" } ], "log": [ "", " * Import 4.0.2", " - CVE-2026-18798 (\"QUIC Server May Trigger Double Free When Processing", " INITIAL Packet\")", " - CVE-2026-63072 (\"Heap Buffer Overflow in CMS Key Unwrapping\")", " - CVE-2026-63076 (\"Invalid Pointer Dereference in CMP Server via Crafted", " protectionAlg\")", " - CVE-2026-14457 (\"RPK Server Signature Algorithm Selection Can Dereference", " a Missing Certificate\")", " - CVE-2026-54874 (\"Excessive Memory Use Buffering DTLS Records for a Future", " Epoch\")", " - CVE-2026-63073 (\"Untrusted Sender DN Used as Format String in CMP Response", " Validation\")", " - CVE-2026-63074 (\"CMP Indefinite Cache Growth of ExtraCerts\")", " - CVE-2026-63075 (\"QUIC ACK-only Packet Retention Can Cause Memory", " Exhaustion\")", " - CVE-2026-75803 (\"AEAD Forgeries with Empty Ciphertext When Using", " EVP_Cipher()\") (Closes: #1145172)", " - CVE-2026-14456 (\"Unbounded Memory Growth in QUIC Server Incoming Channel", " Queue\") (Closes: #1144615)", " - CVE-2026-54876 (\"Client-Side Memory Leak in OCSP Response Checking\") (Closes: #1143841)", "" ], "package": "openssl", "version": "4.0.2-1", "urgency": "medium", "distributions": "experimental", "launchpad_bugs_fixed": [], "author": "Sebastian Andrzej Siewior ", "date": "Tue, 25 Aug 2026 21:19:42 +0200" } ], "notes": null, "is_version_downgrade": false }, { "name": "libstdc++6", "from_version": { "source_package_name": "gcc-16", "source_package_version": "16.2.0-2ubuntu1", "version": "16.2.0-2ubuntu1" }, "to_version": { "source_package_name": "gcc-16", "source_package_version": "16.2.0-3ubuntu1", "version": "16.2.0-3ubuntu1" }, "cves": [], "launchpad_bugs_fixed": [], "changes": [ { "cves": [], "log": [ "", " * Merge with Debian; remaining changes:", " - Build from upstream sources.", "" ], "package": "gcc-16", "version": "16.2.0-3ubuntu1", "urgency": "medium", "distributions": "stonking", "launchpad_bugs_fixed": [], "author": "Matthias Klose ", "date": "Fri, 18 Sep 2026 09:36:18 +0200" }, { "cves": [], "log": [ "", " * Update to git 20260918 from the gcc-16 branch.", " - Fix PR target/127306 (RISCV), PR target/127318 (RISCV),", " PR target/127153 (loongarch), PR target/126932 (RISCV),", " PR middle-end/127256, PR target/126463 (AArch64),", " PR target/126196 (RISCV), PR rtl-optimization/125683, PR debug/125421,", " PR target/127188 (RISCV), PR c++/125642, PR c++/127207, PR c++/123495,", " PR c++/126860, PR c++/124983, PR fortran/127128, PR libstdc++/124121,", " PR libstdc++/127220, PR libstdc++/127219, PR libstdc++/126949,", " PR libstdc++/127325, PR libstdc++/126800, PR target/122535 (PPC),", " PR tree-optimization/127390, PR tree-optimization/127377,", " PR tree-optimization/127262, PR tree-optimization/127130,", " PR tree-optimization/127049, PR tree-optimization/127000,", " PR tree-optimization/127000, PR tree-optimization/126760,", " PR tree-optimization/127391, PR tree-optimization/126658, PR ipa/126153,", " PR tree-optimization/126153, PR ipa/126153, PR libstdc++/127430.", " * Strip compiler executables for release builds. Closes: #1147241.", " * Bootstrap using gnat-14, to be able to remove GCC 15.", " * Add comment why libstdc++.so in the gcc_lib_dir needs to be copy", " of the library, not a symlink.", " * Apply PR target/120165 (m68k only), taken from the trunk.", "" ], "package": "gcc-16", "version": "16.2.0-3", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Matthias Klose ", "date": "Fri, 18 Sep 2026 09:35:21 +0200" } ], "notes": null, "is_version_downgrade": false }, { "name": "libsystemd-shared", "from_version": { "source_package_name": "systemd", "source_package_version": "261.2-1ubuntu2", "version": "261.2-1ubuntu2" }, "to_version": { "source_package_name": "systemd", "source_package_version": "261.3-0ubuntu3", "version": "261.3-0ubuntu3" }, "cves": [], "launchpad_bugs_fixed": [ 2169316 ], "changes": [ { "cves": [], "log": [ "", " * d/rules: remove libssl3t64 Depends (LP: #2169316)", "" ], "package": "systemd", "version": "261.3-0ubuntu3", "urgency": "medium", "distributions": "stonking", "launchpad_bugs_fixed": [ 2169316 ], "author": "Nick Rosbrook ", "date": "Fri, 02 Oct 2026 13:35:38 -0400" }, { "cves": [], "log": [ "", " * d/udev.install: do not install tpm2 rules on i386", "" ], "package": "systemd", "version": "261.3-0ubuntu2", "urgency": "medium", "distributions": "stonking", "launchpad_bugs_fixed": [], "author": "Nick Rosbrook ", "date": "Wed, 23 Sep 2026 08:39:15 -0400" }, { "cves": [], "log": [ "", " * New upstream stable version 261.3", " - d/gbp.conf: set upstream branch to 261.x stable", " - d/watch: track 261.x stable", " - Update upstream source from tag 'upstream/261.3'", " Update to upstream version '261.3'", " with Debian dir 3857375784a9bdd0b319a0e09222392a5d485461", " - Bug fixes", " * mkosi: remove systemd from minimal-base on ubuntu", " * d/systemd.links: stop creating hwclock.service mask", "" ], "package": "systemd", "version": "261.3-0ubuntu1", "urgency": "medium", "distributions": "stonking", "launchpad_bugs_fixed": [], "author": "Nick Rosbrook ", "date": "Mon, 21 Sep 2026 17:15:49 -0400" } ], "notes": null, "is_version_downgrade": false }, { "name": "libsystemd0", "from_version": { "source_package_name": "systemd", "source_package_version": "261.2-1ubuntu2", "version": "261.2-1ubuntu2" }, "to_version": { "source_package_name": "systemd", "source_package_version": "261.3-0ubuntu3", "version": "261.3-0ubuntu3" }, "cves": [], "launchpad_bugs_fixed": [ 2169316 ], "changes": [ { "cves": [], "log": [ "", " * d/rules: remove libssl3t64 Depends (LP: #2169316)", "" ], "package": "systemd", "version": "261.3-0ubuntu3", "urgency": "medium", "distributions": "stonking", "launchpad_bugs_fixed": [ 2169316 ], "author": "Nick Rosbrook ", "date": "Fri, 02 Oct 2026 13:35:38 -0400" }, { "cves": [], "log": [ "", " * d/udev.install: do not install tpm2 rules on i386", "" ], "package": "systemd", "version": "261.3-0ubuntu2", "urgency": "medium", "distributions": "stonking", "launchpad_bugs_fixed": [], "author": "Nick Rosbrook ", "date": "Wed, 23 Sep 2026 08:39:15 -0400" }, { "cves": [], "log": [ "", " * New upstream stable version 261.3", " - d/gbp.conf: set upstream branch to 261.x stable", " - d/watch: track 261.x stable", " - Update upstream source from tag 'upstream/261.3'", " Update to upstream version '261.3'", " with Debian dir 3857375784a9bdd0b319a0e09222392a5d485461", " - Bug fixes", " * mkosi: remove systemd from minimal-base on ubuntu", " * d/systemd.links: stop creating hwclock.service mask", "" ], "package": "systemd", "version": "261.3-0ubuntu1", "urgency": "medium", "distributions": "stonking", "launchpad_bugs_fixed": [], "author": "Nick Rosbrook ", "date": "Mon, 21 Sep 2026 17:15:49 -0400" } ], "notes": null, "is_version_downgrade": false }, { "name": "libudev1", "from_version": { "source_package_name": "systemd", "source_package_version": "261.2-1ubuntu2", "version": "261.2-1ubuntu2" }, "to_version": { "source_package_name": "systemd", "source_package_version": "261.3-0ubuntu3", "version": "261.3-0ubuntu3" }, "cves": [], "launchpad_bugs_fixed": [ 2169316 ], "changes": [ { "cves": [], "log": [ "", " * d/rules: remove libssl3t64 Depends (LP: #2169316)", "" ], "package": "systemd", "version": "261.3-0ubuntu3", "urgency": "medium", "distributions": "stonking", "launchpad_bugs_fixed": [ 2169316 ], "author": "Nick Rosbrook ", "date": "Fri, 02 Oct 2026 13:35:38 -0400" }, { "cves": [], "log": [ "", " * d/udev.install: do not install tpm2 rules on i386", "" ], "package": "systemd", "version": "261.3-0ubuntu2", "urgency": "medium", "distributions": "stonking", "launchpad_bugs_fixed": [], "author": "Nick Rosbrook ", "date": "Wed, 23 Sep 2026 08:39:15 -0400" }, { "cves": [], "log": [ "", " * New upstream stable version 261.3", " - d/gbp.conf: set upstream branch to 261.x stable", " - d/watch: track 261.x stable", " - Update upstream source from tag 'upstream/261.3'", " Update to upstream version '261.3'", " with Debian dir 3857375784a9bdd0b319a0e09222392a5d485461", " - Bug fixes", " * mkosi: remove systemd from minimal-base on ubuntu", " * d/systemd.links: stop creating hwclock.service mask", "" ], "package": "systemd", "version": "261.3-0ubuntu1", "urgency": "medium", "distributions": "stonking", "launchpad_bugs_fixed": [], "author": "Nick Rosbrook ", "date": "Mon, 21 Sep 2026 17:15:49 -0400" } ], "notes": null, "is_version_downgrade": false }, { "name": "libuuid1", "from_version": { "source_package_name": "util-linux", "source_package_version": "2.41.3-3ubuntu2", "version": "2.41.3-3ubuntu2" }, "to_version": { "source_package_name": "util-linux", "source_package_version": "2.42.2-1ubuntu2", "version": "2.42.2-1ubuntu2" }, "cves": [ { "cve": "CVE-2026-53612", "url": "https://ubuntu.com/security/CVE-2026-53612", "cve_description": "[Local Privilege Escalation via TOCTOU in mount(8) hook_owner.c chmod/chown]", "cve_priority": "medium", "cve_public_date": "2026-06-18" }, { "cve": "CVE-2026-53613", "url": "https://ubuntu.com/security/CVE-2026-53613", "cve_description": "[Local Privilege Escalation via TOCTOU in mount(8) - Target Path Redirection]", "cve_priority": "medium", "cve_public_date": "2026-06-18" }, { "cve": "CVE-2026-53614", "url": "https://ubuntu.com/security/CVE-2026-53614", "cve_description": "[Local Privilege Escalation via LIBMOUNT_FORCE_MOUNT2 Environment Variable - nosuid/noexec Bypass in SUID mount(8)]", "cve_priority": "medium", "cve_public_date": "2026-06-18" }, { "cve": "CVE-2026-27456", "url": "https://ubuntu.com/security/CVE-2026-27456", "cve_description": "util-linux is a random collection of Linux utilities. Prior to version 2.41.4, a TOCTOU (Time-of-Check-Time-of-Use) vulnerability has been identified in the SUID binary /usr/bin/mount from util-linux. The mount binary, when setting up loop devices, validates the source file path with user privileges via fork() + setuid() + realpath(), but subsequently re-canonicalizes and opens it with root privileges (euid=0) without verifying that the path has not been replaced between both operations. Neither O_NOFOLLOW, nor inode comparison, nor post-open fstat() are employed. This allows a local unprivileged user to replace the source file with a symlink pointing to any root-owned file or device during the race window, causing the SUID binary to open and mount it as root. Exploitation requires an /etc/fstab entry with user,loop options whose path points to a directory where the attacker has write permission, and that /usr/bin/mount has the SUID bit set (the default configuration on virtually all Linux distributions). The impact is unauthorized read access to root-protected files and block devices, including backup images, disk volumes, and any file containing a valid filesystem. This issue has been patched in version 2.41.4.", "cve_priority": "medium", "cve_public_date": "2026-04-03 22:16:00 UTC" }, { "cve": "CVE-2026-3184", "url": "https://ubuntu.com/security/CVE-2026-3184", "cve_description": "A flaw was found in util-linux. Improper hostname canonicalization in the `login(1)` utility, when invoked with the `-h` option, can modify the supplied remote hostname before setting `PAM_RHOST`. A remote attacker could exploit this by providing a specially crafted hostname, potentially bypassing host-based Pluggable Authentication Modules (PAM) access control rules that rely on fully qualified domain names. This could lead to unauthorized access.", "cve_priority": "medium", "cve_public_date": "2026-04-03 19:17:00 UTC" } ], "launchpad_bugs_fixed": [ 2166882, 2153369, 2125968 ], "changes": [ { "cves": [], "log": [ "", " * d/p/ubuntu/libmount-restricted-live-creds.patch: restore live-credential", " check for libmount restricted mode (LP: #2166882)", "" ], "package": "util-linux", "version": "2.42.2-1ubuntu2", "urgency": "medium", "distributions": "stonking", "launchpad_bugs_fixed": [ 2166882 ], "author": "Nadzeya Hutsko ", "date": "Wed, 16 Sep 2026 19:36:33 +0200" }, { "cves": [], "log": [ "", " * Merge with Debian unstable (LP: #2153369).", " Added changes:", " - tests/fincore: force the use of GNU dd over uutils (LP: #2125968)", " Remaining changes:", " - Add sulogin-fallback-static-sh.patch", " Add support for /bin/static-sh as fallback if the regular shell fails to", " execute. Patch ported from sysvinit. (see LP #505887)", " - Add sulogin-lockedpwd.patch", " Make sure file systems can be fixed on machines with locked root", " accounts (as Ubuntu does by default). Don't require --force for sulogin.", " - d/rules: disable libmount mountfs support", " Disable brand new feature with --disable-libmount-mountfd-support that", " causes inability to deploy MAAS LP #2037417.", " - d/p/ubuntu/su-pty-drop-caps.patch: harden 'su --pty' to temporarily lower", " capabilities while proxying between stdin/stdout and the pty master. This", " is to avoid su from being used to exploit kernel vulnerabilities.", "" ], "package": "util-linux", "version": "2.42.2-1ubuntu1", "urgency": "medium", "distributions": "stonking", "launchpad_bugs_fixed": [ 2153369, 2125968 ], "author": "Florent 'Skia' Jacquet ", "date": "Fri, 26 Jun 2026 12:03:00 +0200" }, { "cves": [ { "cve": "CVE-2026-53612", "url": "https://ubuntu.com/security/CVE-2026-53612", "cve_description": "[Local Privilege Escalation via TOCTOU in mount(8) hook_owner.c chmod/chown]", "cve_priority": "medium", "cve_public_date": "2026-06-18" }, { "cve": "CVE-2026-53613", "url": "https://ubuntu.com/security/CVE-2026-53613", "cve_description": "[Local Privilege Escalation via TOCTOU in mount(8) - Target Path Redirection]", "cve_priority": "medium", "cve_public_date": "2026-06-18" }, { "cve": "CVE-2026-53614", "url": "https://ubuntu.com/security/CVE-2026-53614", "cve_description": "[Local Privilege Escalation via LIBMOUNT_FORCE_MOUNT2 Environment Variable - nosuid/noexec Bypass in SUID mount(8)]", "cve_priority": "medium", "cve_public_date": "2026-06-18" } ], "log": [ "", " * New upstream version, fixing security issues", " CVE-2026-53612, CVE-2026-53613, CVE-2026-53614 (Closes: #1140194,", " #1140195, #1140196)", " * Drop upstream-applied patch.", "" ], "package": "util-linux", "version": "2.42.2-1", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Wed, 17 Jun 2026 11:20:49 +0200" }, { "cves": [], "log": [ "", " * Follow debhelper 14.1, thus putting PAM files back into /etc/pam.d.", " Note that include=login is still undesirable, and packages should", " include common-* instead.", "" ], "package": "util-linux", "version": "2.42.1-6", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Tue, 16 Jun 2026 22:26:25 +0200" }, { "cves": [], "log": [ "", " * PAM config: stop using include.", " Avoid including our own PAM config files, as a workaround until PAM can", " include files from /usr/lib/pam.d.", " Should make su -(l) and runuser -l work again. See #1140029.", "" ], "package": "util-linux", "version": "2.42.1-5", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Mon, 15 Jun 2026 19:34:54 +0200" }, { "cves": [], "log": [ "", " * Update debhelper-compat to v14.", " Remove dh-sequence-installsysusers, remove ${misc:Pre-Depends} from", " Pre-Depends. PAM /etc/pam.d files are replaced by files in", " /usr/lib/pam.d.", "" ], "package": "util-linux", "version": "2.42.1-4", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Sun, 14 Jun 2026 17:28:35 +0200" }, { "cves": [], "log": [ "", " * Use upstream patch to fix FTBFS on systems with non-4K pagesizes", " (Closes: #1138789)", "" ], "package": "util-linux", "version": "2.42.1-3", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Mon, 08 Jun 2026 15:05:17 +0200" }, { "cves": [], "log": [ "", " * Fix FTBFS on systems with non-4K pagesizes (Closes: #1138789)", "" ], "package": "util-linux", "version": "2.42.1-2", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Thu, 04 Jun 2026 13:31:17 +0200" }, { "cves": [], "log": [ "", " * New upstream version", " * Refresh/drop upstream applied patches", "", " [ Karel Zak ]", " * script: fix backward compatibility for options after non-option args", " * script: fix \"--\" separator when used as option argument", " (Closes: #1132887)", "" ], "package": "util-linux", "version": "2.42.1-1", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Wed, 03 Jun 2026 20:12:19 +0200" }, { "cves": [], "log": [ "", " * Stop using Linux crypto API in hardlink(1)", "" ], "package": "util-linux", "version": "2.42-6", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Wed, 06 May 2026 20:41:22 +0200" }, { "cves": [], "log": [ "", " * Remove leftover /etc/init.d/uuidd conffile", "" ], "package": "util-linux", "version": "2.42-5", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Sun, 26 Apr 2026 14:49:42 +0200" }, { "cves": [], "log": [ "", " * Apply upstream revert of su breakage", " (Closes: #1133379, #1132588, #1132610)", "" ], "package": "util-linux", "version": "2.42-4", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Sun, 19 Apr 2026 17:36:56 +0200" }, { "cves": [], "log": [ "", " * Stop pulling deb_systemdsystemunitdir from pkg-config", " * Stop installing uuidd init script", " * Clarify /bin/login situation on Hurd", " * Install bash-completions using normal dh_install mechanism", " * Install more localized man pages", " * Simplify installing into udebs", " * Install lintian overrides into udebs", " * Run a second build without libsystemd for d-i.", " This is not great, but I see no other option at this time.", " Let's hope a libsystemd0-udeb will appear. (Closes: #1132561)", " * util-linux-extra: install copyfilerange, getino", " * Update lintian overrides", " * Update dependency libselinux1-dev to libselinux-dev", "" ], "package": "util-linux", "version": "2.42-3", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Sun, 12 Apr 2026 00:03:33 +0200" }, { "cves": [], "log": [ "", " * Add upstream patches addressing #1132887", "" ], "package": "util-linux", "version": "2.42-2", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Wed, 08 Apr 2026 18:28:21 +0200" }, { "cves": [ { "cve": "CVE-2026-27456", "url": "https://ubuntu.com/security/CVE-2026-27456", "cve_description": "util-linux is a random collection of Linux utilities. Prior to version 2.41.4, a TOCTOU (Time-of-Check-Time-of-Use) vulnerability has been identified in the SUID binary /usr/bin/mount from util-linux. The mount binary, when setting up loop devices, validates the source file path with user privileges via fork() + setuid() + realpath(), but subsequently re-canonicalizes and opens it with root privileges (euid=0) without verifying that the path has not been replaced between both operations. Neither O_NOFOLLOW, nor inode comparison, nor post-open fstat() are employed. This allows a local unprivileged user to replace the source file with a symlink pointing to any root-owned file or device during the race window, causing the SUID binary to open and mount it as root. Exploitation requires an /etc/fstab entry with user,loop options whose path points to a directory where the attacker has write permission, and that /usr/bin/mount has the SUID bit set (the default configuration on virtually all Linux distributions). The impact is unauthorized read access to root-protected files and block devices, including backup images, disk volumes, and any file containing a valid filesystem. This issue has been patched in version 2.41.4.", "cve_priority": "medium", "cve_public_date": "2026-04-03 22:16:00 UTC" } ], "log": [ "", " * New upstream release, fixing CVE-2026-27456 and a CWE-190.", " * Upload to unstable.", "" ], "package": "util-linux", "version": "2.42-1", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Thu, 02 Apr 2026 15:19:42 +0200" }, { "cves": [], "log": [ "", " * New upstream release candidate.", " * Refresh patches", "" ], "package": "util-linux", "version": "2.42~rc2-1", "urgency": "medium", "distributions": "experimental", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Thu, 26 Mar 2026 15:05:59 +0100" }, { "cves": [], "log": [ "", " * Apply upstream patches", " * Fixes unshare issue", " * Use Hurd patches directly from upstream", "" ], "package": "util-linux", "version": "2.42~rc1-3", "urgency": "medium", "distributions": "experimental", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Sun, 22 Mar 2026 15:20:19 +0100" }, { "cves": [], "log": [ "", " * Fix lsmem tests on loong64.", " Using patch from https://github.com/util-linux/util-linux/pull/4090", " * autopkgtests: switch to pkgconf", "", " [ Samuel Thibault ]", " * Fix build on Hurd", "" ], "package": "util-linux", "version": "2.42~rc1-2", "urgency": "medium", "distributions": "experimental", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Tue, 03 Mar 2026 12:43:24 +0100" }, { "cves": [ { "cve": "CVE-2026-3184", "url": "https://ubuntu.com/security/CVE-2026-3184", "cve_description": "A flaw was found in util-linux. Improper hostname canonicalization in the `login(1)` utility, when invoked with the `-h` option, can modify the supplied remote hostname before setting `PAM_RHOST`. A remote attacker could exploit this by providing a specially crafted hostname, potentially bypassing host-based Pluggable Authentication Modules (PAM) access control rules that rely on fully qualified domain names. This could lead to unauthorized access.", "cve_priority": "medium", "cve_public_date": "2026-04-03 19:17:00 UTC" } ], "log": [ "", " * New upstream release candidate.", " * includes fix for CVE-2026-3184:", " * login: use original FQDN for PAM_RHOST", " * libuuid: reset initial cont-clock time on service start (Closes:", " #1126894)", " * Symbols: use (symver) and update lists", " * Stop installing untranslated man pages", "" ], "package": "util-linux", "version": "2.42~rc1-1", "urgency": "medium", "distributions": "experimental", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Sat, 28 Feb 2026 20:37:48 +0100" }, { "cves": [], "log": [ "", " [ Chris Hofstaedtler ]", " * Follow libselinux1-dev to libselinux-dev rename (Closes: #1124751)", " * uuid-runtime: stop removing /var/run/uuidd on purge", " /run is a tmpfs, it will be cleaned up anyway. Lets us drop the postrm", " maintscript.", "", " [ Luca Boccassi ]", " * uuid-runtime: drop manual scripting in postinst and rely on sysusers.d", "" ], "package": "util-linux", "version": "2.41.3-4", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Sat, 21 Feb 2026 17:15:50 +0100" } ], "notes": null, "is_version_downgrade": false }, { "name": "linux-image-virtual", "from_version": { "source_package_name": "linux-meta", "source_package_version": "7.3.0-5.5+3", "version": "7.3.0-5.5+3" }, "to_version": { "source_package_name": "linux-meta", "source_package_version": "7.3.0-8.8", "version": "7.3.0-8.8" }, "cves": [], "launchpad_bugs_fixed": [ 2168012 ], "changes": [ { "cves": [], "log": [ "", " * Main version: 7.3.0-8.8", "", " * Include v4l2loopback in default modules set for 26.04 (LP: #2168012)", " - [Packaging] Add dependencies for v4l2loopback", "" ], "package": "linux-meta", "version": "7.3.0-8.8", "urgency": "medium", "distributions": "stonking", "launchpad_bugs_fixed": [ 2168012 ], "author": "Paolo Pisati ", "date": "Tue, 29 Sep 2026 19:08:40 +0200" }, { "cves": [], "log": [ "", " * Main version: 7.3.0-7.7", "" ], "package": "linux-meta", "version": "7.3.0-7.7", "urgency": "medium", "distributions": "stonking", "launchpad_bugs_fixed": [], "author": "Paolo Pisati ", "date": "Mon, 28 Sep 2026 18:13:36 +0200" }, { "cves": [], "log": [ "", " * Main version: 7.3.0-6.6", "" ], "package": "linux-meta", "version": "7.3.0-6.6", "urgency": "medium", "distributions": "stonking", "launchpad_bugs_fixed": [], "author": "Paolo Pisati ", "date": "Mon, 21 Sep 2026 17:08:03 +0200" } ], "notes": null, "is_version_downgrade": false }, { "name": "login", "from_version": { "source_package_name": "util-linux", "source_package_version": "2.41.3-3ubuntu2", "version": "1:4.16.0-2+really2.41.3-3ubuntu2" }, "to_version": { "source_package_name": "util-linux", "source_package_version": "2.42.2-1ubuntu2", "version": "1:4.16.0-2+really2.42.2-1ubuntu2" }, "cves": [ { "cve": "CVE-2026-53612", "url": "https://ubuntu.com/security/CVE-2026-53612", "cve_description": "[Local Privilege Escalation via TOCTOU in mount(8) hook_owner.c chmod/chown]", "cve_priority": "medium", "cve_public_date": "2026-06-18" }, { "cve": "CVE-2026-53613", "url": "https://ubuntu.com/security/CVE-2026-53613", "cve_description": "[Local Privilege Escalation via TOCTOU in mount(8) - Target Path Redirection]", "cve_priority": "medium", "cve_public_date": "2026-06-18" }, { "cve": "CVE-2026-53614", "url": "https://ubuntu.com/security/CVE-2026-53614", "cve_description": "[Local Privilege Escalation via LIBMOUNT_FORCE_MOUNT2 Environment Variable - nosuid/noexec Bypass in SUID mount(8)]", "cve_priority": "medium", "cve_public_date": "2026-06-18" }, { "cve": "CVE-2026-27456", "url": "https://ubuntu.com/security/CVE-2026-27456", "cve_description": "util-linux is a random collection of Linux utilities. Prior to version 2.41.4, a TOCTOU (Time-of-Check-Time-of-Use) vulnerability has been identified in the SUID binary /usr/bin/mount from util-linux. The mount binary, when setting up loop devices, validates the source file path with user privileges via fork() + setuid() + realpath(), but subsequently re-canonicalizes and opens it with root privileges (euid=0) without verifying that the path has not been replaced between both operations. Neither O_NOFOLLOW, nor inode comparison, nor post-open fstat() are employed. This allows a local unprivileged user to replace the source file with a symlink pointing to any root-owned file or device during the race window, causing the SUID binary to open and mount it as root. Exploitation requires an /etc/fstab entry with user,loop options whose path points to a directory where the attacker has write permission, and that /usr/bin/mount has the SUID bit set (the default configuration on virtually all Linux distributions). The impact is unauthorized read access to root-protected files and block devices, including backup images, disk volumes, and any file containing a valid filesystem. This issue has been patched in version 2.41.4.", "cve_priority": "medium", "cve_public_date": "2026-04-03 22:16:00 UTC" }, { "cve": "CVE-2026-3184", "url": "https://ubuntu.com/security/CVE-2026-3184", "cve_description": "A flaw was found in util-linux. Improper hostname canonicalization in the `login(1)` utility, when invoked with the `-h` option, can modify the supplied remote hostname before setting `PAM_RHOST`. A remote attacker could exploit this by providing a specially crafted hostname, potentially bypassing host-based Pluggable Authentication Modules (PAM) access control rules that rely on fully qualified domain names. This could lead to unauthorized access.", "cve_priority": "medium", "cve_public_date": "2026-04-03 19:17:00 UTC" } ], "launchpad_bugs_fixed": [ 2166882, 2153369, 2125968 ], "changes": [ { "cves": [], "log": [ "", " * d/p/ubuntu/libmount-restricted-live-creds.patch: restore live-credential", " check for libmount restricted mode (LP: #2166882)", "" ], "package": "util-linux", "version": "2.42.2-1ubuntu2", "urgency": "medium", "distributions": "stonking", "launchpad_bugs_fixed": [ 2166882 ], "author": "Nadzeya Hutsko ", "date": "Wed, 16 Sep 2026 19:36:33 +0200" }, { "cves": [], "log": [ "", " * Merge with Debian unstable (LP: #2153369).", " Added changes:", " - tests/fincore: force the use of GNU dd over uutils (LP: #2125968)", " Remaining changes:", " - Add sulogin-fallback-static-sh.patch", " Add support for /bin/static-sh as fallback if the regular shell fails to", " execute. Patch ported from sysvinit. (see LP #505887)", " - Add sulogin-lockedpwd.patch", " Make sure file systems can be fixed on machines with locked root", " accounts (as Ubuntu does by default). Don't require --force for sulogin.", " - d/rules: disable libmount mountfs support", " Disable brand new feature with --disable-libmount-mountfd-support that", " causes inability to deploy MAAS LP #2037417.", " - d/p/ubuntu/su-pty-drop-caps.patch: harden 'su --pty' to temporarily lower", " capabilities while proxying between stdin/stdout and the pty master. This", " is to avoid su from being used to exploit kernel vulnerabilities.", "" ], "package": "util-linux", "version": "2.42.2-1ubuntu1", "urgency": "medium", "distributions": "stonking", "launchpad_bugs_fixed": [ 2153369, 2125968 ], "author": "Florent 'Skia' Jacquet ", "date": "Fri, 26 Jun 2026 12:03:00 +0200" }, { "cves": [ { "cve": "CVE-2026-53612", "url": "https://ubuntu.com/security/CVE-2026-53612", "cve_description": "[Local Privilege Escalation via TOCTOU in mount(8) hook_owner.c chmod/chown]", "cve_priority": "medium", "cve_public_date": "2026-06-18" }, { "cve": "CVE-2026-53613", "url": "https://ubuntu.com/security/CVE-2026-53613", "cve_description": "[Local Privilege Escalation via TOCTOU in mount(8) - Target Path Redirection]", "cve_priority": "medium", "cve_public_date": "2026-06-18" }, { "cve": "CVE-2026-53614", "url": "https://ubuntu.com/security/CVE-2026-53614", "cve_description": "[Local Privilege Escalation via LIBMOUNT_FORCE_MOUNT2 Environment Variable - nosuid/noexec Bypass in SUID mount(8)]", "cve_priority": "medium", "cve_public_date": "2026-06-18" } ], "log": [ "", " * New upstream version, fixing security issues", " CVE-2026-53612, CVE-2026-53613, CVE-2026-53614 (Closes: #1140194,", " #1140195, #1140196)", " * Drop upstream-applied patch.", "" ], "package": "util-linux", "version": "2.42.2-1", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Wed, 17 Jun 2026 11:20:49 +0200" }, { "cves": [], "log": [ "", " * Follow debhelper 14.1, thus putting PAM files back into /etc/pam.d.", " Note that include=login is still undesirable, and packages should", " include common-* instead.", "" ], "package": "util-linux", "version": "2.42.1-6", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Tue, 16 Jun 2026 22:26:25 +0200" }, { "cves": [], "log": [ "", " * PAM config: stop using include.", " Avoid including our own PAM config files, as a workaround until PAM can", " include files from /usr/lib/pam.d.", " Should make su -(l) and runuser -l work again. See #1140029.", "" ], "package": "util-linux", "version": "2.42.1-5", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Mon, 15 Jun 2026 19:34:54 +0200" }, { "cves": [], "log": [ "", " * Update debhelper-compat to v14.", " Remove dh-sequence-installsysusers, remove ${misc:Pre-Depends} from", " Pre-Depends. PAM /etc/pam.d files are replaced by files in", " /usr/lib/pam.d.", "" ], "package": "util-linux", "version": "2.42.1-4", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Sun, 14 Jun 2026 17:28:35 +0200" }, { "cves": [], "log": [ "", " * Use upstream patch to fix FTBFS on systems with non-4K pagesizes", " (Closes: #1138789)", "" ], "package": "util-linux", "version": "2.42.1-3", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Mon, 08 Jun 2026 15:05:17 +0200" }, { "cves": [], "log": [ "", " * Fix FTBFS on systems with non-4K pagesizes (Closes: #1138789)", "" ], "package": "util-linux", "version": "2.42.1-2", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Thu, 04 Jun 2026 13:31:17 +0200" }, { "cves": [], "log": [ "", " * New upstream version", " * Refresh/drop upstream applied patches", "", " [ Karel Zak ]", " * script: fix backward compatibility for options after non-option args", " * script: fix \"--\" separator when used as option argument", " (Closes: #1132887)", "" ], "package": "util-linux", "version": "2.42.1-1", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Wed, 03 Jun 2026 20:12:19 +0200" }, { "cves": [], "log": [ "", " * Stop using Linux crypto API in hardlink(1)", "" ], "package": "util-linux", "version": "2.42-6", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Wed, 06 May 2026 20:41:22 +0200" }, { "cves": [], "log": [ "", " * Remove leftover /etc/init.d/uuidd conffile", "" ], "package": "util-linux", "version": "2.42-5", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Sun, 26 Apr 2026 14:49:42 +0200" }, { "cves": [], "log": [ "", " * Apply upstream revert of su breakage", " (Closes: #1133379, #1132588, #1132610)", "" ], "package": "util-linux", "version": "2.42-4", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Sun, 19 Apr 2026 17:36:56 +0200" }, { "cves": [], "log": [ "", " * Stop pulling deb_systemdsystemunitdir from pkg-config", " * Stop installing uuidd init script", " * Clarify /bin/login situation on Hurd", " * Install bash-completions using normal dh_install mechanism", " * Install more localized man pages", " * Simplify installing into udebs", " * Install lintian overrides into udebs", " * Run a second build without libsystemd for d-i.", " This is not great, but I see no other option at this time.", " Let's hope a libsystemd0-udeb will appear. (Closes: #1132561)", " * util-linux-extra: install copyfilerange, getino", " * Update lintian overrides", " * Update dependency libselinux1-dev to libselinux-dev", "" ], "package": "util-linux", "version": "2.42-3", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Sun, 12 Apr 2026 00:03:33 +0200" }, { "cves": [], "log": [ "", " * Add upstream patches addressing #1132887", "" ], "package": "util-linux", "version": "2.42-2", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Wed, 08 Apr 2026 18:28:21 +0200" }, { "cves": [ { "cve": "CVE-2026-27456", "url": "https://ubuntu.com/security/CVE-2026-27456", "cve_description": "util-linux is a random collection of Linux utilities. Prior to version 2.41.4, a TOCTOU (Time-of-Check-Time-of-Use) vulnerability has been identified in the SUID binary /usr/bin/mount from util-linux. The mount binary, when setting up loop devices, validates the source file path with user privileges via fork() + setuid() + realpath(), but subsequently re-canonicalizes and opens it with root privileges (euid=0) without verifying that the path has not been replaced between both operations. Neither O_NOFOLLOW, nor inode comparison, nor post-open fstat() are employed. This allows a local unprivileged user to replace the source file with a symlink pointing to any root-owned file or device during the race window, causing the SUID binary to open and mount it as root. Exploitation requires an /etc/fstab entry with user,loop options whose path points to a directory where the attacker has write permission, and that /usr/bin/mount has the SUID bit set (the default configuration on virtually all Linux distributions). The impact is unauthorized read access to root-protected files and block devices, including backup images, disk volumes, and any file containing a valid filesystem. This issue has been patched in version 2.41.4.", "cve_priority": "medium", "cve_public_date": "2026-04-03 22:16:00 UTC" } ], "log": [ "", " * New upstream release, fixing CVE-2026-27456 and a CWE-190.", " * Upload to unstable.", "" ], "package": "util-linux", "version": "2.42-1", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Thu, 02 Apr 2026 15:19:42 +0200" }, { "cves": [], "log": [ "", " * New upstream release candidate.", " * Refresh patches", "" ], "package": "util-linux", "version": "2.42~rc2-1", "urgency": "medium", "distributions": "experimental", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Thu, 26 Mar 2026 15:05:59 +0100" }, { "cves": [], "log": [ "", " * Apply upstream patches", " * Fixes unshare issue", " * Use Hurd patches directly from upstream", "" ], "package": "util-linux", "version": "2.42~rc1-3", "urgency": "medium", "distributions": "experimental", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Sun, 22 Mar 2026 15:20:19 +0100" }, { "cves": [], "log": [ "", " * Fix lsmem tests on loong64.", " Using patch from https://github.com/util-linux/util-linux/pull/4090", " * autopkgtests: switch to pkgconf", "", " [ Samuel Thibault ]", " * Fix build on Hurd", "" ], "package": "util-linux", "version": "2.42~rc1-2", "urgency": "medium", "distributions": "experimental", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Tue, 03 Mar 2026 12:43:24 +0100" }, { "cves": [ { "cve": "CVE-2026-3184", "url": "https://ubuntu.com/security/CVE-2026-3184", "cve_description": "A flaw was found in util-linux. Improper hostname canonicalization in the `login(1)` utility, when invoked with the `-h` option, can modify the supplied remote hostname before setting `PAM_RHOST`. A remote attacker could exploit this by providing a specially crafted hostname, potentially bypassing host-based Pluggable Authentication Modules (PAM) access control rules that rely on fully qualified domain names. This could lead to unauthorized access.", "cve_priority": "medium", "cve_public_date": "2026-04-03 19:17:00 UTC" } ], "log": [ "", " * New upstream release candidate.", " * includes fix for CVE-2026-3184:", " * login: use original FQDN for PAM_RHOST", " * libuuid: reset initial cont-clock time on service start (Closes:", " #1126894)", " * Symbols: use (symver) and update lists", " * Stop installing untranslated man pages", "" ], "package": "util-linux", "version": "2.42~rc1-1", "urgency": "medium", "distributions": "experimental", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Sat, 28 Feb 2026 20:37:48 +0100" }, { "cves": [], "log": [ "", " [ Chris Hofstaedtler ]", " * Follow libselinux1-dev to libselinux-dev rename (Closes: #1124751)", " * uuid-runtime: stop removing /var/run/uuidd on purge", " /run is a tmpfs, it will be cleaned up anyway. Lets us drop the postrm", " maintscript.", "", " [ Luca Boccassi ]", " * uuid-runtime: drop manual scripting in postinst and rely on sysusers.d", "" ], "package": "util-linux", "version": "2.41.3-4", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Sat, 21 Feb 2026 17:15:50 +0100" } ], "notes": null, "is_version_downgrade": false }, { "name": "login.defs", "from_version": { "source_package_name": "shadow", "source_package_version": "1:4.19.3-2ubuntu1", "version": "1:4.19.3-2ubuntu1" }, "to_version": { "source_package_name": "shadow", "source_package_version": "1:4.19.3-2ubuntu2", "version": "1:4.19.3-2ubuntu2" }, "cves": [], "launchpad_bugs_fixed": [], "changes": [ { "cves": [], "log": [ "", " * No change rebuild with debhelper 14.5ubuntu1 to drop dependency from", " passwd to systemd.", "" ], "package": "shadow", "version": "1:4.19.3-2ubuntu2", "urgency": "medium", "distributions": "stonking", "launchpad_bugs_fixed": [], "author": "Michael Hudson-Doyle ", "date": "Wed, 23 Sep 2026 10:13:29 +1200" } ], "notes": null, "is_version_downgrade": false }, { "name": "mount", "from_version": { "source_package_name": "util-linux", "source_package_version": "2.41.3-3ubuntu2", "version": "2.41.3-3ubuntu2" }, "to_version": { "source_package_name": "util-linux", "source_package_version": "2.42.2-1ubuntu2", "version": "2.42.2-1ubuntu2" }, "cves": [ { "cve": "CVE-2026-53612", "url": "https://ubuntu.com/security/CVE-2026-53612", "cve_description": "[Local Privilege Escalation via TOCTOU in mount(8) hook_owner.c chmod/chown]", "cve_priority": "medium", "cve_public_date": "2026-06-18" }, { "cve": "CVE-2026-53613", "url": "https://ubuntu.com/security/CVE-2026-53613", "cve_description": "[Local Privilege Escalation via TOCTOU in mount(8) - Target Path Redirection]", "cve_priority": "medium", "cve_public_date": "2026-06-18" }, { "cve": "CVE-2026-53614", "url": "https://ubuntu.com/security/CVE-2026-53614", "cve_description": "[Local Privilege Escalation via LIBMOUNT_FORCE_MOUNT2 Environment Variable - nosuid/noexec Bypass in SUID mount(8)]", "cve_priority": "medium", "cve_public_date": "2026-06-18" }, { "cve": "CVE-2026-27456", "url": "https://ubuntu.com/security/CVE-2026-27456", "cve_description": "util-linux is a random collection of Linux utilities. Prior to version 2.41.4, a TOCTOU (Time-of-Check-Time-of-Use) vulnerability has been identified in the SUID binary /usr/bin/mount from util-linux. The mount binary, when setting up loop devices, validates the source file path with user privileges via fork() + setuid() + realpath(), but subsequently re-canonicalizes and opens it with root privileges (euid=0) without verifying that the path has not been replaced between both operations. Neither O_NOFOLLOW, nor inode comparison, nor post-open fstat() are employed. This allows a local unprivileged user to replace the source file with a symlink pointing to any root-owned file or device during the race window, causing the SUID binary to open and mount it as root. Exploitation requires an /etc/fstab entry with user,loop options whose path points to a directory where the attacker has write permission, and that /usr/bin/mount has the SUID bit set (the default configuration on virtually all Linux distributions). The impact is unauthorized read access to root-protected files and block devices, including backup images, disk volumes, and any file containing a valid filesystem. This issue has been patched in version 2.41.4.", "cve_priority": "medium", "cve_public_date": "2026-04-03 22:16:00 UTC" }, { "cve": "CVE-2026-3184", "url": "https://ubuntu.com/security/CVE-2026-3184", "cve_description": "A flaw was found in util-linux. Improper hostname canonicalization in the `login(1)` utility, when invoked with the `-h` option, can modify the supplied remote hostname before setting `PAM_RHOST`. A remote attacker could exploit this by providing a specially crafted hostname, potentially bypassing host-based Pluggable Authentication Modules (PAM) access control rules that rely on fully qualified domain names. This could lead to unauthorized access.", "cve_priority": "medium", "cve_public_date": "2026-04-03 19:17:00 UTC" } ], "launchpad_bugs_fixed": [ 2166882, 2153369, 2125968 ], "changes": [ { "cves": [], "log": [ "", " * d/p/ubuntu/libmount-restricted-live-creds.patch: restore live-credential", " check for libmount restricted mode (LP: #2166882)", "" ], "package": "util-linux", "version": "2.42.2-1ubuntu2", "urgency": "medium", "distributions": "stonking", "launchpad_bugs_fixed": [ 2166882 ], "author": "Nadzeya Hutsko ", "date": "Wed, 16 Sep 2026 19:36:33 +0200" }, { "cves": [], "log": [ "", " * Merge with Debian unstable (LP: #2153369).", " Added changes:", " - tests/fincore: force the use of GNU dd over uutils (LP: #2125968)", " Remaining changes:", " - Add sulogin-fallback-static-sh.patch", " Add support for /bin/static-sh as fallback if the regular shell fails to", " execute. Patch ported from sysvinit. (see LP #505887)", " - Add sulogin-lockedpwd.patch", " Make sure file systems can be fixed on machines with locked root", " accounts (as Ubuntu does by default). Don't require --force for sulogin.", " - d/rules: disable libmount mountfs support", " Disable brand new feature with --disable-libmount-mountfd-support that", " causes inability to deploy MAAS LP #2037417.", " - d/p/ubuntu/su-pty-drop-caps.patch: harden 'su --pty' to temporarily lower", " capabilities while proxying between stdin/stdout and the pty master. This", " is to avoid su from being used to exploit kernel vulnerabilities.", "" ], "package": "util-linux", "version": "2.42.2-1ubuntu1", "urgency": "medium", "distributions": "stonking", "launchpad_bugs_fixed": [ 2153369, 2125968 ], "author": "Florent 'Skia' Jacquet ", "date": "Fri, 26 Jun 2026 12:03:00 +0200" }, { "cves": [ { "cve": "CVE-2026-53612", "url": "https://ubuntu.com/security/CVE-2026-53612", "cve_description": "[Local Privilege Escalation via TOCTOU in mount(8) hook_owner.c chmod/chown]", "cve_priority": "medium", "cve_public_date": "2026-06-18" }, { "cve": "CVE-2026-53613", "url": "https://ubuntu.com/security/CVE-2026-53613", "cve_description": "[Local Privilege Escalation via TOCTOU in mount(8) - Target Path Redirection]", "cve_priority": "medium", "cve_public_date": "2026-06-18" }, { "cve": "CVE-2026-53614", "url": "https://ubuntu.com/security/CVE-2026-53614", "cve_description": "[Local Privilege Escalation via LIBMOUNT_FORCE_MOUNT2 Environment Variable - nosuid/noexec Bypass in SUID mount(8)]", "cve_priority": "medium", "cve_public_date": "2026-06-18" } ], "log": [ "", " * New upstream version, fixing security issues", " CVE-2026-53612, CVE-2026-53613, CVE-2026-53614 (Closes: #1140194,", " #1140195, #1140196)", " * Drop upstream-applied patch.", "" ], "package": "util-linux", "version": "2.42.2-1", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Wed, 17 Jun 2026 11:20:49 +0200" }, { "cves": [], "log": [ "", " * Follow debhelper 14.1, thus putting PAM files back into /etc/pam.d.", " Note that include=login is still undesirable, and packages should", " include common-* instead.", "" ], "package": "util-linux", "version": "2.42.1-6", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Tue, 16 Jun 2026 22:26:25 +0200" }, { "cves": [], "log": [ "", " * PAM config: stop using include.", " Avoid including our own PAM config files, as a workaround until PAM can", " include files from /usr/lib/pam.d.", " Should make su -(l) and runuser -l work again. See #1140029.", "" ], "package": "util-linux", "version": "2.42.1-5", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Mon, 15 Jun 2026 19:34:54 +0200" }, { "cves": [], "log": [ "", " * Update debhelper-compat to v14.", " Remove dh-sequence-installsysusers, remove ${misc:Pre-Depends} from", " Pre-Depends. PAM /etc/pam.d files are replaced by files in", " /usr/lib/pam.d.", "" ], "package": "util-linux", "version": "2.42.1-4", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Sun, 14 Jun 2026 17:28:35 +0200" }, { "cves": [], "log": [ "", " * Use upstream patch to fix FTBFS on systems with non-4K pagesizes", " (Closes: #1138789)", "" ], "package": "util-linux", "version": "2.42.1-3", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Mon, 08 Jun 2026 15:05:17 +0200" }, { "cves": [], "log": [ "", " * Fix FTBFS on systems with non-4K pagesizes (Closes: #1138789)", "" ], "package": "util-linux", "version": "2.42.1-2", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Thu, 04 Jun 2026 13:31:17 +0200" }, { "cves": [], "log": [ "", " * New upstream version", " * Refresh/drop upstream applied patches", "", " [ Karel Zak ]", " * script: fix backward compatibility for options after non-option args", " * script: fix \"--\" separator when used as option argument", " (Closes: #1132887)", "" ], "package": "util-linux", "version": "2.42.1-1", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Wed, 03 Jun 2026 20:12:19 +0200" }, { "cves": [], "log": [ "", " * Stop using Linux crypto API in hardlink(1)", "" ], "package": "util-linux", "version": "2.42-6", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Wed, 06 May 2026 20:41:22 +0200" }, { "cves": [], "log": [ "", " * Remove leftover /etc/init.d/uuidd conffile", "" ], "package": "util-linux", "version": "2.42-5", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Sun, 26 Apr 2026 14:49:42 +0200" }, { "cves": [], "log": [ "", " * Apply upstream revert of su breakage", " (Closes: #1133379, #1132588, #1132610)", "" ], "package": "util-linux", "version": "2.42-4", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Sun, 19 Apr 2026 17:36:56 +0200" }, { "cves": [], "log": [ "", " * Stop pulling deb_systemdsystemunitdir from pkg-config", " * Stop installing uuidd init script", " * Clarify /bin/login situation on Hurd", " * Install bash-completions using normal dh_install mechanism", " * Install more localized man pages", " * Simplify installing into udebs", " * Install lintian overrides into udebs", " * Run a second build without libsystemd for d-i.", " This is not great, but I see no other option at this time.", " Let's hope a libsystemd0-udeb will appear. (Closes: #1132561)", " * util-linux-extra: install copyfilerange, getino", " * Update lintian overrides", " * Update dependency libselinux1-dev to libselinux-dev", "" ], "package": "util-linux", "version": "2.42-3", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Sun, 12 Apr 2026 00:03:33 +0200" }, { "cves": [], "log": [ "", " * Add upstream patches addressing #1132887", "" ], "package": "util-linux", "version": "2.42-2", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Wed, 08 Apr 2026 18:28:21 +0200" }, { "cves": [ { "cve": "CVE-2026-27456", "url": "https://ubuntu.com/security/CVE-2026-27456", "cve_description": "util-linux is a random collection of Linux utilities. Prior to version 2.41.4, a TOCTOU (Time-of-Check-Time-of-Use) vulnerability has been identified in the SUID binary /usr/bin/mount from util-linux. The mount binary, when setting up loop devices, validates the source file path with user privileges via fork() + setuid() + realpath(), but subsequently re-canonicalizes and opens it with root privileges (euid=0) without verifying that the path has not been replaced between both operations. Neither O_NOFOLLOW, nor inode comparison, nor post-open fstat() are employed. This allows a local unprivileged user to replace the source file with a symlink pointing to any root-owned file or device during the race window, causing the SUID binary to open and mount it as root. Exploitation requires an /etc/fstab entry with user,loop options whose path points to a directory where the attacker has write permission, and that /usr/bin/mount has the SUID bit set (the default configuration on virtually all Linux distributions). The impact is unauthorized read access to root-protected files and block devices, including backup images, disk volumes, and any file containing a valid filesystem. This issue has been patched in version 2.41.4.", "cve_priority": "medium", "cve_public_date": "2026-04-03 22:16:00 UTC" } ], "log": [ "", " * New upstream release, fixing CVE-2026-27456 and a CWE-190.", " * Upload to unstable.", "" ], "package": "util-linux", "version": "2.42-1", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Thu, 02 Apr 2026 15:19:42 +0200" }, { "cves": [], "log": [ "", " * New upstream release candidate.", " * Refresh patches", "" ], "package": "util-linux", "version": "2.42~rc2-1", "urgency": "medium", "distributions": "experimental", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Thu, 26 Mar 2026 15:05:59 +0100" }, { "cves": [], "log": [ "", " * Apply upstream patches", " * Fixes unshare issue", " * Use Hurd patches directly from upstream", "" ], "package": "util-linux", "version": "2.42~rc1-3", "urgency": "medium", "distributions": "experimental", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Sun, 22 Mar 2026 15:20:19 +0100" }, { "cves": [], "log": [ "", " * Fix lsmem tests on loong64.", " Using patch from https://github.com/util-linux/util-linux/pull/4090", " * autopkgtests: switch to pkgconf", "", " [ Samuel Thibault ]", " * Fix build on Hurd", "" ], "package": "util-linux", "version": "2.42~rc1-2", "urgency": "medium", "distributions": "experimental", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Tue, 03 Mar 2026 12:43:24 +0100" }, { "cves": [ { "cve": "CVE-2026-3184", "url": "https://ubuntu.com/security/CVE-2026-3184", "cve_description": "A flaw was found in util-linux. Improper hostname canonicalization in the `login(1)` utility, when invoked with the `-h` option, can modify the supplied remote hostname before setting `PAM_RHOST`. A remote attacker could exploit this by providing a specially crafted hostname, potentially bypassing host-based Pluggable Authentication Modules (PAM) access control rules that rely on fully qualified domain names. This could lead to unauthorized access.", "cve_priority": "medium", "cve_public_date": "2026-04-03 19:17:00 UTC" } ], "log": [ "", " * New upstream release candidate.", " * includes fix for CVE-2026-3184:", " * login: use original FQDN for PAM_RHOST", " * libuuid: reset initial cont-clock time on service start (Closes:", " #1126894)", " * Symbols: use (symver) and update lists", " * Stop installing untranslated man pages", "" ], "package": "util-linux", "version": "2.42~rc1-1", "urgency": "medium", "distributions": "experimental", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Sat, 28 Feb 2026 20:37:48 +0100" }, { "cves": [], "log": [ "", " [ Chris Hofstaedtler ]", " * Follow libselinux1-dev to libselinux-dev rename (Closes: #1124751)", " * uuid-runtime: stop removing /var/run/uuidd on purge", " /run is a tmpfs, it will be cleaned up anyway. Lets us drop the postrm", " maintscript.", "", " [ Luca Boccassi ]", " * uuid-runtime: drop manual scripting in postinst and rely on sysusers.d", "" ], "package": "util-linux", "version": "2.41.3-4", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Sat, 21 Feb 2026 17:15:50 +0100" } ], "notes": null, "is_version_downgrade": false }, { "name": "netplan-generator", "from_version": { "source_package_name": "netplan.io", "source_package_version": "1.2.2-1", "version": "1.2.2-1" }, "to_version": { "source_package_name": "netplan.io", "source_package_version": "1.2.2-3", "version": "1.2.2-3" }, "cves": [], "launchpad_bugs_fixed": [], "changes": [ { "cves": [], "log": [ "", " [ Grayson Wolf ]", " * d/p/lp2168838-ovs-test.patch: Fix autopkgtests on ovs 4 (Closes: #1149299)", "" ], "package": "netplan.io", "version": "1.2.2-3", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Lukas Märdian ", "date": "Wed, 30 Sep 2026 20:59:16 +0200" }, { "cves": [], "log": [ "", " * d/t/prep-testbed: Remove LXC quirks (Closes: #1144818)", " which are not needed for incus-lxc anymore.", "" ], "package": "netplan.io", "version": "1.2.2-2", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Lukas Märdian ", "date": "Thu, 27 Aug 2026 18:12:25 +0200" } ], "notes": null, "is_version_downgrade": false }, { "name": "netplan.io", "from_version": { "source_package_name": "netplan.io", "source_package_version": "1.2.2-1", "version": "1.2.2-1" }, "to_version": { "source_package_name": "netplan.io", "source_package_version": "1.2.2-3", "version": "1.2.2-3" }, "cves": [], "launchpad_bugs_fixed": [], "changes": [ { "cves": [], "log": [ "", " [ Grayson Wolf ]", " * d/p/lp2168838-ovs-test.patch: Fix autopkgtests on ovs 4 (Closes: #1149299)", "" ], "package": "netplan.io", "version": "1.2.2-3", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Lukas Märdian ", "date": "Wed, 30 Sep 2026 20:59:16 +0200" }, { "cves": [], "log": [ "", " * d/t/prep-testbed: Remove LXC quirks (Closes: #1144818)", " which are not needed for incus-lxc anymore.", "" ], "package": "netplan.io", "version": "1.2.2-2", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Lukas Märdian ", "date": "Thu, 27 Aug 2026 18:12:25 +0200" } ], "notes": null, "is_version_downgrade": false }, { "name": "openssl", "from_version": { "source_package_name": "openssl", "source_package_version": "4.0.1-1ubuntu4", "version": "4.0.1-1ubuntu4" }, "to_version": { "source_package_name": "openssl", "source_package_version": "4.0.3-1ubuntu1", "version": "4.0.3-1ubuntu1" }, "cves": [ { "cve": "CVE-2026-84782", "url": "https://ubuntu.com/security/CVE-2026-84782", "cve_description": "Issue summary: The DTLS retransmission logic does not correctly handle a handshake message write that is suspended part-way through. The retransmitted message can be read past the message buffer and the retransmission overwrites the internal state the suspended write needs to resume correctly. Impact summary: The retransmitted message can disclose a heap memory to the peer as plaintext handshake data or cause a crash and a Denial of Service when the read reaches an unmapped memory region. CWE: CWE-125: Out-of-bounds Read Description: DTLS handshake messages can be written out in multiple fragments, and a write can suspend mid-message (returning WANT_WRITE) if the underlying transport temporarily cannot accept more data. While such a write is suspended, the DTLS retransmission timer may independently fire and ask the retransmission logic to resend an earlier, already-acknowledged-as-sent message from its retransmit queue. The retransmission logic reused the same internal buffer and position tracking as the message that was still being written, without resetting the position back to the start of the message being retransmitted. As a result the retransmission was read starting from wherever the suspended write had left off, producing a mislabelled message whose body was leftover bytes from the other, larger message still in flight - content that was never meant to be sent at that point, and which could run past the end of the allocated buffer. Separately, even when the retransmission is positioned correctly, allowing it to run to completion while another write is suspended overwrites the same shared bookkeeping that the suspended write depends on to resume. When the application later resumes the suspended write (via a subsequent SSL_read(), SSL_write(), SSL_accept(), or SSL_connect() call), it finds that bookkeeping in a state inconsistent with the message and aborts the process in a debugging build. The fix resets the retransmission's read position to the start of the message before resending, and skips retransmission entirely whenever a handshake write is still suspended, deferring to the next call that resumes it instead. FIPS impact: no The affected code is outside the FIPS module boundary.", "cve_priority": "high", "cve_public_date": "2026-09-29 16:17:00 UTC" }, { "cve": "CVE-2026-35189", "url": "https://ubuntu.com/security/CVE-2026-35189", "cve_description": "Issue summary: A certificate with many nameRelativeToCRLIssuer CRL distribution points causes disproportionate heap growth when OpenSSL caches X.509 extensions. Impact summary: Receiving a crafted certificate from a malicious peer can lead to significant memory pressure and possible Denial of Service in clients or in servers that solicit client certificates. CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: A certificate or a set of certificates that fits under the limit for size of certificates accepted from the peer (~100 KiB) can result in allocation of several hundred MiB of resident memory on the receiving side during a normal TLS handshake. This may be enough to crash the client or server, if multiple concurrent connections lead to similarly large memory allocations. The fix postpones processing of the CRL distribution points extensions in certificates to the time when the processed value is required for CRL processing. This avoids keeping large memory allocations for a long time when such certificates are received. FIPS impact: no The affected code is outside the FIPS module boundary.", "cve_priority": "low", "cve_public_date": "2026-09-29 16:17:00 UTC" }, { "cve": "CVE-2026-35191", "url": "https://ubuntu.com/security/CVE-2026-35191", "cve_description": "Issue summary: The OpenSSL QUIC server, when configured to not preform address validation, can be forced to count incoming packets multiple times in its unvalidated credit computation, leading to a violation of the RFC 9000 unvalidated connection amplification limit of 3 times the amount of data received. Impact summary: A remote attacker able to spoof packets to a server using the OpenSSL QUIC implementation might use the server for an amplification of a DDoS attack. CWE: CWE-440: Expected Behavior Violation Description: OpenSSL's QUIC stack, when operating as a server, enforces client address validation (RFC 9000, Section 8), to confirm the peer address is not used for a traffic amplification attack. If this feature is disabled on the server, the QUIC stack limits the amount of server data that can be sent to 3 times the amount of data received from the peer address, until such time as the TLS handshake is completed. The OpenSSL QUIC server, when operating in non-validation mode, adds the length of the whole datagram received to the unvalidated credit limit when processing each QUIC packet in the datagram. A remote peer may, after establishing a connection with an initial client hello frame, send a subsequent datagram containing multiple QUIC packets, leading the server to account the entire datagram length for each packet in the datagram, resulting in the server believing that the peer has sent more data than it actually has, thereby violating the 3x amplification limit mandated by the RFC. FIPS impact: no As the QUIC stack lives outside the FIPS module boundary, no FIPS modules are affected by this CVE.", "cve_priority": "low", "cve_public_date": "2026-09-29 16:17:00 UTC" }, { "cve": "CVE-2026-42772", "url": "https://ubuntu.com/security/CVE-2026-42772", "cve_description": "Issue summary: The QUIC stream reassembly algorithm performance deteriorates progressively as packets are arriving out of order. The worst case has a quadratic complexity proportional to the number of stream frames kept in the buffer for the received stream data. Impact summary: A remote QUIC peer that completes the handshake can create a connection-scoped CPU pressure and potentially a Denial of Service using compliant STREAM frames inside the advertised receive window, with low attacker bandwidth. CWE: CWE-407: Inefficient Algorithmic Complexity Description: OpenSSL manages received QUIC stream fragments using a doubly-linked list. While it optimizes for append operations (at the end of the list), it falls back to a head-to-tail linear search for any fragment that does not immediately follow the current `tail`. By manipulating the sequence of offsets, an attacker can force the server to perform O(n^2) operations, consuming excessive CPU time for the QUIC process. FIPS impact: no The FIPS module is not affected as the QUIC implementation is outside of the OpenSSL FIPS module boundary.", "cve_priority": "low", "cve_public_date": "2026-09-29 16:17:00 UTC" }, { "cve": "CVE-2026-54872", "url": "https://ubuntu.com/security/CVE-2026-54872", "cve_description": "Issue summary: The generic elliptic-curve scalar multiplication used for ECDSA and SM2 signature operations with curves that do not have a dedicated implementation leaks information about the secret nonce through timing. Impact summary: An attacker able to measure signing times may learn information about the per-signature secret nonce, which over many signatures can, via a lattice / Hidden Number Problem attack, lead to recovery of the private key. CWE: CWE-208: Observable Timing Discrepancy Description: The generic elliptic-curve scalar multiplication used for curves that do not have a dedicated constant-time implementation pads the secret scalar with non-constant-time BIGNUM operations, so the time taken depends on the value of the secret scalar derived from the ECDSA and SM2 nonce. The leak is very small; observing it requires a large number of measurements. The effect is largest for curves whose group order lies on a machine-word boundary, such as brainpoolP384r1. Applications using ECDSA signing over the Brainpool and other generic prime curves, and SM2 signing on platforms that use the generic implementation, are vulnerable to this issue. The NIST curves P-256, P-384 and P-521 use dedicated constant-time implementations and are not affected. FIPS Impact: no The FIPS modules are not affected: the approved NIST curves used in the FIPS provider have dedicated constant-time implementations and do not use the affected code path.", "cve_priority": "low", "cve_public_date": "2026-09-29 16:17:00 UTC" }, { "cve": "CVE-2026-54873", "url": "https://ubuntu.com/security/CVE-2026-54873", "cve_description": "Issue summary: QUIC process may keep memory for QUIC packet buffer for much longer period than necessary. Impact summary: Remote peer can exploit this vulnerability by sending maliciously crafted packets, making the local QUIC stack to keep the memory for packet buffers allocated. The time for which the memory remains allocated is entirely under the control of the potentially malicious remote peer. CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: To save copy operation from the packet buffer to the stream reassemble buffer the QUIC stack leaves the stream data on the packet buffer waiting to be copied to a buffer provided by the local receiving application. The QUIC stack releases a reference to the packet buffer only after the data are copied to the application buffer. This design is more efficient for legitimate data transfers but enables an attacker to allocate a lot more memory than actually required by the data kept in the receiving stream buffer. To mitigate the vulnerability, the QUIC stack now calculates and monitors memory overhead for every stream. The memory overhead for a single stream frame is calculated as a difference between the size of the whole packet that carries the stream frame and the size of the stream frame itself. The memory overhead for a single stream frame is added to the total (cumulative) memory overhead QUIC stack keeps for each stream. Once the cumulative memory overhead exceeds 64kB, the QUIC stack moves the stream frame data from the packet buffer to the stream buffer, starting with the next packet received. FIPS impact: no The FIPS module is not affected as the QUIC implementation is outside of the OpenSSL FIPS module boundary.", "cve_priority": "low", "cve_public_date": "2026-09-29 16:17:00 UTC" }, { "cve": "CVE-2026-54875", "url": "https://ubuntu.com/security/CVE-2026-54875", "cve_description": "Issue summary: A non-constant-time optimized implementation of scalar point multiplication is used for SM2 private key operations on ARM64 and RISC-V platforms. Impact summary: An attacker able to measure the time taken by, or to observe the cache-line access pattern of SM2 signing or decryption on an affected platform can learn information about the secret scalar. CWE: CWE-208: Observable Timing Discrepancy Description: On ARM64 and RISC-V processors, the SM2 curve uses an optimized scalar multiplication implementation whose conditional branches and table look ups are chosen according to the bits of the secret scalar. The execution time and the cache-access pattern therefore depend on the long-term private key (during SM2 decryption) or the per-signature nonce (during SM2 signature generation), forming a timing and cache side-channel. FIPS Impact: no SM2 is not a FIPS algorithm and the optimized SM2 implementation is not part of the FIPS module. OpenSSL 4.0, 3.6, 3.5 and 3.4 are vulnerable to this issue on AArch64 and RISC-V. OpenSSL 3.0, 1.1.1 and 1.0.2 are not affected by this issue. OpenSSL 4.0 users should upgrade to OpenSSL 4.0.3. OpenSSL 3.6 users should upgrade to OpenSSL 3.6.5. OpenSSL 3.5 users should upgrade to OpenSSL 3.5.9. OpenSSL 3.4 users should upgrade to OpenSSL 3.4.8. This issue was reported on 2 May 2026 by Abhinav Agarwal. It was independently reported on 6 June 2026 by Feng Xue. The fix was developed by Igor Ustinov. -- cut (non-publishing metadata for internal use) -- Reported by: Abhinav Agarwal, Feng Xue Fixed by: Igor Ustinov", "cve_priority": "low", "cve_public_date": "2026-09-29 16:17:00 UTC" }, { "cve": "CVE-2026-72897", "url": "https://ubuntu.com/security/CVE-2026-72897", "cve_description": "Issue summary: A TLS server that calls SSL_set_SSL_CTX() to switch a connection to a different SSL_CTX part way through a handshake may access memory beyond the end of an internal array if the replacement context knows about more provider signature algorithms than the context the connection was created from. Applications which never call SSL_set_SSL_CTX() are not affected. Impact summary: A remote peer may be able to cause a small out-of-bounds read, and in some circumstances a fixed-value out-of-bounds write, on the server heap. This may lead to a Denial of Service. CWE: CWE-787: Out-of-bounds Write Description: A TLS connection records how many certificate slots it has when it is created, taken from the SSL_CTX that created it: the built-in certificate types plus one slot for each provider TLS-SIGALG entry that context was aware of. That count sizes an internal array of per-slot certificate validity flags. An application may replace a connection's SSL_CTX part way through the handshake by calling SSL_set_SSL_CTX(), most commonly from a servername callback in order to serve a different virtual host. Doing so did not refresh the recorded count. A provider signature algorithm's slot index is its position in the list of whichever context resolves it, so if the replacement context is aware of more of them than the original, an algorithm offered by the peer can resolve to an index beyond the end of the array. Processing the peer's signature algorithms then reads one four byte word past the end for each such algorithm and, where the word read is zero, writes a fixed value over it. A peer offering many of them can corrupt heap metadata and abort the process. Only provider signature algorithms which occupy one of the excess slots, and which the server also has configured, have this effect. Codepoints the replacement context does not recognise are discarded without being resolved to a slot, and provider signature algorithms are usable only from TLS 1.3. The two contexts must therefore be aware of different numbers of provider signature algorithms, which requires separate library contexts, a provider loaded between the two being created, or providers which differ in what they advertise - in 4.0, for example, the default provider advertises SM2 where the FIPS provider does not. A deployment meeting the condition is also unable to negotiate the affected algorithms with legitimate clients, since the same stale count hides the corresponding certificates, so the misconfiguration is likely to be noticed. For that reason, and because the configuration is not the default, this issue has been assessed as Low severity. FIPS impact: no No FIPS modules are affected by this issue as the affected code is outside the OpenSSL FIPS module boundary.", "cve_priority": "low", "cve_public_date": "2026-09-29 16:17:00 UTC" }, { "cve": "CVE-2026-75804", "url": "https://ubuntu.com/security/CVE-2026-75804", "cve_description": "Issue summary: OpenSSL QUIC stack does not enforce connection level flow control for streams. Remote peers may send more bytes as long as they fit within the stream flow control limits. Impact summary: A malicious remote peer may exploit the lack of connection flow control for streams to make the QUIC stack receive ~100MB of memory instead of 768 KiB (default flow control window size). CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: The local QUIC stack advertises two flow control limits to its remote peer: stream flow control limit and connection flow control limit. The remote peer must follow both limits when transmitting stream data. Whenever the local QUIC stack receives a stream frame, it validates that the size of the received stream frame stays within flow control limits. If either limit is exceeded (stream level or connection level), then the QUIC stack must close the connection with a flow control error. The vulnerable OpenSSL QUIC stack enforces the stream-level but not the connection-level limit. To exploit the issue, three conditions must be met: - the remote peer opens several streams - each stream must stay within the stream-level flow control limit - there must be no zero-offset byte sent on any of the streams (to prevent the vulnerable QUIC stack from consuming data). By meeting the conditions above, the remote peer may make the local stack allocate 2 x MAX_STREAMS x (stream flow control limit) bytes of memory. MAX_STREAMS defaults to 100, and the limit applies to both bidirectional and unidirectional streams, making it 200 in total. The default flow control window for a stream is 512kB. The remote peer may force the vulnerable QUIC stack to allocate 100MB of heap per connection. FIPS impact: no The FIPS module is not affected as the QUIC implementation is outside of the OpenSSL FIPS module boundary.", "cve_priority": "low", "cve_public_date": "2026-09-29 16:17:00 UTC" }, { "cve": "CVE-2026-75805", "url": "https://ubuntu.com/security/CVE-2026-75805", "cve_description": "Issue summary: A CMP client that requests certificate revocation on the basis of a PKCS#10 CSR may dereference a NULL pointer and terminate abnormally when processing a crafted revocation response. Impact summary: The NULL pointer dereference happens on a read which leads to a crash and a Denial of Service for the affected client application. CWE: CWE-476: NULL-pointer dereference Description: A CMP client revoking a certificate has to tell the server which certificate to revoke, and may do so by supplying a PKCS#10 CSR instead of the certificate itself or its issuer name and serial number. This is 'openssl cmp -cmd rr -csr ' on the command line, or OSSL_CMP_exec_RR_ses() with the certificate supplied via OSSL_CMP_CTX_set1_p10CSR() through the API. A CSR does not contain the issuer name and serial number of the certificate, so the client does not send them. A server may optionally name the certificate it revoked in its response, and the client then compares that name against what it sent. Having sent neither an issuer name nor a serial number, it has nothing to compare against, and a server returning a specially crafted name causes the client to read from a NULL pointer and crash. The revocation response is checked for valid message protection before the affected code is reached, so an attacker must be a malicious or compromised CMP server, or a man-in-the-middle in possession of the secret used for message protection. Clients that identify the certificate to be revoked by a certificate or by issuer and serial number rather than by a PKCS#10 CSR are not affected. FIPS impact: no No FIPS modules are affected by this issue, as the CMP protocol implementation is outside the OpenSSL FIPS module boundary.", "cve_priority": "low", "cve_public_date": "2026-09-29 16:17:00 UTC" }, { "cve": "CVE-2026-75806", "url": "https://ubuntu.com/security/CVE-2026-75806", "cve_description": "Issue summary: An established DTLS 1.2 association using an AEAD cipher suite can be terminated by a single unauthenticated datagram whose encrypted fragment is shorter than the mandatory explicit IV and authentication tag overhead. Impact summary: An attacker who can send a datagram that is routed to an existing DTLS 1.2 association can tear that association down without knowing any key material. This is a Denial of Service limited to the targeted association. There is no memory safety or confidentiality impact. CWE: CWE-1284: Improper Validation of Specified Quantity in Input Description: In TLS 1.2 and DTLS 1.2 every record protected by an AEAD cipher suite carries an explicit IV followed by the ciphertext and an authentication tag. When decrypting such a record the record layer passed the record length to the cipher implementation before checking that the record was long enough to contain the explicit IV and the tag. For a record shorter than that overhead the cipher implementation rejected the impossible length, and the record layer treated this as an internal failure and raised a fatal internal_error alert instead of treating the record as one that failed authentication. In TLS 1.2 the same record causes a fatal internal_error alert instead of the expected bad_record_mac alert. Since any undecryptable record already terminates a TLS connection, this is a protocol conformance issue rather than a security issue in TLS. The fix validates the record length against the explicit IV and tag length before any AEAD processing, so that TLS reports bad_record_mac and DTLS silently discards the record. FIPS impact: no The affected code is outside the FIPS module boundary.", "cve_priority": "low", "cve_public_date": "2026-09-29 16:17:00 UTC" }, { "cve": "CVE-2026-77696", "url": "https://ubuntu.com/security/CVE-2026-77696", "cve_description": "Issue summary: SM2 signature generation uses non-constant-time arithmetic on secret values, forming a timing side-channel. Impact summary: An attacker able to measure SM2 signing times may learn information about the per-signature secret nonce, which over many signatures can, via a lattice / Hidden Number Problem attack, lead to recovery of the private key. CWE: CWE-208: Observable Timing Discrepancy Description: SM2 signature generation computes the signature value using variable-time BIGNUM operations on the secret nonce and the private key, so the time taken to produce an SM2 signature depends on these secret values, forming a timing side-channel. Applications performing SM2 signature generation are affected on all platforms. FIPS Impact: no SM2 is not a FIPS algorithm.", "cve_priority": "low", "cve_public_date": "2026-09-29 16:17:00 UTC" }, { "cve": "CVE-2026-84783", "url": "https://ubuntu.com/security/CVE-2026-84783", "cve_description": "Issue summary: The first concurrent use of the same X.509 certificate by several threads may cause its cached extension data to be freed while another thread is still using it. Impact summary: A remote, unauthenticated peer could crash a multi-threaded TLS client, or a multi-threaded TLS server that requests client certificates, if the first certificate chains built to the same trusted CA certificate are built by several connections at the same time. This is a use-after-free read, which is likely to crash the process, resulting in a Denial of Service. CWE: CWE-416: Use After Free Description: OpenSSL caches the decoded values of a certificate's X.509v3 extensions inside the X509 object the first time they are needed. In OpenSSL 4.0 this cache is built in two phases: the extension values are computed while holding a read lock on the certificate, and the results are then installed into the certificate under a write lock. Because a read lock does not exclude other readers, several threads can compute the cache for the same certificate at the same time. Each thread that subsequently acquires the write lock installs its own results and frees the values installed by the thread before it, even though that earlier thread has already marked the cache as complete and may have returned pointers into it to its caller. A caller still using those pointers then reads freed memory. Any certificate shared between threads is exposed the first time its extensions are decoded. In TLS the certificates at risk are the trusted CA certificates supplied for chain verification, by whatever means, since these are shared by every connection and their extensions are decoded and cached the first time a chain is built to them. Certificates sent by the peer are decoded separately for each connection and are not shared, so they are not affected. In a TLS client verifying server certificates, or a TLS server that requests and verifies client certificates, the use-after-free could only occur if the first chains built to the same trusted CA are built by several connections at the same time. FIPS impact: no The FIPS module is not affected as X.509 certificate handling is outside of the OpenSSL FIPS module boundary. OpenSSL 4.0 is vulnerable to this issue. OpenSSL 3.6, 3.5, 3.4, 3.0, 1.1.1 and 1.0.2 are not affected by this issue. OpenSSL 4.0 users should upgrade to OpenSSL 4.0.3. This issue was reported on 27 August 2026 by Tim Becker (Xint.io) and independently in a public report on 31 August 2026 by aydinmercan. The fix has been developed by Bob Beck. -- cut (non-publishing metadata for internal use) -- Reported by: Tim Becker (Xint.io), aydinmercan Fixed by: Bob Beck", "cve_priority": "medium", "cve_public_date": "2026-09-29 16:17:00 UTC" }, { "cve": "CVE-2026-84784", "url": "https://ubuntu.com/security/CVE-2026-84784", "cve_description": "Issue summary: A malicious remote peer may flood the local QUIC stack with NEW_CONNECTION_ID frames by avoiding a limit check on how many connection IDs the remote QUIC stack can use. Impact summary: The local QUIC stack sends a RETIRE_CONN_ID frame for every NEW_CONNECTION_ID frame it receives. The RETIRE_CONN_ID frame is dispatched via the Control Frame Queue (CFQ). If the remote peer also withholds ACKs, then it can force the local stack to allocate ~400MB (depending on ACK delay). CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: RFC 9000 sections 5.1.1 and 5.1.2 [1] describe the mechanism by which a remote peer can notify the local QUIC stack to change the destination connection ID (a.k.a. CID) the local stack uses to identify the connection at the remote peer. Each CID is associated with a sequence number. The sequence number is transmitted in NEW_CONNECTION_ID and RETIRE_CONNECTION_ID frames to identify the CID which is being either associated with a connection or retired. The remote peer sends a NEW_CONNECTION_ID frame to let the local stack know a new CID is being associated with an existing connection. The NEW_CONNECTION_ID frame carries the new CID, its sequence number, and the retire-prior-to number. The retire-prior-to identifies existing CIDs that are to be retired. The local QUIC stack must send a RETIRE_CONNECTION_ID for every destination CID whose sequence number is less than retire-prior-to. The CID becomes retired after the local stack receives an ACK for its RETIRE_CONNECTION_ID frame. Although the OpenSSL QUIC stack supports at most one destination CID for every connection, it can be tricked into processing more than one RETIRE_CONNECTION_ID frame per connection. The OpenSSL QUIC stack currently retires the destination CID as soon as it receives the NEW_CONNECTION_ID, while in fact the destination CID must be retired after an ACK for the RETIRE_CONNECTION_ID frame is received. Correcting the flawed logic also fixes the backlog growth. [1] https://datatracker.ietf.org/doc/html/rfc9000#name-issuing-connection-ids FIPS impact: no The FIPS module is not affected as the QUIC implementation is outside of the OpenSSL FIPS module boundary.", "cve_priority": "low", "cve_public_date": "2026-09-29 16:17:00 UTC" }, { "cve": "CVE-2026-18798", "url": "https://ubuntu.com/security/CVE-2026-18798", "cve_description": "Issue summary: QUIC server may double free QRX (QUIC record layer RX) object when channel creation fails for initial packet. Impact summary: Double free leads to heap corruption, which typically results in termination of QUIC server process, leading to Denial of Service. There is so far no evidence that this double free is exploitable for remote code execution, thus it is considered highly improbable. CWE: CWE-415: Double Free Description: In order to validate initial packet, OpenSSL QUIC stack default packet handler (port_default_packet_handler()) creates a so-called QRX object. If the initial packet validates successfully with QRX object, the default packet handler proceeds to channel (connection object) creation. The QRX object used for packet validation is passed to port_bind_channel(), so it becomes part of the newly created connection. If port_bind_channel() fails, then it also frees the QRX object. Once port_bind_channel() returns, the port_default_packet_handler() detects the failure and proceeds to the error branch, where the same QRX object is freed for the second time. The failure in port_bind_channel() function can be induced with a relatively low effort by a malformed (non RFC 9000 compliant) INITIAL packet. If the packet carries DCID (destination connection ID) which is shorter than 8 bytes, then port_bind_channel() jumps to the error path after ossl_quic_lcidm_enrol_odcid() detects that the DCID has invalid length. FIPS impact: no The FIPS module is not affected, as the QUIC implementation is outside of the OpenSSL FIPS module boundary.", "cve_priority": "medium", "cve_public_date": "2026-08-25 13:17:00 UTC" }, { "cve": "CVE-2026-63072", "url": "https://ubuntu.com/security/CVE-2026-63072", "cve_description": "Issue summary: OpenSSL CMS decryption sizes the key-unwrap output buffer based on querying the unwrapped key size, but the AES-WRAP-PAD unwrap primitive can write and cleanse more bytes than that query reports, causing an 8-byte out-of-bounds heap write. Impact summary: An attacker who supplies a crafted CMS message can trigger a deterministic 8-byte out-of-bounds heap write when the victim decrypts it with CMS_decrypt(), corrupting the heap and typically resulting in a Denial of Service. CWE: CWE-787: Out-of-bounds Write Description: The key-wrap OID is potentially attacker-controlled on the wire. CMS unwrapping allows both id-aesNNN-wrap-pad and id-aesNNN-wrap ciphers. An attacker can take a legitimate message and change a single OID byte to select the padded variant while leaving the message otherwise valid. Since the unwrap key is derived from the recipient's private operation (ECDH key agreement or ML-KEM decapsulation), the RFC 5649 integrity check cannot pass, and the decryption fails with integrity failure. The write is a fixed-size (8-byte), fixed-value (zero) heap overflow immediately past the allocation, requires no special configuration, and is reachable from the public CMS_decrypt() function. The consequence is a heap corruption leading to a Denial of Service. The fix in the CMS code sizes the unwrap output buffer for the worst case so a failed unwrap cannot write past the allocation. FIPS impact: no As the CMS code lives outside the FIPS module boundary, no FIPS modules are affected by this CVE.", "cve_priority": "medium", "cve_public_date": "2026-08-25 13:19:00 UTC" }, { "cve": "CVE-2026-63076", "url": "https://ubuntu.com/security/CVE-2026-63076", "cve_description": "Issue summary: OpenSSL CMP password based protection verification only checks whether the protectionAlg parameter was not NULL and not its ASN.1 type, before treating it as a PBMParameter. A crafted message can contain a parameter of a different type, which is then dereferenced as an invalid pointer. Impact summary: A remote, unauthenticated attacker can crash an application acting as a CMP server that accepts PBM-protected messages, or a CMP client talking to a malicious or intercepted CMP server, resulting in a Denial of Service. CWE: CWE-476: NULL Pointer Dereference Description: When verifying the password-based MAC protection of a CMP message, OpenSSL library reads the protectionAlg algorithm parameter with X509_ALGOR_get0(), which returns both the parameter type and its value pointer. The value is then cast to an ASN1_STRING and treated as the expected PBMParameter after only checking that pointer is not NULL. The parameter type returned by X509_ALGOR_get0() was never consulted. This happens during protection verification, before any MAC is computed, so no knowledge of the PBM shared secret is required; the only precondition is that PBM verification is reachable. On the server side this is reached from OSSL_CMP_SRV_process_request() for any application that stands up a CMP server accepting PBM-protected messages, and on the client side from CMP response validation against a malicious or on-path (MITM) server. The reliable consequence is a denial of service; there is no memory disclosure, no controlled memory write, and no path to code execution. CMP is a specialized feature that an application must explicitly enable. FIPS impact: no As the CMP code lives outside the FIPS module boundary, no FIPS modules are affected by this CVE.", "cve_priority": "medium", "cve_public_date": "2026-08-25 13:19:00 UTC" }, { "cve": "CVE-2026-14457", "url": "https://ubuntu.com/security/CVE-2026-14457", "cve_description": "Issue summary: In a server or client configuration with RFC7250 Raw Public Keys (RPKs) enabled, and only the private key (with no associated certificate) configured locally, a NULL pointer dereference may occur when the remote peer solicits raw public keys and also sends the typically omitted \"signature_algorithms_cert\" TLS extension. Impact summary: The impact is limited to a possible Denial of Service as a result of an application abort, no data disclosure or remote command execution are possible. CWE: CWE-476: NULL Pointer Dereference Description: While a passing comment in sample code in the documentation suggests that key-only RPK configurations are supported, the best-practice RPK configuration is to always configure a corresponding certificate (possibly self-signed or signed by any convenient CA). When the private key is configured along with a matching certificate, the \"signature_algorithms_cert\" extension is handled reliably even without the fix, and peer clients or servers that don't support raw public keys may be able to complete a TLS connection by pinning or verifying the corresponding certificate or its public key. Deployments that prefer to configure just a private key with no certificate need to upgrade to an updated release as noted below. FIPS impact: no No FIPS modules are affected by this issue, as the SSL protocol implementation is outside the OpenSSL FIPS module boundary.", "cve_priority": "low", "cve_public_date": "2026-08-25 13:17:00 UTC" }, { "cve": "CVE-2026-54874", "url": "https://ubuntu.com/security/CVE-2026-54874", "cve_description": "Issue summary: Receiving a DTLS record for a future epoch while a handshake is in progress causes OpenSSL to buffer far more memory than the record itself requires. Impact summary: A peer can use a small amount of network traffic to make an OpenSSL DTLS endpoint retain a disproportionately large amount of memory, which may lead to a Denial of Service. CWE: CWE-405: Asymmetric Resource Consumption (Amplification) Description: While a DTLS handshake is in progress, a peer may legitimately have already moved on to the next epoch (for example, having sent its ChangeCipherSpec and Finished messages) before the local endpoint has processed the same transition, typically because of reordering on the underlying UDP transport. OpenSSL buffers such early records so that they can be processed once the local endpoint catches up. Buffering a record currently retains the entire read buffer it arrived in, which is sized to hold the largest possible DTLS record (around 16 kilobytes), rather than just the bytes that make up the record itself. Up to 100 such records may be buffered per connection. As a result, a peer that sends a stream of small forged records claiming to belong to the next epoch can cause an OpenSSL DTLS endpoint to retain around 1.7 megabytes of memory, despite sending only a small fraction of that amount of data over the network. An attacker therefore gains a memory amplification factor of around 1200, and can multiply the effect across as many associations as it is able to open, making this a remote memory exhaustion Denial of Service risk for DTLS servers. Since the memory retained per connection remains bounded, and any limit an application already places on the number of concurrent associations also bounds the total exposure, this issue has been assessed as Low severity. FIPS impact: no No FIPS modules are affected by this issue as the affected code is outside the OpenSSL FIPS module boundary. OpenSSL 4.0, 3.6, 3.5, 3.4, 3.0, 1.1.1 and 1.0.2 are vulnerable to this issue. OpenSSL 4.0 users should upgrade to OpenSSL 4.0.2. OpenSSL 3.6 users should upgrade to OpenSSL 3.6.4. OpenSSL 3.5 users should upgrade to OpenSSL 3.5.8. OpenSSL 3.4 users should upgrade to OpenSSL 3.4.7. OpenSSL 3.0 users should upgrade to OpenSSL 3.0.22. Premium support customers only: OpenSSL 1.1.1 users should upgrade to OpenSSL 1.1.1zi OpenSSL 1.0.2 users should upgrade to OpenSSL 1.0.2zr This issue was reported on 18 May 2026 by Amazon Web Services. The fix has been developed by Matt Caswell. -- cut (non-publishing metadata for internal use) -- Reported by: Amazon Web Services Fixed by: Matt Caswell", "cve_priority": "low", "cve_public_date": "2026-08-25 13:19:00 UTC" }, { "cve": "CVE-2026-63073", "url": "https://ubuntu.com/security/CVE-2026-63073", "cve_description": "Issue summary: OpenSSL CMP response validation passed an unexpected response sender distinguished name directly as the format string to `ERR_raise_data()`. Impact summary: A malicious or intercepted CMP endpoint can crash a CMP client that enforces an expected sender or uses a pinned server certificate whose subject becomes the default expected sender. CWE: CWE-134 (Use of Externally-Controlled Format String) Description: When validating a received CMP message, ossl_cmp_msg_check_update() converts the peer-supplied sender distinguished name with X509_NAME_oneline() and passes it directly as the format argument to ERR_raise_data(). Percent characters survive the conversion, so a sender DN such as \"CN=%s%n\" reaches BIO_vsnprintf() as an attacker-controlled format string with no matching variadic arguments. This path is only reached when the caller configures an expected sender or pins a server certificate, which is the normal configuration for a CMP client validating server responses. Since the attacker controls the format string but none of the variadic arguments, such specifiers as %s and %n dereference or write through unrelated stack contents and crash the client. The reliable consequence is a denial of service, when the response comes from a malicious or intercepted CMP endpoint. There is no controlled memory write, arbitrary-address read, or reliable path to remote code execution. FIPS impact: no No FIPS modules are affected by this issue, as the CMP protocol implementation is outside the OpenSSL FIPS module boundary.", "cve_priority": "low", "cve_public_date": "2026-08-25 13:19:00 UTC" }, { "cve": "CVE-2026-63074", "url": "https://ubuntu.com/security/CVE-2026-63074", "cve_description": "Issue summary: The OpenSSL Certificate Management Protocol (CMP) caches additional certificates (extraCerts) sent in a CMP message, but never expunges them (for instance if they are invalid). If a server reuses an OSSL_CMP_CTX frequently, this cache of extraCerts may grow unboundedly, and a malicious client may flood a CMP server with requests driving this growth. Impact summary: Users utilizing a CMP server that reuses a single OSSL_CMP_CTX for the lifetime of a server process may observe unbounded memory growth in the event a malicious client repeatedly sends requests containing unique extra certificates, which may lead to OOM conditions. CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: If a remote user sends CMP messages to a server with a list of extraCerts and the message is rejected, the extraCerts from the message remains in the server contexts untrusted certificate stack. This exposes servers with long lived ctx objects to Denial of Service attacks in which an attacker sends messages intending to be rejected with a large list of additional certificates repeatedly, forcing the server to store them indefinitely. The issue was fixed by removing the added extra certs if the message is rejected, using the same method as when the context is configured to not do caching at all. FIPS impact: no As the CMP code lives outside the FIPS module boundary, no FIPS modules are affected by this CVE.", "cve_priority": "low", "cve_public_date": "2026-08-25 13:19:00 UTC" }, { "cve": "CVE-2026-63075", "url": "https://ubuntu.com/security/CVE-2026-63075", "cve_description": "Issue summary: When OpenSSL processes QUIC traffic from a peer that repeatedly sends ack-eliciting packets while not acknowledging ACK-only responses, the QUIC stack can retain ACK-only packet metadata for the lifetime of the connection. Impact summary: A remote peer that can complete a QUIC handshake can cause connection-scoped memory growth which may lead to Denial of Service through memory exhaustion, especially with sustained traffic or many concurrent QUIC connections. CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: When the OpenSSL QUIC stack sends an ACK-only packet, there is no requirement by the QUIC protocol that the peer will acknowledge that ACK-only packet (i.e. it is itself not ack-eliciting). However, the OpenSSL implementation stores the metadata about the ACK frames regardless. In and of itself that's ok, but if a malicious peer establishes a connection, and then drives the connection such that ACK-only packets are forced from the OpenSSL implementation peer (i.e., by sending numerous PING frames), and then withholding any subsequent acks for ack-eliciting data, like legitimate data, said malicious peer can force inappropriate memory growth on the OpenSSL peer, potentially leading to a Denial of Service. The fix is to ensure that we account for the transmission of the ACK-only packet in the packet histories high and low watermark without actually storing the ACK-only packet metadata itself. FIPS impact: no The OpenSSL FIPS module is not affected as the QUIC code is outside the FIPS module boundary.", "cve_priority": "low", "cve_public_date": "2026-08-25 13:19:00 UTC" }, { "cve": "CVE-2026-75803", "url": "https://ubuntu.com/security/CVE-2026-75803", "cve_description": "Issue summary: ChaCha20-Poly1305 and AES-OCB decryption with an empty ciphertext can report success without verifying the supplied authentication tag when the operation is finalized by calling the EVP_Cipher() function. Impact summary: Applications calling EVP_Cipher() on an empty ciphertext and expecting the call to check the AEAD tag may accept forged messages. CWE: CWE-354 (Improper Validation of Integrity Check Value) Description: The EVP_Cipher() API call for AEAD ciphers behaves like a one shot encryption and decryption call. It also verifies the AEAD tag after the decryption operation. However for AES-OCB and ChaCha20-Poly1305 ciphers it skipped the AEAD tag verification when an empty ciphertext was passed to the function. The callers of this function might believe that a successful return indicates a valid AEAD tag for these ciphers, even when that has not truly been validated in this case. FIPS impact: no The FIPS modules in 4.0, 3.6, 3.5, 3.4, and 3.0 are not affected by this CVE as the affected algorithms are not FIPS approved and thus not implemented in the FIPS module.", "cve_priority": "low", "cve_public_date": "2026-08-25 13:19:00 UTC" }, { "cve": "CVE-2026-14456", "url": "https://ubuntu.com/security/CVE-2026-14456", "cve_description": "Issue summary: When an OpenSSL QUIC server (Listener SSL object) processes valid QUIC Initial packets for unknown destination connection IDs, it can allocate and queue new incoming channels without enforcing any limit. Impact summary: A remote peer that can make many Initial packets reach the server listener faster than the application accepts connections, can cause the memory allocated to store the per-channel state to grow without any limits, potentially making the QUIC listener unavailable and causing Denial of Service. CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: The function that handles inbound QUIC packets uses Connection-Id from the packet header to find an existing connection (QUIC channel). If no existing connection is found and the packet type is INITIAL, the function treats the packet as a new connection. It allocates a new channel object and inserts it into a queue where it waits to be accepted by the local application with SSL_accept(3ossl). The memory occupied by these initial channel objects may grow without bounds if the application is not able to call SSL_accept() frequently enough to serve these inbound connection requests. The issue is present since OpenSSL 3.5 when the QUIC server implementation was added. The fix introduces a limit for pending connections. The default limit is set to 256 pending connections (waiting to be accepted by the local application). Applications may change the default by calling SSL_set_value_uint(3ossl). FIPS impact: no The FIPS module is not affected as the QUIC implementation is outside of the OpenSSL FIPS module boundary.", "cve_priority": "medium", "cve_public_date": "2026-08-13 15:19:00 UTC" }, { "cve": "CVE-2026-54876", "url": "https://ubuntu.com/security/CVE-2026-54876", "cve_description": "Issue summary: A malicious TLS server can cause a memory leak in a TLS client that has enabled OCSP response checking by sending an OCSP response that contains no single response entries. Impact summary: An attacker can leak an attacker-tunable amount of memory per TLS handshake in a victim client application. A long-running client that repeatedly connects to a malicious server can have its memory exhausted, resulting in a Denial of Service. CWE: CWE-401: Missing Release of Memory after Effective Lifetime Description: The affected function is called during X.509 certificate chain verification when OCSP response checking is enabled with the X509_V_FLAG_OCSP_RESP_CHECK or X509_V_FLAG_OCSP_RESP_CHECK_ALL verification flags, for example when a TLS client verifies an OCSP response stapled into the TLS handshake by the server. When the received BasicOCSPResponse contains an empty SEQUENCE OF SingleResponse, which is permitted on the wire and accepted by the OpenSSL decoder, the OCSP_BASICRESP structure allocated by OCSP_response_get1_basic() was not freed because an early return bypassed the cleanup code at the end of the function. The amount of memory leaked per handshake can be amplified by the attacker by padding the certs field of the BasicOCSPResponse with bogus certificates, which are parsed and stored in the leaked structure before the empty response check triggers the early return. A long-running TLS client that repeatedly connects to a malicious server can have its memory exhausted over time. OCSP response checking is not enabled by default. Only client applications that explicitly enable the OCSP response check verification flags are affected. FIPS impact: no The FIPS modules in 4.0 and 3.6 are not affected by this issue as the affected code is outside the OpenSSL FIPS module boundary.", "cve_priority": "medium", "cve_public_date": "2026-08-05 15:16:00 UTC" } ], "launchpad_bugs_fixed": [ 2167826 ], "changes": [ { "cves": [], "log": [ "", " * Merge with Debian experimental (LP: #2167826). Remaining changes:", " - Use perl:native in the autopkgtest for installability on i386.", " - Symlink copyright/changelog.Debian.gz in libssl3* to libssl-dev/openssl", " - Disable LTO with which the codebase is generally incompatible", " (LP #2058017)", " - Default config reads crypto-config and /etc/ssl/openssl.cnf.d dropins", " - Don't enable or package anything FIPS (LP #2087955)", " - Match last filename for output in ecp_nistp521-ppc64.pl (LP #2137464)", " - Enable CPU jitter fluctuations", " - fips patches (debian/patches/fips):", " - crypto: Add kernel FIPS mode detection", " - crypto: Automatically use the FIPS provider...", " - apps/speed: Omit unavailable algorithms in FIPS mode", " - apps: pass -propquery arg to the libctx DRBG fetches", " - test: Ensure encoding runs with the correct context...", " - Add Ubuntu-specific defines to help FIPS certification (LP #2073991)", " + UBUNTU_OSSL_SELF_TEST_DESC_PCT_DH", " + UBUNTU_OSSL_PROV_FIPS_PARAM_UNAPPROVED_USAGE", " - Detect FIPS jitterentropy mode and load jitterentropy enabled FIPS", " provider", " - Fallback to default provider when FIPS provider is missing.", "" ], "package": "openssl", "version": "4.0.3-1ubuntu1", "urgency": "medium", "distributions": "stonking", "launchpad_bugs_fixed": [ 2167826 ], "author": "Ravi Kant Sharma ", "date": "Fri, 02 Oct 2026 12:25:40 +0200" }, { "cves": [ { "cve": "CVE-2026-84782", "url": "https://ubuntu.com/security/CVE-2026-84782", "cve_description": "Issue summary: The DTLS retransmission logic does not correctly handle a handshake message write that is suspended part-way through. The retransmitted message can be read past the message buffer and the retransmission overwrites the internal state the suspended write needs to resume correctly. Impact summary: The retransmitted message can disclose a heap memory to the peer as plaintext handshake data or cause a crash and a Denial of Service when the read reaches an unmapped memory region. CWE: CWE-125: Out-of-bounds Read Description: DTLS handshake messages can be written out in multiple fragments, and a write can suspend mid-message (returning WANT_WRITE) if the underlying transport temporarily cannot accept more data. While such a write is suspended, the DTLS retransmission timer may independently fire and ask the retransmission logic to resend an earlier, already-acknowledged-as-sent message from its retransmit queue. The retransmission logic reused the same internal buffer and position tracking as the message that was still being written, without resetting the position back to the start of the message being retransmitted. As a result the retransmission was read starting from wherever the suspended write had left off, producing a mislabelled message whose body was leftover bytes from the other, larger message still in flight - content that was never meant to be sent at that point, and which could run past the end of the allocated buffer. Separately, even when the retransmission is positioned correctly, allowing it to run to completion while another write is suspended overwrites the same shared bookkeeping that the suspended write depends on to resume. When the application later resumes the suspended write (via a subsequent SSL_read(), SSL_write(), SSL_accept(), or SSL_connect() call), it finds that bookkeeping in a state inconsistent with the message and aborts the process in a debugging build. The fix resets the retransmission's read position to the start of the message before resending, and skips retransmission entirely whenever a handshake write is still suspended, deferring to the next call that resumes it instead. FIPS impact: no The affected code is outside the FIPS module boundary.", "cve_priority": "high", "cve_public_date": "2026-09-29 16:17:00 UTC" }, { "cve": "CVE-2026-35189", "url": "https://ubuntu.com/security/CVE-2026-35189", "cve_description": "Issue summary: A certificate with many nameRelativeToCRLIssuer CRL distribution points causes disproportionate heap growth when OpenSSL caches X.509 extensions. Impact summary: Receiving a crafted certificate from a malicious peer can lead to significant memory pressure and possible Denial of Service in clients or in servers that solicit client certificates. CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: A certificate or a set of certificates that fits under the limit for size of certificates accepted from the peer (~100 KiB) can result in allocation of several hundred MiB of resident memory on the receiving side during a normal TLS handshake. This may be enough to crash the client or server, if multiple concurrent connections lead to similarly large memory allocations. The fix postpones processing of the CRL distribution points extensions in certificates to the time when the processed value is required for CRL processing. This avoids keeping large memory allocations for a long time when such certificates are received. FIPS impact: no The affected code is outside the FIPS module boundary.", "cve_priority": "low", "cve_public_date": "2026-09-29 16:17:00 UTC" }, { "cve": "CVE-2026-35191", "url": "https://ubuntu.com/security/CVE-2026-35191", "cve_description": "Issue summary: The OpenSSL QUIC server, when configured to not preform address validation, can be forced to count incoming packets multiple times in its unvalidated credit computation, leading to a violation of the RFC 9000 unvalidated connection amplification limit of 3 times the amount of data received. Impact summary: A remote attacker able to spoof packets to a server using the OpenSSL QUIC implementation might use the server for an amplification of a DDoS attack. CWE: CWE-440: Expected Behavior Violation Description: OpenSSL's QUIC stack, when operating as a server, enforces client address validation (RFC 9000, Section 8), to confirm the peer address is not used for a traffic amplification attack. If this feature is disabled on the server, the QUIC stack limits the amount of server data that can be sent to 3 times the amount of data received from the peer address, until such time as the TLS handshake is completed. The OpenSSL QUIC server, when operating in non-validation mode, adds the length of the whole datagram received to the unvalidated credit limit when processing each QUIC packet in the datagram. A remote peer may, after establishing a connection with an initial client hello frame, send a subsequent datagram containing multiple QUIC packets, leading the server to account the entire datagram length for each packet in the datagram, resulting in the server believing that the peer has sent more data than it actually has, thereby violating the 3x amplification limit mandated by the RFC. FIPS impact: no As the QUIC stack lives outside the FIPS module boundary, no FIPS modules are affected by this CVE.", "cve_priority": "low", "cve_public_date": "2026-09-29 16:17:00 UTC" }, { "cve": "CVE-2026-42772", "url": "https://ubuntu.com/security/CVE-2026-42772", "cve_description": "Issue summary: The QUIC stream reassembly algorithm performance deteriorates progressively as packets are arriving out of order. The worst case has a quadratic complexity proportional to the number of stream frames kept in the buffer for the received stream data. Impact summary: A remote QUIC peer that completes the handshake can create a connection-scoped CPU pressure and potentially a Denial of Service using compliant STREAM frames inside the advertised receive window, with low attacker bandwidth. CWE: CWE-407: Inefficient Algorithmic Complexity Description: OpenSSL manages received QUIC stream fragments using a doubly-linked list. While it optimizes for append operations (at the end of the list), it falls back to a head-to-tail linear search for any fragment that does not immediately follow the current `tail`. By manipulating the sequence of offsets, an attacker can force the server to perform O(n^2) operations, consuming excessive CPU time for the QUIC process. FIPS impact: no The FIPS module is not affected as the QUIC implementation is outside of the OpenSSL FIPS module boundary.", "cve_priority": "low", "cve_public_date": "2026-09-29 16:17:00 UTC" }, { "cve": "CVE-2026-54872", "url": "https://ubuntu.com/security/CVE-2026-54872", "cve_description": "Issue summary: The generic elliptic-curve scalar multiplication used for ECDSA and SM2 signature operations with curves that do not have a dedicated implementation leaks information about the secret nonce through timing. Impact summary: An attacker able to measure signing times may learn information about the per-signature secret nonce, which over many signatures can, via a lattice / Hidden Number Problem attack, lead to recovery of the private key. CWE: CWE-208: Observable Timing Discrepancy Description: The generic elliptic-curve scalar multiplication used for curves that do not have a dedicated constant-time implementation pads the secret scalar with non-constant-time BIGNUM operations, so the time taken depends on the value of the secret scalar derived from the ECDSA and SM2 nonce. The leak is very small; observing it requires a large number of measurements. The effect is largest for curves whose group order lies on a machine-word boundary, such as brainpoolP384r1. Applications using ECDSA signing over the Brainpool and other generic prime curves, and SM2 signing on platforms that use the generic implementation, are vulnerable to this issue. The NIST curves P-256, P-384 and P-521 use dedicated constant-time implementations and are not affected. FIPS Impact: no The FIPS modules are not affected: the approved NIST curves used in the FIPS provider have dedicated constant-time implementations and do not use the affected code path.", "cve_priority": "low", "cve_public_date": "2026-09-29 16:17:00 UTC" }, { "cve": "CVE-2026-54873", "url": "https://ubuntu.com/security/CVE-2026-54873", "cve_description": "Issue summary: QUIC process may keep memory for QUIC packet buffer for much longer period than necessary. Impact summary: Remote peer can exploit this vulnerability by sending maliciously crafted packets, making the local QUIC stack to keep the memory for packet buffers allocated. The time for which the memory remains allocated is entirely under the control of the potentially malicious remote peer. CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: To save copy operation from the packet buffer to the stream reassemble buffer the QUIC stack leaves the stream data on the packet buffer waiting to be copied to a buffer provided by the local receiving application. The QUIC stack releases a reference to the packet buffer only after the data are copied to the application buffer. This design is more efficient for legitimate data transfers but enables an attacker to allocate a lot more memory than actually required by the data kept in the receiving stream buffer. To mitigate the vulnerability, the QUIC stack now calculates and monitors memory overhead for every stream. The memory overhead for a single stream frame is calculated as a difference between the size of the whole packet that carries the stream frame and the size of the stream frame itself. The memory overhead for a single stream frame is added to the total (cumulative) memory overhead QUIC stack keeps for each stream. Once the cumulative memory overhead exceeds 64kB, the QUIC stack moves the stream frame data from the packet buffer to the stream buffer, starting with the next packet received. FIPS impact: no The FIPS module is not affected as the QUIC implementation is outside of the OpenSSL FIPS module boundary.", "cve_priority": "low", "cve_public_date": "2026-09-29 16:17:00 UTC" }, { "cve": "CVE-2026-54875", "url": "https://ubuntu.com/security/CVE-2026-54875", "cve_description": "Issue summary: A non-constant-time optimized implementation of scalar point multiplication is used for SM2 private key operations on ARM64 and RISC-V platforms. Impact summary: An attacker able to measure the time taken by, or to observe the cache-line access pattern of SM2 signing or decryption on an affected platform can learn information about the secret scalar. CWE: CWE-208: Observable Timing Discrepancy Description: On ARM64 and RISC-V processors, the SM2 curve uses an optimized scalar multiplication implementation whose conditional branches and table look ups are chosen according to the bits of the secret scalar. The execution time and the cache-access pattern therefore depend on the long-term private key (during SM2 decryption) or the per-signature nonce (during SM2 signature generation), forming a timing and cache side-channel. FIPS Impact: no SM2 is not a FIPS algorithm and the optimized SM2 implementation is not part of the FIPS module. OpenSSL 4.0, 3.6, 3.5 and 3.4 are vulnerable to this issue on AArch64 and RISC-V. OpenSSL 3.0, 1.1.1 and 1.0.2 are not affected by this issue. OpenSSL 4.0 users should upgrade to OpenSSL 4.0.3. OpenSSL 3.6 users should upgrade to OpenSSL 3.6.5. OpenSSL 3.5 users should upgrade to OpenSSL 3.5.9. OpenSSL 3.4 users should upgrade to OpenSSL 3.4.8. This issue was reported on 2 May 2026 by Abhinav Agarwal. It was independently reported on 6 June 2026 by Feng Xue. The fix was developed by Igor Ustinov. -- cut (non-publishing metadata for internal use) -- Reported by: Abhinav Agarwal, Feng Xue Fixed by: Igor Ustinov", "cve_priority": "low", "cve_public_date": "2026-09-29 16:17:00 UTC" }, { "cve": "CVE-2026-72897", "url": "https://ubuntu.com/security/CVE-2026-72897", "cve_description": "Issue summary: A TLS server that calls SSL_set_SSL_CTX() to switch a connection to a different SSL_CTX part way through a handshake may access memory beyond the end of an internal array if the replacement context knows about more provider signature algorithms than the context the connection was created from. Applications which never call SSL_set_SSL_CTX() are not affected. Impact summary: A remote peer may be able to cause a small out-of-bounds read, and in some circumstances a fixed-value out-of-bounds write, on the server heap. This may lead to a Denial of Service. CWE: CWE-787: Out-of-bounds Write Description: A TLS connection records how many certificate slots it has when it is created, taken from the SSL_CTX that created it: the built-in certificate types plus one slot for each provider TLS-SIGALG entry that context was aware of. That count sizes an internal array of per-slot certificate validity flags. An application may replace a connection's SSL_CTX part way through the handshake by calling SSL_set_SSL_CTX(), most commonly from a servername callback in order to serve a different virtual host. Doing so did not refresh the recorded count. A provider signature algorithm's slot index is its position in the list of whichever context resolves it, so if the replacement context is aware of more of them than the original, an algorithm offered by the peer can resolve to an index beyond the end of the array. Processing the peer's signature algorithms then reads one four byte word past the end for each such algorithm and, where the word read is zero, writes a fixed value over it. A peer offering many of them can corrupt heap metadata and abort the process. Only provider signature algorithms which occupy one of the excess slots, and which the server also has configured, have this effect. Codepoints the replacement context does not recognise are discarded without being resolved to a slot, and provider signature algorithms are usable only from TLS 1.3. The two contexts must therefore be aware of different numbers of provider signature algorithms, which requires separate library contexts, a provider loaded between the two being created, or providers which differ in what they advertise - in 4.0, for example, the default provider advertises SM2 where the FIPS provider does not. A deployment meeting the condition is also unable to negotiate the affected algorithms with legitimate clients, since the same stale count hides the corresponding certificates, so the misconfiguration is likely to be noticed. For that reason, and because the configuration is not the default, this issue has been assessed as Low severity. FIPS impact: no No FIPS modules are affected by this issue as the affected code is outside the OpenSSL FIPS module boundary.", "cve_priority": "low", "cve_public_date": "2026-09-29 16:17:00 UTC" }, { "cve": "CVE-2026-75804", "url": "https://ubuntu.com/security/CVE-2026-75804", "cve_description": "Issue summary: OpenSSL QUIC stack does not enforce connection level flow control for streams. Remote peers may send more bytes as long as they fit within the stream flow control limits. Impact summary: A malicious remote peer may exploit the lack of connection flow control for streams to make the QUIC stack receive ~100MB of memory instead of 768 KiB (default flow control window size). CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: The local QUIC stack advertises two flow control limits to its remote peer: stream flow control limit and connection flow control limit. The remote peer must follow both limits when transmitting stream data. Whenever the local QUIC stack receives a stream frame, it validates that the size of the received stream frame stays within flow control limits. If either limit is exceeded (stream level or connection level), then the QUIC stack must close the connection with a flow control error. The vulnerable OpenSSL QUIC stack enforces the stream-level but not the connection-level limit. To exploit the issue, three conditions must be met: - the remote peer opens several streams - each stream must stay within the stream-level flow control limit - there must be no zero-offset byte sent on any of the streams (to prevent the vulnerable QUIC stack from consuming data). By meeting the conditions above, the remote peer may make the local stack allocate 2 x MAX_STREAMS x (stream flow control limit) bytes of memory. MAX_STREAMS defaults to 100, and the limit applies to both bidirectional and unidirectional streams, making it 200 in total. The default flow control window for a stream is 512kB. The remote peer may force the vulnerable QUIC stack to allocate 100MB of heap per connection. FIPS impact: no The FIPS module is not affected as the QUIC implementation is outside of the OpenSSL FIPS module boundary.", "cve_priority": "low", "cve_public_date": "2026-09-29 16:17:00 UTC" }, { "cve": "CVE-2026-75805", "url": "https://ubuntu.com/security/CVE-2026-75805", "cve_description": "Issue summary: A CMP client that requests certificate revocation on the basis of a PKCS#10 CSR may dereference a NULL pointer and terminate abnormally when processing a crafted revocation response. Impact summary: The NULL pointer dereference happens on a read which leads to a crash and a Denial of Service for the affected client application. CWE: CWE-476: NULL-pointer dereference Description: A CMP client revoking a certificate has to tell the server which certificate to revoke, and may do so by supplying a PKCS#10 CSR instead of the certificate itself or its issuer name and serial number. This is 'openssl cmp -cmd rr -csr ' on the command line, or OSSL_CMP_exec_RR_ses() with the certificate supplied via OSSL_CMP_CTX_set1_p10CSR() through the API. A CSR does not contain the issuer name and serial number of the certificate, so the client does not send them. A server may optionally name the certificate it revoked in its response, and the client then compares that name against what it sent. Having sent neither an issuer name nor a serial number, it has nothing to compare against, and a server returning a specially crafted name causes the client to read from a NULL pointer and crash. The revocation response is checked for valid message protection before the affected code is reached, so an attacker must be a malicious or compromised CMP server, or a man-in-the-middle in possession of the secret used for message protection. Clients that identify the certificate to be revoked by a certificate or by issuer and serial number rather than by a PKCS#10 CSR are not affected. FIPS impact: no No FIPS modules are affected by this issue, as the CMP protocol implementation is outside the OpenSSL FIPS module boundary.", "cve_priority": "low", "cve_public_date": "2026-09-29 16:17:00 UTC" }, { "cve": "CVE-2026-75806", "url": "https://ubuntu.com/security/CVE-2026-75806", "cve_description": "Issue summary: An established DTLS 1.2 association using an AEAD cipher suite can be terminated by a single unauthenticated datagram whose encrypted fragment is shorter than the mandatory explicit IV and authentication tag overhead. Impact summary: An attacker who can send a datagram that is routed to an existing DTLS 1.2 association can tear that association down without knowing any key material. This is a Denial of Service limited to the targeted association. There is no memory safety or confidentiality impact. CWE: CWE-1284: Improper Validation of Specified Quantity in Input Description: In TLS 1.2 and DTLS 1.2 every record protected by an AEAD cipher suite carries an explicit IV followed by the ciphertext and an authentication tag. When decrypting such a record the record layer passed the record length to the cipher implementation before checking that the record was long enough to contain the explicit IV and the tag. For a record shorter than that overhead the cipher implementation rejected the impossible length, and the record layer treated this as an internal failure and raised a fatal internal_error alert instead of treating the record as one that failed authentication. In TLS 1.2 the same record causes a fatal internal_error alert instead of the expected bad_record_mac alert. Since any undecryptable record already terminates a TLS connection, this is a protocol conformance issue rather than a security issue in TLS. The fix validates the record length against the explicit IV and tag length before any AEAD processing, so that TLS reports bad_record_mac and DTLS silently discards the record. FIPS impact: no The affected code is outside the FIPS module boundary.", "cve_priority": "low", "cve_public_date": "2026-09-29 16:17:00 UTC" }, { "cve": "CVE-2026-77696", "url": "https://ubuntu.com/security/CVE-2026-77696", "cve_description": "Issue summary: SM2 signature generation uses non-constant-time arithmetic on secret values, forming a timing side-channel. Impact summary: An attacker able to measure SM2 signing times may learn information about the per-signature secret nonce, which over many signatures can, via a lattice / Hidden Number Problem attack, lead to recovery of the private key. CWE: CWE-208: Observable Timing Discrepancy Description: SM2 signature generation computes the signature value using variable-time BIGNUM operations on the secret nonce and the private key, so the time taken to produce an SM2 signature depends on these secret values, forming a timing side-channel. Applications performing SM2 signature generation are affected on all platforms. FIPS Impact: no SM2 is not a FIPS algorithm.", "cve_priority": "low", "cve_public_date": "2026-09-29 16:17:00 UTC" }, { "cve": "CVE-2026-84783", "url": "https://ubuntu.com/security/CVE-2026-84783", "cve_description": "Issue summary: The first concurrent use of the same X.509 certificate by several threads may cause its cached extension data to be freed while another thread is still using it. Impact summary: A remote, unauthenticated peer could crash a multi-threaded TLS client, or a multi-threaded TLS server that requests client certificates, if the first certificate chains built to the same trusted CA certificate are built by several connections at the same time. This is a use-after-free read, which is likely to crash the process, resulting in a Denial of Service. CWE: CWE-416: Use After Free Description: OpenSSL caches the decoded values of a certificate's X.509v3 extensions inside the X509 object the first time they are needed. In OpenSSL 4.0 this cache is built in two phases: the extension values are computed while holding a read lock on the certificate, and the results are then installed into the certificate under a write lock. Because a read lock does not exclude other readers, several threads can compute the cache for the same certificate at the same time. Each thread that subsequently acquires the write lock installs its own results and frees the values installed by the thread before it, even though that earlier thread has already marked the cache as complete and may have returned pointers into it to its caller. A caller still using those pointers then reads freed memory. Any certificate shared between threads is exposed the first time its extensions are decoded. In TLS the certificates at risk are the trusted CA certificates supplied for chain verification, by whatever means, since these are shared by every connection and their extensions are decoded and cached the first time a chain is built to them. Certificates sent by the peer are decoded separately for each connection and are not shared, so they are not affected. In a TLS client verifying server certificates, or a TLS server that requests and verifies client certificates, the use-after-free could only occur if the first chains built to the same trusted CA are built by several connections at the same time. FIPS impact: no The FIPS module is not affected as X.509 certificate handling is outside of the OpenSSL FIPS module boundary. OpenSSL 4.0 is vulnerable to this issue. OpenSSL 3.6, 3.5, 3.4, 3.0, 1.1.1 and 1.0.2 are not affected by this issue. OpenSSL 4.0 users should upgrade to OpenSSL 4.0.3. This issue was reported on 27 August 2026 by Tim Becker (Xint.io) and independently in a public report on 31 August 2026 by aydinmercan. The fix has been developed by Bob Beck. -- cut (non-publishing metadata for internal use) -- Reported by: Tim Becker (Xint.io), aydinmercan Fixed by: Bob Beck", "cve_priority": "medium", "cve_public_date": "2026-09-29 16:17:00 UTC" }, { "cve": "CVE-2026-84784", "url": "https://ubuntu.com/security/CVE-2026-84784", "cve_description": "Issue summary: A malicious remote peer may flood the local QUIC stack with NEW_CONNECTION_ID frames by avoiding a limit check on how many connection IDs the remote QUIC stack can use. Impact summary: The local QUIC stack sends a RETIRE_CONN_ID frame for every NEW_CONNECTION_ID frame it receives. The RETIRE_CONN_ID frame is dispatched via the Control Frame Queue (CFQ). If the remote peer also withholds ACKs, then it can force the local stack to allocate ~400MB (depending on ACK delay). CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: RFC 9000 sections 5.1.1 and 5.1.2 [1] describe the mechanism by which a remote peer can notify the local QUIC stack to change the destination connection ID (a.k.a. CID) the local stack uses to identify the connection at the remote peer. Each CID is associated with a sequence number. The sequence number is transmitted in NEW_CONNECTION_ID and RETIRE_CONNECTION_ID frames to identify the CID which is being either associated with a connection or retired. The remote peer sends a NEW_CONNECTION_ID frame to let the local stack know a new CID is being associated with an existing connection. The NEW_CONNECTION_ID frame carries the new CID, its sequence number, and the retire-prior-to number. The retire-prior-to identifies existing CIDs that are to be retired. The local QUIC stack must send a RETIRE_CONNECTION_ID for every destination CID whose sequence number is less than retire-prior-to. The CID becomes retired after the local stack receives an ACK for its RETIRE_CONNECTION_ID frame. Although the OpenSSL QUIC stack supports at most one destination CID for every connection, it can be tricked into processing more than one RETIRE_CONNECTION_ID frame per connection. The OpenSSL QUIC stack currently retires the destination CID as soon as it receives the NEW_CONNECTION_ID, while in fact the destination CID must be retired after an ACK for the RETIRE_CONNECTION_ID frame is received. Correcting the flawed logic also fixes the backlog growth. [1] https://datatracker.ietf.org/doc/html/rfc9000#name-issuing-connection-ids FIPS impact: no The FIPS module is not affected as the QUIC implementation is outside of the OpenSSL FIPS module boundary.", "cve_priority": "low", "cve_public_date": "2026-09-29 16:17:00 UTC" } ], "log": [ "", " * Import 4.0.3", " - CVE-2026-84782 (\"DTLS Retransmits Handshake Messages From a Stale Buffer", " Offset\")", " - CVE-2026-35189 (\"Memory Allocation in Relative CRLDP Processing\")", " - CVE-2026-35191 (\"QUIC Unvalidated Amplification Credit may be Over", " Accounted\")", " - CVE-2026-42772 (\"Potential CPU DoS via O(n^2) Fragment Reassembly in QUIC\")", " - CVE-2026-54872 (\"Timing Side-Channel in Scalar Multiplication for Non-NIST", " EC Curves\")", " - CVE-2026-54873 (\"QUIC STREAM Fragment Metadata DoS\")", " - CVE-2026-54875 (\"Non-Constant-Time SM2 Scalar Multiplication on ARM64 and", " RISC-V\")", " - CVE-2026-72897 (\"Out-of-Bounds Access After SSL_set_SSL_CTX() During a", " Handshake\")", " - CVE-2026-75804 (\"QUIC Connection-Level Flow Control is Not Enforced for", " Streams\")", " - CVE-2026-75805 (\"NULL Pointer Dereference in CMP Client Revocation", " Response Handling\")", " - CVE-2026-75806 (\"Unauthenticated and Undersized DTLS 1.2 AEAD Record", " Causes DoS\")", " - CVE-2026-77696 (\"Timing Side-Channel in SM2 Signature Generation\")", " - CVE-2026-84783 (\"Use-After-Free in X.509 Extension Cache Under Concurrent Use\")", " - CVE-2026-84784 (\"QUIC: Unbounded RETIRE_CONNECTION_ID Backlog\")", "" ], "package": "openssl", "version": "4.0.3-1", "urgency": "medium", "distributions": "experimental", "launchpad_bugs_fixed": [], "author": "Sebastian Andrzej Siewior ", "date": "Tue, 29 Sep 2026 21:40:01 +0200" }, { "cves": [ { "cve": "CVE-2026-18798", "url": "https://ubuntu.com/security/CVE-2026-18798", "cve_description": "Issue summary: QUIC server may double free QRX (QUIC record layer RX) object when channel creation fails for initial packet. Impact summary: Double free leads to heap corruption, which typically results in termination of QUIC server process, leading to Denial of Service. There is so far no evidence that this double free is exploitable for remote code execution, thus it is considered highly improbable. CWE: CWE-415: Double Free Description: In order to validate initial packet, OpenSSL QUIC stack default packet handler (port_default_packet_handler()) creates a so-called QRX object. If the initial packet validates successfully with QRX object, the default packet handler proceeds to channel (connection object) creation. The QRX object used for packet validation is passed to port_bind_channel(), so it becomes part of the newly created connection. If port_bind_channel() fails, then it also frees the QRX object. Once port_bind_channel() returns, the port_default_packet_handler() detects the failure and proceeds to the error branch, where the same QRX object is freed for the second time. The failure in port_bind_channel() function can be induced with a relatively low effort by a malformed (non RFC 9000 compliant) INITIAL packet. If the packet carries DCID (destination connection ID) which is shorter than 8 bytes, then port_bind_channel() jumps to the error path after ossl_quic_lcidm_enrol_odcid() detects that the DCID has invalid length. FIPS impact: no The FIPS module is not affected, as the QUIC implementation is outside of the OpenSSL FIPS module boundary.", "cve_priority": "medium", "cve_public_date": "2026-08-25 13:17:00 UTC" }, { "cve": "CVE-2026-63072", "url": "https://ubuntu.com/security/CVE-2026-63072", "cve_description": "Issue summary: OpenSSL CMS decryption sizes the key-unwrap output buffer based on querying the unwrapped key size, but the AES-WRAP-PAD unwrap primitive can write and cleanse more bytes than that query reports, causing an 8-byte out-of-bounds heap write. Impact summary: An attacker who supplies a crafted CMS message can trigger a deterministic 8-byte out-of-bounds heap write when the victim decrypts it with CMS_decrypt(), corrupting the heap and typically resulting in a Denial of Service. CWE: CWE-787: Out-of-bounds Write Description: The key-wrap OID is potentially attacker-controlled on the wire. CMS unwrapping allows both id-aesNNN-wrap-pad and id-aesNNN-wrap ciphers. An attacker can take a legitimate message and change a single OID byte to select the padded variant while leaving the message otherwise valid. Since the unwrap key is derived from the recipient's private operation (ECDH key agreement or ML-KEM decapsulation), the RFC 5649 integrity check cannot pass, and the decryption fails with integrity failure. The write is a fixed-size (8-byte), fixed-value (zero) heap overflow immediately past the allocation, requires no special configuration, and is reachable from the public CMS_decrypt() function. The consequence is a heap corruption leading to a Denial of Service. The fix in the CMS code sizes the unwrap output buffer for the worst case so a failed unwrap cannot write past the allocation. FIPS impact: no As the CMS code lives outside the FIPS module boundary, no FIPS modules are affected by this CVE.", "cve_priority": "medium", "cve_public_date": "2026-08-25 13:19:00 UTC" }, { "cve": "CVE-2026-63076", "url": "https://ubuntu.com/security/CVE-2026-63076", "cve_description": "Issue summary: OpenSSL CMP password based protection verification only checks whether the protectionAlg parameter was not NULL and not its ASN.1 type, before treating it as a PBMParameter. A crafted message can contain a parameter of a different type, which is then dereferenced as an invalid pointer. Impact summary: A remote, unauthenticated attacker can crash an application acting as a CMP server that accepts PBM-protected messages, or a CMP client talking to a malicious or intercepted CMP server, resulting in a Denial of Service. CWE: CWE-476: NULL Pointer Dereference Description: When verifying the password-based MAC protection of a CMP message, OpenSSL library reads the protectionAlg algorithm parameter with X509_ALGOR_get0(), which returns both the parameter type and its value pointer. The value is then cast to an ASN1_STRING and treated as the expected PBMParameter after only checking that pointer is not NULL. The parameter type returned by X509_ALGOR_get0() was never consulted. This happens during protection verification, before any MAC is computed, so no knowledge of the PBM shared secret is required; the only precondition is that PBM verification is reachable. On the server side this is reached from OSSL_CMP_SRV_process_request() for any application that stands up a CMP server accepting PBM-protected messages, and on the client side from CMP response validation against a malicious or on-path (MITM) server. The reliable consequence is a denial of service; there is no memory disclosure, no controlled memory write, and no path to code execution. CMP is a specialized feature that an application must explicitly enable. FIPS impact: no As the CMP code lives outside the FIPS module boundary, no FIPS modules are affected by this CVE.", "cve_priority": "medium", "cve_public_date": "2026-08-25 13:19:00 UTC" }, { "cve": "CVE-2026-14457", "url": "https://ubuntu.com/security/CVE-2026-14457", "cve_description": "Issue summary: In a server or client configuration with RFC7250 Raw Public Keys (RPKs) enabled, and only the private key (with no associated certificate) configured locally, a NULL pointer dereference may occur when the remote peer solicits raw public keys and also sends the typically omitted \"signature_algorithms_cert\" TLS extension. Impact summary: The impact is limited to a possible Denial of Service as a result of an application abort, no data disclosure or remote command execution are possible. CWE: CWE-476: NULL Pointer Dereference Description: While a passing comment in sample code in the documentation suggests that key-only RPK configurations are supported, the best-practice RPK configuration is to always configure a corresponding certificate (possibly self-signed or signed by any convenient CA). When the private key is configured along with a matching certificate, the \"signature_algorithms_cert\" extension is handled reliably even without the fix, and peer clients or servers that don't support raw public keys may be able to complete a TLS connection by pinning or verifying the corresponding certificate or its public key. Deployments that prefer to configure just a private key with no certificate need to upgrade to an updated release as noted below. FIPS impact: no No FIPS modules are affected by this issue, as the SSL protocol implementation is outside the OpenSSL FIPS module boundary.", "cve_priority": "low", "cve_public_date": "2026-08-25 13:17:00 UTC" }, { "cve": "CVE-2026-54874", "url": "https://ubuntu.com/security/CVE-2026-54874", "cve_description": "Issue summary: Receiving a DTLS record for a future epoch while a handshake is in progress causes OpenSSL to buffer far more memory than the record itself requires. Impact summary: A peer can use a small amount of network traffic to make an OpenSSL DTLS endpoint retain a disproportionately large amount of memory, which may lead to a Denial of Service. CWE: CWE-405: Asymmetric Resource Consumption (Amplification) Description: While a DTLS handshake is in progress, a peer may legitimately have already moved on to the next epoch (for example, having sent its ChangeCipherSpec and Finished messages) before the local endpoint has processed the same transition, typically because of reordering on the underlying UDP transport. OpenSSL buffers such early records so that they can be processed once the local endpoint catches up. Buffering a record currently retains the entire read buffer it arrived in, which is sized to hold the largest possible DTLS record (around 16 kilobytes), rather than just the bytes that make up the record itself. Up to 100 such records may be buffered per connection. As a result, a peer that sends a stream of small forged records claiming to belong to the next epoch can cause an OpenSSL DTLS endpoint to retain around 1.7 megabytes of memory, despite sending only a small fraction of that amount of data over the network. An attacker therefore gains a memory amplification factor of around 1200, and can multiply the effect across as many associations as it is able to open, making this a remote memory exhaustion Denial of Service risk for DTLS servers. Since the memory retained per connection remains bounded, and any limit an application already places on the number of concurrent associations also bounds the total exposure, this issue has been assessed as Low severity. FIPS impact: no No FIPS modules are affected by this issue as the affected code is outside the OpenSSL FIPS module boundary. OpenSSL 4.0, 3.6, 3.5, 3.4, 3.0, 1.1.1 and 1.0.2 are vulnerable to this issue. OpenSSL 4.0 users should upgrade to OpenSSL 4.0.2. OpenSSL 3.6 users should upgrade to OpenSSL 3.6.4. OpenSSL 3.5 users should upgrade to OpenSSL 3.5.8. OpenSSL 3.4 users should upgrade to OpenSSL 3.4.7. OpenSSL 3.0 users should upgrade to OpenSSL 3.0.22. Premium support customers only: OpenSSL 1.1.1 users should upgrade to OpenSSL 1.1.1zi OpenSSL 1.0.2 users should upgrade to OpenSSL 1.0.2zr This issue was reported on 18 May 2026 by Amazon Web Services. The fix has been developed by Matt Caswell. -- cut (non-publishing metadata for internal use) -- Reported by: Amazon Web Services Fixed by: Matt Caswell", "cve_priority": "low", "cve_public_date": "2026-08-25 13:19:00 UTC" }, { "cve": "CVE-2026-63073", "url": "https://ubuntu.com/security/CVE-2026-63073", "cve_description": "Issue summary: OpenSSL CMP response validation passed an unexpected response sender distinguished name directly as the format string to `ERR_raise_data()`. Impact summary: A malicious or intercepted CMP endpoint can crash a CMP client that enforces an expected sender or uses a pinned server certificate whose subject becomes the default expected sender. CWE: CWE-134 (Use of Externally-Controlled Format String) Description: When validating a received CMP message, ossl_cmp_msg_check_update() converts the peer-supplied sender distinguished name with X509_NAME_oneline() and passes it directly as the format argument to ERR_raise_data(). Percent characters survive the conversion, so a sender DN such as \"CN=%s%n\" reaches BIO_vsnprintf() as an attacker-controlled format string with no matching variadic arguments. This path is only reached when the caller configures an expected sender or pins a server certificate, which is the normal configuration for a CMP client validating server responses. Since the attacker controls the format string but none of the variadic arguments, such specifiers as %s and %n dereference or write through unrelated stack contents and crash the client. The reliable consequence is a denial of service, when the response comes from a malicious or intercepted CMP endpoint. There is no controlled memory write, arbitrary-address read, or reliable path to remote code execution. FIPS impact: no No FIPS modules are affected by this issue, as the CMP protocol implementation is outside the OpenSSL FIPS module boundary.", "cve_priority": "low", "cve_public_date": "2026-08-25 13:19:00 UTC" }, { "cve": "CVE-2026-63074", "url": "https://ubuntu.com/security/CVE-2026-63074", "cve_description": "Issue summary: The OpenSSL Certificate Management Protocol (CMP) caches additional certificates (extraCerts) sent in a CMP message, but never expunges them (for instance if they are invalid). If a server reuses an OSSL_CMP_CTX frequently, this cache of extraCerts may grow unboundedly, and a malicious client may flood a CMP server with requests driving this growth. Impact summary: Users utilizing a CMP server that reuses a single OSSL_CMP_CTX for the lifetime of a server process may observe unbounded memory growth in the event a malicious client repeatedly sends requests containing unique extra certificates, which may lead to OOM conditions. CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: If a remote user sends CMP messages to a server with a list of extraCerts and the message is rejected, the extraCerts from the message remains in the server contexts untrusted certificate stack. This exposes servers with long lived ctx objects to Denial of Service attacks in which an attacker sends messages intending to be rejected with a large list of additional certificates repeatedly, forcing the server to store them indefinitely. The issue was fixed by removing the added extra certs if the message is rejected, using the same method as when the context is configured to not do caching at all. FIPS impact: no As the CMP code lives outside the FIPS module boundary, no FIPS modules are affected by this CVE.", "cve_priority": "low", "cve_public_date": "2026-08-25 13:19:00 UTC" }, { "cve": "CVE-2026-63075", "url": "https://ubuntu.com/security/CVE-2026-63075", "cve_description": "Issue summary: When OpenSSL processes QUIC traffic from a peer that repeatedly sends ack-eliciting packets while not acknowledging ACK-only responses, the QUIC stack can retain ACK-only packet metadata for the lifetime of the connection. Impact summary: A remote peer that can complete a QUIC handshake can cause connection-scoped memory growth which may lead to Denial of Service through memory exhaustion, especially with sustained traffic or many concurrent QUIC connections. CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: When the OpenSSL QUIC stack sends an ACK-only packet, there is no requirement by the QUIC protocol that the peer will acknowledge that ACK-only packet (i.e. it is itself not ack-eliciting). However, the OpenSSL implementation stores the metadata about the ACK frames regardless. In and of itself that's ok, but if a malicious peer establishes a connection, and then drives the connection such that ACK-only packets are forced from the OpenSSL implementation peer (i.e., by sending numerous PING frames), and then withholding any subsequent acks for ack-eliciting data, like legitimate data, said malicious peer can force inappropriate memory growth on the OpenSSL peer, potentially leading to a Denial of Service. The fix is to ensure that we account for the transmission of the ACK-only packet in the packet histories high and low watermark without actually storing the ACK-only packet metadata itself. FIPS impact: no The OpenSSL FIPS module is not affected as the QUIC code is outside the FIPS module boundary.", "cve_priority": "low", "cve_public_date": "2026-08-25 13:19:00 UTC" }, { "cve": "CVE-2026-75803", "url": "https://ubuntu.com/security/CVE-2026-75803", "cve_description": "Issue summary: ChaCha20-Poly1305 and AES-OCB decryption with an empty ciphertext can report success without verifying the supplied authentication tag when the operation is finalized by calling the EVP_Cipher() function. Impact summary: Applications calling EVP_Cipher() on an empty ciphertext and expecting the call to check the AEAD tag may accept forged messages. CWE: CWE-354 (Improper Validation of Integrity Check Value) Description: The EVP_Cipher() API call for AEAD ciphers behaves like a one shot encryption and decryption call. It also verifies the AEAD tag after the decryption operation. However for AES-OCB and ChaCha20-Poly1305 ciphers it skipped the AEAD tag verification when an empty ciphertext was passed to the function. The callers of this function might believe that a successful return indicates a valid AEAD tag for these ciphers, even when that has not truly been validated in this case. FIPS impact: no The FIPS modules in 4.0, 3.6, 3.5, 3.4, and 3.0 are not affected by this CVE as the affected algorithms are not FIPS approved and thus not implemented in the FIPS module.", "cve_priority": "low", "cve_public_date": "2026-08-25 13:19:00 UTC" }, { "cve": "CVE-2026-14456", "url": "https://ubuntu.com/security/CVE-2026-14456", "cve_description": "Issue summary: When an OpenSSL QUIC server (Listener SSL object) processes valid QUIC Initial packets for unknown destination connection IDs, it can allocate and queue new incoming channels without enforcing any limit. Impact summary: A remote peer that can make many Initial packets reach the server listener faster than the application accepts connections, can cause the memory allocated to store the per-channel state to grow without any limits, potentially making the QUIC listener unavailable and causing Denial of Service. CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: The function that handles inbound QUIC packets uses Connection-Id from the packet header to find an existing connection (QUIC channel). If no existing connection is found and the packet type is INITIAL, the function treats the packet as a new connection. It allocates a new channel object and inserts it into a queue where it waits to be accepted by the local application with SSL_accept(3ossl). The memory occupied by these initial channel objects may grow without bounds if the application is not able to call SSL_accept() frequently enough to serve these inbound connection requests. The issue is present since OpenSSL 3.5 when the QUIC server implementation was added. The fix introduces a limit for pending connections. The default limit is set to 256 pending connections (waiting to be accepted by the local application). Applications may change the default by calling SSL_set_value_uint(3ossl). FIPS impact: no The FIPS module is not affected as the QUIC implementation is outside of the OpenSSL FIPS module boundary.", "cve_priority": "medium", "cve_public_date": "2026-08-13 15:19:00 UTC" }, { "cve": "CVE-2026-54876", "url": "https://ubuntu.com/security/CVE-2026-54876", "cve_description": "Issue summary: A malicious TLS server can cause a memory leak in a TLS client that has enabled OCSP response checking by sending an OCSP response that contains no single response entries. Impact summary: An attacker can leak an attacker-tunable amount of memory per TLS handshake in a victim client application. A long-running client that repeatedly connects to a malicious server can have its memory exhausted, resulting in a Denial of Service. CWE: CWE-401: Missing Release of Memory after Effective Lifetime Description: The affected function is called during X.509 certificate chain verification when OCSP response checking is enabled with the X509_V_FLAG_OCSP_RESP_CHECK or X509_V_FLAG_OCSP_RESP_CHECK_ALL verification flags, for example when a TLS client verifies an OCSP response stapled into the TLS handshake by the server. When the received BasicOCSPResponse contains an empty SEQUENCE OF SingleResponse, which is permitted on the wire and accepted by the OpenSSL decoder, the OCSP_BASICRESP structure allocated by OCSP_response_get1_basic() was not freed because an early return bypassed the cleanup code at the end of the function. The amount of memory leaked per handshake can be amplified by the attacker by padding the certs field of the BasicOCSPResponse with bogus certificates, which are parsed and stored in the leaked structure before the empty response check triggers the early return. A long-running TLS client that repeatedly connects to a malicious server can have its memory exhausted over time. OCSP response checking is not enabled by default. Only client applications that explicitly enable the OCSP response check verification flags are affected. FIPS impact: no The FIPS modules in 4.0 and 3.6 are not affected by this issue as the affected code is outside the OpenSSL FIPS module boundary.", "cve_priority": "medium", "cve_public_date": "2026-08-05 15:16:00 UTC" } ], "log": [ "", " * Import 4.0.2", " - CVE-2026-18798 (\"QUIC Server May Trigger Double Free When Processing", " INITIAL Packet\")", " - CVE-2026-63072 (\"Heap Buffer Overflow in CMS Key Unwrapping\")", " - CVE-2026-63076 (\"Invalid Pointer Dereference in CMP Server via Crafted", " protectionAlg\")", " - CVE-2026-14457 (\"RPK Server Signature Algorithm Selection Can Dereference", " a Missing Certificate\")", " - CVE-2026-54874 (\"Excessive Memory Use Buffering DTLS Records for a Future", " Epoch\")", " - CVE-2026-63073 (\"Untrusted Sender DN Used as Format String in CMP Response", " Validation\")", " - CVE-2026-63074 (\"CMP Indefinite Cache Growth of ExtraCerts\")", " - CVE-2026-63075 (\"QUIC ACK-only Packet Retention Can Cause Memory", " Exhaustion\")", " - CVE-2026-75803 (\"AEAD Forgeries with Empty Ciphertext When Using", " EVP_Cipher()\") (Closes: #1145172)", " - CVE-2026-14456 (\"Unbounded Memory Growth in QUIC Server Incoming Channel", " Queue\") (Closes: #1144615)", " - CVE-2026-54876 (\"Client-Side Memory Leak in OCSP Response Checking\") (Closes: #1143841)", "" ], "package": "openssl", "version": "4.0.2-1", "urgency": "medium", "distributions": "experimental", "launchpad_bugs_fixed": [], "author": "Sebastian Andrzej Siewior ", "date": "Tue, 25 Aug 2026 21:19:42 +0200" } ], "notes": null, "is_version_downgrade": false }, { "name": "openssl-provider-legacy", "from_version": { "source_package_name": "openssl", "source_package_version": "4.0.1-1ubuntu4", "version": "4.0.1-1ubuntu4" }, "to_version": { "source_package_name": "openssl", "source_package_version": "4.0.3-1ubuntu1", "version": "4.0.3-1ubuntu1" }, "cves": [ { "cve": "CVE-2026-84782", "url": "https://ubuntu.com/security/CVE-2026-84782", "cve_description": "Issue summary: The DTLS retransmission logic does not correctly handle a handshake message write that is suspended part-way through. The retransmitted message can be read past the message buffer and the retransmission overwrites the internal state the suspended write needs to resume correctly. Impact summary: The retransmitted message can disclose a heap memory to the peer as plaintext handshake data or cause a crash and a Denial of Service when the read reaches an unmapped memory region. CWE: CWE-125: Out-of-bounds Read Description: DTLS handshake messages can be written out in multiple fragments, and a write can suspend mid-message (returning WANT_WRITE) if the underlying transport temporarily cannot accept more data. While such a write is suspended, the DTLS retransmission timer may independently fire and ask the retransmission logic to resend an earlier, already-acknowledged-as-sent message from its retransmit queue. The retransmission logic reused the same internal buffer and position tracking as the message that was still being written, without resetting the position back to the start of the message being retransmitted. As a result the retransmission was read starting from wherever the suspended write had left off, producing a mislabelled message whose body was leftover bytes from the other, larger message still in flight - content that was never meant to be sent at that point, and which could run past the end of the allocated buffer. Separately, even when the retransmission is positioned correctly, allowing it to run to completion while another write is suspended overwrites the same shared bookkeeping that the suspended write depends on to resume. When the application later resumes the suspended write (via a subsequent SSL_read(), SSL_write(), SSL_accept(), or SSL_connect() call), it finds that bookkeeping in a state inconsistent with the message and aborts the process in a debugging build. The fix resets the retransmission's read position to the start of the message before resending, and skips retransmission entirely whenever a handshake write is still suspended, deferring to the next call that resumes it instead. FIPS impact: no The affected code is outside the FIPS module boundary.", "cve_priority": "high", "cve_public_date": "2026-09-29 16:17:00 UTC" }, { "cve": "CVE-2026-35189", "url": "https://ubuntu.com/security/CVE-2026-35189", "cve_description": "Issue summary: A certificate with many nameRelativeToCRLIssuer CRL distribution points causes disproportionate heap growth when OpenSSL caches X.509 extensions. Impact summary: Receiving a crafted certificate from a malicious peer can lead to significant memory pressure and possible Denial of Service in clients or in servers that solicit client certificates. CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: A certificate or a set of certificates that fits under the limit for size of certificates accepted from the peer (~100 KiB) can result in allocation of several hundred MiB of resident memory on the receiving side during a normal TLS handshake. This may be enough to crash the client or server, if multiple concurrent connections lead to similarly large memory allocations. The fix postpones processing of the CRL distribution points extensions in certificates to the time when the processed value is required for CRL processing. This avoids keeping large memory allocations for a long time when such certificates are received. FIPS impact: no The affected code is outside the FIPS module boundary.", "cve_priority": "low", "cve_public_date": "2026-09-29 16:17:00 UTC" }, { "cve": "CVE-2026-35191", "url": "https://ubuntu.com/security/CVE-2026-35191", "cve_description": "Issue summary: The OpenSSL QUIC server, when configured to not preform address validation, can be forced to count incoming packets multiple times in its unvalidated credit computation, leading to a violation of the RFC 9000 unvalidated connection amplification limit of 3 times the amount of data received. Impact summary: A remote attacker able to spoof packets to a server using the OpenSSL QUIC implementation might use the server for an amplification of a DDoS attack. CWE: CWE-440: Expected Behavior Violation Description: OpenSSL's QUIC stack, when operating as a server, enforces client address validation (RFC 9000, Section 8), to confirm the peer address is not used for a traffic amplification attack. If this feature is disabled on the server, the QUIC stack limits the amount of server data that can be sent to 3 times the amount of data received from the peer address, until such time as the TLS handshake is completed. The OpenSSL QUIC server, when operating in non-validation mode, adds the length of the whole datagram received to the unvalidated credit limit when processing each QUIC packet in the datagram. A remote peer may, after establishing a connection with an initial client hello frame, send a subsequent datagram containing multiple QUIC packets, leading the server to account the entire datagram length for each packet in the datagram, resulting in the server believing that the peer has sent more data than it actually has, thereby violating the 3x amplification limit mandated by the RFC. FIPS impact: no As the QUIC stack lives outside the FIPS module boundary, no FIPS modules are affected by this CVE.", "cve_priority": "low", "cve_public_date": "2026-09-29 16:17:00 UTC" }, { "cve": "CVE-2026-42772", "url": "https://ubuntu.com/security/CVE-2026-42772", "cve_description": "Issue summary: The QUIC stream reassembly algorithm performance deteriorates progressively as packets are arriving out of order. The worst case has a quadratic complexity proportional to the number of stream frames kept in the buffer for the received stream data. Impact summary: A remote QUIC peer that completes the handshake can create a connection-scoped CPU pressure and potentially a Denial of Service using compliant STREAM frames inside the advertised receive window, with low attacker bandwidth. CWE: CWE-407: Inefficient Algorithmic Complexity Description: OpenSSL manages received QUIC stream fragments using a doubly-linked list. While it optimizes for append operations (at the end of the list), it falls back to a head-to-tail linear search for any fragment that does not immediately follow the current `tail`. By manipulating the sequence of offsets, an attacker can force the server to perform O(n^2) operations, consuming excessive CPU time for the QUIC process. FIPS impact: no The FIPS module is not affected as the QUIC implementation is outside of the OpenSSL FIPS module boundary.", "cve_priority": "low", "cve_public_date": "2026-09-29 16:17:00 UTC" }, { "cve": "CVE-2026-54872", "url": "https://ubuntu.com/security/CVE-2026-54872", "cve_description": "Issue summary: The generic elliptic-curve scalar multiplication used for ECDSA and SM2 signature operations with curves that do not have a dedicated implementation leaks information about the secret nonce through timing. Impact summary: An attacker able to measure signing times may learn information about the per-signature secret nonce, which over many signatures can, via a lattice / Hidden Number Problem attack, lead to recovery of the private key. CWE: CWE-208: Observable Timing Discrepancy Description: The generic elliptic-curve scalar multiplication used for curves that do not have a dedicated constant-time implementation pads the secret scalar with non-constant-time BIGNUM operations, so the time taken depends on the value of the secret scalar derived from the ECDSA and SM2 nonce. The leak is very small; observing it requires a large number of measurements. The effect is largest for curves whose group order lies on a machine-word boundary, such as brainpoolP384r1. Applications using ECDSA signing over the Brainpool and other generic prime curves, and SM2 signing on platforms that use the generic implementation, are vulnerable to this issue. The NIST curves P-256, P-384 and P-521 use dedicated constant-time implementations and are not affected. FIPS Impact: no The FIPS modules are not affected: the approved NIST curves used in the FIPS provider have dedicated constant-time implementations and do not use the affected code path.", "cve_priority": "low", "cve_public_date": "2026-09-29 16:17:00 UTC" }, { "cve": "CVE-2026-54873", "url": "https://ubuntu.com/security/CVE-2026-54873", "cve_description": "Issue summary: QUIC process may keep memory for QUIC packet buffer for much longer period than necessary. Impact summary: Remote peer can exploit this vulnerability by sending maliciously crafted packets, making the local QUIC stack to keep the memory for packet buffers allocated. The time for which the memory remains allocated is entirely under the control of the potentially malicious remote peer. CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: To save copy operation from the packet buffer to the stream reassemble buffer the QUIC stack leaves the stream data on the packet buffer waiting to be copied to a buffer provided by the local receiving application. The QUIC stack releases a reference to the packet buffer only after the data are copied to the application buffer. This design is more efficient for legitimate data transfers but enables an attacker to allocate a lot more memory than actually required by the data kept in the receiving stream buffer. To mitigate the vulnerability, the QUIC stack now calculates and monitors memory overhead for every stream. The memory overhead for a single stream frame is calculated as a difference between the size of the whole packet that carries the stream frame and the size of the stream frame itself. The memory overhead for a single stream frame is added to the total (cumulative) memory overhead QUIC stack keeps for each stream. Once the cumulative memory overhead exceeds 64kB, the QUIC stack moves the stream frame data from the packet buffer to the stream buffer, starting with the next packet received. FIPS impact: no The FIPS module is not affected as the QUIC implementation is outside of the OpenSSL FIPS module boundary.", "cve_priority": "low", "cve_public_date": "2026-09-29 16:17:00 UTC" }, { "cve": "CVE-2026-54875", "url": "https://ubuntu.com/security/CVE-2026-54875", "cve_description": "Issue summary: A non-constant-time optimized implementation of scalar point multiplication is used for SM2 private key operations on ARM64 and RISC-V platforms. Impact summary: An attacker able to measure the time taken by, or to observe the cache-line access pattern of SM2 signing or decryption on an affected platform can learn information about the secret scalar. CWE: CWE-208: Observable Timing Discrepancy Description: On ARM64 and RISC-V processors, the SM2 curve uses an optimized scalar multiplication implementation whose conditional branches and table look ups are chosen according to the bits of the secret scalar. The execution time and the cache-access pattern therefore depend on the long-term private key (during SM2 decryption) or the per-signature nonce (during SM2 signature generation), forming a timing and cache side-channel. FIPS Impact: no SM2 is not a FIPS algorithm and the optimized SM2 implementation is not part of the FIPS module. OpenSSL 4.0, 3.6, 3.5 and 3.4 are vulnerable to this issue on AArch64 and RISC-V. OpenSSL 3.0, 1.1.1 and 1.0.2 are not affected by this issue. OpenSSL 4.0 users should upgrade to OpenSSL 4.0.3. OpenSSL 3.6 users should upgrade to OpenSSL 3.6.5. OpenSSL 3.5 users should upgrade to OpenSSL 3.5.9. OpenSSL 3.4 users should upgrade to OpenSSL 3.4.8. This issue was reported on 2 May 2026 by Abhinav Agarwal. It was independently reported on 6 June 2026 by Feng Xue. The fix was developed by Igor Ustinov. -- cut (non-publishing metadata for internal use) -- Reported by: Abhinav Agarwal, Feng Xue Fixed by: Igor Ustinov", "cve_priority": "low", "cve_public_date": "2026-09-29 16:17:00 UTC" }, { "cve": "CVE-2026-72897", "url": "https://ubuntu.com/security/CVE-2026-72897", "cve_description": "Issue summary: A TLS server that calls SSL_set_SSL_CTX() to switch a connection to a different SSL_CTX part way through a handshake may access memory beyond the end of an internal array if the replacement context knows about more provider signature algorithms than the context the connection was created from. Applications which never call SSL_set_SSL_CTX() are not affected. Impact summary: A remote peer may be able to cause a small out-of-bounds read, and in some circumstances a fixed-value out-of-bounds write, on the server heap. This may lead to a Denial of Service. CWE: CWE-787: Out-of-bounds Write Description: A TLS connection records how many certificate slots it has when it is created, taken from the SSL_CTX that created it: the built-in certificate types plus one slot for each provider TLS-SIGALG entry that context was aware of. That count sizes an internal array of per-slot certificate validity flags. An application may replace a connection's SSL_CTX part way through the handshake by calling SSL_set_SSL_CTX(), most commonly from a servername callback in order to serve a different virtual host. Doing so did not refresh the recorded count. A provider signature algorithm's slot index is its position in the list of whichever context resolves it, so if the replacement context is aware of more of them than the original, an algorithm offered by the peer can resolve to an index beyond the end of the array. Processing the peer's signature algorithms then reads one four byte word past the end for each such algorithm and, where the word read is zero, writes a fixed value over it. A peer offering many of them can corrupt heap metadata and abort the process. Only provider signature algorithms which occupy one of the excess slots, and which the server also has configured, have this effect. Codepoints the replacement context does not recognise are discarded without being resolved to a slot, and provider signature algorithms are usable only from TLS 1.3. The two contexts must therefore be aware of different numbers of provider signature algorithms, which requires separate library contexts, a provider loaded between the two being created, or providers which differ in what they advertise - in 4.0, for example, the default provider advertises SM2 where the FIPS provider does not. A deployment meeting the condition is also unable to negotiate the affected algorithms with legitimate clients, since the same stale count hides the corresponding certificates, so the misconfiguration is likely to be noticed. For that reason, and because the configuration is not the default, this issue has been assessed as Low severity. FIPS impact: no No FIPS modules are affected by this issue as the affected code is outside the OpenSSL FIPS module boundary.", "cve_priority": "low", "cve_public_date": "2026-09-29 16:17:00 UTC" }, { "cve": "CVE-2026-75804", "url": "https://ubuntu.com/security/CVE-2026-75804", "cve_description": "Issue summary: OpenSSL QUIC stack does not enforce connection level flow control for streams. Remote peers may send more bytes as long as they fit within the stream flow control limits. Impact summary: A malicious remote peer may exploit the lack of connection flow control for streams to make the QUIC stack receive ~100MB of memory instead of 768 KiB (default flow control window size). CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: The local QUIC stack advertises two flow control limits to its remote peer: stream flow control limit and connection flow control limit. The remote peer must follow both limits when transmitting stream data. Whenever the local QUIC stack receives a stream frame, it validates that the size of the received stream frame stays within flow control limits. If either limit is exceeded (stream level or connection level), then the QUIC stack must close the connection with a flow control error. The vulnerable OpenSSL QUIC stack enforces the stream-level but not the connection-level limit. To exploit the issue, three conditions must be met: - the remote peer opens several streams - each stream must stay within the stream-level flow control limit - there must be no zero-offset byte sent on any of the streams (to prevent the vulnerable QUIC stack from consuming data). By meeting the conditions above, the remote peer may make the local stack allocate 2 x MAX_STREAMS x (stream flow control limit) bytes of memory. MAX_STREAMS defaults to 100, and the limit applies to both bidirectional and unidirectional streams, making it 200 in total. The default flow control window for a stream is 512kB. The remote peer may force the vulnerable QUIC stack to allocate 100MB of heap per connection. FIPS impact: no The FIPS module is not affected as the QUIC implementation is outside of the OpenSSL FIPS module boundary.", "cve_priority": "low", "cve_public_date": "2026-09-29 16:17:00 UTC" }, { "cve": "CVE-2026-75805", "url": "https://ubuntu.com/security/CVE-2026-75805", "cve_description": "Issue summary: A CMP client that requests certificate revocation on the basis of a PKCS#10 CSR may dereference a NULL pointer and terminate abnormally when processing a crafted revocation response. Impact summary: The NULL pointer dereference happens on a read which leads to a crash and a Denial of Service for the affected client application. CWE: CWE-476: NULL-pointer dereference Description: A CMP client revoking a certificate has to tell the server which certificate to revoke, and may do so by supplying a PKCS#10 CSR instead of the certificate itself or its issuer name and serial number. This is 'openssl cmp -cmd rr -csr ' on the command line, or OSSL_CMP_exec_RR_ses() with the certificate supplied via OSSL_CMP_CTX_set1_p10CSR() through the API. A CSR does not contain the issuer name and serial number of the certificate, so the client does not send them. A server may optionally name the certificate it revoked in its response, and the client then compares that name against what it sent. Having sent neither an issuer name nor a serial number, it has nothing to compare against, and a server returning a specially crafted name causes the client to read from a NULL pointer and crash. The revocation response is checked for valid message protection before the affected code is reached, so an attacker must be a malicious or compromised CMP server, or a man-in-the-middle in possession of the secret used for message protection. Clients that identify the certificate to be revoked by a certificate or by issuer and serial number rather than by a PKCS#10 CSR are not affected. FIPS impact: no No FIPS modules are affected by this issue, as the CMP protocol implementation is outside the OpenSSL FIPS module boundary.", "cve_priority": "low", "cve_public_date": "2026-09-29 16:17:00 UTC" }, { "cve": "CVE-2026-75806", "url": "https://ubuntu.com/security/CVE-2026-75806", "cve_description": "Issue summary: An established DTLS 1.2 association using an AEAD cipher suite can be terminated by a single unauthenticated datagram whose encrypted fragment is shorter than the mandatory explicit IV and authentication tag overhead. Impact summary: An attacker who can send a datagram that is routed to an existing DTLS 1.2 association can tear that association down without knowing any key material. This is a Denial of Service limited to the targeted association. There is no memory safety or confidentiality impact. CWE: CWE-1284: Improper Validation of Specified Quantity in Input Description: In TLS 1.2 and DTLS 1.2 every record protected by an AEAD cipher suite carries an explicit IV followed by the ciphertext and an authentication tag. When decrypting such a record the record layer passed the record length to the cipher implementation before checking that the record was long enough to contain the explicit IV and the tag. For a record shorter than that overhead the cipher implementation rejected the impossible length, and the record layer treated this as an internal failure and raised a fatal internal_error alert instead of treating the record as one that failed authentication. In TLS 1.2 the same record causes a fatal internal_error alert instead of the expected bad_record_mac alert. Since any undecryptable record already terminates a TLS connection, this is a protocol conformance issue rather than a security issue in TLS. The fix validates the record length against the explicit IV and tag length before any AEAD processing, so that TLS reports bad_record_mac and DTLS silently discards the record. FIPS impact: no The affected code is outside the FIPS module boundary.", "cve_priority": "low", "cve_public_date": "2026-09-29 16:17:00 UTC" }, { "cve": "CVE-2026-77696", "url": "https://ubuntu.com/security/CVE-2026-77696", "cve_description": "Issue summary: SM2 signature generation uses non-constant-time arithmetic on secret values, forming a timing side-channel. Impact summary: An attacker able to measure SM2 signing times may learn information about the per-signature secret nonce, which over many signatures can, via a lattice / Hidden Number Problem attack, lead to recovery of the private key. CWE: CWE-208: Observable Timing Discrepancy Description: SM2 signature generation computes the signature value using variable-time BIGNUM operations on the secret nonce and the private key, so the time taken to produce an SM2 signature depends on these secret values, forming a timing side-channel. Applications performing SM2 signature generation are affected on all platforms. FIPS Impact: no SM2 is not a FIPS algorithm.", "cve_priority": "low", "cve_public_date": "2026-09-29 16:17:00 UTC" }, { "cve": "CVE-2026-84783", "url": "https://ubuntu.com/security/CVE-2026-84783", "cve_description": "Issue summary: The first concurrent use of the same X.509 certificate by several threads may cause its cached extension data to be freed while another thread is still using it. Impact summary: A remote, unauthenticated peer could crash a multi-threaded TLS client, or a multi-threaded TLS server that requests client certificates, if the first certificate chains built to the same trusted CA certificate are built by several connections at the same time. This is a use-after-free read, which is likely to crash the process, resulting in a Denial of Service. CWE: CWE-416: Use After Free Description: OpenSSL caches the decoded values of a certificate's X.509v3 extensions inside the X509 object the first time they are needed. In OpenSSL 4.0 this cache is built in two phases: the extension values are computed while holding a read lock on the certificate, and the results are then installed into the certificate under a write lock. Because a read lock does not exclude other readers, several threads can compute the cache for the same certificate at the same time. Each thread that subsequently acquires the write lock installs its own results and frees the values installed by the thread before it, even though that earlier thread has already marked the cache as complete and may have returned pointers into it to its caller. A caller still using those pointers then reads freed memory. Any certificate shared between threads is exposed the first time its extensions are decoded. In TLS the certificates at risk are the trusted CA certificates supplied for chain verification, by whatever means, since these are shared by every connection and their extensions are decoded and cached the first time a chain is built to them. Certificates sent by the peer are decoded separately for each connection and are not shared, so they are not affected. In a TLS client verifying server certificates, or a TLS server that requests and verifies client certificates, the use-after-free could only occur if the first chains built to the same trusted CA are built by several connections at the same time. FIPS impact: no The FIPS module is not affected as X.509 certificate handling is outside of the OpenSSL FIPS module boundary. OpenSSL 4.0 is vulnerable to this issue. OpenSSL 3.6, 3.5, 3.4, 3.0, 1.1.1 and 1.0.2 are not affected by this issue. OpenSSL 4.0 users should upgrade to OpenSSL 4.0.3. This issue was reported on 27 August 2026 by Tim Becker (Xint.io) and independently in a public report on 31 August 2026 by aydinmercan. The fix has been developed by Bob Beck. -- cut (non-publishing metadata for internal use) -- Reported by: Tim Becker (Xint.io), aydinmercan Fixed by: Bob Beck", "cve_priority": "medium", "cve_public_date": "2026-09-29 16:17:00 UTC" }, { "cve": "CVE-2026-84784", "url": "https://ubuntu.com/security/CVE-2026-84784", "cve_description": "Issue summary: A malicious remote peer may flood the local QUIC stack with NEW_CONNECTION_ID frames by avoiding a limit check on how many connection IDs the remote QUIC stack can use. Impact summary: The local QUIC stack sends a RETIRE_CONN_ID frame for every NEW_CONNECTION_ID frame it receives. The RETIRE_CONN_ID frame is dispatched via the Control Frame Queue (CFQ). If the remote peer also withholds ACKs, then it can force the local stack to allocate ~400MB (depending on ACK delay). CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: RFC 9000 sections 5.1.1 and 5.1.2 [1] describe the mechanism by which a remote peer can notify the local QUIC stack to change the destination connection ID (a.k.a. CID) the local stack uses to identify the connection at the remote peer. Each CID is associated with a sequence number. The sequence number is transmitted in NEW_CONNECTION_ID and RETIRE_CONNECTION_ID frames to identify the CID which is being either associated with a connection or retired. The remote peer sends a NEW_CONNECTION_ID frame to let the local stack know a new CID is being associated with an existing connection. The NEW_CONNECTION_ID frame carries the new CID, its sequence number, and the retire-prior-to number. The retire-prior-to identifies existing CIDs that are to be retired. The local QUIC stack must send a RETIRE_CONNECTION_ID for every destination CID whose sequence number is less than retire-prior-to. The CID becomes retired after the local stack receives an ACK for its RETIRE_CONNECTION_ID frame. Although the OpenSSL QUIC stack supports at most one destination CID for every connection, it can be tricked into processing more than one RETIRE_CONNECTION_ID frame per connection. The OpenSSL QUIC stack currently retires the destination CID as soon as it receives the NEW_CONNECTION_ID, while in fact the destination CID must be retired after an ACK for the RETIRE_CONNECTION_ID frame is received. Correcting the flawed logic also fixes the backlog growth. [1] https://datatracker.ietf.org/doc/html/rfc9000#name-issuing-connection-ids FIPS impact: no The FIPS module is not affected as the QUIC implementation is outside of the OpenSSL FIPS module boundary.", "cve_priority": "low", "cve_public_date": "2026-09-29 16:17:00 UTC" }, { "cve": "CVE-2026-18798", "url": "https://ubuntu.com/security/CVE-2026-18798", "cve_description": "Issue summary: QUIC server may double free QRX (QUIC record layer RX) object when channel creation fails for initial packet. Impact summary: Double free leads to heap corruption, which typically results in termination of QUIC server process, leading to Denial of Service. There is so far no evidence that this double free is exploitable for remote code execution, thus it is considered highly improbable. CWE: CWE-415: Double Free Description: In order to validate initial packet, OpenSSL QUIC stack default packet handler (port_default_packet_handler()) creates a so-called QRX object. If the initial packet validates successfully with QRX object, the default packet handler proceeds to channel (connection object) creation. The QRX object used for packet validation is passed to port_bind_channel(), so it becomes part of the newly created connection. If port_bind_channel() fails, then it also frees the QRX object. Once port_bind_channel() returns, the port_default_packet_handler() detects the failure and proceeds to the error branch, where the same QRX object is freed for the second time. The failure in port_bind_channel() function can be induced with a relatively low effort by a malformed (non RFC 9000 compliant) INITIAL packet. If the packet carries DCID (destination connection ID) which is shorter than 8 bytes, then port_bind_channel() jumps to the error path after ossl_quic_lcidm_enrol_odcid() detects that the DCID has invalid length. FIPS impact: no The FIPS module is not affected, as the QUIC implementation is outside of the OpenSSL FIPS module boundary.", "cve_priority": "medium", "cve_public_date": "2026-08-25 13:17:00 UTC" }, { "cve": "CVE-2026-63072", "url": "https://ubuntu.com/security/CVE-2026-63072", "cve_description": "Issue summary: OpenSSL CMS decryption sizes the key-unwrap output buffer based on querying the unwrapped key size, but the AES-WRAP-PAD unwrap primitive can write and cleanse more bytes than that query reports, causing an 8-byte out-of-bounds heap write. Impact summary: An attacker who supplies a crafted CMS message can trigger a deterministic 8-byte out-of-bounds heap write when the victim decrypts it with CMS_decrypt(), corrupting the heap and typically resulting in a Denial of Service. CWE: CWE-787: Out-of-bounds Write Description: The key-wrap OID is potentially attacker-controlled on the wire. CMS unwrapping allows both id-aesNNN-wrap-pad and id-aesNNN-wrap ciphers. An attacker can take a legitimate message and change a single OID byte to select the padded variant while leaving the message otherwise valid. Since the unwrap key is derived from the recipient's private operation (ECDH key agreement or ML-KEM decapsulation), the RFC 5649 integrity check cannot pass, and the decryption fails with integrity failure. The write is a fixed-size (8-byte), fixed-value (zero) heap overflow immediately past the allocation, requires no special configuration, and is reachable from the public CMS_decrypt() function. The consequence is a heap corruption leading to a Denial of Service. The fix in the CMS code sizes the unwrap output buffer for the worst case so a failed unwrap cannot write past the allocation. FIPS impact: no As the CMS code lives outside the FIPS module boundary, no FIPS modules are affected by this CVE.", "cve_priority": "medium", "cve_public_date": "2026-08-25 13:19:00 UTC" }, { "cve": "CVE-2026-63076", "url": "https://ubuntu.com/security/CVE-2026-63076", "cve_description": "Issue summary: OpenSSL CMP password based protection verification only checks whether the protectionAlg parameter was not NULL and not its ASN.1 type, before treating it as a PBMParameter. A crafted message can contain a parameter of a different type, which is then dereferenced as an invalid pointer. Impact summary: A remote, unauthenticated attacker can crash an application acting as a CMP server that accepts PBM-protected messages, or a CMP client talking to a malicious or intercepted CMP server, resulting in a Denial of Service. CWE: CWE-476: NULL Pointer Dereference Description: When verifying the password-based MAC protection of a CMP message, OpenSSL library reads the protectionAlg algorithm parameter with X509_ALGOR_get0(), which returns both the parameter type and its value pointer. The value is then cast to an ASN1_STRING and treated as the expected PBMParameter after only checking that pointer is not NULL. The parameter type returned by X509_ALGOR_get0() was never consulted. This happens during protection verification, before any MAC is computed, so no knowledge of the PBM shared secret is required; the only precondition is that PBM verification is reachable. On the server side this is reached from OSSL_CMP_SRV_process_request() for any application that stands up a CMP server accepting PBM-protected messages, and on the client side from CMP response validation against a malicious or on-path (MITM) server. The reliable consequence is a denial of service; there is no memory disclosure, no controlled memory write, and no path to code execution. CMP is a specialized feature that an application must explicitly enable. FIPS impact: no As the CMP code lives outside the FIPS module boundary, no FIPS modules are affected by this CVE.", "cve_priority": "medium", "cve_public_date": "2026-08-25 13:19:00 UTC" }, { "cve": "CVE-2026-14457", "url": "https://ubuntu.com/security/CVE-2026-14457", "cve_description": "Issue summary: In a server or client configuration with RFC7250 Raw Public Keys (RPKs) enabled, and only the private key (with no associated certificate) configured locally, a NULL pointer dereference may occur when the remote peer solicits raw public keys and also sends the typically omitted \"signature_algorithms_cert\" TLS extension. Impact summary: The impact is limited to a possible Denial of Service as a result of an application abort, no data disclosure or remote command execution are possible. CWE: CWE-476: NULL Pointer Dereference Description: While a passing comment in sample code in the documentation suggests that key-only RPK configurations are supported, the best-practice RPK configuration is to always configure a corresponding certificate (possibly self-signed or signed by any convenient CA). When the private key is configured along with a matching certificate, the \"signature_algorithms_cert\" extension is handled reliably even without the fix, and peer clients or servers that don't support raw public keys may be able to complete a TLS connection by pinning or verifying the corresponding certificate or its public key. Deployments that prefer to configure just a private key with no certificate need to upgrade to an updated release as noted below. FIPS impact: no No FIPS modules are affected by this issue, as the SSL protocol implementation is outside the OpenSSL FIPS module boundary.", "cve_priority": "low", "cve_public_date": "2026-08-25 13:17:00 UTC" }, { "cve": "CVE-2026-54874", "url": "https://ubuntu.com/security/CVE-2026-54874", "cve_description": "Issue summary: Receiving a DTLS record for a future epoch while a handshake is in progress causes OpenSSL to buffer far more memory than the record itself requires. Impact summary: A peer can use a small amount of network traffic to make an OpenSSL DTLS endpoint retain a disproportionately large amount of memory, which may lead to a Denial of Service. CWE: CWE-405: Asymmetric Resource Consumption (Amplification) Description: While a DTLS handshake is in progress, a peer may legitimately have already moved on to the next epoch (for example, having sent its ChangeCipherSpec and Finished messages) before the local endpoint has processed the same transition, typically because of reordering on the underlying UDP transport. OpenSSL buffers such early records so that they can be processed once the local endpoint catches up. Buffering a record currently retains the entire read buffer it arrived in, which is sized to hold the largest possible DTLS record (around 16 kilobytes), rather than just the bytes that make up the record itself. Up to 100 such records may be buffered per connection. As a result, a peer that sends a stream of small forged records claiming to belong to the next epoch can cause an OpenSSL DTLS endpoint to retain around 1.7 megabytes of memory, despite sending only a small fraction of that amount of data over the network. An attacker therefore gains a memory amplification factor of around 1200, and can multiply the effect across as many associations as it is able to open, making this a remote memory exhaustion Denial of Service risk for DTLS servers. Since the memory retained per connection remains bounded, and any limit an application already places on the number of concurrent associations also bounds the total exposure, this issue has been assessed as Low severity. FIPS impact: no No FIPS modules are affected by this issue as the affected code is outside the OpenSSL FIPS module boundary. OpenSSL 4.0, 3.6, 3.5, 3.4, 3.0, 1.1.1 and 1.0.2 are vulnerable to this issue. OpenSSL 4.0 users should upgrade to OpenSSL 4.0.2. OpenSSL 3.6 users should upgrade to OpenSSL 3.6.4. OpenSSL 3.5 users should upgrade to OpenSSL 3.5.8. OpenSSL 3.4 users should upgrade to OpenSSL 3.4.7. OpenSSL 3.0 users should upgrade to OpenSSL 3.0.22. Premium support customers only: OpenSSL 1.1.1 users should upgrade to OpenSSL 1.1.1zi OpenSSL 1.0.2 users should upgrade to OpenSSL 1.0.2zr This issue was reported on 18 May 2026 by Amazon Web Services. The fix has been developed by Matt Caswell. -- cut (non-publishing metadata for internal use) -- Reported by: Amazon Web Services Fixed by: Matt Caswell", "cve_priority": "low", "cve_public_date": "2026-08-25 13:19:00 UTC" }, { "cve": "CVE-2026-63073", "url": "https://ubuntu.com/security/CVE-2026-63073", "cve_description": "Issue summary: OpenSSL CMP response validation passed an unexpected response sender distinguished name directly as the format string to `ERR_raise_data()`. Impact summary: A malicious or intercepted CMP endpoint can crash a CMP client that enforces an expected sender or uses a pinned server certificate whose subject becomes the default expected sender. CWE: CWE-134 (Use of Externally-Controlled Format String) Description: When validating a received CMP message, ossl_cmp_msg_check_update() converts the peer-supplied sender distinguished name with X509_NAME_oneline() and passes it directly as the format argument to ERR_raise_data(). Percent characters survive the conversion, so a sender DN such as \"CN=%s%n\" reaches BIO_vsnprintf() as an attacker-controlled format string with no matching variadic arguments. This path is only reached when the caller configures an expected sender or pins a server certificate, which is the normal configuration for a CMP client validating server responses. Since the attacker controls the format string but none of the variadic arguments, such specifiers as %s and %n dereference or write through unrelated stack contents and crash the client. The reliable consequence is a denial of service, when the response comes from a malicious or intercepted CMP endpoint. There is no controlled memory write, arbitrary-address read, or reliable path to remote code execution. FIPS impact: no No FIPS modules are affected by this issue, as the CMP protocol implementation is outside the OpenSSL FIPS module boundary.", "cve_priority": "low", "cve_public_date": "2026-08-25 13:19:00 UTC" }, { "cve": "CVE-2026-63074", "url": "https://ubuntu.com/security/CVE-2026-63074", "cve_description": "Issue summary: The OpenSSL Certificate Management Protocol (CMP) caches additional certificates (extraCerts) sent in a CMP message, but never expunges them (for instance if they are invalid). If a server reuses an OSSL_CMP_CTX frequently, this cache of extraCerts may grow unboundedly, and a malicious client may flood a CMP server with requests driving this growth. Impact summary: Users utilizing a CMP server that reuses a single OSSL_CMP_CTX for the lifetime of a server process may observe unbounded memory growth in the event a malicious client repeatedly sends requests containing unique extra certificates, which may lead to OOM conditions. CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: If a remote user sends CMP messages to a server with a list of extraCerts and the message is rejected, the extraCerts from the message remains in the server contexts untrusted certificate stack. This exposes servers with long lived ctx objects to Denial of Service attacks in which an attacker sends messages intending to be rejected with a large list of additional certificates repeatedly, forcing the server to store them indefinitely. The issue was fixed by removing the added extra certs if the message is rejected, using the same method as when the context is configured to not do caching at all. FIPS impact: no As the CMP code lives outside the FIPS module boundary, no FIPS modules are affected by this CVE.", "cve_priority": "low", "cve_public_date": "2026-08-25 13:19:00 UTC" }, { "cve": "CVE-2026-63075", "url": "https://ubuntu.com/security/CVE-2026-63075", "cve_description": "Issue summary: When OpenSSL processes QUIC traffic from a peer that repeatedly sends ack-eliciting packets while not acknowledging ACK-only responses, the QUIC stack can retain ACK-only packet metadata for the lifetime of the connection. Impact summary: A remote peer that can complete a QUIC handshake can cause connection-scoped memory growth which may lead to Denial of Service through memory exhaustion, especially with sustained traffic or many concurrent QUIC connections. CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: When the OpenSSL QUIC stack sends an ACK-only packet, there is no requirement by the QUIC protocol that the peer will acknowledge that ACK-only packet (i.e. it is itself not ack-eliciting). However, the OpenSSL implementation stores the metadata about the ACK frames regardless. In and of itself that's ok, but if a malicious peer establishes a connection, and then drives the connection such that ACK-only packets are forced from the OpenSSL implementation peer (i.e., by sending numerous PING frames), and then withholding any subsequent acks for ack-eliciting data, like legitimate data, said malicious peer can force inappropriate memory growth on the OpenSSL peer, potentially leading to a Denial of Service. The fix is to ensure that we account for the transmission of the ACK-only packet in the packet histories high and low watermark without actually storing the ACK-only packet metadata itself. FIPS impact: no The OpenSSL FIPS module is not affected as the QUIC code is outside the FIPS module boundary.", "cve_priority": "low", "cve_public_date": "2026-08-25 13:19:00 UTC" }, { "cve": "CVE-2026-75803", "url": "https://ubuntu.com/security/CVE-2026-75803", "cve_description": "Issue summary: ChaCha20-Poly1305 and AES-OCB decryption with an empty ciphertext can report success without verifying the supplied authentication tag when the operation is finalized by calling the EVP_Cipher() function. Impact summary: Applications calling EVP_Cipher() on an empty ciphertext and expecting the call to check the AEAD tag may accept forged messages. CWE: CWE-354 (Improper Validation of Integrity Check Value) Description: The EVP_Cipher() API call for AEAD ciphers behaves like a one shot encryption and decryption call. It also verifies the AEAD tag after the decryption operation. However for AES-OCB and ChaCha20-Poly1305 ciphers it skipped the AEAD tag verification when an empty ciphertext was passed to the function. The callers of this function might believe that a successful return indicates a valid AEAD tag for these ciphers, even when that has not truly been validated in this case. FIPS impact: no The FIPS modules in 4.0, 3.6, 3.5, 3.4, and 3.0 are not affected by this CVE as the affected algorithms are not FIPS approved and thus not implemented in the FIPS module.", "cve_priority": "low", "cve_public_date": "2026-08-25 13:19:00 UTC" }, { "cve": "CVE-2026-14456", "url": "https://ubuntu.com/security/CVE-2026-14456", "cve_description": "Issue summary: When an OpenSSL QUIC server (Listener SSL object) processes valid QUIC Initial packets for unknown destination connection IDs, it can allocate and queue new incoming channels without enforcing any limit. Impact summary: A remote peer that can make many Initial packets reach the server listener faster than the application accepts connections, can cause the memory allocated to store the per-channel state to grow without any limits, potentially making the QUIC listener unavailable and causing Denial of Service. CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: The function that handles inbound QUIC packets uses Connection-Id from the packet header to find an existing connection (QUIC channel). If no existing connection is found and the packet type is INITIAL, the function treats the packet as a new connection. It allocates a new channel object and inserts it into a queue where it waits to be accepted by the local application with SSL_accept(3ossl). The memory occupied by these initial channel objects may grow without bounds if the application is not able to call SSL_accept() frequently enough to serve these inbound connection requests. The issue is present since OpenSSL 3.5 when the QUIC server implementation was added. The fix introduces a limit for pending connections. The default limit is set to 256 pending connections (waiting to be accepted by the local application). Applications may change the default by calling SSL_set_value_uint(3ossl). FIPS impact: no The FIPS module is not affected as the QUIC implementation is outside of the OpenSSL FIPS module boundary.", "cve_priority": "medium", "cve_public_date": "2026-08-13 15:19:00 UTC" }, { "cve": "CVE-2026-54876", "url": "https://ubuntu.com/security/CVE-2026-54876", "cve_description": "Issue summary: A malicious TLS server can cause a memory leak in a TLS client that has enabled OCSP response checking by sending an OCSP response that contains no single response entries. Impact summary: An attacker can leak an attacker-tunable amount of memory per TLS handshake in a victim client application. A long-running client that repeatedly connects to a malicious server can have its memory exhausted, resulting in a Denial of Service. CWE: CWE-401: Missing Release of Memory after Effective Lifetime Description: The affected function is called during X.509 certificate chain verification when OCSP response checking is enabled with the X509_V_FLAG_OCSP_RESP_CHECK or X509_V_FLAG_OCSP_RESP_CHECK_ALL verification flags, for example when a TLS client verifies an OCSP response stapled into the TLS handshake by the server. When the received BasicOCSPResponse contains an empty SEQUENCE OF SingleResponse, which is permitted on the wire and accepted by the OpenSSL decoder, the OCSP_BASICRESP structure allocated by OCSP_response_get1_basic() was not freed because an early return bypassed the cleanup code at the end of the function. The amount of memory leaked per handshake can be amplified by the attacker by padding the certs field of the BasicOCSPResponse with bogus certificates, which are parsed and stored in the leaked structure before the empty response check triggers the early return. A long-running TLS client that repeatedly connects to a malicious server can have its memory exhausted over time. OCSP response checking is not enabled by default. Only client applications that explicitly enable the OCSP response check verification flags are affected. FIPS impact: no The FIPS modules in 4.0 and 3.6 are not affected by this issue as the affected code is outside the OpenSSL FIPS module boundary.", "cve_priority": "medium", "cve_public_date": "2026-08-05 15:16:00 UTC" } ], "launchpad_bugs_fixed": [ 2167826 ], "changes": [ { "cves": [], "log": [ "", " * Merge with Debian experimental (LP: #2167826). Remaining changes:", " - Use perl:native in the autopkgtest for installability on i386.", " - Symlink copyright/changelog.Debian.gz in libssl3* to libssl-dev/openssl", " - Disable LTO with which the codebase is generally incompatible", " (LP #2058017)", " - Default config reads crypto-config and /etc/ssl/openssl.cnf.d dropins", " - Don't enable or package anything FIPS (LP #2087955)", " - Match last filename for output in ecp_nistp521-ppc64.pl (LP #2137464)", " - Enable CPU jitter fluctuations", " - fips patches (debian/patches/fips):", " - crypto: Add kernel FIPS mode detection", " - crypto: Automatically use the FIPS provider...", " - apps/speed: Omit unavailable algorithms in FIPS mode", " - apps: pass -propquery arg to the libctx DRBG fetches", " - test: Ensure encoding runs with the correct context...", " - Add Ubuntu-specific defines to help FIPS certification (LP #2073991)", " + UBUNTU_OSSL_SELF_TEST_DESC_PCT_DH", " + UBUNTU_OSSL_PROV_FIPS_PARAM_UNAPPROVED_USAGE", " - Detect FIPS jitterentropy mode and load jitterentropy enabled FIPS", " provider", " - Fallback to default provider when FIPS provider is missing.", "" ], "package": "openssl", "version": "4.0.3-1ubuntu1", "urgency": "medium", "distributions": "stonking", "launchpad_bugs_fixed": [ 2167826 ], "author": "Ravi Kant Sharma ", "date": "Fri, 02 Oct 2026 12:25:40 +0200" }, { "cves": [ { "cve": "CVE-2026-84782", "url": "https://ubuntu.com/security/CVE-2026-84782", "cve_description": "Issue summary: The DTLS retransmission logic does not correctly handle a handshake message write that is suspended part-way through. The retransmitted message can be read past the message buffer and the retransmission overwrites the internal state the suspended write needs to resume correctly. Impact summary: The retransmitted message can disclose a heap memory to the peer as plaintext handshake data or cause a crash and a Denial of Service when the read reaches an unmapped memory region. CWE: CWE-125: Out-of-bounds Read Description: DTLS handshake messages can be written out in multiple fragments, and a write can suspend mid-message (returning WANT_WRITE) if the underlying transport temporarily cannot accept more data. While such a write is suspended, the DTLS retransmission timer may independently fire and ask the retransmission logic to resend an earlier, already-acknowledged-as-sent message from its retransmit queue. The retransmission logic reused the same internal buffer and position tracking as the message that was still being written, without resetting the position back to the start of the message being retransmitted. As a result the retransmission was read starting from wherever the suspended write had left off, producing a mislabelled message whose body was leftover bytes from the other, larger message still in flight - content that was never meant to be sent at that point, and which could run past the end of the allocated buffer. Separately, even when the retransmission is positioned correctly, allowing it to run to completion while another write is suspended overwrites the same shared bookkeeping that the suspended write depends on to resume. When the application later resumes the suspended write (via a subsequent SSL_read(), SSL_write(), SSL_accept(), or SSL_connect() call), it finds that bookkeeping in a state inconsistent with the message and aborts the process in a debugging build. The fix resets the retransmission's read position to the start of the message before resending, and skips retransmission entirely whenever a handshake write is still suspended, deferring to the next call that resumes it instead. FIPS impact: no The affected code is outside the FIPS module boundary.", "cve_priority": "high", "cve_public_date": "2026-09-29 16:17:00 UTC" }, { "cve": "CVE-2026-35189", "url": "https://ubuntu.com/security/CVE-2026-35189", "cve_description": "Issue summary: A certificate with many nameRelativeToCRLIssuer CRL distribution points causes disproportionate heap growth when OpenSSL caches X.509 extensions. Impact summary: Receiving a crafted certificate from a malicious peer can lead to significant memory pressure and possible Denial of Service in clients or in servers that solicit client certificates. CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: A certificate or a set of certificates that fits under the limit for size of certificates accepted from the peer (~100 KiB) can result in allocation of several hundred MiB of resident memory on the receiving side during a normal TLS handshake. This may be enough to crash the client or server, if multiple concurrent connections lead to similarly large memory allocations. The fix postpones processing of the CRL distribution points extensions in certificates to the time when the processed value is required for CRL processing. This avoids keeping large memory allocations for a long time when such certificates are received. FIPS impact: no The affected code is outside the FIPS module boundary.", "cve_priority": "low", "cve_public_date": "2026-09-29 16:17:00 UTC" }, { "cve": "CVE-2026-35191", "url": "https://ubuntu.com/security/CVE-2026-35191", "cve_description": "Issue summary: The OpenSSL QUIC server, when configured to not preform address validation, can be forced to count incoming packets multiple times in its unvalidated credit computation, leading to a violation of the RFC 9000 unvalidated connection amplification limit of 3 times the amount of data received. Impact summary: A remote attacker able to spoof packets to a server using the OpenSSL QUIC implementation might use the server for an amplification of a DDoS attack. CWE: CWE-440: Expected Behavior Violation Description: OpenSSL's QUIC stack, when operating as a server, enforces client address validation (RFC 9000, Section 8), to confirm the peer address is not used for a traffic amplification attack. If this feature is disabled on the server, the QUIC stack limits the amount of server data that can be sent to 3 times the amount of data received from the peer address, until such time as the TLS handshake is completed. The OpenSSL QUIC server, when operating in non-validation mode, adds the length of the whole datagram received to the unvalidated credit limit when processing each QUIC packet in the datagram. A remote peer may, after establishing a connection with an initial client hello frame, send a subsequent datagram containing multiple QUIC packets, leading the server to account the entire datagram length for each packet in the datagram, resulting in the server believing that the peer has sent more data than it actually has, thereby violating the 3x amplification limit mandated by the RFC. FIPS impact: no As the QUIC stack lives outside the FIPS module boundary, no FIPS modules are affected by this CVE.", "cve_priority": "low", "cve_public_date": "2026-09-29 16:17:00 UTC" }, { "cve": "CVE-2026-42772", "url": "https://ubuntu.com/security/CVE-2026-42772", "cve_description": "Issue summary: The QUIC stream reassembly algorithm performance deteriorates progressively as packets are arriving out of order. The worst case has a quadratic complexity proportional to the number of stream frames kept in the buffer for the received stream data. Impact summary: A remote QUIC peer that completes the handshake can create a connection-scoped CPU pressure and potentially a Denial of Service using compliant STREAM frames inside the advertised receive window, with low attacker bandwidth. CWE: CWE-407: Inefficient Algorithmic Complexity Description: OpenSSL manages received QUIC stream fragments using a doubly-linked list. While it optimizes for append operations (at the end of the list), it falls back to a head-to-tail linear search for any fragment that does not immediately follow the current `tail`. By manipulating the sequence of offsets, an attacker can force the server to perform O(n^2) operations, consuming excessive CPU time for the QUIC process. FIPS impact: no The FIPS module is not affected as the QUIC implementation is outside of the OpenSSL FIPS module boundary.", "cve_priority": "low", "cve_public_date": "2026-09-29 16:17:00 UTC" }, { "cve": "CVE-2026-54872", "url": "https://ubuntu.com/security/CVE-2026-54872", "cve_description": "Issue summary: The generic elliptic-curve scalar multiplication used for ECDSA and SM2 signature operations with curves that do not have a dedicated implementation leaks information about the secret nonce through timing. Impact summary: An attacker able to measure signing times may learn information about the per-signature secret nonce, which over many signatures can, via a lattice / Hidden Number Problem attack, lead to recovery of the private key. CWE: CWE-208: Observable Timing Discrepancy Description: The generic elliptic-curve scalar multiplication used for curves that do not have a dedicated constant-time implementation pads the secret scalar with non-constant-time BIGNUM operations, so the time taken depends on the value of the secret scalar derived from the ECDSA and SM2 nonce. The leak is very small; observing it requires a large number of measurements. The effect is largest for curves whose group order lies on a machine-word boundary, such as brainpoolP384r1. Applications using ECDSA signing over the Brainpool and other generic prime curves, and SM2 signing on platforms that use the generic implementation, are vulnerable to this issue. The NIST curves P-256, P-384 and P-521 use dedicated constant-time implementations and are not affected. FIPS Impact: no The FIPS modules are not affected: the approved NIST curves used in the FIPS provider have dedicated constant-time implementations and do not use the affected code path.", "cve_priority": "low", "cve_public_date": "2026-09-29 16:17:00 UTC" }, { "cve": "CVE-2026-54873", "url": "https://ubuntu.com/security/CVE-2026-54873", "cve_description": "Issue summary: QUIC process may keep memory for QUIC packet buffer for much longer period than necessary. Impact summary: Remote peer can exploit this vulnerability by sending maliciously crafted packets, making the local QUIC stack to keep the memory for packet buffers allocated. The time for which the memory remains allocated is entirely under the control of the potentially malicious remote peer. CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: To save copy operation from the packet buffer to the stream reassemble buffer the QUIC stack leaves the stream data on the packet buffer waiting to be copied to a buffer provided by the local receiving application. The QUIC stack releases a reference to the packet buffer only after the data are copied to the application buffer. This design is more efficient for legitimate data transfers but enables an attacker to allocate a lot more memory than actually required by the data kept in the receiving stream buffer. To mitigate the vulnerability, the QUIC stack now calculates and monitors memory overhead for every stream. The memory overhead for a single stream frame is calculated as a difference between the size of the whole packet that carries the stream frame and the size of the stream frame itself. The memory overhead for a single stream frame is added to the total (cumulative) memory overhead QUIC stack keeps for each stream. Once the cumulative memory overhead exceeds 64kB, the QUIC stack moves the stream frame data from the packet buffer to the stream buffer, starting with the next packet received. FIPS impact: no The FIPS module is not affected as the QUIC implementation is outside of the OpenSSL FIPS module boundary.", "cve_priority": "low", "cve_public_date": "2026-09-29 16:17:00 UTC" }, { "cve": "CVE-2026-54875", "url": "https://ubuntu.com/security/CVE-2026-54875", "cve_description": "Issue summary: A non-constant-time optimized implementation of scalar point multiplication is used for SM2 private key operations on ARM64 and RISC-V platforms. Impact summary: An attacker able to measure the time taken by, or to observe the cache-line access pattern of SM2 signing or decryption on an affected platform can learn information about the secret scalar. CWE: CWE-208: Observable Timing Discrepancy Description: On ARM64 and RISC-V processors, the SM2 curve uses an optimized scalar multiplication implementation whose conditional branches and table look ups are chosen according to the bits of the secret scalar. The execution time and the cache-access pattern therefore depend on the long-term private key (during SM2 decryption) or the per-signature nonce (during SM2 signature generation), forming a timing and cache side-channel. FIPS Impact: no SM2 is not a FIPS algorithm and the optimized SM2 implementation is not part of the FIPS module. OpenSSL 4.0, 3.6, 3.5 and 3.4 are vulnerable to this issue on AArch64 and RISC-V. OpenSSL 3.0, 1.1.1 and 1.0.2 are not affected by this issue. OpenSSL 4.0 users should upgrade to OpenSSL 4.0.3. OpenSSL 3.6 users should upgrade to OpenSSL 3.6.5. OpenSSL 3.5 users should upgrade to OpenSSL 3.5.9. OpenSSL 3.4 users should upgrade to OpenSSL 3.4.8. This issue was reported on 2 May 2026 by Abhinav Agarwal. It was independently reported on 6 June 2026 by Feng Xue. The fix was developed by Igor Ustinov. -- cut (non-publishing metadata for internal use) -- Reported by: Abhinav Agarwal, Feng Xue Fixed by: Igor Ustinov", "cve_priority": "low", "cve_public_date": "2026-09-29 16:17:00 UTC" }, { "cve": "CVE-2026-72897", "url": "https://ubuntu.com/security/CVE-2026-72897", "cve_description": "Issue summary: A TLS server that calls SSL_set_SSL_CTX() to switch a connection to a different SSL_CTX part way through a handshake may access memory beyond the end of an internal array if the replacement context knows about more provider signature algorithms than the context the connection was created from. Applications which never call SSL_set_SSL_CTX() are not affected. Impact summary: A remote peer may be able to cause a small out-of-bounds read, and in some circumstances a fixed-value out-of-bounds write, on the server heap. This may lead to a Denial of Service. CWE: CWE-787: Out-of-bounds Write Description: A TLS connection records how many certificate slots it has when it is created, taken from the SSL_CTX that created it: the built-in certificate types plus one slot for each provider TLS-SIGALG entry that context was aware of. That count sizes an internal array of per-slot certificate validity flags. An application may replace a connection's SSL_CTX part way through the handshake by calling SSL_set_SSL_CTX(), most commonly from a servername callback in order to serve a different virtual host. Doing so did not refresh the recorded count. A provider signature algorithm's slot index is its position in the list of whichever context resolves it, so if the replacement context is aware of more of them than the original, an algorithm offered by the peer can resolve to an index beyond the end of the array. Processing the peer's signature algorithms then reads one four byte word past the end for each such algorithm and, where the word read is zero, writes a fixed value over it. A peer offering many of them can corrupt heap metadata and abort the process. Only provider signature algorithms which occupy one of the excess slots, and which the server also has configured, have this effect. Codepoints the replacement context does not recognise are discarded without being resolved to a slot, and provider signature algorithms are usable only from TLS 1.3. The two contexts must therefore be aware of different numbers of provider signature algorithms, which requires separate library contexts, a provider loaded between the two being created, or providers which differ in what they advertise - in 4.0, for example, the default provider advertises SM2 where the FIPS provider does not. A deployment meeting the condition is also unable to negotiate the affected algorithms with legitimate clients, since the same stale count hides the corresponding certificates, so the misconfiguration is likely to be noticed. For that reason, and because the configuration is not the default, this issue has been assessed as Low severity. FIPS impact: no No FIPS modules are affected by this issue as the affected code is outside the OpenSSL FIPS module boundary.", "cve_priority": "low", "cve_public_date": "2026-09-29 16:17:00 UTC" }, { "cve": "CVE-2026-75804", "url": "https://ubuntu.com/security/CVE-2026-75804", "cve_description": "Issue summary: OpenSSL QUIC stack does not enforce connection level flow control for streams. Remote peers may send more bytes as long as they fit within the stream flow control limits. Impact summary: A malicious remote peer may exploit the lack of connection flow control for streams to make the QUIC stack receive ~100MB of memory instead of 768 KiB (default flow control window size). CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: The local QUIC stack advertises two flow control limits to its remote peer: stream flow control limit and connection flow control limit. The remote peer must follow both limits when transmitting stream data. Whenever the local QUIC stack receives a stream frame, it validates that the size of the received stream frame stays within flow control limits. If either limit is exceeded (stream level or connection level), then the QUIC stack must close the connection with a flow control error. The vulnerable OpenSSL QUIC stack enforces the stream-level but not the connection-level limit. To exploit the issue, three conditions must be met: - the remote peer opens several streams - each stream must stay within the stream-level flow control limit - there must be no zero-offset byte sent on any of the streams (to prevent the vulnerable QUIC stack from consuming data). By meeting the conditions above, the remote peer may make the local stack allocate 2 x MAX_STREAMS x (stream flow control limit) bytes of memory. MAX_STREAMS defaults to 100, and the limit applies to both bidirectional and unidirectional streams, making it 200 in total. The default flow control window for a stream is 512kB. The remote peer may force the vulnerable QUIC stack to allocate 100MB of heap per connection. FIPS impact: no The FIPS module is not affected as the QUIC implementation is outside of the OpenSSL FIPS module boundary.", "cve_priority": "low", "cve_public_date": "2026-09-29 16:17:00 UTC" }, { "cve": "CVE-2026-75805", "url": "https://ubuntu.com/security/CVE-2026-75805", "cve_description": "Issue summary: A CMP client that requests certificate revocation on the basis of a PKCS#10 CSR may dereference a NULL pointer and terminate abnormally when processing a crafted revocation response. Impact summary: The NULL pointer dereference happens on a read which leads to a crash and a Denial of Service for the affected client application. CWE: CWE-476: NULL-pointer dereference Description: A CMP client revoking a certificate has to tell the server which certificate to revoke, and may do so by supplying a PKCS#10 CSR instead of the certificate itself or its issuer name and serial number. This is 'openssl cmp -cmd rr -csr ' on the command line, or OSSL_CMP_exec_RR_ses() with the certificate supplied via OSSL_CMP_CTX_set1_p10CSR() through the API. A CSR does not contain the issuer name and serial number of the certificate, so the client does not send them. A server may optionally name the certificate it revoked in its response, and the client then compares that name against what it sent. Having sent neither an issuer name nor a serial number, it has nothing to compare against, and a server returning a specially crafted name causes the client to read from a NULL pointer and crash. The revocation response is checked for valid message protection before the affected code is reached, so an attacker must be a malicious or compromised CMP server, or a man-in-the-middle in possession of the secret used for message protection. Clients that identify the certificate to be revoked by a certificate or by issuer and serial number rather than by a PKCS#10 CSR are not affected. FIPS impact: no No FIPS modules are affected by this issue, as the CMP protocol implementation is outside the OpenSSL FIPS module boundary.", "cve_priority": "low", "cve_public_date": "2026-09-29 16:17:00 UTC" }, { "cve": "CVE-2026-75806", "url": "https://ubuntu.com/security/CVE-2026-75806", "cve_description": "Issue summary: An established DTLS 1.2 association using an AEAD cipher suite can be terminated by a single unauthenticated datagram whose encrypted fragment is shorter than the mandatory explicit IV and authentication tag overhead. Impact summary: An attacker who can send a datagram that is routed to an existing DTLS 1.2 association can tear that association down without knowing any key material. This is a Denial of Service limited to the targeted association. There is no memory safety or confidentiality impact. CWE: CWE-1284: Improper Validation of Specified Quantity in Input Description: In TLS 1.2 and DTLS 1.2 every record protected by an AEAD cipher suite carries an explicit IV followed by the ciphertext and an authentication tag. When decrypting such a record the record layer passed the record length to the cipher implementation before checking that the record was long enough to contain the explicit IV and the tag. For a record shorter than that overhead the cipher implementation rejected the impossible length, and the record layer treated this as an internal failure and raised a fatal internal_error alert instead of treating the record as one that failed authentication. In TLS 1.2 the same record causes a fatal internal_error alert instead of the expected bad_record_mac alert. Since any undecryptable record already terminates a TLS connection, this is a protocol conformance issue rather than a security issue in TLS. The fix validates the record length against the explicit IV and tag length before any AEAD processing, so that TLS reports bad_record_mac and DTLS silently discards the record. FIPS impact: no The affected code is outside the FIPS module boundary.", "cve_priority": "low", "cve_public_date": "2026-09-29 16:17:00 UTC" }, { "cve": "CVE-2026-77696", "url": "https://ubuntu.com/security/CVE-2026-77696", "cve_description": "Issue summary: SM2 signature generation uses non-constant-time arithmetic on secret values, forming a timing side-channel. Impact summary: An attacker able to measure SM2 signing times may learn information about the per-signature secret nonce, which over many signatures can, via a lattice / Hidden Number Problem attack, lead to recovery of the private key. CWE: CWE-208: Observable Timing Discrepancy Description: SM2 signature generation computes the signature value using variable-time BIGNUM operations on the secret nonce and the private key, so the time taken to produce an SM2 signature depends on these secret values, forming a timing side-channel. Applications performing SM2 signature generation are affected on all platforms. FIPS Impact: no SM2 is not a FIPS algorithm.", "cve_priority": "low", "cve_public_date": "2026-09-29 16:17:00 UTC" }, { "cve": "CVE-2026-84783", "url": "https://ubuntu.com/security/CVE-2026-84783", "cve_description": "Issue summary: The first concurrent use of the same X.509 certificate by several threads may cause its cached extension data to be freed while another thread is still using it. Impact summary: A remote, unauthenticated peer could crash a multi-threaded TLS client, or a multi-threaded TLS server that requests client certificates, if the first certificate chains built to the same trusted CA certificate are built by several connections at the same time. This is a use-after-free read, which is likely to crash the process, resulting in a Denial of Service. CWE: CWE-416: Use After Free Description: OpenSSL caches the decoded values of a certificate's X.509v3 extensions inside the X509 object the first time they are needed. In OpenSSL 4.0 this cache is built in two phases: the extension values are computed while holding a read lock on the certificate, and the results are then installed into the certificate under a write lock. Because a read lock does not exclude other readers, several threads can compute the cache for the same certificate at the same time. Each thread that subsequently acquires the write lock installs its own results and frees the values installed by the thread before it, even though that earlier thread has already marked the cache as complete and may have returned pointers into it to its caller. A caller still using those pointers then reads freed memory. Any certificate shared between threads is exposed the first time its extensions are decoded. In TLS the certificates at risk are the trusted CA certificates supplied for chain verification, by whatever means, since these are shared by every connection and their extensions are decoded and cached the first time a chain is built to them. Certificates sent by the peer are decoded separately for each connection and are not shared, so they are not affected. In a TLS client verifying server certificates, or a TLS server that requests and verifies client certificates, the use-after-free could only occur if the first chains built to the same trusted CA are built by several connections at the same time. FIPS impact: no The FIPS module is not affected as X.509 certificate handling is outside of the OpenSSL FIPS module boundary. OpenSSL 4.0 is vulnerable to this issue. OpenSSL 3.6, 3.5, 3.4, 3.0, 1.1.1 and 1.0.2 are not affected by this issue. OpenSSL 4.0 users should upgrade to OpenSSL 4.0.3. This issue was reported on 27 August 2026 by Tim Becker (Xint.io) and independently in a public report on 31 August 2026 by aydinmercan. The fix has been developed by Bob Beck. -- cut (non-publishing metadata for internal use) -- Reported by: Tim Becker (Xint.io), aydinmercan Fixed by: Bob Beck", "cve_priority": "medium", "cve_public_date": "2026-09-29 16:17:00 UTC" }, { "cve": "CVE-2026-84784", "url": "https://ubuntu.com/security/CVE-2026-84784", "cve_description": "Issue summary: A malicious remote peer may flood the local QUIC stack with NEW_CONNECTION_ID frames by avoiding a limit check on how many connection IDs the remote QUIC stack can use. Impact summary: The local QUIC stack sends a RETIRE_CONN_ID frame for every NEW_CONNECTION_ID frame it receives. The RETIRE_CONN_ID frame is dispatched via the Control Frame Queue (CFQ). If the remote peer also withholds ACKs, then it can force the local stack to allocate ~400MB (depending on ACK delay). CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: RFC 9000 sections 5.1.1 and 5.1.2 [1] describe the mechanism by which a remote peer can notify the local QUIC stack to change the destination connection ID (a.k.a. CID) the local stack uses to identify the connection at the remote peer. Each CID is associated with a sequence number. The sequence number is transmitted in NEW_CONNECTION_ID and RETIRE_CONNECTION_ID frames to identify the CID which is being either associated with a connection or retired. The remote peer sends a NEW_CONNECTION_ID frame to let the local stack know a new CID is being associated with an existing connection. The NEW_CONNECTION_ID frame carries the new CID, its sequence number, and the retire-prior-to number. The retire-prior-to identifies existing CIDs that are to be retired. The local QUIC stack must send a RETIRE_CONNECTION_ID for every destination CID whose sequence number is less than retire-prior-to. The CID becomes retired after the local stack receives an ACK for its RETIRE_CONNECTION_ID frame. Although the OpenSSL QUIC stack supports at most one destination CID for every connection, it can be tricked into processing more than one RETIRE_CONNECTION_ID frame per connection. The OpenSSL QUIC stack currently retires the destination CID as soon as it receives the NEW_CONNECTION_ID, while in fact the destination CID must be retired after an ACK for the RETIRE_CONNECTION_ID frame is received. Correcting the flawed logic also fixes the backlog growth. [1] https://datatracker.ietf.org/doc/html/rfc9000#name-issuing-connection-ids FIPS impact: no The FIPS module is not affected as the QUIC implementation is outside of the OpenSSL FIPS module boundary.", "cve_priority": "low", "cve_public_date": "2026-09-29 16:17:00 UTC" } ], "log": [ "", " * Import 4.0.3", " - CVE-2026-84782 (\"DTLS Retransmits Handshake Messages From a Stale Buffer", " Offset\")", " - CVE-2026-35189 (\"Memory Allocation in Relative CRLDP Processing\")", " - CVE-2026-35191 (\"QUIC Unvalidated Amplification Credit may be Over", " Accounted\")", " - CVE-2026-42772 (\"Potential CPU DoS via O(n^2) Fragment Reassembly in QUIC\")", " - CVE-2026-54872 (\"Timing Side-Channel in Scalar Multiplication for Non-NIST", " EC Curves\")", " - CVE-2026-54873 (\"QUIC STREAM Fragment Metadata DoS\")", " - CVE-2026-54875 (\"Non-Constant-Time SM2 Scalar Multiplication on ARM64 and", " RISC-V\")", " - CVE-2026-72897 (\"Out-of-Bounds Access After SSL_set_SSL_CTX() During a", " Handshake\")", " - CVE-2026-75804 (\"QUIC Connection-Level Flow Control is Not Enforced for", " Streams\")", " - CVE-2026-75805 (\"NULL Pointer Dereference in CMP Client Revocation", " Response Handling\")", " - CVE-2026-75806 (\"Unauthenticated and Undersized DTLS 1.2 AEAD Record", " Causes DoS\")", " - CVE-2026-77696 (\"Timing Side-Channel in SM2 Signature Generation\")", " - CVE-2026-84783 (\"Use-After-Free in X.509 Extension Cache Under Concurrent Use\")", " - CVE-2026-84784 (\"QUIC: Unbounded RETIRE_CONNECTION_ID Backlog\")", "" ], "package": "openssl", "version": "4.0.3-1", "urgency": "medium", "distributions": "experimental", "launchpad_bugs_fixed": [], "author": "Sebastian Andrzej Siewior ", "date": "Tue, 29 Sep 2026 21:40:01 +0200" }, { "cves": [ { "cve": "CVE-2026-18798", "url": "https://ubuntu.com/security/CVE-2026-18798", "cve_description": "Issue summary: QUIC server may double free QRX (QUIC record layer RX) object when channel creation fails for initial packet. Impact summary: Double free leads to heap corruption, which typically results in termination of QUIC server process, leading to Denial of Service. There is so far no evidence that this double free is exploitable for remote code execution, thus it is considered highly improbable. CWE: CWE-415: Double Free Description: In order to validate initial packet, OpenSSL QUIC stack default packet handler (port_default_packet_handler()) creates a so-called QRX object. If the initial packet validates successfully with QRX object, the default packet handler proceeds to channel (connection object) creation. The QRX object used for packet validation is passed to port_bind_channel(), so it becomes part of the newly created connection. If port_bind_channel() fails, then it also frees the QRX object. Once port_bind_channel() returns, the port_default_packet_handler() detects the failure and proceeds to the error branch, where the same QRX object is freed for the second time. The failure in port_bind_channel() function can be induced with a relatively low effort by a malformed (non RFC 9000 compliant) INITIAL packet. If the packet carries DCID (destination connection ID) which is shorter than 8 bytes, then port_bind_channel() jumps to the error path after ossl_quic_lcidm_enrol_odcid() detects that the DCID has invalid length. FIPS impact: no The FIPS module is not affected, as the QUIC implementation is outside of the OpenSSL FIPS module boundary.", "cve_priority": "medium", "cve_public_date": "2026-08-25 13:17:00 UTC" }, { "cve": "CVE-2026-63072", "url": "https://ubuntu.com/security/CVE-2026-63072", "cve_description": "Issue summary: OpenSSL CMS decryption sizes the key-unwrap output buffer based on querying the unwrapped key size, but the AES-WRAP-PAD unwrap primitive can write and cleanse more bytes than that query reports, causing an 8-byte out-of-bounds heap write. Impact summary: An attacker who supplies a crafted CMS message can trigger a deterministic 8-byte out-of-bounds heap write when the victim decrypts it with CMS_decrypt(), corrupting the heap and typically resulting in a Denial of Service. CWE: CWE-787: Out-of-bounds Write Description: The key-wrap OID is potentially attacker-controlled on the wire. CMS unwrapping allows both id-aesNNN-wrap-pad and id-aesNNN-wrap ciphers. An attacker can take a legitimate message and change a single OID byte to select the padded variant while leaving the message otherwise valid. Since the unwrap key is derived from the recipient's private operation (ECDH key agreement or ML-KEM decapsulation), the RFC 5649 integrity check cannot pass, and the decryption fails with integrity failure. The write is a fixed-size (8-byte), fixed-value (zero) heap overflow immediately past the allocation, requires no special configuration, and is reachable from the public CMS_decrypt() function. The consequence is a heap corruption leading to a Denial of Service. The fix in the CMS code sizes the unwrap output buffer for the worst case so a failed unwrap cannot write past the allocation. FIPS impact: no As the CMS code lives outside the FIPS module boundary, no FIPS modules are affected by this CVE.", "cve_priority": "medium", "cve_public_date": "2026-08-25 13:19:00 UTC" }, { "cve": "CVE-2026-63076", "url": "https://ubuntu.com/security/CVE-2026-63076", "cve_description": "Issue summary: OpenSSL CMP password based protection verification only checks whether the protectionAlg parameter was not NULL and not its ASN.1 type, before treating it as a PBMParameter. A crafted message can contain a parameter of a different type, which is then dereferenced as an invalid pointer. Impact summary: A remote, unauthenticated attacker can crash an application acting as a CMP server that accepts PBM-protected messages, or a CMP client talking to a malicious or intercepted CMP server, resulting in a Denial of Service. CWE: CWE-476: NULL Pointer Dereference Description: When verifying the password-based MAC protection of a CMP message, OpenSSL library reads the protectionAlg algorithm parameter with X509_ALGOR_get0(), which returns both the parameter type and its value pointer. The value is then cast to an ASN1_STRING and treated as the expected PBMParameter after only checking that pointer is not NULL. The parameter type returned by X509_ALGOR_get0() was never consulted. This happens during protection verification, before any MAC is computed, so no knowledge of the PBM shared secret is required; the only precondition is that PBM verification is reachable. On the server side this is reached from OSSL_CMP_SRV_process_request() for any application that stands up a CMP server accepting PBM-protected messages, and on the client side from CMP response validation against a malicious or on-path (MITM) server. The reliable consequence is a denial of service; there is no memory disclosure, no controlled memory write, and no path to code execution. CMP is a specialized feature that an application must explicitly enable. FIPS impact: no As the CMP code lives outside the FIPS module boundary, no FIPS modules are affected by this CVE.", "cve_priority": "medium", "cve_public_date": "2026-08-25 13:19:00 UTC" }, { "cve": "CVE-2026-14457", "url": "https://ubuntu.com/security/CVE-2026-14457", "cve_description": "Issue summary: In a server or client configuration with RFC7250 Raw Public Keys (RPKs) enabled, and only the private key (with no associated certificate) configured locally, a NULL pointer dereference may occur when the remote peer solicits raw public keys and also sends the typically omitted \"signature_algorithms_cert\" TLS extension. Impact summary: The impact is limited to a possible Denial of Service as a result of an application abort, no data disclosure or remote command execution are possible. CWE: CWE-476: NULL Pointer Dereference Description: While a passing comment in sample code in the documentation suggests that key-only RPK configurations are supported, the best-practice RPK configuration is to always configure a corresponding certificate (possibly self-signed or signed by any convenient CA). When the private key is configured along with a matching certificate, the \"signature_algorithms_cert\" extension is handled reliably even without the fix, and peer clients or servers that don't support raw public keys may be able to complete a TLS connection by pinning or verifying the corresponding certificate or its public key. Deployments that prefer to configure just a private key with no certificate need to upgrade to an updated release as noted below. FIPS impact: no No FIPS modules are affected by this issue, as the SSL protocol implementation is outside the OpenSSL FIPS module boundary.", "cve_priority": "low", "cve_public_date": "2026-08-25 13:17:00 UTC" }, { "cve": "CVE-2026-54874", "url": "https://ubuntu.com/security/CVE-2026-54874", "cve_description": "Issue summary: Receiving a DTLS record for a future epoch while a handshake is in progress causes OpenSSL to buffer far more memory than the record itself requires. Impact summary: A peer can use a small amount of network traffic to make an OpenSSL DTLS endpoint retain a disproportionately large amount of memory, which may lead to a Denial of Service. CWE: CWE-405: Asymmetric Resource Consumption (Amplification) Description: While a DTLS handshake is in progress, a peer may legitimately have already moved on to the next epoch (for example, having sent its ChangeCipherSpec and Finished messages) before the local endpoint has processed the same transition, typically because of reordering on the underlying UDP transport. OpenSSL buffers such early records so that they can be processed once the local endpoint catches up. Buffering a record currently retains the entire read buffer it arrived in, which is sized to hold the largest possible DTLS record (around 16 kilobytes), rather than just the bytes that make up the record itself. Up to 100 such records may be buffered per connection. As a result, a peer that sends a stream of small forged records claiming to belong to the next epoch can cause an OpenSSL DTLS endpoint to retain around 1.7 megabytes of memory, despite sending only a small fraction of that amount of data over the network. An attacker therefore gains a memory amplification factor of around 1200, and can multiply the effect across as many associations as it is able to open, making this a remote memory exhaustion Denial of Service risk for DTLS servers. Since the memory retained per connection remains bounded, and any limit an application already places on the number of concurrent associations also bounds the total exposure, this issue has been assessed as Low severity. FIPS impact: no No FIPS modules are affected by this issue as the affected code is outside the OpenSSL FIPS module boundary. OpenSSL 4.0, 3.6, 3.5, 3.4, 3.0, 1.1.1 and 1.0.2 are vulnerable to this issue. OpenSSL 4.0 users should upgrade to OpenSSL 4.0.2. OpenSSL 3.6 users should upgrade to OpenSSL 3.6.4. OpenSSL 3.5 users should upgrade to OpenSSL 3.5.8. OpenSSL 3.4 users should upgrade to OpenSSL 3.4.7. OpenSSL 3.0 users should upgrade to OpenSSL 3.0.22. Premium support customers only: OpenSSL 1.1.1 users should upgrade to OpenSSL 1.1.1zi OpenSSL 1.0.2 users should upgrade to OpenSSL 1.0.2zr This issue was reported on 18 May 2026 by Amazon Web Services. The fix has been developed by Matt Caswell. -- cut (non-publishing metadata for internal use) -- Reported by: Amazon Web Services Fixed by: Matt Caswell", "cve_priority": "low", "cve_public_date": "2026-08-25 13:19:00 UTC" }, { "cve": "CVE-2026-63073", "url": "https://ubuntu.com/security/CVE-2026-63073", "cve_description": "Issue summary: OpenSSL CMP response validation passed an unexpected response sender distinguished name directly as the format string to `ERR_raise_data()`. Impact summary: A malicious or intercepted CMP endpoint can crash a CMP client that enforces an expected sender or uses a pinned server certificate whose subject becomes the default expected sender. CWE: CWE-134 (Use of Externally-Controlled Format String) Description: When validating a received CMP message, ossl_cmp_msg_check_update() converts the peer-supplied sender distinguished name with X509_NAME_oneline() and passes it directly as the format argument to ERR_raise_data(). Percent characters survive the conversion, so a sender DN such as \"CN=%s%n\" reaches BIO_vsnprintf() as an attacker-controlled format string with no matching variadic arguments. This path is only reached when the caller configures an expected sender or pins a server certificate, which is the normal configuration for a CMP client validating server responses. Since the attacker controls the format string but none of the variadic arguments, such specifiers as %s and %n dereference or write through unrelated stack contents and crash the client. The reliable consequence is a denial of service, when the response comes from a malicious or intercepted CMP endpoint. There is no controlled memory write, arbitrary-address read, or reliable path to remote code execution. FIPS impact: no No FIPS modules are affected by this issue, as the CMP protocol implementation is outside the OpenSSL FIPS module boundary.", "cve_priority": "low", "cve_public_date": "2026-08-25 13:19:00 UTC" }, { "cve": "CVE-2026-63074", "url": "https://ubuntu.com/security/CVE-2026-63074", "cve_description": "Issue summary: The OpenSSL Certificate Management Protocol (CMP) caches additional certificates (extraCerts) sent in a CMP message, but never expunges them (for instance if they are invalid). If a server reuses an OSSL_CMP_CTX frequently, this cache of extraCerts may grow unboundedly, and a malicious client may flood a CMP server with requests driving this growth. Impact summary: Users utilizing a CMP server that reuses a single OSSL_CMP_CTX for the lifetime of a server process may observe unbounded memory growth in the event a malicious client repeatedly sends requests containing unique extra certificates, which may lead to OOM conditions. CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: If a remote user sends CMP messages to a server with a list of extraCerts and the message is rejected, the extraCerts from the message remains in the server contexts untrusted certificate stack. This exposes servers with long lived ctx objects to Denial of Service attacks in which an attacker sends messages intending to be rejected with a large list of additional certificates repeatedly, forcing the server to store them indefinitely. The issue was fixed by removing the added extra certs if the message is rejected, using the same method as when the context is configured to not do caching at all. FIPS impact: no As the CMP code lives outside the FIPS module boundary, no FIPS modules are affected by this CVE.", "cve_priority": "low", "cve_public_date": "2026-08-25 13:19:00 UTC" }, { "cve": "CVE-2026-63075", "url": "https://ubuntu.com/security/CVE-2026-63075", "cve_description": "Issue summary: When OpenSSL processes QUIC traffic from a peer that repeatedly sends ack-eliciting packets while not acknowledging ACK-only responses, the QUIC stack can retain ACK-only packet metadata for the lifetime of the connection. Impact summary: A remote peer that can complete a QUIC handshake can cause connection-scoped memory growth which may lead to Denial of Service through memory exhaustion, especially with sustained traffic or many concurrent QUIC connections. CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: When the OpenSSL QUIC stack sends an ACK-only packet, there is no requirement by the QUIC protocol that the peer will acknowledge that ACK-only packet (i.e. it is itself not ack-eliciting). However, the OpenSSL implementation stores the metadata about the ACK frames regardless. In and of itself that's ok, but if a malicious peer establishes a connection, and then drives the connection such that ACK-only packets are forced from the OpenSSL implementation peer (i.e., by sending numerous PING frames), and then withholding any subsequent acks for ack-eliciting data, like legitimate data, said malicious peer can force inappropriate memory growth on the OpenSSL peer, potentially leading to a Denial of Service. The fix is to ensure that we account for the transmission of the ACK-only packet in the packet histories high and low watermark without actually storing the ACK-only packet metadata itself. FIPS impact: no The OpenSSL FIPS module is not affected as the QUIC code is outside the FIPS module boundary.", "cve_priority": "low", "cve_public_date": "2026-08-25 13:19:00 UTC" }, { "cve": "CVE-2026-75803", "url": "https://ubuntu.com/security/CVE-2026-75803", "cve_description": "Issue summary: ChaCha20-Poly1305 and AES-OCB decryption with an empty ciphertext can report success without verifying the supplied authentication tag when the operation is finalized by calling the EVP_Cipher() function. Impact summary: Applications calling EVP_Cipher() on an empty ciphertext and expecting the call to check the AEAD tag may accept forged messages. CWE: CWE-354 (Improper Validation of Integrity Check Value) Description: The EVP_Cipher() API call for AEAD ciphers behaves like a one shot encryption and decryption call. It also verifies the AEAD tag after the decryption operation. However for AES-OCB and ChaCha20-Poly1305 ciphers it skipped the AEAD tag verification when an empty ciphertext was passed to the function. The callers of this function might believe that a successful return indicates a valid AEAD tag for these ciphers, even when that has not truly been validated in this case. FIPS impact: no The FIPS modules in 4.0, 3.6, 3.5, 3.4, and 3.0 are not affected by this CVE as the affected algorithms are not FIPS approved and thus not implemented in the FIPS module.", "cve_priority": "low", "cve_public_date": "2026-08-25 13:19:00 UTC" }, { "cve": "CVE-2026-14456", "url": "https://ubuntu.com/security/CVE-2026-14456", "cve_description": "Issue summary: When an OpenSSL QUIC server (Listener SSL object) processes valid QUIC Initial packets for unknown destination connection IDs, it can allocate and queue new incoming channels without enforcing any limit. Impact summary: A remote peer that can make many Initial packets reach the server listener faster than the application accepts connections, can cause the memory allocated to store the per-channel state to grow without any limits, potentially making the QUIC listener unavailable and causing Denial of Service. CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: The function that handles inbound QUIC packets uses Connection-Id from the packet header to find an existing connection (QUIC channel). If no existing connection is found and the packet type is INITIAL, the function treats the packet as a new connection. It allocates a new channel object and inserts it into a queue where it waits to be accepted by the local application with SSL_accept(3ossl). The memory occupied by these initial channel objects may grow without bounds if the application is not able to call SSL_accept() frequently enough to serve these inbound connection requests. The issue is present since OpenSSL 3.5 when the QUIC server implementation was added. The fix introduces a limit for pending connections. The default limit is set to 256 pending connections (waiting to be accepted by the local application). Applications may change the default by calling SSL_set_value_uint(3ossl). FIPS impact: no The FIPS module is not affected as the QUIC implementation is outside of the OpenSSL FIPS module boundary.", "cve_priority": "medium", "cve_public_date": "2026-08-13 15:19:00 UTC" }, { "cve": "CVE-2026-54876", "url": "https://ubuntu.com/security/CVE-2026-54876", "cve_description": "Issue summary: A malicious TLS server can cause a memory leak in a TLS client that has enabled OCSP response checking by sending an OCSP response that contains no single response entries. Impact summary: An attacker can leak an attacker-tunable amount of memory per TLS handshake in a victim client application. A long-running client that repeatedly connects to a malicious server can have its memory exhausted, resulting in a Denial of Service. CWE: CWE-401: Missing Release of Memory after Effective Lifetime Description: The affected function is called during X.509 certificate chain verification when OCSP response checking is enabled with the X509_V_FLAG_OCSP_RESP_CHECK or X509_V_FLAG_OCSP_RESP_CHECK_ALL verification flags, for example when a TLS client verifies an OCSP response stapled into the TLS handshake by the server. When the received BasicOCSPResponse contains an empty SEQUENCE OF SingleResponse, which is permitted on the wire and accepted by the OpenSSL decoder, the OCSP_BASICRESP structure allocated by OCSP_response_get1_basic() was not freed because an early return bypassed the cleanup code at the end of the function. The amount of memory leaked per handshake can be amplified by the attacker by padding the certs field of the BasicOCSPResponse with bogus certificates, which are parsed and stored in the leaked structure before the empty response check triggers the early return. A long-running TLS client that repeatedly connects to a malicious server can have its memory exhausted over time. OCSP response checking is not enabled by default. Only client applications that explicitly enable the OCSP response check verification flags are affected. FIPS impact: no The FIPS modules in 4.0 and 3.6 are not affected by this issue as the affected code is outside the OpenSSL FIPS module boundary.", "cve_priority": "medium", "cve_public_date": "2026-08-05 15:16:00 UTC" } ], "log": [ "", " * Import 4.0.2", " - CVE-2026-18798 (\"QUIC Server May Trigger Double Free When Processing", " INITIAL Packet\")", " - CVE-2026-63072 (\"Heap Buffer Overflow in CMS Key Unwrapping\")", " - CVE-2026-63076 (\"Invalid Pointer Dereference in CMP Server via Crafted", " protectionAlg\")", " - CVE-2026-14457 (\"RPK Server Signature Algorithm Selection Can Dereference", " a Missing Certificate\")", " - CVE-2026-54874 (\"Excessive Memory Use Buffering DTLS Records for a Future", " Epoch\")", " - CVE-2026-63073 (\"Untrusted Sender DN Used as Format String in CMP Response", " Validation\")", " - CVE-2026-63074 (\"CMP Indefinite Cache Growth of ExtraCerts\")", " - CVE-2026-63075 (\"QUIC ACK-only Packet Retention Can Cause Memory", " Exhaustion\")", " - CVE-2026-75803 (\"AEAD Forgeries with Empty Ciphertext When Using", " EVP_Cipher()\") (Closes: #1145172)", " - CVE-2026-14456 (\"Unbounded Memory Growth in QUIC Server Incoming Channel", " Queue\") (Closes: #1144615)", " - CVE-2026-54876 (\"Client-Side Memory Leak in OCSP Response Checking\") (Closes: #1143841)", "" ], "package": "openssl", "version": "4.0.2-1", "urgency": "medium", "distributions": "experimental", "launchpad_bugs_fixed": [], "author": "Sebastian Andrzej Siewior ", "date": "Tue, 25 Aug 2026 21:19:42 +0200" } ], "notes": null, "is_version_downgrade": false }, { "name": "parted", "from_version": { "source_package_name": "parted", "source_package_version": "3.7-1", "version": "3.7-1" }, "to_version": { "source_package_name": "parted", "source_package_version": "3.8-2", "version": "3.8-2" }, "cves": [ { "cve": "CVE-2026-89085", "url": "https://ubuntu.com/security/CVE-2026-89085", "cve_description": "[heap buffer overflow in _init_fats / fat_table_read]", "cve_priority": "medium", "cve_public_date": "2026-09-17" }, { "cve": "CVE-2026-89088", "url": "https://ubuntu.com/security/CVE-2026-89088", "cve_description": "[heap buffer overflow in duplicate_legacy_root_dir]", "cve_priority": "medium", "cve_public_date": "2026-09-17" } ], "launchpad_bugs_fixed": [], "changes": [ { "cves": [], "log": [ "", " * Reupload pointing dgit to the correct upstream tag.", "" ], "package": "parted", "version": "3.8-2", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Colin Watson ", "date": "Fri, 25 Sep 2026 10:10:23 +0100" }, { "cves": [ { "cve": "CVE-2026-89085", "url": "https://ubuntu.com/security/CVE-2026-89085", "cve_description": "[heap buffer overflow in _init_fats / fat_table_read]", "cve_priority": "medium", "cve_public_date": "2026-09-17" }, { "cve": "CVE-2026-89088", "url": "https://ubuntu.com/security/CVE-2026-89088", "cve_description": "[heap buffer overflow in duplicate_legacy_root_dir]", "cve_priority": "medium", "cve_public_date": "2026-09-17" } ], "log": [ "", " * New upstream release:", " - CVE-2026-89085, CVE-2026-89088: Catch errors triggered by bad FAT", " metadata (closes: #1148169).", "" ], "package": "parted", "version": "3.8-1", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Colin Watson ", "date": "Fri, 25 Sep 2026 09:31:05 +0100" } ], "notes": null, "is_version_downgrade": false }, { "name": "passwd", "from_version": { "source_package_name": "shadow", "source_package_version": "1:4.19.3-2ubuntu1", "version": "1:4.19.3-2ubuntu1" }, "to_version": { "source_package_name": "shadow", "source_package_version": "1:4.19.3-2ubuntu2", "version": "1:4.19.3-2ubuntu2" }, "cves": [], "launchpad_bugs_fixed": [], "changes": [ { "cves": [], "log": [ "", " * No change rebuild with debhelper 14.5ubuntu1 to drop dependency from", " passwd to systemd.", "" ], "package": "shadow", "version": "1:4.19.3-2ubuntu2", "urgency": "medium", "distributions": "stonking", "launchpad_bugs_fixed": [], "author": "Michael Hudson-Doyle ", "date": "Wed, 23 Sep 2026 10:13:29 +1200" } ], "notes": null, "is_version_downgrade": false }, { "name": "python3-distro-info", "from_version": { "source_package_name": "distro-info", "source_package_version": "1.17", "version": "1.17" }, "to_version": { "source_package_name": "distro-info", "source_package_version": "1.19", "version": "1.19" }, "cves": [], "launchpad_bugs_fixed": [ 2131678 ], "changes": [ { "cves": [], "log": [ "", " * Makefile: remove python/.mypy_cache on clean", "" ], "package": "distro-info", "version": "1.19", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Benjamin Drung ", "date": "Tue, 29 Sep 2026 12:41:41 +0200" }, { "cves": [], "log": [ "", " * Support Ubuntu Pro with Legacy add-on (LP: #2131678):", " - ubuntu-distro-info: add --supported-legacy", " - python: add UbuntuDistroInfo.supported_legacy", " - perl: add UbuntuDistroInfo.supported_legacy", " * Add test cases for ubuntu-distro-info --supported-esm", "" ], "package": "distro-info", "version": "1.18", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [ 2131678 ], "author": "Benjamin Drung ", "date": "Mon, 28 Sep 2026 16:01:16 +0200" } ], "notes": null, "is_version_downgrade": false }, { "name": "python3-launchpadlib", "from_version": { "source_package_name": "python-launchpadlib", "source_package_version": "2.1.0-1build1", "version": "2.1.0-1build1" }, "to_version": { "source_package_name": "python-launchpadlib", "source_package_version": "2.1.0-2", "version": "2.1.0-2" }, "cves": [], "launchpad_bugs_fixed": [], "changes": [ { "cves": [], "log": [ "", " * Team upload.", "", " [ Alexandre Detiste ]", " * Remove redundant Priority: optional from source stanza.", " * Upgrade upstream signing key to new packet format.", " * Update standards version to 4.7.4, no changes needed.", " * Stop Suggesting removed python3-pkg-resources.", " * Drop \"Rules-Requires-Root: no\": it is the default now.", " * Rewrite d/watch in v5 format.", " * Add debian/salsa-ci.yml.", " * Use dh-sequence-python3.", "", " [ Colin Watson ]", " * Remove pkg_resources (closes: #1147419).", "" ], "package": "python-launchpadlib", "version": "2.1.0-2", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Colin Watson ", "date": "Tue, 15 Sep 2026 16:27:15 +0100" } ], "notes": null, "is_version_downgrade": false }, { "name": "python3-netplan", "from_version": { "source_package_name": "netplan.io", "source_package_version": "1.2.2-1", "version": "1.2.2-1" }, "to_version": { "source_package_name": "netplan.io", "source_package_version": "1.2.2-3", "version": "1.2.2-3" }, "cves": [], "launchpad_bugs_fixed": [], "changes": [ { "cves": [], "log": [ "", " [ Grayson Wolf ]", " * d/p/lp2168838-ovs-test.patch: Fix autopkgtests on ovs 4 (Closes: #1149299)", "" ], "package": "netplan.io", "version": "1.2.2-3", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Lukas Märdian ", "date": "Wed, 30 Sep 2026 20:59:16 +0200" }, { "cves": [], "log": [ "", " * d/t/prep-testbed: Remove LXC quirks (Closes: #1144818)", " which are not needed for incus-lxc anymore.", "" ], "package": "netplan.io", "version": "1.2.2-2", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Lukas Märdian ", "date": "Thu, 27 Aug 2026 18:12:25 +0200" } ], "notes": null, "is_version_downgrade": false }, { "name": "python3-requests", "from_version": { "source_package_name": "requests", "source_package_version": "2.34.2-1", "version": "2.34.2-1" }, "to_version": { "source_package_name": "requests", "source_package_version": "2.34.2-1ubuntu1", "version": "2.34.2-1ubuntu1" }, "cves": [], "launchpad_bugs_fixed": [ 2166950, 2166950 ], "changes": [ { "cves": [], "log": [ "", " * d/p/0003-help-Catch-AttributeError-from-urllib3-contrib-pyopenssl.patch:", " Catch AttributeError when importing urllib3.contrib.pyopenssl in", " requests.help (LP: #2166950)", " * d/p/0004-certs-Add-SKID-and-AKID-extensions.patch: add subjectKeyIdentifier", " and authorityKeyIdentifier to the regenerated test certificates", " (LP: #2166950)", "" ], "package": "requests", "version": "2.34.2-1ubuntu1", "urgency": "medium", "distributions": "stonking", "launchpad_bugs_fixed": [ 2166950, 2166950 ], "author": "Grayson Wolf ", "date": "Tue, 15 Sep 2026 17:30:46 -0400" } ], "notes": null, "is_version_downgrade": false }, { "name": "python3-urllib3", "from_version": { "source_package_name": "python-urllib3", "source_package_version": "2.7.0-3", "version": "2.7.0-3" }, "to_version": { "source_package_name": "python-urllib3", "source_package_version": "2.8.0-1", "version": "2.8.0-1" }, "cves": [], "launchpad_bugs_fixed": [], "changes": [ { "cves": [], "log": [ "", " * Team upload.", " * New upstream release:", " - GHSA-8988-9cw3-xx77: The TLS configuration for HTTPS proxies could be", " ignored or overridden.", " - GHSA-vxq7-64xx-v4gw: HTTPResponse.stream() and read_chunked() could", " buffer a chunk-size line of unbounded length in memory.", " - GHSA-gh4c-6fx4-qh6g: Chunked Deflate streaming could enter an infinite", " loop.", " * Drop python3-backports.zstd build/test-dependencies.", " * Skip tests that fail due to recent changes in Python.", "" ], "package": "python-urllib3", "version": "2.8.0-1", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Colin Watson ", "date": "Sun, 20 Sep 2026 14:30:46 +0100" } ], "notes": null, "is_version_downgrade": false }, { "name": "python3.14", "from_version": { "source_package_name": "python3.14", "source_package_version": "3.14.7-4ubuntu2", "version": "3.14.7-4ubuntu2" }, "to_version": { "source_package_name": "python3.14", "source_package_version": "3.14.8-1ubuntu1", "version": "3.14.8-1ubuntu1" }, "cves": [], "launchpad_bugs_fixed": [], "changes": [ { "cves": [], "log": [ "", " * Merge with Debian; remaining changes:", " - Revert the module-install-* autopkg tests to run with setuptools v78.", "" ], "package": "python3.14", "version": "3.14.8-1ubuntu1", "urgency": "medium", "distributions": "stonking", "launchpad_bugs_fixed": [], "author": "Matthias Klose ", "date": "Thu, 01 Oct 2026 22:09:47 +0200" }, { "cves": [], "log": [ "", " * Python 3.14.8 release.", " * Refresh patches.", "" ], "package": "python3.14", "version": "3.14.8-1", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Matthias Klose ", "date": "Thu, 01 Oct 2026 21:55:55 +0200" }, { "cves": [], "log": [ "", " * Merge with Debian; remaining changes:", " - Revert the module-install-* autopkg tests to run with setuptools v78.", "" ], "package": "python3.14", "version": "3.14.7-5ubuntu1", "urgency": "medium", "distributions": "stonking", "launchpad_bugs_fixed": [], "author": "Matthias Klose ", "date": "Sun, 27 Sep 2026 09:49:39 +0200" }, { "cves": [], "log": [ "", " * Update to the 3.14 branch 2026-09-27.", " * Update devhelp documentation for devhelp format v2 (Simon McVittie).", " Addresses: #1147626.", "" ], "package": "python3.14", "version": "3.14.7-5", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Matthias Klose ", "date": "Sun, 27 Sep 2026 09:22:20 +0200" } ], "notes": null, "is_version_downgrade": false }, { "name": "python3.14-minimal", "from_version": { "source_package_name": "python3.14", "source_package_version": "3.14.7-4ubuntu2", "version": "3.14.7-4ubuntu2" }, "to_version": { "source_package_name": "python3.14", "source_package_version": "3.14.8-1ubuntu1", "version": "3.14.8-1ubuntu1" }, "cves": [], "launchpad_bugs_fixed": [], "changes": [ { "cves": [], "log": [ "", " * Merge with Debian; remaining changes:", " - Revert the module-install-* autopkg tests to run with setuptools v78.", "" ], "package": "python3.14", "version": "3.14.8-1ubuntu1", "urgency": "medium", "distributions": "stonking", "launchpad_bugs_fixed": [], "author": "Matthias Klose ", "date": "Thu, 01 Oct 2026 22:09:47 +0200" }, { "cves": [], "log": [ "", " * Python 3.14.8 release.", " * Refresh patches.", "" ], "package": "python3.14", "version": "3.14.8-1", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Matthias Klose ", "date": "Thu, 01 Oct 2026 21:55:55 +0200" }, { "cves": [], "log": [ "", " * Merge with Debian; remaining changes:", " - Revert the module-install-* autopkg tests to run with setuptools v78.", "" ], "package": "python3.14", "version": "3.14.7-5ubuntu1", "urgency": "medium", "distributions": "stonking", "launchpad_bugs_fixed": [], "author": "Matthias Klose ", "date": "Sun, 27 Sep 2026 09:49:39 +0200" }, { "cves": [], "log": [ "", " * Update to the 3.14 branch 2026-09-27.", " * Update devhelp documentation for devhelp format v2 (Simon McVittie).", " Addresses: #1147626.", "" ], "package": "python3.14", "version": "3.14.7-5", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Matthias Klose ", "date": "Sun, 27 Sep 2026 09:22:20 +0200" } ], "notes": null, "is_version_downgrade": false }, { "name": "rust-coreutils", "from_version": { "source_package_name": "rust-coreutils", "source_package_version": "0.12.0-1ubuntu1", "version": "0.12.0-1ubuntu1" }, "to_version": { "source_package_name": "rust-coreutils", "source_package_version": "0.12.0-1ubuntu2", "version": "0.12.0-1ubuntu2" }, "cves": [], "launchpad_bugs_fixed": [ 2167794 ], "changes": [ { "cves": [], "log": [ "", " * d/p/safe-traversal-eoverflow-32bit: Fix EOVERFLOW in safe-traversal on 32-bit", " architectures (LP: #2167794)", " * d/p/ln-follow-symlinked-parent: Follow a symlinked parent directory", " when replacing a link", "" ], "package": "rust-coreutils", "version": "0.12.0-1ubuntu2", "urgency": "medium", "distributions": "stonking", "launchpad_bugs_fixed": [ 2167794 ], "author": "Varun Varma ", "date": "Mon, 25 Sep 2026 17:50:00 -0400" } ], "notes": null, "is_version_downgrade": false }, { "name": "systemd", "from_version": { "source_package_name": "systemd", "source_package_version": "261.2-1ubuntu2", "version": "261.2-1ubuntu2" }, "to_version": { "source_package_name": "systemd", "source_package_version": "261.3-0ubuntu3", "version": "261.3-0ubuntu3" }, "cves": [], "launchpad_bugs_fixed": [ 2169316 ], "changes": [ { "cves": [], "log": [ "", " * d/rules: remove libssl3t64 Depends (LP: #2169316)", "" ], "package": "systemd", "version": "261.3-0ubuntu3", "urgency": "medium", "distributions": "stonking", "launchpad_bugs_fixed": [ 2169316 ], "author": "Nick Rosbrook ", "date": "Fri, 02 Oct 2026 13:35:38 -0400" }, { "cves": [], "log": [ "", " * d/udev.install: do not install tpm2 rules on i386", "" ], "package": "systemd", "version": "261.3-0ubuntu2", "urgency": "medium", "distributions": "stonking", "launchpad_bugs_fixed": [], "author": "Nick Rosbrook ", "date": "Wed, 23 Sep 2026 08:39:15 -0400" }, { "cves": [], "log": [ "", " * New upstream stable version 261.3", " - d/gbp.conf: set upstream branch to 261.x stable", " - d/watch: track 261.x stable", " - Update upstream source from tag 'upstream/261.3'", " Update to upstream version '261.3'", " with Debian dir 3857375784a9bdd0b319a0e09222392a5d485461", " - Bug fixes", " * mkosi: remove systemd from minimal-base on ubuntu", " * d/systemd.links: stop creating hwclock.service mask", "" ], "package": "systemd", "version": "261.3-0ubuntu1", "urgency": "medium", "distributions": "stonking", "launchpad_bugs_fixed": [], "author": "Nick Rosbrook ", "date": "Mon, 21 Sep 2026 17:15:49 -0400" } ], "notes": null, "is_version_downgrade": false }, { "name": "systemd-resolved", "from_version": { "source_package_name": "systemd", "source_package_version": "261.2-1ubuntu2", "version": "261.2-1ubuntu2" }, "to_version": { "source_package_name": "systemd", "source_package_version": "261.3-0ubuntu3", "version": "261.3-0ubuntu3" }, "cves": [], "launchpad_bugs_fixed": [ 2169316 ], "changes": [ { "cves": [], "log": [ "", " * d/rules: remove libssl3t64 Depends (LP: #2169316)", "" ], "package": "systemd", "version": "261.3-0ubuntu3", "urgency": "medium", "distributions": "stonking", "launchpad_bugs_fixed": [ 2169316 ], "author": "Nick Rosbrook ", "date": "Fri, 02 Oct 2026 13:35:38 -0400" }, { "cves": [], "log": [ "", " * d/udev.install: do not install tpm2 rules on i386", "" ], "package": "systemd", "version": "261.3-0ubuntu2", "urgency": "medium", "distributions": "stonking", "launchpad_bugs_fixed": [], "author": "Nick Rosbrook ", "date": "Wed, 23 Sep 2026 08:39:15 -0400" }, { "cves": [], "log": [ "", " * New upstream stable version 261.3", " - d/gbp.conf: set upstream branch to 261.x stable", " - d/watch: track 261.x stable", " - Update upstream source from tag 'upstream/261.3'", " Update to upstream version '261.3'", " with Debian dir 3857375784a9bdd0b319a0e09222392a5d485461", " - Bug fixes", " * mkosi: remove systemd from minimal-base on ubuntu", " * d/systemd.links: stop creating hwclock.service mask", "" ], "package": "systemd", "version": "261.3-0ubuntu1", "urgency": "medium", "distributions": "stonking", "launchpad_bugs_fixed": [], "author": "Nick Rosbrook ", "date": "Mon, 21 Sep 2026 17:15:49 -0400" } ], "notes": null, "is_version_downgrade": false }, { "name": "systemd-sysv", "from_version": { "source_package_name": "systemd", "source_package_version": "261.2-1ubuntu2", "version": "261.2-1ubuntu2" }, "to_version": { "source_package_name": "systemd", "source_package_version": "261.3-0ubuntu3", "version": "261.3-0ubuntu3" }, "cves": [], "launchpad_bugs_fixed": [ 2169316 ], "changes": [ { "cves": [], "log": [ "", " * d/rules: remove libssl3t64 Depends (LP: #2169316)", "" ], "package": "systemd", "version": "261.3-0ubuntu3", "urgency": "medium", "distributions": "stonking", "launchpad_bugs_fixed": [ 2169316 ], "author": "Nick Rosbrook ", "date": "Fri, 02 Oct 2026 13:35:38 -0400" }, { "cves": [], "log": [ "", " * d/udev.install: do not install tpm2 rules on i386", "" ], "package": "systemd", "version": "261.3-0ubuntu2", "urgency": "medium", "distributions": "stonking", "launchpad_bugs_fixed": [], "author": "Nick Rosbrook ", "date": "Wed, 23 Sep 2026 08:39:15 -0400" }, { "cves": [], "log": [ "", " * New upstream stable version 261.3", " - d/gbp.conf: set upstream branch to 261.x stable", " - d/watch: track 261.x stable", " - Update upstream source from tag 'upstream/261.3'", " Update to upstream version '261.3'", " with Debian dir 3857375784a9bdd0b319a0e09222392a5d485461", " - Bug fixes", " * mkosi: remove systemd from minimal-base on ubuntu", " * d/systemd.links: stop creating hwclock.service mask", "" ], "package": "systemd", "version": "261.3-0ubuntu1", "urgency": "medium", "distributions": "stonking", "launchpad_bugs_fixed": [], "author": "Nick Rosbrook ", "date": "Mon, 21 Sep 2026 17:15:49 -0400" } ], "notes": null, "is_version_downgrade": false }, { "name": "tar", "from_version": { "source_package_name": "tar", "source_package_version": "1.35+dfsg-4", "version": "1.35+dfsg-4" }, "to_version": { "source_package_name": "tar", "source_package_version": "1.35+dfsg-5ubuntu1", "version": "1.35+dfsg-5ubuntu1" }, "cves": [ { "cve": "CVE-2025-45582", "url": "https://ubuntu.com/security/CVE-2025-45582", "cve_description": "GNU Tar through 1.35 allows file overwrite via directory traversal in crafted TAR archives, with a certain two-step process. First, the victim must extract an archive that contains a ../ symlink to a critical directory. Second, the victim must extract an archive that contains a critical file, specified via a relative pathname that begins with the symlink name and ends with that critical file's name. Here, the extraction follows the symlink and overwrites the critical file. This bypasses the protection mechanism of \"Member name contains '..'\" that would occur for a single TAR archive that attempted to specify the critical file via a ../ approach. For example, the first archive can contain \"x -> ../../../../../home/victim/.ssh\" and the second archive can contain x/authorized_keys. This can affect server applications that automatically extract any number of user-supplied TAR archives, and were relying on the blocking of traversal. This can also affect software installation processes in which \"tar xf\" is run more than once (e.g., when installing a package can automatically install two dependencies that are set up as untrusted tarballs instead of official packages). NOTE: the official GNU Tar manual has an otherwise-empty directory for each \"tar xf\" in its Security Rules of Thumb; however, third-party advice leads users to run \"tar xf\" more than once into the same directory.", "cve_priority": "medium", "cve_public_date": "2025-07-11 17:15:00 UTC" }, { "cve": "CVE-2026-5704", "url": "https://ubuntu.com/security/CVE-2026-5704", "cve_description": "A flaw was found in tar. A remote attacker could exploit this vulnerability by crafting a malicious archive, leading to hidden file injection with fully attacker-controlled content. This bypasses pre-extraction inspection mechanisms, potentially allowing an attacker to introduce malicious files onto a system without detection.", "cve_priority": "medium", "cve_public_date": "2026-04-06 16:16:00 UTC" }, { "cve": "CVE-2026-5704", "url": "https://ubuntu.com/security/CVE-2026-5704", "cve_description": "A flaw was found in tar. A remote attacker could exploit this vulnerability by crafting a malicious archive, leading to hidden file injection with fully attacker-controlled content. This bypasses pre-extraction inspection mechanisms, potentially allowing an attacker to introduce malicious files onto a system without detection.", "cve_priority": "medium", "cve_public_date": "2026-04-06 16:16:00 UTC" }, { "cve": "CVE-2026-5704", "url": "https://ubuntu.com/security/CVE-2026-5704", "cve_description": "A flaw was found in tar. A remote attacker could exploit this vulnerability by crafting a malicious archive, leading to hidden file injection with fully attacker-controlled content. This bypasses pre-extraction inspection mechanisms, potentially allowing an attacker to introduce malicious files onto a system without detection.", "cve_priority": "medium", "cve_public_date": "2026-04-06 16:16:00 UTC" }, { "cve": "CVE-2025-45582", "url": "https://ubuntu.com/security/CVE-2025-45582", "cve_description": "GNU Tar through 1.35 allows file overwrite via directory traversal in crafted TAR archives, with a certain two-step process. First, the victim must extract an archive that contains a ../ symlink to a critical directory. Second, the victim must extract an archive that contains a critical file, specified via a relative pathname that begins with the symlink name and ends with that critical file's name. Here, the extraction follows the symlink and overwrites the critical file. This bypasses the protection mechanism of \"Member name contains '..'\" that would occur for a single TAR archive that attempted to specify the critical file via a ../ approach. For example, the first archive can contain \"x -> ../../../../../home/victim/.ssh\" and the second archive can contain x/authorized_keys. This can affect server applications that automatically extract any number of user-supplied TAR archives, and were relying on the blocking of traversal. This can also affect software installation processes in which \"tar xf\" is run more than once (e.g., when installing a package can automatically install two dependencies that are set up as untrusted tarballs instead of official packages). NOTE: the official GNU Tar manual has an otherwise-empty directory for each \"tar xf\" in its Security Rules of Thumb; however, third-party advice leads users to run \"tar xf\" more than once into the same directory.", "cve_priority": "medium", "cve_public_date": "2025-07-11 17:15:00 UTC" } ], "launchpad_bugs_fixed": [ 2163533, 2160650, 2161311 ], "changes": [ { "cves": [ { "cve": "CVE-2025-45582", "url": "https://ubuntu.com/security/CVE-2025-45582", "cve_description": "GNU Tar through 1.35 allows file overwrite via directory traversal in crafted TAR archives, with a certain two-step process. First, the victim must extract an archive that contains a ../ symlink to a critical directory. Second, the victim must extract an archive that contains a critical file, specified via a relative pathname that begins with the symlink name and ends with that critical file's name. Here, the extraction follows the symlink and overwrites the critical file. This bypasses the protection mechanism of \"Member name contains '..'\" that would occur for a single TAR archive that attempted to specify the critical file via a ../ approach. For example, the first archive can contain \"x -> ../../../../../home/victim/.ssh\" and the second archive can contain x/authorized_keys. This can affect server applications that automatically extract any number of user-supplied TAR archives, and were relying on the blocking of traversal. This can also affect software installation processes in which \"tar xf\" is run more than once (e.g., when installing a package can automatically install two dependencies that are set up as untrusted tarballs instead of official packages). NOTE: the official GNU Tar manual has an otherwise-empty directory for each \"tar xf\" in its Security Rules of Thumb; however, third-party advice leads users to run \"tar xf\" more than once into the same directory.", "cve_priority": "medium", "cve_public_date": "2025-07-11 17:15:00 UTC" }, { "cve": "CVE-2026-5704", "url": "https://ubuntu.com/security/CVE-2026-5704", "cve_description": "A flaw was found in tar. A remote attacker could exploit this vulnerability by crafting a malicious archive, leading to hidden file injection with fully attacker-controlled content. This bypasses pre-extraction inspection mechanisms, potentially allowing an attacker to introduce malicious files onto a system without detection.", "cve_priority": "medium", "cve_public_date": "2026-04-06 16:16:00 UTC" } ], "log": [ "", " * Merge with Debian unstable. (LP: #2163533) Remaining changes:", " - d/patches:", " + SECURITY UPDATE: File overwrite via directory traversal", " - debian/patches/CVE-2025-45582-*.patch: Backport openat2 support in order", " to jailify the extraction directory.", " - Addresses CVE-2025-45582", " + SECURITY UPDATE: file injection via crafted archive", " - debian/patches/CVE-2026-5704.patch: always call skip_member() after", " extraction in src/extract.c, fix skim_member() to skip directory data", " in src/list.c, remove conditional skip_member() call from", " purge_directory in src/incremen.c", " - debian/patches/CVE-2026-5704-*.patch: address a regression that makes", " valid files not extract in src/list.c, tests/Makefile.am,", " tests/extrac32.at, tests/extrac34.at, test/testsuite.at, src/extract.c,", " tests/extract23, tests/extrac30.at.", " - debian/patches/CVE-2026-5704-5.patch: fix \"Old archives with nonzero", " directory sizes failing to be extracted\" by forcing the size to zero", " afor DIRTYPE in read_header() in src/list.c", " - Addresses CVE-2026-5704", " * New changes:", " - d/patches:", " + Fix d/p/0001 line markers", "" ], "package": "tar", "version": "1.35+dfsg-5ubuntu1", "urgency": "medium", "distributions": "stonking", "launchpad_bugs_fixed": [ 2163533 ], "author": "Pierre-Elliott Bécue ", "date": "Tue, 18 Aug 2026 19:58:00 +0200" }, { "cves": [], "log": [ "", " * Team upload (salsa.debian.org/debian namespace)", " * Add libacl FTBFS fix from bug-tar mailing list (Closes: #1141146)", " * Slight tweak of upstream patch to apply cleanly to 1.35", "" ], "package": "tar", "version": "1.35+dfsg-5", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Simon Josefsson ", "date": "Sat, 01 Aug 2026 14:00:00 +0200" }, { "cves": [ { "cve": "CVE-2026-5704", "url": "https://ubuntu.com/security/CVE-2026-5704", "cve_description": "A flaw was found in tar. A remote attacker could exploit this vulnerability by crafting a malicious archive, leading to hidden file injection with fully attacker-controlled content. This bypasses pre-extraction inspection mechanisms, potentially allowing an attacker to introduce malicious files onto a system without detection.", "cve_priority": "medium", "cve_public_date": "2026-04-06 16:16:00 UTC" } ], "log": [ "", " [ Leonidas Da Silva Barbosa ]", " * SECURITY REGRESSION: Extract files issue", " - debian/patches/CVE-2026-5704-*.patch: address a regression", " that makes valid files not extract in src/list.c,", " tests/Makefile.am, tests/extrac32.at, tests/extrac34.at,", " test/testsuite.at, src/extract.c, tests/extract23,", " tests/extrac30.at (LP: #2160650).", " * SECURITY REGRESSION: Old archives with nonzero directory sizes", " failing to be extracted", " - debian/patches/CVE-2026-5704-5.patch: fix this by forcing", " the size to zero for DIRTYPE in read_header() in src/list.c", " (LP: #2161311)", "" ], "package": "tar", "version": "1.35+dfsg-4ubuntu2", "urgency": "medium", "distributions": "stonking", "launchpad_bugs_fixed": [ 2160650, 2161311 ], "author": "Marc Deslauriers ", "date": "Mon, 27 Jul 2026 12:58:33 -0400" }, { "cves": [ { "cve": "CVE-2026-5704", "url": "https://ubuntu.com/security/CVE-2026-5704", "cve_description": "A flaw was found in tar. A remote attacker could exploit this vulnerability by crafting a malicious archive, leading to hidden file injection with fully attacker-controlled content. This bypasses pre-extraction inspection mechanisms, potentially allowing an attacker to introduce malicious files onto a system without detection.", "cve_priority": "medium", "cve_public_date": "2026-04-06 16:16:00 UTC" }, { "cve": "CVE-2025-45582", "url": "https://ubuntu.com/security/CVE-2025-45582", "cve_description": "GNU Tar through 1.35 allows file overwrite via directory traversal in crafted TAR archives, with a certain two-step process. First, the victim must extract an archive that contains a ../ symlink to a critical directory. Second, the victim must extract an archive that contains a critical file, specified via a relative pathname that begins with the symlink name and ends with that critical file's name. Here, the extraction follows the symlink and overwrites the critical file. This bypasses the protection mechanism of \"Member name contains '..'\" that would occur for a single TAR archive that attempted to specify the critical file via a ../ approach. For example, the first archive can contain \"x -> ../../../../../home/victim/.ssh\" and the second archive can contain x/authorized_keys. This can affect server applications that automatically extract any number of user-supplied TAR archives, and were relying on the blocking of traversal. This can also affect software installation processes in which \"tar xf\" is run more than once (e.g., when installing a package can automatically install two dependencies that are set up as untrusted tarballs instead of official packages). NOTE: the official GNU Tar manual has an otherwise-empty directory for each \"tar xf\" in its Security Rules of Thumb; however, third-party advice leads users to run \"tar xf\" more than once into the same directory.", "cve_priority": "medium", "cve_public_date": "2025-07-11 17:15:00 UTC" } ], "log": [ "", " [ Leonidas Da Silva Barbosa ]", " * SECURITY UPDATE: file injection via crafted archive", " - debian/patches/CVE-2026-5704.patch: always call skip_member() after", " extraction in src/extract.c, fix skim_member() to skip directory data", " in src/list.c, remove conditional skip_member() call from", " purge_directory in src/incremen.c", " - CVE-2026-5704", "", " [ Marc Deslauriers ]", " * SECURITY UPDATE: File overwrite via directory traversal", " - debian/patches/CVE-2025-45582-*.patch: Backport openat2 support in", " order to jailify the extraction directory.", " - CVE-2025-45582", "" ], "package": "tar", "version": "1.35+dfsg-4ubuntu1", "urgency": "medium", "distributions": "stonking", "launchpad_bugs_fixed": [], "author": "Marc Deslauriers ", "date": "Mon, 29 Jun 2026 07:52:01 -0400" } ], "notes": null, "is_version_downgrade": false }, { "name": "tzdata", "from_version": { "source_package_name": "tzdata", "source_package_version": "2026c-1ubuntu1", "version": "2026c-1ubuntu1" }, "to_version": { "source_package_name": "tzdata", "source_package_version": "2026e-1ubuntu1", "version": "2026e-1ubuntu1" }, "cves": [], "launchpad_bugs_fixed": [ 2169125 ], "changes": [ { "cves": [], "log": [ "", " * Merge with Debian unstable (LP: #2169125). Remaining changes:", " - Ship 2026c ICU timezone data which are utilized by PHP in tzdata-icu", " - Add autopkgtest test case for ICU timezone data", " - Point Vcs-Browser/Git to Launchpad", " * Update the ICU timezone data to 2026e", " * Add autopkgtest test case for ICU timezone data 2026d and 2026e", "" ], "package": "tzdata", "version": "2026e-1ubuntu1", "urgency": "medium", "distributions": "stonking", "launchpad_bugs_fixed": [ 2169125 ], "author": "Benjamin Drung ", "date": "Fri, 02 Oct 2026 13:21:30 +0200" }, { "cves": [], "log": [ "", " * New upstream version 2026d:", " - Canada’s Northwest Territories moved to permanent -06 on 2026-08-21 and", " will not fall back from -06 to -07 on 2026-11-01", " * New upstream version 2026e:", " - Manitoba moves to permanent -05 on 2026-10-31 and will not fall back", " from -05 to -06 on 2026-11-01", " * Add autopkgtest test cases for 2026d and 2026e releases", " * Revert POSIX conformance of old SysV names EST5EDT, CST6CDT, MST7MDT and", " PST8PDT", " * Bump debhelper compatibility to 14", "" ], "package": "tzdata", "version": "2026e-1", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Aurelien Jarno ", "date": "Wed, 30 Sep 2026 21:01:06 +0000" } ], "notes": null, "is_version_downgrade": false }, { "name": "ubuntu-drivers-common", "from_version": { "source_package_name": "ubuntu-drivers-common", "source_package_version": "1:0.10.11", "version": "1:0.10.11" }, "to_version": { "source_package_name": "ubuntu-drivers-common", "source_package_version": "1:0.10.13", "version": "1:0.10.13" }, "cves": [], "launchpad_bugs_fixed": [ 2168955, 2165071 ], "changes": [ { "cves": [], "log": [ "", " [ Mitchell Augustin ]", " * Exclude dmidecode from dependency list on ppc64el and s390x", "", " [ Kai Chuan Hsieh ]", " * Prioritize custom GPU config and fix runtimepm/-open handling (LP: #2168955)", "" ], "package": "ubuntu-drivers-common", "version": "1:0.10.13", "urgency": "medium", "distributions": "stonking", "launchpad_bugs_fixed": [ 2168955 ], "author": "Mitchell Augustin ", "date": "Thu, 01 Oct 2026 13:54:43 -0500" }, { "cves": [], "log": [ "", " [ Andreas Glinserer ]", " * Add modalias detection (LP: #2165071)", "", " [ Mitchell Augustin ]", " * Add MIDR detection (LP #2165071)", "" ], "package": "ubuntu-drivers-common", "version": "1:0.10.12", "urgency": "medium", "distributions": "stonking", "launchpad_bugs_fixed": [ 2165071 ], "author": "Mitchell Augustin ", "date": "Fri, 25 Sep 2026 12:23:02 -0500" } ], "notes": null, "is_version_downgrade": false }, { "name": "udev", "from_version": { "source_package_name": "systemd", "source_package_version": "261.2-1ubuntu2", "version": "261.2-1ubuntu2" }, "to_version": { "source_package_name": "systemd", "source_package_version": "261.3-0ubuntu3", "version": "261.3-0ubuntu3" }, "cves": [], "launchpad_bugs_fixed": [ 2169316 ], "changes": [ { "cves": [], "log": [ "", " * d/rules: remove libssl3t64 Depends (LP: #2169316)", "" ], "package": "systemd", "version": "261.3-0ubuntu3", "urgency": "medium", "distributions": "stonking", "launchpad_bugs_fixed": [ 2169316 ], "author": "Nick Rosbrook ", "date": "Fri, 02 Oct 2026 13:35:38 -0400" }, { "cves": [], "log": [ "", " * d/udev.install: do not install tpm2 rules on i386", "" ], "package": "systemd", "version": "261.3-0ubuntu2", "urgency": "medium", "distributions": "stonking", "launchpad_bugs_fixed": [], "author": "Nick Rosbrook ", "date": "Wed, 23 Sep 2026 08:39:15 -0400" }, { "cves": [], "log": [ "", " * New upstream stable version 261.3", " - d/gbp.conf: set upstream branch to 261.x stable", " - d/watch: track 261.x stable", " - Update upstream source from tag 'upstream/261.3'", " Update to upstream version '261.3'", " with Debian dir 3857375784a9bdd0b319a0e09222392a5d485461", " - Bug fixes", " * mkosi: remove systemd from minimal-base on ubuntu", " * d/systemd.links: stop creating hwclock.service mask", "" ], "package": "systemd", "version": "261.3-0ubuntu1", "urgency": "medium", "distributions": "stonking", "launchpad_bugs_fixed": [], "author": "Nick Rosbrook ", "date": "Mon, 21 Sep 2026 17:15:49 -0400" } ], "notes": null, "is_version_downgrade": false }, { "name": "util-linux", "from_version": { "source_package_name": "util-linux", "source_package_version": "2.41.3-3ubuntu2", "version": "2.41.3-3ubuntu2" }, "to_version": { "source_package_name": "util-linux", "source_package_version": "2.42.2-1ubuntu2", "version": "2.42.2-1ubuntu2" }, "cves": [ { "cve": "CVE-2026-53612", "url": "https://ubuntu.com/security/CVE-2026-53612", "cve_description": "[Local Privilege Escalation via TOCTOU in mount(8) hook_owner.c chmod/chown]", "cve_priority": "medium", "cve_public_date": "2026-06-18" }, { "cve": "CVE-2026-53613", "url": "https://ubuntu.com/security/CVE-2026-53613", "cve_description": "[Local Privilege Escalation via TOCTOU in mount(8) - Target Path Redirection]", "cve_priority": "medium", "cve_public_date": "2026-06-18" }, { "cve": "CVE-2026-53614", "url": "https://ubuntu.com/security/CVE-2026-53614", "cve_description": "[Local Privilege Escalation via LIBMOUNT_FORCE_MOUNT2 Environment Variable - nosuid/noexec Bypass in SUID mount(8)]", "cve_priority": "medium", "cve_public_date": "2026-06-18" }, { "cve": "CVE-2026-27456", "url": "https://ubuntu.com/security/CVE-2026-27456", "cve_description": "util-linux is a random collection of Linux utilities. Prior to version 2.41.4, a TOCTOU (Time-of-Check-Time-of-Use) vulnerability has been identified in the SUID binary /usr/bin/mount from util-linux. The mount binary, when setting up loop devices, validates the source file path with user privileges via fork() + setuid() + realpath(), but subsequently re-canonicalizes and opens it with root privileges (euid=0) without verifying that the path has not been replaced between both operations. Neither O_NOFOLLOW, nor inode comparison, nor post-open fstat() are employed. This allows a local unprivileged user to replace the source file with a symlink pointing to any root-owned file or device during the race window, causing the SUID binary to open and mount it as root. Exploitation requires an /etc/fstab entry with user,loop options whose path points to a directory where the attacker has write permission, and that /usr/bin/mount has the SUID bit set (the default configuration on virtually all Linux distributions). The impact is unauthorized read access to root-protected files and block devices, including backup images, disk volumes, and any file containing a valid filesystem. This issue has been patched in version 2.41.4.", "cve_priority": "medium", "cve_public_date": "2026-04-03 22:16:00 UTC" }, { "cve": "CVE-2026-3184", "url": "https://ubuntu.com/security/CVE-2026-3184", "cve_description": "A flaw was found in util-linux. Improper hostname canonicalization in the `login(1)` utility, when invoked with the `-h` option, can modify the supplied remote hostname before setting `PAM_RHOST`. A remote attacker could exploit this by providing a specially crafted hostname, potentially bypassing host-based Pluggable Authentication Modules (PAM) access control rules that rely on fully qualified domain names. This could lead to unauthorized access.", "cve_priority": "medium", "cve_public_date": "2026-04-03 19:17:00 UTC" } ], "launchpad_bugs_fixed": [ 2166882, 2153369, 2125968 ], "changes": [ { "cves": [], "log": [ "", " * d/p/ubuntu/libmount-restricted-live-creds.patch: restore live-credential", " check for libmount restricted mode (LP: #2166882)", "" ], "package": "util-linux", "version": "2.42.2-1ubuntu2", "urgency": "medium", "distributions": "stonking", "launchpad_bugs_fixed": [ 2166882 ], "author": "Nadzeya Hutsko ", "date": "Wed, 16 Sep 2026 19:36:33 +0200" }, { "cves": [], "log": [ "", " * Merge with Debian unstable (LP: #2153369).", " Added changes:", " - tests/fincore: force the use of GNU dd over uutils (LP: #2125968)", " Remaining changes:", " - Add sulogin-fallback-static-sh.patch", " Add support for /bin/static-sh as fallback if the regular shell fails to", " execute. Patch ported from sysvinit. (see LP #505887)", " - Add sulogin-lockedpwd.patch", " Make sure file systems can be fixed on machines with locked root", " accounts (as Ubuntu does by default). Don't require --force for sulogin.", " - d/rules: disable libmount mountfs support", " Disable brand new feature with --disable-libmount-mountfd-support that", " causes inability to deploy MAAS LP #2037417.", " - d/p/ubuntu/su-pty-drop-caps.patch: harden 'su --pty' to temporarily lower", " capabilities while proxying between stdin/stdout and the pty master. This", " is to avoid su from being used to exploit kernel vulnerabilities.", "" ], "package": "util-linux", "version": "2.42.2-1ubuntu1", "urgency": "medium", "distributions": "stonking", "launchpad_bugs_fixed": [ 2153369, 2125968 ], "author": "Florent 'Skia' Jacquet ", "date": "Fri, 26 Jun 2026 12:03:00 +0200" }, { "cves": [ { "cve": "CVE-2026-53612", "url": "https://ubuntu.com/security/CVE-2026-53612", "cve_description": "[Local Privilege Escalation via TOCTOU in mount(8) hook_owner.c chmod/chown]", "cve_priority": "medium", "cve_public_date": "2026-06-18" }, { "cve": "CVE-2026-53613", "url": "https://ubuntu.com/security/CVE-2026-53613", "cve_description": "[Local Privilege Escalation via TOCTOU in mount(8) - Target Path Redirection]", "cve_priority": "medium", "cve_public_date": "2026-06-18" }, { "cve": "CVE-2026-53614", "url": "https://ubuntu.com/security/CVE-2026-53614", "cve_description": "[Local Privilege Escalation via LIBMOUNT_FORCE_MOUNT2 Environment Variable - nosuid/noexec Bypass in SUID mount(8)]", "cve_priority": "medium", "cve_public_date": "2026-06-18" } ], "log": [ "", " * New upstream version, fixing security issues", " CVE-2026-53612, CVE-2026-53613, CVE-2026-53614 (Closes: #1140194,", " #1140195, #1140196)", " * Drop upstream-applied patch.", "" ], "package": "util-linux", "version": "2.42.2-1", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Wed, 17 Jun 2026 11:20:49 +0200" }, { "cves": [], "log": [ "", " * Follow debhelper 14.1, thus putting PAM files back into /etc/pam.d.", " Note that include=login is still undesirable, and packages should", " include common-* instead.", "" ], "package": "util-linux", "version": "2.42.1-6", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Tue, 16 Jun 2026 22:26:25 +0200" }, { "cves": [], "log": [ "", " * PAM config: stop using include.", " Avoid including our own PAM config files, as a workaround until PAM can", " include files from /usr/lib/pam.d.", " Should make su -(l) and runuser -l work again. See #1140029.", "" ], "package": "util-linux", "version": "2.42.1-5", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Mon, 15 Jun 2026 19:34:54 +0200" }, { "cves": [], "log": [ "", " * Update debhelper-compat to v14.", " Remove dh-sequence-installsysusers, remove ${misc:Pre-Depends} from", " Pre-Depends. PAM /etc/pam.d files are replaced by files in", " /usr/lib/pam.d.", "" ], "package": "util-linux", "version": "2.42.1-4", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Sun, 14 Jun 2026 17:28:35 +0200" }, { "cves": [], "log": [ "", " * Use upstream patch to fix FTBFS on systems with non-4K pagesizes", " (Closes: #1138789)", "" ], "package": "util-linux", "version": "2.42.1-3", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Mon, 08 Jun 2026 15:05:17 +0200" }, { "cves": [], "log": [ "", " * Fix FTBFS on systems with non-4K pagesizes (Closes: #1138789)", "" ], "package": "util-linux", "version": "2.42.1-2", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Thu, 04 Jun 2026 13:31:17 +0200" }, { "cves": [], "log": [ "", " * New upstream version", " * Refresh/drop upstream applied patches", "", " [ Karel Zak ]", " * script: fix backward compatibility for options after non-option args", " * script: fix \"--\" separator when used as option argument", " (Closes: #1132887)", "" ], "package": "util-linux", "version": "2.42.1-1", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Wed, 03 Jun 2026 20:12:19 +0200" }, { "cves": [], "log": [ "", " * Stop using Linux crypto API in hardlink(1)", "" ], "package": "util-linux", "version": "2.42-6", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Wed, 06 May 2026 20:41:22 +0200" }, { "cves": [], "log": [ "", " * Remove leftover /etc/init.d/uuidd conffile", "" ], "package": "util-linux", "version": "2.42-5", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Sun, 26 Apr 2026 14:49:42 +0200" }, { "cves": [], "log": [ "", " * Apply upstream revert of su breakage", " (Closes: #1133379, #1132588, #1132610)", "" ], "package": "util-linux", "version": "2.42-4", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Sun, 19 Apr 2026 17:36:56 +0200" }, { "cves": [], "log": [ "", " * Stop pulling deb_systemdsystemunitdir from pkg-config", " * Stop installing uuidd init script", " * Clarify /bin/login situation on Hurd", " * Install bash-completions using normal dh_install mechanism", " * Install more localized man pages", " * Simplify installing into udebs", " * Install lintian overrides into udebs", " * Run a second build without libsystemd for d-i.", " This is not great, but I see no other option at this time.", " Let's hope a libsystemd0-udeb will appear. (Closes: #1132561)", " * util-linux-extra: install copyfilerange, getino", " * Update lintian overrides", " * Update dependency libselinux1-dev to libselinux-dev", "" ], "package": "util-linux", "version": "2.42-3", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Sun, 12 Apr 2026 00:03:33 +0200" }, { "cves": [], "log": [ "", " * Add upstream patches addressing #1132887", "" ], "package": "util-linux", "version": "2.42-2", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Wed, 08 Apr 2026 18:28:21 +0200" }, { "cves": [ { "cve": "CVE-2026-27456", "url": "https://ubuntu.com/security/CVE-2026-27456", "cve_description": "util-linux is a random collection of Linux utilities. Prior to version 2.41.4, a TOCTOU (Time-of-Check-Time-of-Use) vulnerability has been identified in the SUID binary /usr/bin/mount from util-linux. The mount binary, when setting up loop devices, validates the source file path with user privileges via fork() + setuid() + realpath(), but subsequently re-canonicalizes and opens it with root privileges (euid=0) without verifying that the path has not been replaced between both operations. Neither O_NOFOLLOW, nor inode comparison, nor post-open fstat() are employed. This allows a local unprivileged user to replace the source file with a symlink pointing to any root-owned file or device during the race window, causing the SUID binary to open and mount it as root. Exploitation requires an /etc/fstab entry with user,loop options whose path points to a directory where the attacker has write permission, and that /usr/bin/mount has the SUID bit set (the default configuration on virtually all Linux distributions). The impact is unauthorized read access to root-protected files and block devices, including backup images, disk volumes, and any file containing a valid filesystem. This issue has been patched in version 2.41.4.", "cve_priority": "medium", "cve_public_date": "2026-04-03 22:16:00 UTC" } ], "log": [ "", " * New upstream release, fixing CVE-2026-27456 and a CWE-190.", " * Upload to unstable.", "" ], "package": "util-linux", "version": "2.42-1", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Thu, 02 Apr 2026 15:19:42 +0200" }, { "cves": [], "log": [ "", " * New upstream release candidate.", " * Refresh patches", "" ], "package": "util-linux", "version": "2.42~rc2-1", "urgency": "medium", "distributions": "experimental", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Thu, 26 Mar 2026 15:05:59 +0100" }, { "cves": [], "log": [ "", " * Apply upstream patches", " * Fixes unshare issue", " * Use Hurd patches directly from upstream", "" ], "package": "util-linux", "version": "2.42~rc1-3", "urgency": "medium", "distributions": "experimental", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Sun, 22 Mar 2026 15:20:19 +0100" }, { "cves": [], "log": [ "", " * Fix lsmem tests on loong64.", " Using patch from https://github.com/util-linux/util-linux/pull/4090", " * autopkgtests: switch to pkgconf", "", " [ Samuel Thibault ]", " * Fix build on Hurd", "" ], "package": "util-linux", "version": "2.42~rc1-2", "urgency": "medium", "distributions": "experimental", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Tue, 03 Mar 2026 12:43:24 +0100" }, { "cves": [ { "cve": "CVE-2026-3184", "url": "https://ubuntu.com/security/CVE-2026-3184", "cve_description": "A flaw was found in util-linux. Improper hostname canonicalization in the `login(1)` utility, when invoked with the `-h` option, can modify the supplied remote hostname before setting `PAM_RHOST`. A remote attacker could exploit this by providing a specially crafted hostname, potentially bypassing host-based Pluggable Authentication Modules (PAM) access control rules that rely on fully qualified domain names. This could lead to unauthorized access.", "cve_priority": "medium", "cve_public_date": "2026-04-03 19:17:00 UTC" } ], "log": [ "", " * New upstream release candidate.", " * includes fix for CVE-2026-3184:", " * login: use original FQDN for PAM_RHOST", " * libuuid: reset initial cont-clock time on service start (Closes:", " #1126894)", " * Symbols: use (symver) and update lists", " * Stop installing untranslated man pages", "" ], "package": "util-linux", "version": "2.42~rc1-1", "urgency": "medium", "distributions": "experimental", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Sat, 28 Feb 2026 20:37:48 +0100" }, { "cves": [], "log": [ "", " [ Chris Hofstaedtler ]", " * Follow libselinux1-dev to libselinux-dev rename (Closes: #1124751)", " * uuid-runtime: stop removing /var/run/uuidd on purge", " /run is a tmpfs, it will be cleaned up anyway. Lets us drop the postrm", " maintscript.", "", " [ Luca Boccassi ]", " * uuid-runtime: drop manual scripting in postinst and rely on sysusers.d", "" ], "package": "util-linux", "version": "2.41.3-4", "urgency": "medium", "distributions": "unstable", "launchpad_bugs_fixed": [], "author": "Chris Hofstaedtler ", "date": "Sat, 21 Feb 2026 17:15:50 +0100" } ], "notes": null, "is_version_downgrade": false } ], "snap": [] }, "added": { "deb": [ { "name": "linux-image-7.3.0-8-generic", "from_version": { "source_package_name": "linux-signed", "source_package_version": "7.3.0-5.5", "version": null }, "to_version": { "source_package_name": "linux-signed", "source_package_version": "7.3.0-8.8", "version": "7.3.0-8.8" }, "cves": [], "launchpad_bugs_fixed": [ 1786013, 1786013, 1786013 ], "changes": [ { "cves": [], "log": [ "", " * Main version: 7.3.0-8.8", "", " * Packaging resync (LP: #1786013)", " - [Packaging] debian/tracking-bug -- resync from main package", "" ], "package": "linux-signed", "version": "7.3.0-8.8", "urgency": "medium", "distributions": "stonking", "launchpad_bugs_fixed": [ 1786013 ], "author": "Paolo Pisati ", "date": "Tue, 29 Sep 2026 19:08:49 +0200" }, { "cves": [], "log": [ "", " * Main version: 7.3.0-7.7", "", " * Packaging resync (LP: #1786013)", " - [Packaging] debian/tracking-bug -- resync from main package", "" ], "package": "linux-signed", "version": "7.3.0-7.7", "urgency": "medium", "distributions": "stonking", "launchpad_bugs_fixed": [ 1786013 ], "author": "Paolo Pisati ", "date": "Mon, 28 Sep 2026 18:13:46 +0200" }, { "cves": [], "log": [ "", " * Main version: 7.3.0-6.6", "", " * Packaging resync (LP: #1786013)", " - [Packaging] debian/tracking-bug -- resync from main package", "" ], "package": "linux-signed", "version": "7.3.0-6.6", "urgency": "medium", "distributions": "stonking", "launchpad_bugs_fixed": [ 1786013 ], "author": "Paolo Pisati ", "date": "Mon, 21 Sep 2026 17:08:13 +0200" } ], "notes": "linux-image-7.3.0-8-generic version '7.3.0-8.8' (source package linux-signed version '7.3.0-8.8') was added. linux-image-7.3.0-8-generic version '7.3.0-8.8' has the same source package name, linux-signed, as removed package linux-image-7.3.0-5-generic. As such we can use the source package version of the removed package, '7.3.0-5.5', as the starting point in our changelog diff. Kernel packages are an example of where the binary package name changes for the same source package. Using the removed package source package version as our starting point means we can still get meaningful changelog diffs even for what appears to be a new package.", "is_version_downgrade": false }, { "name": "linux-main-modules-v4l2loopback-7.3.0-8-generic", "from_version": { "source_package_name": "linux-main-signed", "source_package_version": "7.3.0-5.5", "version": null }, "to_version": { "source_package_name": "linux-main-signed", "source_package_version": "7.3.0-8.8+1", "version": "7.3.0-8.8+1" }, "cves": [], "launchpad_bugs_fixed": [ 1786013, 1786013, 1786013, 2166733, 1786013 ], "changes": [ { "cves": [], "log": [ "", " * Packaging resync (LP: #1786013)", " - [Packaging] debian/dkms-versions -- update from kernel-versions", " (main/d2026.09.28)", "", " * Miscellaneous Ubuntu changes", " - [Packaging] lmm: Process all modules and fail only at the end if any failed", " - [Packaging] Add various dependencies for Lustre", " - [Packaging] Fix dkms.conf PACKAGE_VERSION parsing across newlines", " - [Packaging]: Add an rdepends option for dependent modules", " - [Packaging]: Update manifest file with new patches", "" ], "package": "linux-main-signed", "version": "7.3.0-8.8+1", "urgency": "medium", "distributions": "stonking", "launchpad_bugs_fixed": [ 1786013 ], "author": "Paolo Pisati ", "date": "Wed, 30 Sep 2026 15:06:15 +0200" }, { "cves": [], "log": [ "", " * Main version: 7.3.0-8.8", "", " * Packaging resync (LP: #1786013)", " - [Packaging] debian/tracking-bug -- resync from main package", "" ], "package": "linux-main-signed", "version": "7.3.0-8.8", "urgency": "medium", "distributions": "stonking", "launchpad_bugs_fixed": [ 1786013 ], "author": "Paolo Pisati ", "date": "Tue, 29 Sep 2026 19:09:11 +0200" }, { "cves": [], "log": [ "", " * Main version: 7.3.0-7.7", "", " * Packaging resync (LP: #1786013)", " - [Packaging] debian/tracking-bug -- resync from main package", " - [Packaging] debian/dkms-versions -- update from kernel-versions", " (main/d2026.09.28)", "" ], "package": "linux-main-signed", "version": "7.3.0-7.7", "urgency": "medium", "distributions": "stonking", "launchpad_bugs_fixed": [ 1786013 ], "author": "Paolo Pisati ", "date": "Mon, 28 Sep 2026 18:14:13 +0200" }, { "cves": [], "log": [ "", "", " * New upstream core24.60 release (LP: #2166733)", " - [Packaging] add bison/flex for iwlwifi", "", " * Miscellaneous Ubuntu changes", " - [Packaging]: lmm: Add the kernel version to the kernel variant", " - [Packaging] lmm: Add flavour migration support", " - [Packaging] Allow debpaths of additional formats", " - [Packaging] Remove compat file from lmg ancillary", " - [Packaging]: Update manifest file with new patches", "" ], "package": "linux-main-signed", "version": "7.3.0-6.6+1", "urgency": "medium", "distributions": "stonking", "launchpad_bugs_fixed": [ 2166733 ], "author": "Paolo Pisati ", "date": "Tue, 22 Sep 2026 09:33:03 +0200" }, { "cves": [], "log": [ "", " * Main version: 7.3.0-6.6", "", " * Packaging resync (LP: #1786013)", " - [Packaging] debian/tracking-bug -- resync from main package", " - [Packaging] debian/dkms-versions -- update from kernel-versions", " (main/d2026.09.21)", "" ], "package": "linux-main-signed", "version": "7.3.0-6.6", "urgency": "medium", "distributions": "stonking", "launchpad_bugs_fixed": [ 1786013 ], "author": "Paolo Pisati ", "date": "Mon, 21 Sep 2026 17:08:41 +0200" } ], "notes": "linux-main-modules-v4l2loopback-7.3.0-8-generic version '7.3.0-8.8+1' (source package linux-main-signed version '7.3.0-8.8+1') was added. linux-main-modules-v4l2loopback-7.3.0-8-generic version '7.3.0-8.8+1' has the same source package name, linux-main-signed, as removed package linux-main-modules-zfs-7.3.0-5-generic. As such we can use the source package version of the removed package, '7.3.0-5.5', as the starting point in our changelog diff. Kernel packages are an example of where the binary package name changes for the same source package. Using the removed package source package version as our starting point means we can still get meaningful changelog diffs even for what appears to be a new package.", "is_version_downgrade": false }, { "name": "linux-main-modules-zfs-7.3.0-8-generic", "from_version": { "source_package_name": "linux-main-signed", "source_package_version": "7.3.0-5.5", "version": null }, "to_version": { "source_package_name": "linux-main-signed", "source_package_version": "7.3.0-8.8+1", "version": "7.3.0-8.8+1" }, "cves": [], "launchpad_bugs_fixed": [ 1786013, 1786013, 1786013, 2166733, 1786013 ], "changes": [ { "cves": [], "log": [ "", " * Packaging resync (LP: #1786013)", " - [Packaging] debian/dkms-versions -- update from kernel-versions", " (main/d2026.09.28)", "", " * Miscellaneous Ubuntu changes", " - [Packaging] lmm: Process all modules and fail only at the end if any failed", " - [Packaging] Add various dependencies for Lustre", " - [Packaging] Fix dkms.conf PACKAGE_VERSION parsing across newlines", " - [Packaging]: Add an rdepends option for dependent modules", " - [Packaging]: Update manifest file with new patches", "" ], "package": "linux-main-signed", "version": "7.3.0-8.8+1", "urgency": "medium", "distributions": "stonking", "launchpad_bugs_fixed": [ 1786013 ], "author": "Paolo Pisati ", "date": "Wed, 30 Sep 2026 15:06:15 +0200" }, { "cves": [], "log": [ "", " * Main version: 7.3.0-8.8", "", " * Packaging resync (LP: #1786013)", " - [Packaging] debian/tracking-bug -- resync from main package", "" ], "package": "linux-main-signed", "version": "7.3.0-8.8", "urgency": "medium", "distributions": "stonking", "launchpad_bugs_fixed": [ 1786013 ], "author": "Paolo Pisati ", "date": "Tue, 29 Sep 2026 19:09:11 +0200" }, { "cves": [], "log": [ "", " * Main version: 7.3.0-7.7", "", " * Packaging resync (LP: #1786013)", " - [Packaging] debian/tracking-bug -- resync from main package", " - [Packaging] debian/dkms-versions -- update from kernel-versions", " (main/d2026.09.28)", "" ], "package": "linux-main-signed", "version": "7.3.0-7.7", "urgency": "medium", "distributions": "stonking", "launchpad_bugs_fixed": [ 1786013 ], "author": "Paolo Pisati ", "date": "Mon, 28 Sep 2026 18:14:13 +0200" }, { "cves": [], "log": [ "", "", " * New upstream core24.60 release (LP: #2166733)", " - [Packaging] add bison/flex for iwlwifi", "", " * Miscellaneous Ubuntu changes", " - [Packaging]: lmm: Add the kernel version to the kernel variant", " - [Packaging] lmm: Add flavour migration support", " - [Packaging] Allow debpaths of additional formats", " - [Packaging] Remove compat file from lmg ancillary", " - [Packaging]: Update manifest file with new patches", "" ], "package": "linux-main-signed", "version": "7.3.0-6.6+1", "urgency": "medium", "distributions": "stonking", "launchpad_bugs_fixed": [ 2166733 ], "author": "Paolo Pisati ", "date": "Tue, 22 Sep 2026 09:33:03 +0200" }, { "cves": [], "log": [ "", " * Main version: 7.3.0-6.6", "", " * Packaging resync (LP: #1786013)", " - [Packaging] debian/tracking-bug -- resync from main package", " - [Packaging] debian/dkms-versions -- update from kernel-versions", " (main/d2026.09.21)", "" ], "package": "linux-main-signed", "version": "7.3.0-6.6", "urgency": "medium", "distributions": "stonking", "launchpad_bugs_fixed": [ 1786013 ], "author": "Paolo Pisati ", "date": "Mon, 21 Sep 2026 17:08:41 +0200" } ], "notes": "linux-main-modules-zfs-7.3.0-8-generic version '7.3.0-8.8+1' (source package linux-main-signed version '7.3.0-8.8+1') was added. linux-main-modules-zfs-7.3.0-8-generic version '7.3.0-8.8+1' has the same source package name, linux-main-signed, as removed package linux-main-modules-zfs-7.3.0-5-generic. As such we can use the source package version of the removed package, '7.3.0-5.5', as the starting point in our changelog diff. Kernel packages are an example of where the binary package name changes for the same source package. Using the removed package source package version as our starting point means we can still get meaningful changelog diffs even for what appears to be a new package.", "is_version_downgrade": false }, { "name": "linux-modules-7.3.0-8-generic", "from_version": { "source_package_name": "linux", "source_package_version": "7.3.0-5.5", "version": null }, "to_version": { "source_package_name": "linux", "source_package_version": "7.3.0-8.8", "version": "7.3.0-8.8" }, "cves": [], "launchpad_bugs_fixed": [ 2168832, 2150845, 2168012, 2158501, 2168730, 2168432, 2160082, 2167819, 2167217, 2167689, 2167558, 2167555, 2167552, 2167550, 2121852, 2121477, 2144643, 2167219, 2166235, 2158462 ], "changes": [ { "cves": [], "log": [ "", " * stonking/linux: 7.3.0-8.8 -proposed tracker (LP: #2168832)", "", " * Ubuntu 26.04 linux kernel has non-functional nova-core GPU driver enabled,", " conflicting with nouveau (LP: #2150845)", " - [Config] Disable DRM_NOVA", " - [Config] Disable NOVA_CORE", "", " * Include v4l2loopback in default modules set for 26.04 (LP: #2168012)", " - [Packaging] Add dependency for v4l2loopback", "", " * linux: enable CONFIG_EROFS_FS_PAGE_CACHE_SHARE (LP: #2158501)", " - [Config] Enable CONFIG_EROFS_FS_PAGE_CACHE_SHARE", "" ], "package": "linux", "version": "7.3.0-8.8", "urgency": "medium", "distributions": "stonking", "launchpad_bugs_fixed": [ 2168832, 2150845, 2168012, 2158501 ], "author": "Paolo Pisati ", "date": "Tue, 29 Sep 2026 19:04:39 +0200" }, { "cves": [], "log": [ "", " * stonking/linux: 7.3.0-7.7 -proposed tracker (LP: #2168730)", "", " * Stonking real-time patchset v7.3-rc4-rt1 (LP: #2168432)", " - SAUCE: drm/i915: Use preempt_disable/enable_rt() where recommended", " - SAUCE: drm/i915: Don't disable interrupts on PREEMPT_RT during atomic", " updates", " - SAUCE: drm/i915: Disable tracing points on PREEMPT_RT", " - SAUCE: drm/i915/gt: Use spin_lock_irq() instead of local_irq_disable() +", " spin_lock()", " - SAUCE: drm/i915: Drop the irqs_disabled() check", " - SAUCE: drm/i915/guc: Consider also RCU depth in busy loop.", " - SAUCE: Revert \"drm/i915: Depend on !PREEMPT_RT.\"", " - SAUCE: drm/i915: Consider RCU read section as atomic.", " - [debian] update master upstream-realtime", "", " * Linux, Ubuntu, 24.04, System hangs for about 10 seconds when unplug", " external monitor cable on non TBT dock (LP: #2160082)", " - Revert \"UBUNTU: SAUCE: drm/i915/lnl+/tc: Fix false disconnect of active", " DP-alt TC port during long HPD pulse\"", "" ], "package": "linux", "version": "7.3.0-7.7", "urgency": "medium", "distributions": "stonking", "launchpad_bugs_fixed": [ 2168730, 2168432, 2160082 ], "author": "Paolo Pisati ", "date": "Mon, 28 Sep 2026 17:46:02 +0200" }, { "cves": [], "log": [ "", " * stonking/linux: 7.3.0-6.6 -proposed tracker (LP: #2167819)", "", " * 26.10 Snapdragon X Elite: Sync concept kernel changes (LP: #2167217)", " - SAUCE: arm64: dts: qcom: x1e78100-lenovo-thinkpad-t14s: Describe the", " PCIe M.2 Key M connector", " - SAUCE: arm64: dts: qcom: x1e78100-lenovo-thinkpad-t14s: Describe PCIe", " M.2 1620 LGA connector", " - SAUCE: arm64: dts: qcom: hamoa/purwa: Add QREF regulator supplies", " - SAUCE: dt-bindings: arm: qcom: Distinguish IdeaCentre Mini 01Q8X10 SKUs", " - SAUCE: arm64: dts: qcom: Split IdeaCentre Mini into a common DTSI", " - SAUCE: arm64: dts: qcom: Add Purwa IdeaCentre Mini 01Q8X10", " - SAUCE: arm64: dts: qcom: ideacentre-mini: Build the Hamoa EL2 DTB", " - SAUCE: arm64: dts: qcom: ideacentre-mini: Fix the second M.2 3V3 rail", " - SAUCE: arm64: dts: qcom: ideacentre-mini: Wire up DP sound names and VA", " macro", " - SAUCE: arm64: dts: qcom: ideacentre-mini: Drop the unused USB MP port", " - SAUCE: dt-bindings: arm: qcom: Add Lenovo Ideapad Slim 5 variants", " - SAUCE: firmware: qcom: scm: Allow QSEECOM on Lenovo IdeaPad 5 models", " - SAUCE: arm64: dts: qcom: Add Lenovo IdeaPad Slim 5x 14Q8X9", " - SAUCE: arm64: dts: qcom: glymur: Add PCIe3 PHY and PCIe3a controller", " nodes", " - SAUCE: arm64: dts: qcom: glymur-crd: Add PHY supplies for pcie3_phy", " - SAUCE: dt-bindings: arm: qcom: Add Asus Zenbook A14 (UX3407NA)", " - SAUCE: arm64: dts: qcom: glymur: Add Asus Zenbook A14 (UX3407NA)", " - SAUCE: firmware: qcom: scm: Allow QSEECOM on Asus Zenbook A14 (UX3407NA)", " - SAUCE: dt-bindings: arm: qcom: Add HP EliteBook X G2q 14 AI", " - SAUCE: arm64: dts: qcom: Add HP EliteBook X G2q 14 AI", " - SAUCE: firmware: qcom: scm: Allow QSEECOM on HP EliteBook X G2q 14 AI", " - SAUCE: dt-bindings: arm: qcom: Add Lenovo Yoga Slim 7x Gen11", " - SAUCE: arm64: dts: qcom: glymur: Add Lenovo Yoga Slim 7x Gen11", " - SAUCE: firmware: qcom: scm: Allow QSEECOM on Yoga Slim 7x Gen11", " - SAUCE: phy: qcom: edp: split power-on sequencing by PHY version", " - SAUCE: phy: qcom: edp: update v8 power-on programming sequence", "", " * Support TI TAC5xx2 audio codec on Intel NVL platform (LP: #2167689)", " - soundwire: intel_auxdevice: add tac5xx2 family to wake_capable_list", "", " * Add support for Zen6 EPP tunings (LP: #2167558)", " - cpufreq/amd-pstate: Add per SoC and per core type EPP tuning values", " - cpufreq/amd-pstate: Add EPP tunings for Zen6 client platforms", " - cpufreq/amd-pstate: Show a warning if missing EPP tunings", "", " * Zen 6 client HSMP support (LP: #2167555)", " - SAUCE: platform/x86/amd/hsmp: Add HSMP client support for Family 1Ah", " - SAUCE: platform/x86/amd/hsmp: Route metric table through the client", " messages", " - SAUCE: platform/x86/amd/hsmp: Add ACPI client support for Family 1Ah", " - SAUCE: platform/x86/amd/hsmp: Document and expose client telemetry table", " in UAPI", "", " * Fix fTPM handling on Zen 6 platforms (LP: #2167552)", " - tpm: Call cmd_ready/go_idle for each command transmission", "", " * Add support for CPPC values for Zen6 (LP: #2167550)", " - SAUCE: ACPI: CPPC: Refactor boost ratio handling", " - SAUCE: cpufreq/acpi-cpufreq: Use amd_get_boost_ratio()", " - SAUCE: cpufreq/amd-pstate: Get Highest Freq for a CPU", "", " * Support Samsung S5K3J1 sensor for Intel MIPI camera (LP: #2121852)", " - SAUCE: media: ipu-bridge: Support s5k3j1 sensor", "", " * 25.10 Snapdragon X Elite: Sync concept kernel changes (LP: #2121477)", " - SAUCE: arm64: dts: qcom: x1e80100-dell-xps13-9345: Add Left/Right", " Speakers and Tweeter", " - SAUCE: arm64: dts: qcom: x1e80100-dell-xps13-9345: enable MICs LDO", " - SAUCE: arm64: dts: qcom: x1e80100-dell-xps13-9345: Mark audio channels", " as left-right swapped", " - SAUCE: arm64: dts: qcom: x1-acer-swift-14: Add support for Acer Swift 14", " - SAUCE: dt-bindings: arm: qcom: Add Acer Swift 14 AI", " - SAUCE: Update x1-acer device trees for v7.3", "", " * 26.04 Snapdragon X Elite: Sync concept kernel changes (LP: #2144643)", " - SAUCE: dt-bindings: phy: qcom: Add CSI2 C-PHY/DPHY schema", " - SAUCE: phy: qcom-mipi-csi2: Add a CSI2 MIPI DPHY driver", " - SAUCE: dt-bindings: media: qcom,x1e80100-camss: Add simple-mfd", " compatible", " - SAUCE: dt-bindings: media: qcom,x1e80100-camss: Add optional PHY handle", " definitions", " - SAUCE: dt-bindings: media: qcom,x1e80100-camss: Add support for combo-", " mode endpoints", " - SAUCE: dt-bindings: media: qcom,x1e80100-camss: Describe iommu entries", " - SAUCE: media: qcom: camss: Add legacy_phy flag to SoC definition", " structures", " - SAUCE: media: qcom: camss: Add support for PHY API devices", " - SAUCE: media: qcom: camss: Drop legacy PHY descriptions from x1e", " - SAUCE: arm64: dts: qcom: x1e80100: Add CCI definitions", " - SAUCE: arm64: dts: qcom: x1e80100: Add CAMSS block definition", " - SAUCE: arm64: dts: qcom: x1e80100-crd: Add pm8010 CRD pmic,id=m", " regulators", " - SAUCE: arm64: dts: qcom: x1e80100-crd: Add ov08x40 RGB sensor on CSIPHY4", " - SAUCE: arm64: dts: qcom: x1e80100-t14s: Add pm8010 camera PMIC with", " voltage levels for IR and RGB camera", " - SAUCE: arm64: dts: qcom: x1e80100-t14s: Add on ov02c10 RGB sensor on", " CSIPHY4", " - SAUCE: arm64: dts: qcom: x1e80100-lenovo-yoga-slim7x: Add pm8010 camera", " PMIC with voltage levels for IR and RGB camera", " - SAUCE: arm64: dts: qcom: x1e80100-lenovo-yoga-slim7x: Add l7b_2p8", " voltage regulator for RGB camera", " - SAUCE: arm64: dts: qcom: x1e80100-lenovo-yoga-slim7x: Add ov02c10 RGB", " sensor on CSIPHY4", " - SAUCE: arm64: dts: qcom: x1e80100-dell-inspiron14-7441: Switch on CAMSS", " RGB sensor", " - SAUCE: arm64: dts: qcom: x1e78100-t14s: enable camera privacy indicator", " - SAUCE: arm64: dts: qcom: x1e80100-lenovo-yoga-slim7x: enable camera", " privacy indicator", " - SAUCE: arm64: dts: qcom: x1-asus-zenbook-a14: Add on OV02C10 RGB sensor", " on CSIPHY4", " - SAUCE: arm64: dts: qcom: x1e80100-dell-xps13-9345: add camera support", " - SAUCE: arm64: dts: qcom: x1e80100-dell-xps13-9345: enable camera privacy", " indicator", " - SAUCE: arm64: dts: qcom: x1e-acer-swift-14: Move PCIe PERST and Wake", " GPIOs to port nodes", "", " * Add support for AMD Zen6 client SFH (LP: #2167219)", " - SAUCE: HID: amd_sfh: Add DMI quirk and module param to disable", " interrupts", " - SAUCE: HID: amd_sfh: Add support for newer AMD SoCs", " - SAUCE: HID: amd_sfh: Add HPD support for new AMD SOC", " - SAUCE: HID: amd_sfh: Add device mode support for latest AMD SOC.", "", " * append bpf to CONFIG_LSM (LP: #2166235)", " - [Config] append bpf to CONFIG_LSM", "", " * Malformed HV_LINUX_VENDOR_ID breaks VM Availability Metric on Azure", " (LP: #2158462)", " - SAUCE: (no-up) hv: Fix supplied vendor ID", "", " * Miscellaneous Ubuntu changes", " - [Packaging] Add incremental rebuild support", " - [Packaging] Snapshot incremental rebuild packages", " - SAUCE: arm64: dts: qcom: x1p42100-hp-elitebook-6-g1q: DT for HP", " EliteBook 6 G1q", " - SAUCE: arm64: dts: qcom: x1e80100-lenovo-yoga-slim7x: Fix RGB camera", " supplies", " - SAUCE: dt-bindings: arm: qcom: Document HP EliteBook 6 G1q", " - SAUCE: firmware: qcom: scm: Allow QSEECOM for HP EliteBook 6 G1q", " - [packaging] Create a linux-main-modules dependency toggle", " - [Config] toolchain version update", " - [Config] updateconfigs after v7.3-rc4 rebase", " - [Config] enable new v7.3-rc4 drivers as modules", " - [Packaging] Build-depend on clang/LLVM 22 to match rustc", " - [Packaging] compress the SPDX SBOM documents in linux-buildinfo", "" ], "package": "linux", "version": "7.3.0-6.6", "urgency": "medium", "distributions": "stonking", "launchpad_bugs_fixed": [ 2167819, 2167217, 2167689, 2167558, 2167555, 2167552, 2167550, 2121852, 2121477, 2144643, 2167219, 2166235, 2158462 ], "author": "Paolo Pisati ", "date": "Mon, 21 Sep 2026 16:57:39 +0200" } ], "notes": "linux-modules-7.3.0-8-generic version '7.3.0-8.8' (source package linux version '7.3.0-8.8') was added. linux-modules-7.3.0-8-generic version '7.3.0-8.8' has the same source package name, linux, as removed package linux-modules-7.3.0-5-generic. As such we can use the source package version of the removed package, '7.3.0-5.5', as the starting point in our changelog diff. Kernel packages are an example of where the binary package name changes for the same source package. Using the removed package source package version as our starting point means we can still get meaningful changelog diffs even for what appears to be a new package.", "is_version_downgrade": false } ], "snap": [] }, "removed": { "deb": [ { "name": "linux-image-7.3.0-5-generic", "from_version": { "source_package_name": "linux-signed", "source_package_version": "7.3.0-5.5", "version": "7.3.0-5.5" }, "to_version": { "source_package_name": null, "source_package_version": null, "version": null }, "cves": [], "launchpad_bugs_fixed": [], "changes": [], "notes": null, "is_version_downgrade": false }, { "name": "linux-main-modules-zfs-7.3.0-5-generic", "from_version": { "source_package_name": "linux-main-signed", "source_package_version": "7.3.0-5.5", "version": "7.3.0-5.5" }, "to_version": { "source_package_name": null, "source_package_version": null, "version": null }, "cves": [], "launchpad_bugs_fixed": [], "changes": [], "notes": null, "is_version_downgrade": false }, { "name": "linux-modules-7.3.0-5-generic", "from_version": { "source_package_name": "linux", "source_package_version": "7.3.0-5.5", "version": "7.3.0-5.5" }, "to_version": { "source_package_name": null, "source_package_version": null, "version": null }, "cves": [], "launchpad_bugs_fixed": [], "changes": [], "notes": null, "is_version_downgrade": false } ], "snap": [] }, "notes": "Changelog diff for Ubuntu 26.10 stonking image from daily image serial 20260925 to 20261006", "from_series": "stonking", "to_series": "stonking", "from_serial": "20260925", "to_serial": "20261006", "from_manifest_filename": "daily_manifest.previous", "to_manifest_filename": "manifest.current" }