Linux Kernel up to 6.19.3 tpm get_burstcount memory leak

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
5.4$0-$5k0.00

Summaryinfo

A vulnerability was found in Linux Kernel up to 6.19.3. It has been classified as critical. The affected element is the function get_burstcount of the component tpm. Performing a manipulation results in an unknown weakness. This vulnerability was named CVE-2026-45941. There is no available exploit. Upgrading the affected component is recommended.

Detailsinfo

A vulnerability classified as critical has been found in Linux Kernel up to 6.19.3. This affects the function get_burstcount of the component tpm. CWE is classifying the issue as CWE-401. The product does not sufficiently track and release allocated memory after it has been used, which slowly consumes remaining memory. The impact remains unknown. The summary by CVE is:

In the Linux kernel, the following vulnerability has been resolved: tpm: tpm_i2c_infineon: Fix locality leak on get_burstcount() failure get_burstcount() can return -EBUSY on timeout. When this happens, the function returns directly without releasing the locality that was acquired at the beginning of tpm_tis_i2c_send(). Use goto out_err to ensure proper cleanup when get_burstcount() fails.

The advisory is shared at git.kernel.org. This vulnerability is uniquely identified as CVE-2026-45941 since 05/13/2026. The exploitability is told to be easy. Technical details are known, but no exploit is available.

Upgrading to version 5.10.252, 5.15.202, 6.1.165, 6.6.128, 6.12.75, 6.18.14 or 6.19.4 eliminates this vulnerability. Applying the patch 8f124c5582d443ac9fb690db26d08cab5d6ba76e/c24c9c4cab11858f22f309521ba7ea5b1e7385f2/1bb8f8826d0748b4b92a98fb6b6dfe52081739f5/948966e546f29af04391d98b8e378e4a7670c1c1/a61b8412e3eb8b71646dba867e8252d8560a1a27/1a22048c1117cdfac185ba450aba67ed6b65dc87/2f7a665e1323359d99c74301d1e180f5e2c40181/bbd6e97c836cbeb9606d7b7e5dcf8a1d89525713 is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 5.5
VulDB Meta Temp Score: 5.4

VulDB Base Score: 5.5
VulDB Temp Score: 5.3
VulDB Vector: 🔒
VulDB Reliability: 🔍

NVD Base Score: 5.5
NVD Vector: 🔒

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: Memory leak
CWE: CWE-401 / CWE-404
CAPEC: 🔒
ATT&CK: 🔒

Physical: Partially
Local: Yes
Remote: Partially

Availability: 🔒
Status: Not defined

EPSS Score: 🔒
EPSS Percentile: 🔒

Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔒

Upgrade: Kernel 5.10.252/5.15.202/6.1.165/6.6.128/6.12.75/6.18.14/6.19.4
Patch: 8f124c5582d443ac9fb690db26d08cab5d6ba76e/c24c9c4cab11858f22f309521ba7ea5b1e7385f2/1bb8f8826d0748b4b92a98fb6b6dfe52081739f5/948966e546f29af04391d98b8e378e4a7670c1c1/a61b8412e3eb8b71646dba867e8252d8560a1a27/1a22048c1117cdfac185ba450aba67ed6b65dc87/2f7a665e1323359d99c74301d1e180f5e2c40181/bbd6e97c836cbeb9606d7b7e5dcf8a1d89525713

Timelineinfo

05/13/2026 CVE reserved
05/27/2026 +14 days Advisory disclosed
05/27/2026 +0 days VulDB entry created
06/25/2026 +28 days VulDB entry last update

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2026-45941 (🔒)
GCVE (CVE): GCVE-0-2026-45941
GCVE (VulDB): GCVE-100-366273

Entryinfo

Created: 05/27/2026 17:25
Updated: 06/25/2026 01:15
Changes: 05/27/2026 17:25 (58), 06/25/2026 01:15 (12)
Complete: 🔍
Cache ID: 216::103

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

Want to know what is going to be exploited?

We predict KEV entries!