Menu

Star on GitHub · 3.5k

CVE-2026-80779

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 equ…

Published Sep 4, 2026EPSS 0.17%

Overview

CVE-2026-80779 is a known-severity vulnerability. It was published on September 4, 2026.

Technical description

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.

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2026-80779?

CVE-2026-80779 is a known-severity vulnerability. It was published on September 4, 2026.

How severe is CVE-2026-80779?

CVSS score information is not yet available for this vulnerability. Check back as the CVE record is updated by NVD analysts.

How do I fix or remediate CVE-2026-80779?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2026-80779?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2026-80779 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

CyberStrike v2 is here — more intelligence, greater reach