/sys/devices/virtual/powercap accessible by default to containers

Exploitation

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

CVSS

not scored

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

Intel's RAPL (Running Average Power Limit) feature, introduced by the Sandy Bridge microarchitecture, provides software insights into hardware energy consumption. To facilitate this, Intel introduced the powercap framework in Linux kernel 3.13, which reads values via relevant MSRs (model specific registers) and provides unprivileged userspace access via sysfs. As RAPL is an interface to access a hardware feature, it is only available when running on bare metal with the module compiled into the kernel. By 2019, it was realized that in some cases unprivileged access to RAPL readings could be exploited as a power-based side-channel against security features including AES-NI (potentially inside a SGX enclave) and KASLR (kernel address space layout randomization). Also known as the PLATYPUS attack, Intel assigned CVE-2020-8694 and CVE-2020-8695, and AMD assigned CVE-2020-12912. Several mitigations were applied; Intel reduced the sampling resolution via a microcode update, and the Linux…

Published by the source

30 Oct 2023, 15:25 UTC

Last modified by the source

27 Dec 2023, 16:08 UTC

Source last checked

26 Oct 2026, 15:03 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-jq35-85cj-fj4p

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

# Patch Next advisory brief: GHSA-jq35-85cj-fj4p

Advisory: /sys/devices/virtual/powercap accessible by default to containers
IDs: GHSA-jq35-85cj-fj4p
Record: https://patchnext.com/advisories/ghsa-jq35-85cj-fj4p (revision 1, source checked 26 Oct 2026, 15:03 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/docker/docker 24.0.7, 23.0.8, 20.10.27. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/docker/docker: affected >= 24.0.0, < 24.0.7; >= 21.0.0, < 23.0.8; < 20.10.27; fixed in 24.0.7, 20.10.27, 23.0.8

## Suggested inspection (read-only)
- Go github.com/docker/docker: 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/docker/docker.
- 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-jq35-85cj-fj4p (GitHub-reviewed advisory GHSA-jq35-85cj-fj4p lists affected ranges: Go github.com/docker/docker >=24.0.0 =21.0.0 =0 <20.10.27)

Commands are suggestions: review each one before running it.