rxrpc: proc: size address buffers for %pISpc output
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 75b54cb57ca34cbe7a87c6ac757c55360a624590 · < db297c78ce537c9ac96f0eda9b25ad72c8caefa9| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
rxrpc: proc: size address buffers for %pISpc output
The AF_RXRPC procfs helpers format local and remote socket addresses into fixed 50-byte stack buffers with "%pISpc".
That is too small for the longest current-tree IPv6-with-port form the formatter can produce. In lib/vsprintf.c, the compressed IPv6 path uses a dotted-quad tail not only for v4mapped addresses, but also for ISATAP addresses via ipv6_addr_is_isatap().
As a result, a case such as
[ffff:ffff:ffff:ffff:0:5efe:255.255.255.255]:65535
is possible with the current formatter. That is 50 visible characters, so 51 bytes including the trailing NUL, which does not fit in the existing char[50] buffers used by net/rxrpc/proc.c.
Size the buffers from the formatter's maximum textual form and switch the call sites to scnprintf().
From the CVE record · Linux
Linux kernel rxrpc procfs helpers use 50-byte stack buffers for socket addresses that can require 51 bytes when formatted. A local user reading the affected procfs output could trigger a stack buffer overflow if an address reaches that maximum length; the input does not specify authentication requirements.
Engineers running Linux kernels with the affected rxrpc procfs helpers should check their kernel versions.