Linux i915 GPU kernel driver (TLB invalidation): MULTI-TENANT ISOLATION: An incorrect TLB flush in i915 leaves the GPU

Impact

MULTI-TENANT ISOLATION: An incorrect TLB flush in i915 leaves the GPU able to reach memory it should no longer see, producing random memory corruption or leakage across contexts. Same family as the earlier GTT TLB bug and with the same consequence for a shared GPU node: one tenant's GPU reads or corrupts pages that now belong to someone else.

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

Kernel update and reboot. Drain the node first. No firmware or microcode component; the fix is entirely in the driver's invalidation logic.

References