https://db.gcve.eu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Mon, 02 Nov 2026 06:04:58 +0000 https://db.gcve.eu/vuln/certfr-2026-avi-1375 certfr-2026-avi-1375 https://db.gcve.eu/vuln/certfr-2026-avi-1375 https://db.gcve.eu/vuln/fkie_cve-2026-98728 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>tpm: fix off-by-four bounds check in tpm2_get_random()</p> <p>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&#39;s random bytes.</p> <p>Fix this by checking the response length against &#39;offset&#39;, which already includes the skipped parameter size field.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>tpm: fix off-by-four bounds check in tpm2_get_random()</p> <p>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&#39;s random bytes.</p> <p>Fix this by checking the response length against &#39;offset&#39;, which already includes the skipped parameter size field.</p> https://db.gcve.eu/vuln/fkie_cve-2026-98728 https://db.gcve.eu/vuln/ghsa-m4p2-cqr5-x7cx <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>tpm: fix off-by-four bounds check in tpm2_get_random()</p> <p>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&#39;s random bytes.</p> <p>Fix this by checking the response length against &#39;offset&#39;, which already includes the skipped parameter size field.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>tpm: fix off-by-four bounds check in tpm2_get_random()</p> <p>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&#39;s random bytes.</p> <p>Fix this by checking the response length against &#39;offset&#39;, which already includes the skipped parameter size field.</p> https://db.gcve.eu/vuln/ghsa-m4p2-cqr5-x7cx https://db.gcve.eu/vuln/msrc_cve-2026-98728 msrc_CVE-2026-98728 https://db.gcve.eu/vuln/msrc_cve-2026-98728 https://db.gcve.eu/vuln/ubuntu-cve-2026-98728 <p><strong>Affected:</strong> Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 120 more</p> <p>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&#39;s random bytes. Fix this by checking the response length against &#39;offset&#39;, which already includes the skipped parameter size field.</p> <p><strong>Affected:</strong> Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 120 more</p> <p>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&#39;s random bytes. Fix this by checking the response length against &#39;offset&#39;, which already includes the skipped parameter size field.</p> https://db.gcve.eu/vuln/ubuntu-cve-2026-98728