GPU VulnDB

Database/Kernel, userspace & hypervisor

Linux KEYS: miscalculated output buffer length overflows on keyctl asymmetric key operations

CVSS 7.8CVE-2026-63824Kernel, userspace & hypervisorcurated

Impact

The internal output buffer for keyctl public-key operations was sized from a bad calculation, so a caller that supplies a buffer smaller than the cryptographic primitive's output causes an overflow inside the kernel. The fix stops trusting the caller-supplied size and allocates for the maximum primitive length. This is reachable by any local user through the keyctl() asymmetric key interface, which nodes use for module signing keys, IMA and trusted-key workflows. No exploitation detail is in the record beyond the overflow itself. Separate flaw from the request_key_auth refcount bug published the same day - different code path, different fix.

Who can reach it

Local unprivileged user calling keyctl() public-key operations with an undersized output buffer. No GPU or device access needed; no remote path.

What to do

Update to a stable kernel carrying the corrected allocation in keyctl_pkey_params_get_2(). No published workaround; blocking keyctl() via seccomp is the only mitigation and breaks legitimate key users. Pick the fix up with the distro kernel and reboot each node.

References

Related entries

All Kernel, userspace & hypervisor entries

This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.