Skip to content
Noroxi
CVE-2026-80779· NVD / CVE Program· CNA Linux

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

Noroxi assessment

Priority: Monitor (action score 0/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.16% (FIRST EPSS).
  • Fixed version: Linux Linux 39fc615e355b65b8d43be30da57aa95ae6eaf688, 881a805a8029ba48c0ce81c6674910f8d83f7afb, d92255b405fb6f5acca408239ccd742e0a42c9cb.

Low priority for now. Upgrade to Linux Linux 39fc615e355b65b8d43be30da57aa95ae6eaf688, 881a805a8029ba48c0ce81c6674910f8d83f7afb, d92255b405fb6f5acca408239ccd742e0a42c9cb or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

—No exploit Fix available
Published
Sep 4, 2026
Updated
Oct 19, 2026
EPSS
0.1% · 5th percentile
CWE
—

Report tools

JSON

Action score

0

Monitor

Low priority for now.

CVSS
0 / 40 · —
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-80779

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 6.9affected
    • 8eeed8373e1cca836799bf8e4a05cffa8e444908 and later · before 881a805a8029ba48c0ce81c6674910f8d83f7afbaffected · git
    • 8eeed8373e1cca836799bf8e4a05cffa8e444908 and later · before 39fc615e355b65b8d43be30da57aa95ae6eaf688affected · git
    • 8eeed8373e1cca836799bf8e4a05cffa8e444908 and later · before f3868046e8e2e761d4d943a232bd109ff22a7d5baffected · git
    • 8eeed8373e1cca836799bf8e4a05cffa8e444908 and later · before ea081b4435515ac7177eb598a3c0678d1b9e7911affected · git
    • 8eeed8373e1cca836799bf8e4a05cffa8e444908 and later · before d92255b405fb6f5acca408239ccd742e0a42c9cbaffected · git
    • before 6.9not affected · semver
    • 6.12.106 and later · up to and including 6.12.*not affected · semver
    • 6.18.47 and later · up to and including 6.18.*not affected · semver
    • 7.1.11 and later · up to and including 7.1.*not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linux-6.12before 6.12.107-1~deb12u16.12.107-1~deb12u1
Debian:13linuxbefore 6.12.107-16.12.107-1
Debian:14linuxbefore 7.1.12-17.1.12-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2026-80777Sep 4, 2026 · futex/pi: Plug private futex exec() race
    0Monitor
  • ← EarlierCVE-2026-80778Sep 4, 2026 · futex/pi: Reject cross-mm private futex owners
    0Monitor
  • Later →CVE-2026-80780Sep 4, 2026 · HID: pidff: fix OOB write when hid->inputs is empty
    0Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux39fc615e355b65b8d43be30da57aa95ae6eaf688Vendor (CNA)
Linux Linux881a805a8029ba48c0ce81c6674910f8d83f7afbVendor (CNA)
Linux Linuxd92255b405fb6f5acca408239ccd742e0a42c9cbVendor (CNA)
Linux Linuxea081b4435515ac7177eb598a3c0678d1b9e7911Vendor (CNA)
Linux Linuxf3868046e8e2e761d4d943a232bd109ff22a7d5bVendor (CNA)
debian:linux6.12.107-1 · Debian:13Package registry (OSV)
debian:linux-6.126.12.107-1~deb12u1 · Debian:12Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

No CVSS vector for this record, so attack conditions can't be derived.

Weakness class (CWE)

—

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (4 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records