CVE-2026-43116

HIGHPre-NVD 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.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.8Exploit: NoneExposed: 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
EPSS
0.9%
KEV
Not listed

Published

May 6, 2026

Last Modified

June 19, 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(3)

Vendor / EcosystemFixed in / PatchReleasedSource
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.

Weakness Classification(1)

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

Data Freshness Timeline

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

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

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 June 19, 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.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-43116?
CVE-2026-43116 has a CVSS v3 base score of 7.8 (NVD).
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

Explore the affected products and dependency analysis for 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.