Bug 2467729 (CVE-2026-41684) - CVE-2026-41684 github.com/lxc/incus: Incus: Denial of Service via crafted backup archive
Summary: CVE-2026-41684 github.com/lxc/incus: Incus: Denial of Service via crafted bac...
Keywords:
Status: NEW
Alias: CVE-2026-41684
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 2477852
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-05-07 14:01 UTC by OSIDB Bzimport
Modified: 2026-05-15 12:55 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-05-07 14:01:46 UTC
Incus is a system container and virtual machine manager. Prior to version 7.0.0, backup.GetInfo() trusts the inline backup/index.yaml config when present and only falls back to parsing the legacy backup/container/backup.yaml file if result.Config == nil. As a result, an archive can carry a valid inline config that passes the initial import preflight while also carrying a malformed legacy backup/container/backup.yaml file that is reparsed later from the restored file system. ParseConfigYamlFile() accepts YAML documents with no container section, and multiple downstream consumers then dereference. Container without checking for nil. Confirmed examples in the instance restore and import flow include backup.UpdateInstanceConfig() and internalImportFromBackup(). An authenticated user with permission to import instance backups may be able to crash the Incus daemon with a crafted backup archive whose inline backup/index.yaml is valid but whose extracted legacy backup.yaml omits container. The crash occurs in the restore path after archive extraction has begun. This issue has been patched in version 7.0.0.


Note You need to log in before you can comment on or make changes to this bug.