CVE-2026-43208

CRITICALNVD 9.89.8
EchelonGraph scoreMEDIUM confidence

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-05-06. NVD baseline CVSS 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
9.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 9.8Exploit: None knownExposed: 0

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

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

net: do not pass flow_id to set_rps_cpu()

Blamed commit made the assumption that the RPS table for each receive queue would have the same size, and that it would not change.

Compute flow_id in set_rps_cpu(), do not assume we can use the value computed by get_rps_cpu(). Otherwise we risk out-of-bound access and/or crashes.

CVSS v3
9.8
EG Score
9.8(medium)
EG Risk
49(Track)
EG Risk 49/100SSVC: Track

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
Severity98% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
40%
KEV
Not listed

Published

May 6, 2026

Last Modified

August 5, 2026

Advisory Details (3)

Auto-updated Sep 9, 2026
No patch confirmed yet.
generic

net: do not pass flow_id to set_rps_cpu() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8a8a9fac9efa6423fd74938b940cb7d731780718
generic

net: do not pass flow_id to set_rps_cpu() - kernel/git/stable/linux.git - Linux kernel stable tree

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

net: do not pass flow_id to set_rps_cpu() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5455a232edea6b946b99449f15ca771a8874a5a6

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
linuxKernel @ 6.18.16osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.19~rc8-1~exp1 (116 versions)6.19.6-1

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 30× 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 280 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-43208?
CVE-2026-43208 is a critical vulnerability published on May 6, 2026. In the Linux kernel, the following vulnerability has been resolved: net: do not pass flowid to setrps_cpu() Blamed commit made the assumption that the RPS table for each receive queue would have the same size, and that it would not change. Compute flowid in setrps_cpu(), do not assume we can use…
When was CVE-2026-43208 disclosed?
CVE-2026-43208 was first published in the National Vulnerability Database on May 6, 2026, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-43208 actively exploited?
CVE-2026-43208 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 59.9% of all scored CVEs.
What is the CVSS score of CVE-2026-43208?
CVE-2026-43208 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-43208?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-43208, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-43208?

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