Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2026-80990: net: thunderbolt: Release the Rx HopID that was handed out on mismatch

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.21% (FIRST EPSS).
  • Fixed version: Linux Linux 1c361f6cf39be7cc0ce37c0b67bd1cdf74b0a0c1, 2f1463554d0561a2fead81e3888604e5c1125e29, 47981eb66461ba4e74bbaea0f139adaaeb3991e9.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 1c361f6cf39be7cc0ce37c0b67bd1cdf74b0a0c1, 2f1463554d0561a2fead81e3888604e5c1125e29, 47981eb66461ba4e74bbaea0f139adaaeb3991e9 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: thunderbolt: Release the Rx HopID that was handed out on mismatch tb_xdomain_alloc_in_hopid() passes the wanted HopID to ida_alloc_range() as the lower bound, so a taken id is not an error there: the allocator returns the next free one above it. tbnet_connected_work() asks for the peer's transmit path, treats any other id as a failure and returns without releasing what it got, so that allocation stays live for the rest of the XDomain connection with nothing left holding a reference to it. Release the id when it is not the one we asked for, the same way the error unwind at the end of the function releases the expected one.

—No exploit Fix available
Published
Sep 11, 2026
Updated
Oct 30, 2026
EPSS
0.2% · 11th 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.2%

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-80990

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

  • 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.

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

    • 5.13affected
    • 180b0689425c6fb2b35e69a3316ee38371a782df and later · before b098f01638a142afbb1e00b323e2fc40f237907aaffected · git
    • 180b0689425c6fb2b35e69a3316ee38371a782df and later · before 47981eb66461ba4e74bbaea0f139adaaeb3991e9affected · git
    • 180b0689425c6fb2b35e69a3316ee38371a782df and later · before 9eac1817bfc5fa76e3a2d1b8fd824cc6ef5a9ab0affected · git
    • 180b0689425c6fb2b35e69a3316ee38371a782df and later · before 61ff3c353e5d2ff4eb9d0b6d8d9e47805b136eeaaffected · git
    • 180b0689425c6fb2b35e69a3316ee38371a782df and later · before 1c361f6cf39be7cc0ce37c0b67bd1cdf74b0a0c1affected · git
    • 180b0689425c6fb2b35e69a3316ee38371a782df and later · before 2f1463554d0561a2fead81e3888604e5c1125e29affected · git
    • before 5.13not affected · semver
    • 6.1.191 and later · up to and including 6.1.*not affected · semver
    • 6.6.157 and later · up to and including 6.6.*not affected · semver

Package-level exposure

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

EcosystemPackageAffected rangeFix
Debian:12linuxfrom 0—
Debian:12linux-6.12before 6.12.111-1~deb12u16.12.111-1~deb12u1
Debian:13linuxbefore 6.12.111-16.12.111-1
Debian:14linuxbefore 7.2.6-17.2.6-1

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-80988Sep 11, 2026 · NTB: ntb_transport: Fail TX enqueue when the QP link is down
    0Monitor
  • ← EarlierCVE-2026-80989Sep 11, 2026 · net: thunderbolt: Mark the connection down when bringing it up fails
    35Monitor
  • Later →CVE-2026-80991Sep 11, 2026 · net: ravb: serialize PTP clock teardown
    31Monitor

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 Linux1c361f6cf39be7cc0ce37c0b67bd1cdf74b0a0c1Vendor (CNA)
Linux Linux2f1463554d0561a2fead81e3888604e5c1125e29Vendor (CNA)
Linux Linux47981eb66461ba4e74bbaea0f139adaaeb3991e9Vendor (CNA)
Linux Linux61ff3c353e5d2ff4eb9d0b6d8d9e47805b136eeaVendor (CNA)
Linux Linux9eac1817bfc5fa76e3a2d1b8fd824cc6ef5a9ab0Vendor (CNA)
Linux Linuxb098f01638a142afbb1e00b323e2fc40f237907aVendor (CNA)
debian:linux6.12.111-1 · Debian:13Package registry (OSV)
debian:linux-6.126.12.111-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.

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).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

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

All records