CVE-2026-93061: Linux kernel · gpu: host1x: Avoid stack over-read in debug output helpers
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in ebab3a25a0403bcbc0c40ef77d69d23270e45547 : update Linux kernel when convenient.
Data as of 26 Oct 2026, 12:55 UTC
Rated by Threat Radar · CVSS not yet scored by NVD
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 11% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in ebab3a25a0403bcbc0c40ef77d69d23270e45547, d7a560dc912756fd8b39b28b10818d931e863d2d, bc17ac285fb708f22a8fa2c0ed32eceb1d37e6d6 +5
Exploitation evidence
Disclosed: evidence found.
CVE published 17 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
Description
In the Linux kernel, the following vulnerability has been resolved: gpu: host1x: Avoid stack over-read in debug output helpers host1x_debug_output() and host1x_debug_cont() used vsnprintf(), which returns the length the formatted string would have reached with an unbounded buffer. That return value was passed straight to o->fn as the number of bytes to emit. This could cause a read past end of the output buffer if a call to host1x_debug_* produced a string longer than 256 bytes. This only affected the debugfs files as the printk debug sink ignores the number of bytes. In practice, this is very unlikely to occur. Fix by switching to vscnprintf(), which returns the number of bytes actually written.
References
- git.kernel.org/stable/c/d7a560dc912756fd8b39b28b10818d931e863d2d (opens in a new tab)
- git.kernel.org/stable/c/41517c46002afd717f0f2d0975c740dd610f87fe (opens in a new tab)
- git.kernel.org/stable/c/ebab3a25a0403bcbc0c40ef77d69d23270e45547 (opens in a new tab)
- git.kernel.org/stable/c/4f9f0afdbdf513a49065207ff6b7e1d15051175a (opens in a new tab)
- git.kernel.org/stable/c/819dd96a6571f2b12496b080e5187ba3fa897232 (opens in a new tab)
- git.kernel.org/stable/c/9ad7a6ccc7b839247663d57d3dbb4481dec492de (opens in a new tab)
- git.kernel.org/stable/c/b00290d1dc23a5ef9a0d3103aad1fe2274e86569 (opens in a new tab)
- git.kernel.org/stable/c/bc17ac285fb708f22a8fa2c0ed32eceb1d37e6d6 (opens in a new tab)