CVE-2026-43260

HIGHNVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
7.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: 7.8Exploit: None knownExposed: 0

A fix is available — apply it.

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

bnxt_en: Fix RSS context delete logic

We need to free the corresponding RSS context VNIC in FW everytime an RSS context is deleted in driver. Commit 667ac333dbb7 added a check to delete the VNIC in FW only when netif_running() is true to help delete RSS contexts with interface down.

Having that condition will make the driver leak VNICs in FW whenever close() happens with active RSS contexts. On the subsequent open(), as part of RSS context restoration, we will end up trying to create extra VNICs for which we did not make any reservation. FW can fail this request, thereby making us lose active RSS contexts.

Suppose an RSS context is deleted already and we try to process a delete request again, then the HWRM functions will check for validity of the request and they simply return if the resource is already freed. So, even for delete-when-down cases, netif_running() check is not necessary.

Remove the netif_running() condition check when deleting an RSS context.

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
40(Track)
EG Risk 40/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
Severity78% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
4%
KEV
Not listed

Published

May 6, 2026

Last Modified

May 8, 2026

Advisory Details (4)

Auto-updated May 8, 2026
No patch confirmed yet.
generic

bnxt_en: Fix RSS context delete logic - kernel/git/stable/linux.git - Linux kernel stable tree

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

bnxt_en: Fix RSS context delete logic - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9a9b89eea4a9cc7726702946ff688d716962fabd
generic

bnxt_en: Fix RSS context delete logic - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/348a5f8d06c7bdf954e13c17ad5f80b59a075604
generic

bnxt_en: Fix RSS context delete logic - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/079986d6db1f8e3d50c55f400cf998ac9690d2c8

Vendor Advisories for CVE-2026-43260(2)

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

Patch Availability(3)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatkernel-0:5.14.0-687.17.1.el9_82026-06-22redhat
redhatkernel-0:6.12.0-211.26.1.el10_22026-06-20redhat
linuxKernel @ 6.12.75—osv

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

