Answer in brief
CVE-2026-98728 records a Unknown severity vulnerability in tpm: fix off-by-four bounds check in tpm2_get_random(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=1b6d7f9eb150305dcb0da4f7101a8d30dcdf0497 <be54101992c2c5218be0e0a87827ccc96e3089af || >=1b6d7f9eb150305dcb0da4f7101a8d30dcdf0497 <e30a2406408d2df6d9cd48c2e59e913cf266a05a || >=1b6d7f9eb150305dcb0da4f7101a8d30dcdf0497 <42bb6216b861e892512128219ff23010d656ba14 || >=1b6d7f9eb150305dcb0da4f7101a8d30dcdf0497 <9b522400bf5c082feb9a0037a053ea822a2c7e4d | be54101992c2c5218be0e0a87827ccc96e3089af, e30a2406408d2df6d9cd48c2e59e913cf266a05a, 42bb6216b861e892512128219ff23010d656ba14, 9b522400bf5c082feb9a0037a053ea822a2c7e4d |
| Linux/Linuxgeneric | 6.10 | Not reported |
Published upstream
Oct 18, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 19, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Oct 18, 2026
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.
Quoted source text, attributed separately from HOL analysis.