In the Linux kernel, the following vulnerability has been resolved:

net/ionic: avoid OOB TX partner lookup for hwstamp RXQ

The dedicated hardware timestamp RX queue is allocated with q->index
equal to lif->ionic->nrxqs_per_lif. The normal txqcqs array only
contains the regular queue pairs, so using that index to set rxq->partner
can read one entry past txqcqs[] and then write through the derived
pointer.
Only link RX/TX partners for normal queue-pair indexes. Leave the hwstamp
RX queue unpaired, and make the XDP_TX path abort cleanly if an RX queue
has no TX partner.

References

• https://nvd.nist.gov/vuln/detail/CVE-2026-80779
• https://git.kernel.org/stable/c/39fc615e355b65b8d43be30da57aa95ae6eaf688
• https://git.kernel.org/stable/c/881a805a8029ba48c0ce81c6674910f8d83f7afb
• https://git.kernel.org/stable/c/d92255b405fb6f5acca408239ccd742e0a42c9cb
• https://git.kernel.org/stable/c/ea081b4435515ac7177eb598a3c0678d1b9e7911
• https://git.kernel.org/stable/c/f3868046e8e2e761d4d943a232bd109ff22a7d5b