Ubuntu USN-8833-1 Fixes libvirt Vulnerabilities
Tech GuruQuick Answer
Ubuntu 26.04's libvirt-hwe update in USN-8833-1 covers six vulnerabilities and requires a reboot. Confirm that this is the source stream behind your installed libvirt packages; the similarly named USN-8831-1 is not a reason to ignore this separate mapping.
Confirm Scope And Apply The Supported Fix
Next step: Match installed binary packages to Canonical's libvirt-hwe table, plan guest maintenance, and arrange console recovery before updating and rebooting the host.
Last verified: 2026-09-28 UTC. Recheck the authoritative advisory and supported distribution channel before changing production.
Scope And Authority
| Product scope | libvirt vulnerabilities on Ubuntu 26.04 LTS (resolute) |
|---|---|
| Advisory | USN-8833-1 |
| CVEs | CVE-2026-18917, CVE-2026-61477, CVE-2026-61478, CVE-2026-63622, CVE-2026-63623, CVE-2026-77159 |
| Authoritative release date | 2026-09-28 11:57:56.856825 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-8833-1: Ubuntu 26.04 LTS (resolute). |
| Fixed version | resolute: libvirt-hwe 12.0.0-1ubuntu5.5 |
| 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 issues include RPC overflow, XML-related denial of service, TPM-state ownership changes, disk-volume permissions, and injection of dnsmasq directives through network definitions. The latter requires the relevant network-definition privileges. Do not collapse these prerequisites into a claim of anonymous remote access to every guest.
What To Validate Now
- Inventory. Record the Ubuntu release, enabled repositories, installed binary packages (including the libvirt binary packages mapped to libvirt-hwe by Canonical), running consumers, and service owner. Check bundled application copies and container images separately.
- Establish applicability. Compare installed binary packages with USN-8833-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. After reboot, check guest management, DHCP/DNS on defined virtual networks, TPM-backed guests, and storage ownership and permissions. Use disposable network and volume definitions for permission checks; do not alter production guest disks to test a security boundary.
- 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.
