tpm: fix off-by-four bounds check in tpm2_get_random()
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 6.12.113, 6.18.56, 7.2.10
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 1b6d7f9eb150305dcb0da4f7101a8d30dcdf0497 · fixed in be54101992c2c5218be0e0a87827ccc96e3089af; From 1b6d7f9eb150305dcb0da4f7101a8d30dcdf0497 · fixed in e30a2406408d2df6d9cd48c2e59e913cf266a05a; From 1b6d7f9eb150305dcb0da4f7101a8d30dcdf0497 · fixed in 42bb6216b861e892512128219ff23010d656ba14; From 1b6d7f9eb150305dcb0da4f7101a8d30dcdf0497 · fixed in 9b522400bf5c082feb9a0037a053ea822a2c7e4d
- Linux Linux
6.10
- KernelLinux
From 6.10.0 · fixed in 6.12.113; From 6.13.0 · fixed in 6.18.56; From 6.19.0 · fixed in 7.2.10