Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Unrated

Canonical LXD documentation improvement to make clear restricted.devices.disk=allow without restricted.devices.disk.paths also allows shift=true

GHSA-x9qq-236j-gj97

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (github.com/canonical/lxd 5.20.0, 0.0.0-20240118092008-ce1bd0dd37bb), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • Go github.com/canonical/lxd

    Affected
    >= 5.19.0, <= 5.19.0>= 0.0.0-20230920084527-cbe39c5d3f14, < 0.0.0-20240118092008-ce1bd0dd37bb
    Fixed in
    5.20.0, 0.0.0-20240118092008-ce1bd0dd37bb

Sources

  • GitHub Advisory Database and maintainer security advisories on GitHub

    GitHub-reviewed advisory GHSA-x9qq-236j-gj97 lists affected ranges: Go github.com/canonical/lxd >=5.19.0 =0.0.0-20230920084527-cbe39c5d3f14 <0.0.0-20240118092008-ce1bd0dd37bb

    VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
not scored
EPSS
No dated EPSS signal available.
Source description

As published by the source; long descriptions are shortened.

Summary If a user has restricted access to a project that is configured with restricted=true, they can gain root access on the system by creating a disk device with shift=true and creating a setuid root executable. This is possible because the shift property is not restricted unless restricted.devices.disk.paths is set. Details The following patch shows the offending code with a possible fix: PoC Created https://github.com/canonical/lxd/issues/12606 to improve the documentation as per https://github.com/canonical/lxd/security/advisories/GHSA-x9qq-236j-gj97#advisory-comment-91918

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from ghsa record GHSA-x9qq-236j-gj97

Agent brief

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

# Patch Next advisory brief: GHSA-x9qq-236j-gj97

Advisory: Canonical LXD documentation improvement to make clear restricted.devices.disk=allow without restricted.devices.disk.paths also allows shift=true
IDs: GHSA-x9qq-236j-gj97
Record: https://patchnext.com/advisories/ghsa-x9qq-236j-gj97 (revision 1, source checked 26 Oct 2026, 15:09 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Unrated
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/canonical/lxd 5.20.0, 0.0.0-20240118092008-ce1bd0dd37bb. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/canonical/lxd: affected >= 5.19.0, <= 5.19.0; >= 0.0.0-20230920084527-cbe39c5d3f14, < 0.0.0-20240118092008-ce1bd0dd37bb; fixed in 5.20.0, 0.0.0-20240118092008-ce1bd0dd37bb

## Suggested inspection (read-only)
- Go github.com/canonical/lxd: 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/canonical/lxd.
- 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-x9qq-236j-gj97 (GitHub-reviewed advisory GHSA-x9qq-236j-gj97 lists affected ranges: Go github.com/canonical/lxd >=5.19.0 =0.0.0-20230920084527-cbe39c5d3f14 <0.0.0-20240118092008-ce1bd0dd37bb)

Commands are suggestions: review each one before running it.

Loading voting…