Skip to main content
VulnerabilityPublished Updated

CVE-2025-71077: Linux kernel · tpm: Cap the number of PCR banks

Affects Linux kernelSource CVE Database V5

0

Not known to be exploited · fixed in faf07e611dfa464b201223a7253e9dc5ee0f3c9e : update Linux kernel when convenient.

Data as of 26 Oct 2026, 17:16 UTC

Severity
Unrated

Rated by Threat Radar · No CVSS score from NVD or the CNA

EPSS
0.1% chance of exploitation in 30 days – higher than 3% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CISA SSVC
Exploitation
No evidence of active exploitation and no public proof of concept
Automatable
Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact
Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-06-10.

Patch
Available – fixed in faf07e611dfa464b201223a7253e9dc5ee0f3c9e, d88481653d74d622d1d0d2c9bad845fc2cc6fd23, ceb70d31da5671d298bad94ae6c20e4bbb800f96 +4

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 13 Jan 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ bcfff8384f6c4e6627676ef07ccad9cfacd67849, < faf07e611dfa464b201223a7253e9dc5ee0f3c9e
Fixed in
  • faf07e611dfa464b201223a7253e9dc5ee0f3c9e
LinuxLinuxAffected
  • ≥ bcfff8384f6c4e6627676ef07ccad9cfacd67849, < d88481653d74d622d1d0d2c9bad845fc2cc6fd23
Fixed in
  • d88481653d74d622d1d0d2c9bad845fc2cc6fd23
LinuxLinuxAffected
  • ≥ bcfff8384f6c4e6627676ef07ccad9cfacd67849, < ceb70d31da5671d298bad94ae6c20e4bbb800f96
Fixed in
  • ceb70d31da5671d298bad94ae6c20e4bbb800f96
LinuxLinuxAffected
  • ≥ bcfff8384f6c4e6627676ef07ccad9cfacd67849, < b69492161c056d36789aee42a87a33c18c8ed5e1
Fixed in
  • b69492161c056d36789aee42a87a33c18c8ed5e1
LinuxLinuxAffected
  • ≥ bcfff8384f6c4e6627676ef07ccad9cfacd67849, < 858344bc9210bea9ab2bdc7e9e331ba84c164e50
Fixed in
  • 858344bc9210bea9ab2bdc7e9e331ba84c164e50
LinuxLinuxAffected
  • ≥ bcfff8384f6c4e6627676ef07ccad9cfacd67849, < 275c686f1e3cc056ec66c764489ec1fe1e51b950
Fixed in
  • 275c686f1e3cc056ec66c764489ec1fe1e51b950

Description

In the Linux kernel, the following vulnerability has been resolved: tpm: Cap the number of PCR banks tpm2_get_pcr_allocation() does not cap any upper limit for the number of banks. Cap the limit to eight banks so that out of bounds values coming from external I/O cause on only limited harm.

References

Community reviews

Loading reviews…