CVE-2026-98728

Unknown

Last modified

CVE-2026-98728 is a vulnerability of currently unknown severity. In the Linux kernel, the following vulnerability has been resolved: tpm: fix off-by-four bounds check in tpm2_get_random() When the response carries the TPM2_ST_SESSIONS tag, tpm2_get_random() skips the 4-byte parameter size field before locating the random data, but the bounds check still validates the response length against TPM_HEADER_SIZE. A truncated response can pass the check and make memcpy() read up to 4 bytes past the response end, so stale buffer contents end up in the caller's random bytes. Fix this by checking the response length against 'offset', which already includes the skipped parameter size field..

Description

In the Linux kernel, the following vulnerability has been resolved: tpm: fix off-by-four bounds check in tpm2_get_random() When the response carries the TPM2_ST_SESSIONS tag, tpm2_get_random() skips the 4-byte parameter size field before locating the random data, but the bounds check still validates the response length against TPM_HEADER_SIZE. A truncated response can pass the check and make memcpy() read up to 4 bytes past the response end, so stale buffer contents end up in the caller's random bytes. Fix this by checking the response length against 'offset', which already includes the skipped parameter size field.

Affected Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= 1b6d7f9eb150305dcb0da4f7101a8d30dcdf0497, < be54101992c2c5218be0e0a87827ccc96e3089af; >= 1b6d7f9eb150305dcb0da4f7101a8d30dcdf0497, < e30a2406408d2df6d9cd48c2e59e913cf266a05a; >= 1b6d7f9eb150305dcb0da4f7101a8d30dcdf0497, < 42bb6216b861e892512128219ff23010d656ba14; >= 1b6d7f9eb150305dcb0da4f7101a8d30dcdf0497, < 9b522400bf5c082feb9a0037a053ea822a2c7e4d
LinuxLinux6.10

References

Timeline

Published
Last Modified
Status
Received

Frequently Asked Questions

What is CVE-2026-98728?
In the Linux kernel, the following vulnerability has been resolved: tpm: fix off-by-four bounds check in tpm2_get_random() When the response carries the TPM2_ST_SESSIONS tag, tpm2_get_random() skips the 4-byte parameter size field before locating the random data, but the bounds check still validates the response length against TPM_HEADER_SIZE. A truncated response can pass the check and make memcpy() read up to 4 bytes past the response end, so stale buffer contents end up in the caller's random bytes. Fix this by checking the response length against 'offset', which already includes the skipped parameter size field.
How severe is CVE-2026-98728?
Severity scoring for CVE-2026-98728 is pending analysis.
How do I fix CVE-2026-98728?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2026

Are you affected by CVE-2026-98728?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST