CVE-2026-72135tpm: Make the TPM character devices non-seekable
- 7.8HighCVSS base score
- 0.17%Exploitation in 30 daysEPSS · top 94% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
In the Linux kernel, the following vulnerability has been resolved: tpm: Make the TPM character devices non-seekable The TPM character devices expose a sequential command/response interface, but their open handlers leave FMODE_PREAD and FMODE_PWRITE enabled. After a command leaves a response pending, pread(fd, buf, 16, 0x1400) passes 0x1400 as *off to tpm_common_read(). The transfer length is bounded by response_length, but the offset is used unchecked when forming data_buffer + *off. A sufficiently large offset therefore causes an out-of-bounds heap read through copy_to_user() and, if the copy succeeds, an out-of-bounds zero-write through the following memset(). Positional I/O does not provide coherent semantics for this interface. An arbitrary pread offset cannot represent how much of a response has been consumed sequentially. The write callback always stores a command at the start of data_buffer, while pwrite() does not update file->f_pos and can leave the sequential read cursor stale. Call nonseekable_open() from both open handlers. This removes FMODE_PREAD and FMODE_PWRITE, causing positional reads and writes to fail with -ESPIPE before reaching the TPM callbacks, and explicitly marks the files non-seekable. Normal read() and write() continue to use the existing sequential f_pos cursor, leaving the response state machine unchanged. Tested on Linux 6.12 with KASAN and a swtpm TPM2 device: - sequential partial reads returned the complete response - pread() and preadv() with offset 0x1400 returned -ESPIPE - pwrite() and pwritev() with offset zero returned -ESPIPE - the pending response remained intact after the rejected operations - a subsequent normal command/response cycle completed normally - no KASAN report was produced.
Timeline
ID reserved
By Linux
- 6 days later
· 6 days later
Published
- 2 months later
· 2 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| LinuxCNA (assigner) | 3.1 | High7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVDNVD · Received | 3.1 | High7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
- EPSS (exploitation in 30 days)
- 0.17% · top 94% of all CVEs (16 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: total
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.
Affected products
- affected 9488585b21bef0df1217e510c7134905d1d376a7 – < ed0ffc2c016629e40ba041ed0424a772d8b02e2c
- affected 9488585b21bef0df1217e510c7134905d1d376a7 – < 232dcf908eb7eb9d8046a9597975caf44270966e
- affected 9488585b21bef0df1217e510c7134905d1d376a7 – < dda695fab5e21f923d29e8cb01df256468ddfbd1
- affected 9488585b21bef0df1217e510c7134905d1d376a7 – < 9c513dabd4540f811585a2087f23069767a284da
- affected 9488585b21bef0df1217e510c7134905d1d376a7 – < 21a13f932972bc9836f58c44fcd47c62abdecd95
- affected 9488585b21bef0df1217e510c7134905d1d376a7 – < ada4b9a5087ea7f30dd8e4c6411a4fb6547eb1ed
- affected 9488585b21bef0df1217e510c7134905d1d376a7 – < 947b773caaa548672184df025271b29bdc80b0f1
- affected 9488585b21bef0df1217e510c7134905d1d376a7 – < f20d61c22bcaf172d6790b6500e3838e532e71c8
- affected 5.0
- unaffected < 5.0
- unaffected 5.10.261 – ≤ 5.10.*
- unaffected 5.15.212 – ≤ 5.15.*
- unaffected 6.1.178 – ≤ 6.1.*
- unaffected 6.6.145 – ≤ 6.6.*
- unaffected 6.12.97 – ≤ 6.12.*
- unaffected 6.18.40 – ≤ 6.18.*
- unaffected 7.1.5 – ≤ 7.1.*
- unaffected 7.2 – ≤ *
References
References8
- https://git.kernel.org/stable/c/ed0ffc2c016629e40ba041ed0424a772d8b02e2c (opens in a new tab)
- https://git.kernel.org/stable/c/232dcf908eb7eb9d8046a9597975caf44270966e (opens in a new tab)
- https://git.kernel.org/stable/c/dda695fab5e21f923d29e8cb01df256468ddfbd1 (opens in a new tab)
- https://git.kernel.org/stable/c/9c513dabd4540f811585a2087f23069767a284da (opens in a new tab)
- https://git.kernel.org/stable/c/21a13f932972bc9836f58c44fcd47c62abdecd95 (opens in a new tab)
- https://git.kernel.org/stable/c/ada4b9a5087ea7f30dd8e4c6411a4fb6547eb1ed (opens in a new tab)
- https://git.kernel.org/stable/c/947b773caaa548672184df025271b29bdc80b0f1 (opens in a new tab)
- https://git.kernel.org/stable/c/f20d61c22bcaf172d6790b6500e3838e532e71c8 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-58893 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-72135)Record last updated .