SUNRPC: svcauth_gss: avoid NULL deref on zero length gss_token in gss_read_proxy_verf
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 5866efa8cbfbadf3905072798e96652faf02dbe8 · < 1c8bb965e9b0559ff0f5690615a527c30f651dd8| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
SUNRPC: svcauth_gss: avoid NULL deref on zero length gss_token in gss_read_proxy_verf
A zero length gss_token results in pages == 0 and in_token->pages[0] is NULL. The code unconditionally evaluates page_address(in_token->pages[0]) for the initial memcpy, which can dereference NULL even when the copy length is 0. Guard the first memcpy so it only runs when length > 0.
From the CVE record · Linux
The Linux kernel’s SUNRPC svcauth_gss code can dereference a NULL pointer when gss_read_proxy_verf processes a zero-length gss_token. The input does not specify whether an attacker can trigger this over a network or locally, or whether authentication or user interaction is required.
Engineers running the Linux kernel should check their version; affected versions are not specified in the input.