Database/AI/ML frameworks & serving
Linux i915 GPU kernel driver (execbuffer VMA array): The execbuffer VMA array was not zero-initialised, so
Impact
The execbuffer VMA array was not zero-initialised, so uninitialised kernel stack/heap contents could be acted on or leaked back through the GPU submission path. Info-leak-grade on its own, and useful as the KASLR-defeating first stage for one of the neighbouring i915 use-after-frees.
Who can reach it
Any local user or container with a DRM render node - i.e. any tenant that was scheduled a GPU. No privileged capability needed.
What to do
Fix ships in the Linux kernel. Update the kernel and reboot the node - in practice this is a drain plus reboot because the accelerator driver cannot be unloaded while jobs hold device file descriptors. No BIOS or firmware update needed.
References
Related entries
- Keras: Safe-mode bypass in Keras 3.0.0–3.10.0CVE-2025-8747 · KerasHigh
- Keras (`TorchModuleWrapper`): Unsafe deserialization of attacker-controlled PyTorch pickle inside a Keras modelCVE-2026-12484 · Keras (`TorchModuleWrapper`)High
- timm: untrusted checkpoint deserialization executes arbitrary code in the loading processCVE-2026-15679 · Hugging Face pytorch-image-models (timm) checkpoint loadingHigh
- HuggingFace transformers (`Trainer._load_rng_state`): Arbitrary code execution when a training run resumesCVE-2026-1839 · HuggingFace transformers (`Trainer._load_rng_state`)High
- NVIDIA NeMo Speech: malicious input data leads to remote code executionCVE-2026-24239 · NVIDIA NeMo SpeechHigh
- NVIDIA NeMo Speech: RCE and privilege escalation in the speech data explorerCVE-2026-24267 · NVIDIA NeMo Speech (speech data explorer)High
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.