CVE-2026-93061: gpu: host1x: Avoid stack over-read in debug output helpers
In the Linux kernel, the following vulnerability has been resolved:
gpu: host1x: Avoid stack over-read in debug output helpers
host1xdebugoutput() and host1xdebugcont() 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 host1xdebug 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.
Affected Software
Event History
Frequently Asked Questions
Which interfaces are affected by this issue?
Only the host1x debugfs files are affected. The printk debug sink ignores the byte count and is not affected by this behavior.
What condition is required to trigger the over-read?
A call to host1x_debug_output() or host1x_debug_cont() must produce formatted output longer than 256 bytes. The oversized length returned by vsnprintf() could then be used to emit bytes beyond the output buffer.
How likely is this to occur in practice?
The available information states that this is very unlikely to occur in practice.
What change resolves the issue?
The fix replaces vsnprintf() with vscnprintf() in the affected debug output helpers, so the emitted length reflects the bytes actually written to the buffer.