CVE-2026-90110

CRITICALPre-NVD 9.49.4—
EchelonGraph scoreHIGH confidence

Score 9.4 from GitHub Security Advisory (severity: CRITICAL) published 2026-09-17. A secondary CVSS source baseline 9.4; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
9.4EG
EchelonGraph verdictPlan mitigationSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.6%CVSS: 9.4Exploit: None knownExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

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

inetpeer: randomize RB-tree node comparison using SipHash

The inetpeer rate limiting system stores peer entries in a Red-Black tree keyed deterministically on the remote IP address. Because tree lookups walk the RB-tree using standard lexicographical comparisons (inetpeer_addr_cmp), an off-path adversary can predict the exact topology of the tree and the sequence of nodes traversed during lookups (the gc_stack candidate list).

By combining deterministic tree traversal with aggressive garbage collection (triggered when tree size exceeds inet_peer_threshold), an attacker can selectively force the eviction of targeted inet_peer nodes. When an evicted node is subsequently re-created upon receiving a new packet, its rate-limiting token bucket (rate_tokens, rate_last) is reset to full capacity. This creates a side-channel primitive allowing off-path attackers to bypass IP-keyed ICMP rate limits and infer open UDP ports (similar to SAD DNS style attacks).

Mitigate this by randomizing the RB-tree node comparison logic using SipHash with a secret key (inetpeer_hash_key) initialized via net_get_random_once(). Nodes are ordered in the tree by SipHash(addr, key) rather than raw IP addresses. Because the secret key is unknown to external entities, the tree layout and lookup traversal paths are unpredictable to off-path adversaries, breaking the deterministic eviction gadget.

Cache the computed 64-bit SipHash (hash) in struct inet_peer and compute the target hash (dhash) once at the beginning of inet_getpeer() to avoid recomputing SipHash at every step of the RB-tree walk.

