Vulnerability in Kernel package: tpm: efi: Use local variable for calculating final log size

Kernel Updated 02 Oct 2025

Summary

31/05/2021

Disclosed on

N/A

Severity

No i

Fix available

Unrated

Severity

Not published

CVSS Score

GSD-2021-1000174: tpm: efi: Use local variable for calculating final log size. Affects Kernel versions >= 166a2809d65b282272c474835ec22c882a39ca1b, < 2f12258b5224cfaa808c54fd29345f3c1cbfca76. No fix is published. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or Browse

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats

SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml

Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile

Javascript package-lock.json · yarn.lock · pnpm-lock.yaml

PHP composer.lock

Python poetry.lock · requirements.txt · Pipfile.lock

Go go.mod

Rust Cargo.lock

Ruby Gemfile.lock

Dart pubspec.lock

C/C++ conan.lock

Elixir mix.lock

Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Background

The Kernel package is a critical component of the Linux operating system, responsible for managing the system's core functionality. It provides essential services, such as process management, memory management, and device drivers. The tpm: efi module within the Kernel package is specifically related to the Trusted Platform Module (TPM) functionality and handles interactions with the TPM hardware. The TPM is a hardware-based security feature that provides cryptographic functions and secure storage for sensitive data. This vulnerability affects the tpm: efi module and can potentially impact the security and integrity of the system.

Vulnerability Detail

The vulnerability arises from a flaw in the calculation of the final log size within the tpm: efi module. By not using a local variable for this calculation, an attacker may be able to manipulate the log size, leading to potential memory corruption or buffer overflow issues. The exact impact and attack plausibility of this vulnerability have not been proven yet. However, if successfully exploited, an attacker could potentially gain unauthorized access to sensitive information or execute arbitrary code with elevated privileges. This vulnerability was introduced in version v5.3 of the Linux Kernel and has been fixed in version v5.4.118.

How To Fix

No fixed version is published for this vulnerability.

To fix this vulnerability, it is recommended to update the Linux Kernel package to version v5.4.118 or later. This update includes the necessary patch to address the flaw in the tpm: efi module. Users can obtain the updated Kernel package from the official Linux Kernel repository at https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/. Once the updated package is installed, the vulnerability should be mitigated.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Conclusion

In conclusion, the vulnerability in the tpm: efi module of the Kernel package poses a potential risk to the security and integrity of Linux systems. It is crucial to update the Linux Kernel package to version v5.4.118 or later to mitigate this vulnerability. For further support and assistance with vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for Kernel →

FAQ

What is the impact of this vulnerability?

If successfully exploited, this vulnerability could allow an attacker to gain unauthorized access to sensitive information or execute arbitrary code with elevated privileges.

How can I check if my system is affected by this vulnerability?

You can use the Vulert Playground at Vulert Scanner to check if your system is affected by this vulnerability. Simply upload your package-lock.json file, and Vulert will analyze it in real-time to identify any open-source vulnerabilities, including this one.

You can find more information about this vulnerability in the GSD-2021-1000174 entry of the GSD Database maintained by the Cloud Security Alliance. The entry can be accessed at https://github.com/cloudsecurityalliance/gsd-database/blob/main/2021/1000xxx/GSD-2021-1000174.json.