USN-9150-1 covers two SWUpdate vulnerabilities, but they are not the same problem. CVE-2025-41259 concerns path cleanup and a race condition; CVE-2026-109399 concerns how SWUpdate builds a certificate chain from CMS signatures. The advisory matters most to deployments that rely on SWUpdate as a security boundary for installing signed updates. [1]
Scope note: This is a Track A scope explainer, not a patching or firmware-deployment procedure. Canonical’s package table and the device’s actual update design must be evaluated separately.
What does CVE-2025-41259 change?
CVE-2025-41259 is a local race-condition issue in SWUpdate’s cleanup handling. Canonical says SWUpdate did not verify that a path was a directory before cleaning it up; under the stated conditions, a local attacker could possibly escalate privileges or install untrusted content using a signed update. [1]
The important boundary is the relationship between local filesystem state, SWUpdate’s cleanup behavior, and the authority granted to a signed update. The advisory does not establish that every device running SWUpdate has the same local permissions, cleanup path, or reachable code path.
What does CVE-2026-109399 change?
CVE-2026-109399 concerns certificate-chain construction for CMS signatures. Canonical says SWUpdate used untrusted certificates embedded in CMS signatures when building the chain, so an attacker with a signing key from another intermediate certificate authority under the same root could possibly install malicious updates. [1]
Canonical also describes the fix behavior: after the update, SWUpdate ignores certificates embedded in CMS signatures. The advisory says this issue affects Ubuntu 22.04 LTS and Ubuntu 26.04 LTS. [1]
That is narrower than saying “signed updates are broken.” Signature verification can involve several decisions: which roots are trusted, which certificates may build a chain, how the device receives metadata, and which update images the device accepts. A valid signature under one trust configuration is not automatically proof that the intended signer was authorized for that device.
Which Ubuntu releases and package rows are listed?
USN-9150-1 lists SWUpdate package rows for Ubuntu 22.04 LTS, 24.04 LTS, and 26.04 LTS. The published table includes Ubuntu ProFix/ESM Apps wording for those rows. [1]
Those rows are advisory scope, not a universal statement about every SWUpdate deployment. A device image may use a vendor package, a backport, a different distribution, or an independently built SWUpdate binary. Conversely, a matching package row does not by itself prove that the vulnerable feature path is enabled or reachable.
Do not translate an upstream or advisory version string into a device-level exposure decision without checking the authoritative package source and the device’s update architecture.
Why is this more than a routine package vulnerability?
SWUpdate sits inside an update trust boundary: it helps decide whether new software is accepted and installed. A flaw in filesystem cleanup can affect what the updater changes locally. A flaw in certificate-chain handling can affect which signer is considered acceptable. Those are different failure modes, but both can undermine the assumptions behind signed updates. [1]
The advisory therefore deserves architectural attention from embedded Linux maintainers, not just a search for a CVE number. The relevant questions include whether SWUpdate runs with elevated authority, how signing roots and intermediates are managed, whether update artifacts can be supplied by an untrusted party, and whether the device has a recovery path if an update is rejected or partially applied.
This article does not answer those environment-specific questions from the advisory alone.
What should a maintainer establish before making a decision?
Use the following questions to frame a review:
- Which Ubuntu release, vendor image, or independently built package supplies SWUpdate?
- Is the deployment within the release and package scope listed by Canonical?
- Does the device use CMS signatures, and which roots and intermediate certificates are trusted?
- Can an untrusted local user reach the affected cleanup path, or can an untrusted party supply update material?
- Which package or vendor record establishes the fixed state for the actual device image?
- What rollback or recovery path exists if the updater rejects an image or the update process fails?
These questions separate advisory applicability from incident evidence. They also prevent a common mistake: treating the presence of a signed update as proof that the entire update supply chain is correctly authorized.
What USN-9150-1 does not prove
The advisory does not prove that every SWUpdate installation is exploitable, that every signed update can be replaced, or that every embedded Linux device has the same certificate and cleanup configuration. It also does not provide enough information to infer a device’s installed state without environment-specific package and image evidence. [1]
For adjacent trust-boundary decisions, see the Linux server security hub, the flatpak-builder build-host boundary explainer, and the container image-signing and provenance guide. Those pages address different components; none substitutes for the Canonical advisory or the device vendor’s package and recovery documentation.
Sources
- Canonical USN-9150-1: SWUpdate vulnerabilities — advisory details, affected-release statement, and package table.
- Canonical CVE-2025-41259 — Ubuntu’s CVE description and release-specific package status.
- Canonical CVE-2026-109399 — Ubuntu’s CVE record linked by the advisory.
- Upstream SWUpdate cleanup fix — path-type check added before cleanup.
- Upstream SWUpdate CMS certificate-chain fix — direct-signer validation without additional certificates from the CMS payload.
Sources checked 2026-11-21. Package and CVE status can change; re-open the Canonical records for a current decision.