GPU VulnDB

Database/Kernel, userspace & hypervisor

Linux kernel ibmvfc: a malicious VIO server leaks kernel memory through an unclamped target count

CVSS 8.1CVE-2026-31464Kernel, userspace & hypervisorcurated

Impact

The ibmvfc driver trusted the num_written field in a discover-targets response from the VIO server and used it as the loop bound over a buffer sized for max_targets entries. A compromised or hostile VIOS returns a larger count, the driver indexes past the DMA-coherent allocation, and the out-of-bounds kernel memory is then packed into Implicit Logout and PLOGI messages sent back to the VIO server - a direct kernel memory disclosure channel, plus the usual crash risk from reading unmapped pages. This only matters to operators whose accelerator nodes are IBM Power LPARs with virtual Fibre Channel, so the blast radius in most GPU fleets is zero; where it applies, the storage path is shared across LPARs and the untrusted party is the virtualization layer the guest cannot audit.

Who can reach it

Adjacent - requires control of the VIO server that serves the LPAR's virtual Fibre Channel adapter. No authentication step beyond that position; an unprivileged user inside the LPAR cannot trigger it.

What to do

Apply the stable kernel update that clamps num_written to max_targets; fixes are in five stable branches. Rollout is a kernel install and an LPAR reboot, so drain the node first. No configuration-level mitigation exists short of not using virtual FC. Nodes on physical FC HBAs or on non-Power hardware are unaffected and need no maintenance window.

References

Related entries

All Kernel, userspace & hypervisor 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.