Linux vulnerability

In the Linux kernel, the following vulnerability has been resolved: net: mana: validate rx_req_idx to prevent out-of-bounds array access In mana_hwc_rx_event_handler(), rx_req_idx is derived from sge->address in DMA-coherent memory. In Confidential VMs (SEV-SNP/TDX), this memory is shared unencrypted and HW can modify WQE contents at any time. No bounds check exists on rx_req_idx, which can lead to an out-of-bounds access into reqs[]. Add bounds check on rx_req_idx in mana_hwc_rx_event_handler() before using it to index the reqs[] array.

Published 19 Jul 2026Updated 13 Oct 20267 sources
CVSS 9.3

What happened

In the Linux kernel, the following vulnerability has been resolved: net: mana: validate rx_req_idx to prevent out-of-bounds array access In mana_hwc_rx_event_handler(), rx_req_idx is derived from sge->address in DMA-coherent memory. In Confidential VMs (SEV-SNP/TDX), this memory is shared unencrypted and HW can modify WQE contents at any time. No bounds check exists on rx_req_idx, which can lead to an out-of-bounds access into reqs[]. Add bounds check on rx_req_idx in mana_hwc_rx_event_handler() before using it to index the reqs[] array.

Affected versions

Linux: ca9c54d2d6a5ab2430c4eda364c77125d62e5e0f through before 5ddc715324badd7f2641bc177db1d027b402adae (git); ca9c54d2d6a5ab2430c4eda364c77125d62e5e0f through before ff1d5af207bcea857d45fe81505f1bc4b29eaef0 (git); ca9c54d2d6a5ab2430c4eda364c77125d62e5e0f through before 01f7f893d5e1baae995beeb86cd0f3e6bb2a3b01 (git); ca9c54d2d6a5ab2430c4eda364c77125d62e5e0f through before 763a372d344fb12fae566d36ddb46e92454ad58c (git); ca9c54d2d6a5ab2430c4eda364c77125d62e5e0f through before fa627a5eaa83fc0261f44ef3769693b886ca6e27 (git); ca9c54d2d6a5ab2430c4eda364c77125d62e5e0f through before 355e9f2b2a7887ca38100127989af3e422ba71d0 (git); ca9c54d2d6a5ab2430c4eda364c77125d62e5e0f through before b809d0409991b75a6cff846a5ac27c3062953f84 (git); 5.13 Fixed: See vendor advisory.

Why it matters

Review the vendor advisory and exposure of the affected product to determine operational impact.

Detection & mitigation

  • Apply vendor-provided updates or mitigations.
  • Review affected product exposure and access logs.

Public PoC references

No public PoC reference has passed the current publication threshold.