CVE-2026-43306

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2026-05-08. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: 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:

bpf: crypto: Use the correct destructor kfunc type

With CONFIG_CFI enabled, the kernel strictly enforces that indirect function calls use a function pointer type that matches the target function. I ran into the following type mismatch when running BPF self-tests:

CFI failure at bpf_obj_free_fields+0x190/0x238 (target: bpf_crypto_ctx_release+0x0/0x94; expected type: 0xa488ebfc) Internal error: Oops - CFI: 00000000f2008228 [#1] SMP ...

As bpf_crypto_ctx_release() is also used in BPF programs and using a void pointer as the argument would make the verifier unhappy, add a simple stub function with the correct type and register it as the destructor kfunc instead.

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

Published

May 8, 2026

Last Modified

May 15, 2026

Advisory Details (4)

Auto-updated Jun 15, 2026
No patch confirmed yet.
generic

bpf: crypto: Use the correct destructor kfunc type - kernel/git/stable/linux.git - Linux kernel stable tree

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

bpf: crypto: Use the correct destructor kfunc type - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/50d6fd69388cc7b05dce72f09080674dcede4ac9
generic

bpf: crypto: Use the correct destructor kfunc type - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4e3e57dbf46dad3498f8c4219ce2dba756875962
generic

bpf: crypto: Use the correct destructor kfunc type - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3979a550fe06b370d73647f59cf462fa525c9ec4

Vendor Advisories for CVE-2026-43306(2)

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

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
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 (113 versions)6.19.6-1—

Data Freshness Timeline

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

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

Frequently asked(5)

What is CVE-2026-43306?
CVE-2026-43306 is a medium vulnerability published on May 8, 2026. In the Linux kernel, the following vulnerability has been resolved: bpf: crypto: Use the correct destructor kfunc type With CONFIG_CFI enabled, the kernel strictly enforces that indirect function calls use a function pointer type that matches the target function. I ran into the following type…
When was CVE-2026-43306 disclosed?
CVE-2026-43306 was first published in the National Vulnerability Database on May 8, 2026, with the most recent update on May 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-43306 actively exploited?
CVE-2026-43306 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 97.8% of all scored CVEs.
What is the CVSS score of CVE-2026-43306?
CVE-2026-43306 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-43306?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-43306, 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-43306

Explore →

Is Your Infrastructure Affected by CVE-2026-43306?

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

Start Free Scan →Browse All CVEs