nitro-tpm-pcr-compute may allow kernel command line modification by an account operator

Exploitation

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

CVSS

6.0 · CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:N

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

Summary Adding default PCR12 validation to ensure that account operators can not modify kernel command line parameters, potentially bypassing root filesystem integrity validation. Attestable AMIs are based on the systemd Unified Kernel Image (UKI) concept which uses systemd-boot to create a single measured UEFI binary from a Linux kernel, its initramfs, and kernel command line. The embedded kernel command line contains a dm-verity hash value that establishes trust in the root file system. When UEFI Secure Boot is disabled, systemd-boot appends any command line it receives to the kernel command line. Account operators with the ability to modify UefiData can install a boot variable with a command line that deactivates root file system integrity validation, while preserving the original PCR4 value. Systemd-boot provides separate measurement of command line modifications in PCR12. Impact In line with the TPM 2.0 specification and systemd-stub logic, KMS policies that do not include…

Published by the source

5 Dec 2025, 18:57 UTC

Last modified by the source

5 Dec 2025, 18:57 UTC

Source last checked

26 Oct 2026, 15:39 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-xrv8-2pf5-f3q7

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

# Patch Next advisory brief: GHSA-xrv8-2pf5-f3q7

Advisory: nitro-tpm-pcr-compute may allow kernel command line modification by an account operator
IDs: GHSA-xrv8-2pf5-f3q7
Record: https://patchnext.com/advisories/ghsa-xrv8-2pf5-f3q7 (revision 1, source checked 26 Oct 2026, 15:39 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.0)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: nitro-tpm-pcr-compute 1.1.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- crates.io nitro-tpm-pcr-compute: affected < 1.1.0; fixed in 1.1.0

## Suggested inspection (read-only)
- crates.io nitro-tpm-pcr-compute: 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 nitro-tpm-pcr-compute.
- 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-xrv8-2pf5-f3q7 (GitHub-reviewed advisory GHSA-xrv8-2pf5-f3q7 lists affected ranges: crates.io nitro-tpm-pcr-compute >=0 <1.1.0)

Commands are suggestions: review each one before running it.