net/ionic: avoid OOB TX partner lookup for hwstamp RXQ (CVE-2026-80779) | HOL Guard CVE

Unknown severity · Source severity not reportedCVE-2026-80779

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

Answer in brief

CVE-2026-80779 records a Unknown severity vulnerability in net/ionic: avoid OOB TX partner lookup for hwstamp RXQ. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Sep 4, 2026Updated Sep 4, 2026Source checked Sep 4, 2026First seen by HOL Sep 4, 2026Material review Sep 4, 2026

Upstream Advisory

Key facts

Risk: Unknown severitySource severity not reported
Exploitation: Not marked as known exploited
Affected software: 2 mapped packages or products
Fix availability: Available

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
Linux/Linuxgeneric	>=8eeed8373e1cca836799bf8e4a05cffa8e444908 <881a805a8029ba48c0ce81c6674910f8d83f7afb \|\| >=8eeed8373e1cca836799bf8e4a05cffa8e444908 <39fc615e355b65b8d43be30da57aa95ae6eaf688 \|\| >=8eeed8373e1cca836799bf8e4a05cffa8e444908 <f3868046e8e2e761d4d943a232bd109ff22a7d5b \|\| >=8eeed8373e1cca836799bf8e4a05cffa8e444908 <ea081b4435515ac7177eb598a3c0678d1b9e7911 \|\| >=8eeed8373e1cca836799bf8e4a05cffa8e444908 <d92255b405fb6f5acca408239ccd742e0a42c9cb	881a805a8029ba48c0ce81c6674910f8d83f7afb, 39fc615e355b65b8d43be30da57aa95ae6eaf688, f3868046e8e2e761d4d943a232bd109ff22a7d5b, ea081b4435515ac7177eb598a3c0678d1b9e7911, d92255b405fb6f5acca408239ccd742e0a42c9cb
Linux/Linuxgeneric	6.9	Not reported

Recommended response

Check inventory. Check lockfiles and deployed manifests for Linux/Linux, Linux/Linux.
Review the reported fix. Update Linux/Linux to 881a805a8029ba48c0ce81c6674910f8d83f7afb if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Sep 4, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Sep 4, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Sep 4, 2026

Sources and claim methodology

Upstream source 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.

Quoted source text, attributed separately from HOL analysis.