GPU VulnDB

Database/Kernel, userspace & hypervisor

Linux kernel: integer overflow in asymmetric_key_generate_id can overflow a key-id buffer

CVSS 7.8CVE-2025-68724Kernel, userspace & hypervisorcurated

Impact

asymmetric_key_generate_id adds caller-supplied blob lengths to the size of an asymmetric_key_id structure without overflow checking, so arbitrarily large X.509 fields - ASN.1 INTEGER serial numbers, issuer names - can wrap the computation and overflow the copy. This is reached wherever the kernel parses certificates into the keyring: module signature verification, IMA/EVM appraisal, kexec image signatures, and dm-verity key loading. On a GPU node that means the certificate-parsing path sitting under out-of-tree driver module loading, which is exactly the path that runs at boot and on every driver reinstall. The fix returns -EOVERFLOW instead; the record gives no evidence of remote reachability, and triggering it needs a local path that feeds an attacker-chosen certificate into the kernel.

Who can reach it

Local, authenticated: a user or process able to submit an attacker-crafted X.509 certificate to a kernel keyring or signature-verification path. Not reachable from the network in a default server configuration.

What to do

Take the stable kernel updates carrying the check_add_overflow() fix (five stable branches have backports). Kernel package upgrade means a node reboot: drain the GPU node, let running jobs finish or checkpoint, then reboot - the usual expensive part on a fleet where a node holds long training runs. No mitigation short of patching is described; the only reduction in exposure is limiting who can load certificates into kernel keyrings.

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.