Ubuntu USN-8826-1 Fixes LXC Vulnerabilities
Tech GuruQuick Answer
USN-8826-1 updates LXC and requires restarting LXC containers after the update. Plan for that interruption before patching a container host. Use Canonical's binary-package table for your Ubuntu release; the source builds below are references, not an instruction to install source code.
Confirm Scope And Apply The Supported Fix
Next step: Inventory the host's LXC packages and containers, check the applicable Pro/ESM repository, and schedule the update and container restarts with workload owners.
Last verified: 2026-09-28 UTC. Recheck the authoritative advisory and supported distribution channel before changing production.
Scope And Authority
| Product scope | LXC vulnerabilities on Ubuntu 26.04 LTS (resolute), Ubuntu 24.04 LTS (noble), Ubuntu 22.04 LTS (jammy), Ubuntu 20.04 ESM (focal), Ubuntu 18.04 ESM (bionic), Ubuntu 16.04 ESM (xenial) |
|---|---|
| Advisory | USN-8826-1 |
| CVEs | CVE-2022-47952, CVE-2026-39402 |
| Authoritative release date | 2026-09-28 05:47:13.948996 UTC |
| Authority revision date | No separate material revision date is stated by Ubuntu; verified against the first-party notice API. |
| Affected versions | The Ubuntu releases and source packages enumerated in USN-8826-1: Ubuntu 26.04 LTS (resolute), Ubuntu 24.04 LTS (noble), Ubuntu 22.04 LTS (jammy), Ubuntu 20.04 ESM (focal), Ubuntu 18.04 ESM (bionic), Ubuntu 16.04 ESM (xenial). |
| Fixed version | bionic: lxc 3.0.3-0ubuntu1~18.04.3+esm1 / focal: lxc 1:4.0.12-0ubuntu1~20.04.1+esm1 / jammy: lxc 1:5.0.0~git2209-g5a7b9ce67-0ubuntu1.1+esm1 / noble: lxc 1:5.0.3-2ubuntu7.3+esm1 / resolute: lxc 1:6.0.6-1ubuntu1+esm1 / xenial: lxc 2.0.11-0ubuntu1~16.04.3+esm1 |
| CVSS base score | Not provided by the authority |
| CVSS severity | Not provided by the authority |
| Exploitation status | Not stated by the authority; no exploitation claim is inferred. |
What Changed
The notice covers information exposure involving failed logging and a separate authorization-related denial of service. The logging issue is described for Ubuntu 16.04 through 24.04; do not assign that same scope to 26.04 merely because it also has packages in this combined notice.
What To Validate Now
- Inventory. Record the Ubuntu release, enabled repositories, installed binary packages (including the applicable lxc and liblxc packages), running consumers, and service owner. Check bundled application copies and container images separately.
- Establish applicability. Compare installed binary packages with USN-8826-1's release-specific package table. The source-package builds summarized above identify the advisory's source release; they are not literal package-install commands.
- Remediate. Follow Canonical's current update instructions for the affected binary packages on this Ubuntu release. Confirm security or Pro/ESM repository access as applicable. Do not install a source-package name merely because it appears in the summary table.
- Validate. Confirm the updated LXC binaries, restart the affected containers as Canonical requires, and test container startup, expected access controls, networking, storage mounts, and logging. A healthy host package transaction does not prove every container workload recovered.
- Retain evidence. Preserve asset and owner identifiers, the applicability decision, before-and-after versions, change approval, installation output, validation results, and any exception or rollback record.
Operational Cautions
Some listed fixes are delivered through Ubuntu Pro or ESM. Confirm entitlement and repository state before the change, use the exact supported release stream, and test dependent services, clusters, and rollback. Severity alone is not evidence of exploitation.
Evidence To Retain
- Exact product, release stream, package or application version, enabled feature, environment, and accountable owner.
- UTC timestamps, authority revision, approved change record, installer or package-manager output, and resulting version.
- Relevant logs and monitoring evidence, test results, exceptions, compensating controls, and rollback decisions.
Related TechGeeks Resources
Authoritative References
Correction policy: If the authority changes affected versions, fixed versions, severity, exploitation information, mitigations, or required action, TechGeeks will update this notice and its verification date.
