CVE-2026-43116

HIGHPre-NVD 7.87.8
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
Trending — 4 sources updated this week
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:

netfilter: ctnetlink: ensure safe access to master conntrack

Holding reference on the expectation is not sufficient, the master conntrack object can just go away, making exp->master invalid.

To access exp->master safely:

  • Grab the nf_conntrack_expect_lock, this gets serialized with
clean_from_lists() which also holds this lock when the master conntrack goes away.
  • Hold reference on master conntrack via nf_conntrack_find_get().
Not so easy since the master tuple to look up for the master conntrack is not available in the existing problematic paths.

This patch goes for extending the nf_conntrack_expect_lock section to address this issue for simplicity, in the cases that are described below this is just slightly extending the lock section.

The add expectation command already holds a reference to the master conntrack from ctnetlink_create_expect().

However, the delete expectation command needs to grab the spinlock before looking up for the expectation. Expand the existing spinlock section to address this to cover the expectation lookup. Note that, the nf_ct_expect_iterate_net() calls already grabs the spinlock while iterating over the expectation table, which is correct.

The get expectation command needs to grab the spinlock to ensure master conntrack does not go away. This also expands the existing spinlock section to cover the expectation lookup too. I needed to move the netlink skb allocation out of the spinlock to keep it GFP_KERNEL.

For the expectation events, the IPEXP_DESTROY event is already delivered under the spinlock, just move the delivery of IPEXP_NEW under the spinlock too because the master conntrack event cache is reached through exp->master.

While at it, add lockdep notations to help identify what codepaths need to grab the spinlock.

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
1%
KEV
Not listed

Published

May 6, 2026

Last Modified

August 5, 2026

Advisory Details (3)

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

netfilter: ctnetlink: ensure safe access to master conntrack - kernel/git/stable/linux.git - Linux kernel stable tree

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

netfilter: ctnetlink: ensure safe access to master conntrack - kernel/git/stable/linux.git - Linux kernel stable tree

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

netfilter: ctnetlink: ensure safe access to master conntrack - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/497f99b26fffdc5635706d1b4811f1ed8ee21a5b

Patch Availability(13)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatkernel-0:4.18.0-553.150.1.el8_102026-07-31redhat
redhatkernel-rt-0:4.18.0-553.150.1.rt7.491.el8_102026-07-31redhat
redhatkernel-0:5.14.0-427.132.1.el9_42026-06-22redhat
redhatkernel-0:5.14.0-570.123.1.el9_62026-06-22redhat
redhatkernel-0:6.12.0-55.82.1.el10_02026-06-22redhat
redhatkernel-0:4.18.0-305.194.1.el8_42026-06-17redhat
redhatkernel-0:4.18.0-477.147.1.el8_82026-06-17redhat
redhatkernel-0:4.18.0-372.196.1.el8_62026-06-17redhat
redhatkernel-0:5.14.0-284.176.1.el9_22026-06-17redhat
redhatkernel-rt-0:5.14.0-284.176.1.rt14.461.el9_22026-06-17redhat
redhatkernel-0:5.14.0-687.15.1.el9_82026-06-11redhat
redhatkernel-0:6.12.0-211.18.1.el10_22026-05-28redhat
linuxKernel @ 6.1.176osv

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

(5 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 7.2~rc5-1~exp1 (496 versions)
linux-6.16.1.106-3~deb11u1 ... 6.1.174-1~deb11u1 (20 versions)6.1.176-1~deb11u1
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (53 versions)6.1.176-1
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.94-1~bpo12+1 (27 versions)6.12.94-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.19~rc8-1~exp1 (126 versions)6.19.14-1

Weakness Classification(1)

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

Data Freshness Timeline

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

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

Frequently asked(5)

What is CVE-2026-43116?
CVE-2026-43116 is a high vulnerability published on May 6, 2026. In the Linux kernel, the following vulnerability has been resolved: netfilter: ctnetlink: ensure safe access to master conntrack Holding reference on the expectation is not sufficient, the master conntrack object can just go away, making exp->master invalid. To access exp->master safely: Grab the…
When was CVE-2026-43116 disclosed?
CVE-2026-43116 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-43116 actively exploited?
CVE-2026-43116 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 99.2% of all scored CVEs.
What is the CVSS score of CVE-2026-43116?
CVE-2026-43116 has a CVSS v4.0 base score of 7.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-43116?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-43116, 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-43116

Explore →

Is Your Infrastructure Affected by CVE-2026-43116?

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