CVSS v3
9.4
EG Score
9.4CRITICALhigh confidence
EG Risk
47
EG Risk 47/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity94% × 45%
Exploitation1% × 40%
Automatability30% × 15%
CISA SSVC: Track at low or medium mission impact; Track* or Attend at high (mission-essential systems).
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
0.6%
EPSS %ILE
48th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track* or Attend at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact total (CVSS ≥ 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

September 17, 2026

Last Modified

September 18, 2026

Advisory Details (6)

Auto-updated Oct 2, 2026
No patch confirmed yet.
generic

inetpeer: randomize RB-tree node comparison using SipHash - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/b20e98f0bb668a59abaf7bcf85d75c073e90d352
generic

inetpeer: randomize RB-tree node comparison using SipHash - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/857681f6835d5b0a7bc4a34a026baeaaf5215623
generic

inetpeer: randomize RB-tree node comparison using SipHash - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7109bb63667a53e4542ad845476f97d0c8b28a61
generic

inetpeer: randomize RB-tree node comparison using SipHash - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5f127e3cc9647a8a70db12c65dbd0de473545380
generic

inetpeer: randomize RB-tree node comparison using SipHash - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2ee66e9487172fcd189bc52a767c30dad7141c09
generic

inetpeer: randomize RB-tree node comparison using SipHash - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/199fcf285e498111e029137d088949bc6c26d578

Vendor Advisories for CVE-2026-90110(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(4 across 3 ecosystems)
Debian:12(2)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 7.2~rc7-1~exp1 (360 versions)
  • every version on: no fix on record
—
linux-6.126.12.100-1~deb12u1, 6.12.101-1~deb12u1, 6.12.107-1~deb12u1
  • every version up to 6.12.111-1~deb12u1: fixed in 6.12.111-1~deb12u1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 6.12.96-1 (35 versions)
  • every version up to 6.12.111-1: fixed in 6.12.111-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (179 versions)
  • every version up to 7.2.6-1: fixed in 7.2.6-1
—

Data Freshness Timeline

(refreshed 56× in last 7d / 142× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 142 total refreshes for this CVE.

  1. 2026-10-05 08:44 UTCGHSA enrichment
  2. 2026-10-05 04:57 UTCGHSA enrichment
  3. 2026-10-05 01:09 UTCEG score recompute
  4. 2026-10-05 01:09 UTCGHSA enrichment
  5. 2026-10-04 23:22 UTCEPSS rescore
  6. 2026-10-04 21:22 UTCGHSA enrichment
  7. 2026-10-04 17:34 UTCGHSA enrichment
  8. 2026-10-04 13:47 UTCGHSA enrichment
  9. 2026-10-04 10:00 UTCGHSA enrichment
  10. 2026-10-04 06:12 UTCGHSA enrichment
  11. 2026-10-04 02:25 UTCGHSA enrichment
  12. 2026-10-03 22:36 UTCGHSA enrichment
  13. 2026-10-03 18:49 UTCGHSA enrichment
  14. 2026-10-03 14:48 UTCEG score recompute
  15. 2026-10-03 14:48 UTCGHSA enrichment
  16. 2026-10-03 11:01 UTCGHSA enrichment
  17. 2026-10-03 07:14 UTCGHSA enrichment
  18. 2026-10-03 03:27 UTCGHSA enrichment
  19. 2026-10-02 23:40 UTCGHSA enrichment
  20. 2026-10-02 19:53 UTCEG score recompute
  21. 2026-10-02 19:53 UTCGHSA enrichment
  22. 2026-10-02 16:05 UTCGHSA enrichment
  23. 2026-10-02 12:18 UTCGHSA enrichment
  24. 2026-10-02 07:49 UTCGHSA enrichment
  25. 2026-10-02 03:59 UTCGHSA enrichment
Show 75 more
  1. 2026-10-02 00:09 UTCEG score recompute
  2. 2026-10-02 00:08 UTCGHSA enrichment
  3. 2026-10-01 19:51 UTCEPSS rescore
  4. 2026-10-01 19:33 UTCGHSA enrichment
  5. 2026-10-01 15:46 UTCGHSA enrichment
  6. 2026-10-01 11:58 UTCGHSA enrichment
  7. 2026-10-01 08:11 UTCGHSA enrichment
  8. 2026-10-01 04:24 UTCGHSA enrichment
  9. 2026-10-01 00:37 UTCGHSA enrichment
  10. 2026-09-30 20:40 UTCGHSA enrichment
  11. 2026-09-30 16:53 UTCEG score recompute
  12. 2026-09-30 16:53 UTCGHSA enrichment
  13. 2026-09-30 15:04 UTCEPSS rescore
  14. 2026-09-30 12:18 UTCGHSA enrichment
  15. 2026-09-30 08:31 UTCGHSA enrichment
  16. 2026-09-30 04:44 UTCGHSA enrichment
  17. 2026-09-30 00:45 UTCGHSA enrichment
  18. 2026-09-29 18:23 UTCEG score recompute
  19. 2026-09-29 18:23 UTCGHSA enrichment
  20. 2026-09-29 14:37 UTCGHSA enrichment
  21. 2026-09-29 10:49 UTCGHSA enrichment
  22. 2026-09-29 07:01 UTCGHSA enrichment
  23. 2026-09-29 03:14 UTCGHSA enrichment
  24. 2026-09-28 23:25 UTCEG score recompute
  25. 2026-09-28 23:25 UTCGHSA enrichment
  26. 2026-09-28 19:38 UTCGHSA enrichment
  27. 2026-09-28 15:37 UTCEG score recompute
  28. 2026-09-28 15:37 UTCGHSA enrichment
  29. 2026-09-28 13:52 UTCEPSS rescore
  30. 2026-09-28 13:52 UTCEPSS rescore
  31. 2026-09-28 11:43 UTCGHSA enrichment
  32. 2026-09-28 07:52 UTCGHSA enrichment
  33. 2026-09-28 04:05 UTCGHSA enrichment
  34. 2026-09-28 00:18 UTCGHSA enrichment
  35. 2026-09-27 20:31 UTCGHSA enrichment
  36. 2026-09-27 16:44 UTCEG score recompute
  37. 2026-09-27 16:44 UTCGHSA enrichment
  38. 2026-09-27 13:49 UTCEPSS rescore
  39. 2026-09-27 12:57 UTCGHSA enrichment
  40. 2026-09-27 09:09 UTCGHSA enrichment
  41. 2026-09-27 05:19 UTCGHSA enrichment
  42. 2026-09-27 01:31 UTCGHSA enrichment
  43. 2026-09-26 21:40 UTCGHSA enrichment
  44. 2026-09-26 17:54 UTCEG score recompute
  45. 2026-09-26 17:53 UTCGHSA enrichment
  46. 2026-09-26 15:59 UTCEPSS rescore
  47. 2026-09-26 14:04 UTCGHSA enrichment
  48. 2026-09-26 10:01 UTCGHSA enrichment
  49. 2026-09-26 06:11 UTCGHSA enrichment
  50. 2026-09-26 02:20 UTCEG score recompute
  51. 2026-09-26 02:20 UTCGHSA enrichment
  52. 2026-09-25 22:32 UTCGHSA enrichment
  53. 2026-09-25 18:22 UTCGHSA enrichment
  54. 2026-09-25 14:10 UTCGHSA enrichment
  55. 2026-09-25 10:22 UTCGHSA enrichment
  56. 2026-09-25 06:35 UTCGHSA enrichment
  57. 2026-09-25 02:48 UTCGHSA enrichment
  58. 2026-09-24 23:00 UTCGHSA enrichment
  59. 2026-09-24 19:00 UTCGHSA enrichment
  60. 2026-09-24 15:13 UTCEG score recompute
  61. 2026-09-24 15:13 UTCGHSA enrichment
  62. 2026-09-24 14:04 UTCEPSS rescore
  63. 2026-09-24 11:26 UTCGHSA enrichment
  64. 2026-09-24 07:39 UTCGHSA enrichment
  65. 2026-09-24 03:51 UTCGHSA enrichment
  66. 2026-09-23 23:57 UTCGHSA enrichment
  67. 2026-09-23 20:10 UTCEG score recompute
  68. 2026-09-23 20:10 UTCGHSA enrichment
  69. 2026-09-23 17:54 UTCEPSS rescore
  70. 2026-09-23 16:23 UTCGHSA enrichment
  71. 2026-09-23 12:36 UTCGHSA enrichment
  72. 2026-09-23 08:49 UTCGHSA enrichment
  73. 2026-09-23 05:02 UTCGHSA enrichment
  74. 2026-09-23 01:14 UTCGHSA enrichment
  75. 2026-09-22 21:27 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2026-90110?
CVE-2026-90110 is a critical vulnerability published on September 17, 2026. In the Linux kernel, the following vulnerability has been resolved: inetpeer: randomize RB-tree node comparison using SipHash The inetpeer rate limiting system stores peer entries in a Red-Black tree keyed deterministically on the remote IP address. Because tree lookups walk the RB-tree using…
When was CVE-2026-90110 disclosed?
CVE-2026-90110 was first published on September 17, 2026, with the most recent update on September 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-90110 actively exploited?
CVE-2026-90110 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (48th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-90110?
CVE-2026-90110 has a CVSS base score of 9.4 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-90110?
No fix for CVE-2026-90110 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2026-90110 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-90110

Explore →

Is Your Infrastructure Affected by CVE-2026-90110?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.