Skip to content
Fencer Vulns
medium 6.1

CVE-2021-3623 json

A flaw was found in libtpms.

published 2022-03-02 4 y ago modified 2026-06-17 4 mo ago also EUVD-2021-26926

cvss
6.1
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.3%
EPSS 0.3% chance of exploitation in 30 days, percentile 25%
public exploits
0
none known

Summary

A flaw was found in libtpms. The flaw can be triggered by specially-crafted TPM 2 command packets containing illegal values and may lead to an out-of-bounds access when the volatile state of the TPM 2 is marshalled/written or unmarshalled/read. The highest threat from this vulnerability is to system availability.

Patch / fix

  • libtpms_project libtpms 0.6.5, 0.7.8, 0.8.4
  • libtpms Debian 14, Debian 13, Debian 12 0.9.1-1

debian advisories DEBIAN-CVE-2021-3623

  • libtpms SLE Module for Server Applications 15 SP4, SLE Module for Server Applications 15 SP3, SLE Micro 5.3 +6 more 0.8.2-150300.3.6.1

suse advisories SUSE-SU-2022:4457-1

  • libtpms Arch Linux 0.8.4-1

arch linux advisories AVG-2108

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2021-3623 updated cvss 6.1

libtpms: out-of-bounds access when trying to resume the state of the vTPM

  • Red Hat Enterprise Linux 8 Advanced Virtualization libtpms
    affected: workaround, no fix available, no fix planned “Will not fix”
  • Red Hat Enterprise Linux 9 libtpms
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

0.32% chance of exploitation in the next 30 days, higher than 25% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
NVD 3.1 6.1 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:H
NVD 2.0 3.6 AV:L/AC:L/Au:N/C:P/I:N/A:P

Affected products

  • n/a libtpms

Classification

Weakness

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.