Database/Kernel, userspace & hypervisor
Linux i915 GPU kernel driver (active barrier tracking): Non-idle barriers were misused as fence trackers, corrupting
Impact
Non-idle barriers were misused as fence trackers, corrupting kernel lists when i915 perf is in use. Users hit this as an oops on list corruption - node down, jobs lost.
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
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.