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
- NVIDIA Megatron-LM: unsafe deserialization of untrusted data allows code executionCVE-2026-100967 · NVIDIA Megatron-LMHigh
- NVIDIA Megatron-LM: unsafe deserialization in dataset loading allows code executionCVE-2026-100968 · NVIDIA Megatron-LM (dataset loading)High
- MLflow: pickle evaluation artifact deserialization runs arbitrary code when a model is loadedCVE-2026-118623 · MLflow model artifact loading (PickleEvaluationArtifact)High
- MLflow: loading a SHAP explainer model deserializes untrusted data and runs arbitrary codeCVE-2026-118627 · MLflow SHAP explainer loading (load_explainer)High
- TorchServe: predictable /tmp extraction path lets a local user swap a model handler and run code as the service accountCVE-2026-123974 · PyTorch TorchServe (model archive extraction directory in /tmp)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.