(2 across 2 ecosystems)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.85-1~bpo12+1 (17 versions)6.12.85-1—
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 206 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-01 13:54 UTCEPSS rescore
  12. 2026-08-30 19:17 UTCEPSS rescore
  13. 2026-08-30 01:22 UTCEPSS rescore
  14. 2026-08-28 21:41 UTCEPSS rescore
  15. 2026-08-27 14:25 UTCEPSS rescore
  16. 2026-08-26 14:46 UTCEPSS rescore
  17. 2026-08-25 13:49 UTCEPSS rescore
  18. 2026-08-23 19:53 UTCEG score recompute
  19. 2026-08-23 19:53 UTCVendor advisory
  20. 2026-08-23 19:53 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:54 UTCEG score recompute
  3. 2026-08-17 12:54 UTCVendor advisory
  4. 2026-08-17 12:54 UTCGHSA enrichment
  5. 2026-08-16 14:56 UTCEPSS rescore
  6. 2026-08-16 04:52 UTCEG score recompute
  7. 2026-08-16 04:52 UTCVendor advisory
  8. 2026-08-16 04:52 UTCGHSA enrichment
  9. 2026-08-16 02:14 UTCEPSS rescore
  10. 2026-08-15 01:30 UTCEPSS rescore
  11. 2026-08-14 15:31 UTCVendor advisory
  12. 2026-08-14 15:31 UTCGHSA enrichment
  13. 2026-08-14 03:26 UTCEG score recompute
  14. 2026-08-14 03:26 UTCVendor advisory
  15. 2026-08-14 03:26 UTCGHSA enrichment
  16. 2026-08-13 22:00 UTCEPSS rescore
  17. 2026-08-13 06:07 UTCVendor advisory
  18. 2026-08-13 06:07 UTCGHSA enrichment
  19. 2026-08-12 17:00 UTCEG score recompute
  20. 2026-08-12 17:00 UTCVendor advisory
  21. 2026-08-12 17:00 UTCGHSA enrichment
  22. 2026-08-12 13:51 UTCEPSS rescore
  23. 2026-08-11 16:00 UTCEG score recompute
  24. 2026-08-11 16:00 UTCVendor advisory
  25. 2026-08-11 15:59 UTCGHSA enrichment
  26. 2026-08-11 13:43 UTCEPSS rescore
  27. 2026-08-11 01:31 UTCEG score recompute
  28. 2026-08-11 01:31 UTCVendor advisory
  29. 2026-08-11 01:31 UTCGHSA enrichment
  30. 2026-08-11 00:00 UTCEPSS rescore
  31. 2026-08-10 02:43 UTCVendor advisory
  32. 2026-08-10 02:43 UTCGHSA enrichment
  33. 2026-08-09 14:38 UTCEG score recompute
  34. 2026-08-09 14:38 UTCVendor advisory
  35. 2026-08-09 14:38 UTCGHSA enrichment
  36. 2026-08-09 13:46 UTCEPSS rescore
  37. 2026-08-09 02:34 UTCEG score recompute
  38. 2026-08-09 02:34 UTCVendor advisory
  39. 2026-08-09 02:34 UTCGHSA enrichment
  40. 2026-08-08 16:37 UTCEPSS rescore
  41. 2026-08-08 02:01 UTCEG score recompute
  42. 2026-08-08 02:01 UTCVendor advisory
  43. 2026-08-08 02:01 UTCGHSA enrichment
  44. 2026-08-07 13:58 UTCVendor advisory
  45. 2026-08-07 13:57 UTCGHSA enrichment
  46. 2026-08-07 01:53 UTCEG score recompute
  47. 2026-08-07 01:53 UTCVendor advisory
  48. 2026-08-07 01:53 UTCGHSA enrichment
  49. 2026-08-06 13:46 UTCEPSS rescore
  50. 2026-08-06 10:24 UTCVendor advisory
  51. 2026-08-06 10:24 UTCGHSA enrichment
  52. 2026-08-05 22:20 UTCEG score recompute
  53. 2026-08-05 22:20 UTCVendor advisory
  54. 2026-08-05 22:20 UTCGHSA enrichment
  55. 2026-08-05 19:17 UTCEPSS rescore
  56. 2026-08-04 15:10 UTCEPSS rescore
  57. 2026-08-04 10:38 UTCEPSS rescore
  58. 2026-08-03 19:51 UTCEG score recompute
  59. 2026-08-03 19:51 UTCVendor advisory
  60. 2026-08-03 19:51 UTCGHSA enrichment
  61. 2026-08-03 10:36 UTCEPSS rescore
  62. 2026-08-02 17:11 UTCVendor advisory
  63. 2026-08-02 17:11 UTCGHSA enrichment
  64. 2026-08-02 05:06 UTCEG score recompute
  65. 2026-08-02 05:06 UTCVendor advisory
  66. 2026-08-02 05:06 UTCGHSA enrichment
  67. 2026-08-02 02:27 UTCEPSS rescore
  68. 2026-08-01 04:16 UTCEPSS rescore
  69. 2026-07-30 16:28 UTCEPSS rescore
  70. 2026-07-30 01:30 UTCEPSS rescore
  71. 2026-07-28 15:36 UTCEPSS rescore
  72. 2026-07-27 14:13 UTCEPSS rescore
  73. 2026-07-26 14:54 UTCEPSS rescore
  74. 2026-07-26 14:54 UTCEPSS rescore
  75. 2026-07-25 14:18 UTCEPSS rescore

Frequently asked(5)

What is CVE-2026-43260?
CVE-2026-43260 is a high vulnerability published on May 6, 2026. In the Linux kernel, the following vulnerability has been resolved: bnxt_en: Fix RSS context delete logic We need to free the corresponding RSS context VNIC in FW everytime an RSS context is deleted in driver. Commit 667ac333dbb7 added a check to delete the VNIC in FW only when netif_running() is…
When was CVE-2026-43260 disclosed?
CVE-2026-43260 was first published in the National Vulnerability Database on May 6, 2026, with the most recent update on May 8, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-43260 actively exploited?
CVE-2026-43260 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 96.5% of all scored CVEs.
What is the CVSS score of CVE-2026-43260?
CVE-2026-43260 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-43260?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-43260, 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-43260

Explore →

Is Your Infrastructure Affected by CVE-2026-43260?

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

Start Free Scan →Browse All CVEs