GPU VulnDB

Database/Kernel, userspace & hypervisor

Linux kernel crypto/ecc: missing carry in 128-bit accumulation corrupts ECC arithmetic at a boundary

CVE-2026-64313Kernel, userspace & hypervisorcurated

Impact

The carry check in the kernel's ECC big-integer multiply only compares the high words and misses the case where they are equal and the low-word addition also carries, so results are wrong at a saturated-high-word boundary. crypto/ecc.c is the shared arithmetic behind the kernel's ECDH and ECDSA implementations, so this is a correctness defect in a primitive, not a memory-safety bug: the record shows no attacker-controlled memory corruption and no demonstrated exploit path. Practical exposure depends entirely on which consumer is compiled in and reachable on a headless server - the historical caller of this code is Bluetooth LE pairing, which datacenter hosts do not run, while the ECDSA side is used for signature verification. Treat this as a correctness fix to pick up on the normal cadence, not as a reason to open a window tonight.

Who can reach it

The kernel CNA scored it AV:A/PR:N, which points at an adjacent-network pairing path rather than anything a tenant can reach from a GPU pod. The record does not name a reachable path on a headless server, and states only that the carry condition is mishandled.

What to do

Pick up a stable kernel containing the five fix commits in the record at your next scheduled node reboot. No mitigation is needed or offered in the record, and no fixed release number is stated - map the commits through your distro's advisory. Nothing here justifies an out-of-band drain of GPU nodes.

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.