GPU VulnDB

Database/NVIDIA / GPU stack

Linux drm/amdgpu: BAR0 fallback read path narrowed to SR-IOV VFs only

UnscoredCVE-2026-98165NVIDIA / GPU stackcurated

Impact

The BAR0 fallback read path exists as a workaround for SR-IOV virtual functions, where the VRAM aperture is not available during early initialization. Upstream restricted it so it is only taken on SR-IOV VFs, where it is actually needed, instead of on bare-metal devices too. The record gives no attacker, no crash signature and no CVSS; what it changes is which register-access path amdgpu takes while bringing up a device, which matters most on hosts that pass AMD GPUs to guests via SR-IOV. Treat it as a correctness fix in the GPU init path, not as an exploitable flaw - the record does not support a stronger claim.

Who can reach it

Not established by the record. The affected code runs during driver initialization, before any tenant workload exists; no remote or local attacker path is described.

What to do

Fixed in stable; take the kernel carrying commit 5612934c255a / bd1f08246b8a (cherry-picked from d8a0affd207c). Kernel update plus a node reboot; nothing urgent here, roll it with your normal kernel currency cycle.

References

Related entries

All NVIDIA / GPU stack 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.