Incus: Nil-pointer dereference in createDependentVolumesFromBackup on disk.{Volume,VolumeSnapshots,Pool}

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

2.1 · CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:P · score source

EPSS

• CVE-2026-48754: 0.38% estimated exploitation activity in the next 30 days; percentile 32.28 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary (backend).createDependentVolumesFromBackup in internal/server/storage/backend.go contains a cluster of unguarded pointer derefs on every dependent-volume entry's VolumeSnapshots[i], Volume, and Pool sub-fields. An authenticated user with cancreateinstances permission on any project can crash the incusd daemon by uploading an instance backup tarball whose dependentvolumes[] block contains a nil snapshot pointer (or omits volume: / pool:). This is a sibling-field variant of the 2026-05-04 batch fix d768f81c0a1d985f35ae56219519822b080bf5e3 ("Properly check dependent volumes on import"). That commit added if disk == nil at the top of the outer loop, but did not guard the four sub-pointer fields the loop body dereferences naked. Vulnerable code internal/server/storage/backend.go:9352-9412: disk has type config.Config (declared in internal/server/backup/config/backupconfig.go:8). Its Volume field is api.StorageVolume, Pool is api.StoragePool, VolumeSnapshots is…

Published by the source

26 Jun 2026, 18:52 UTC

Last modified by the source

26 Jun 2026, 18:52 UTC

Source last checked

26 Oct 2026, 15:24 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-4xg6-52mh-fpw8

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-48754

Advisory: Incus: Nil-pointer dereference in createDependentVolumesFromBackup on disk.{Volume,VolumeSnapshots,Pool}
IDs: CVE-2026-48754, GHSA-4xg6-52mh-fpw8
Record: https://patchnext.com/advisories/cve-2026-48754 (revision 1, source checked 26 Oct 2026, 15:24 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Low (CVSS 2.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/lxc/incus/v7/cmd/incusd 7.1.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/lxc/incus/v7/cmd/incusd: affected < 7.1.0; fixed in 7.1.0

## Suggested inspection (read-only)
- Go github.com/lxc/incus/v7/cmd/incusd: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/lxc/incus/v7/cmd/incusd.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-4xg6-52mh-fpw8 (GitHub-reviewed advisory GHSA-4xg6-52mh-fpw8 lists affected ranges: Go github.com/lxc/incus/v7/cmd/incusd >=0 <7.1.0)

Commands are suggestions: review each one before running it.