CVE-2026-23351

HIGHPre-NVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
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: nft_set_pipapo: split gc into unlink and reclaim phase

Yiming Qian reports Use-after-free in the pipapo set type: Under a large number of expired elements, commit-time GC can run for a very long time in a non-preemptible context, triggering soft lockup warnings and RCU stall reports (local denial of service).

We must split GC in an unlink and a reclaim phase.

We cannot queue elements for freeing until pointers have been swapped. Expired elements are still exposed to both the packet path and userspace dumpers via the live copy of the data structure.

call_rcu() does not protect us: dump operations or element lookups starting after call_rcu has fired can still observe the free'd element, unless the commit phase has made enough progress to swap the clone and live pointers before any new reader has picked up the old version.

This a similar approach as done recently for the rbtree backend in commit 35f83a75529a ("netfilter: nft_set_rbtree: don't gc elements on insert").

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

Published

March 25, 2026

Last Modified

August 5, 2026

Advisory Details (8)

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

netfilter: nft_set_pipapo: split gc into unlink and reclaim phase - kernel/git/stable/linux.git - Linux kernel stable tree

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

netfilter: nft_set_pipapo: split gc into unlink and reclaim phase - kernel/git/stable/linux.git - Linux kernel stable tree

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

netfilter: nft_set_pipapo: split gc into unlink and reclaim phase - kernel/git/stable/linux.git - Linux kernel stable tree

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

netfilter: nft_set_pipapo: split gc into unlink and reclaim phase - kernel/git/stable/linux.git - Linux kernel stable tree

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

netfilter: nft_set_pipapo: split gc into unlink and reclaim phase - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7864c667aed01a58b87ca518a631322cd0ac34c0
generic

netfilter: nft_set_pipapo: split gc into unlink and reclaim phase - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/65ca51b9fb85477ab92a04295aed34b38f7c062e
generic

netfilter: nft_set_pipapo: split gc into unlink and reclaim phase - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/500a50a301ce962b019ab95053ac70264fec2c21
generic

netfilter: nft_set_pipapo: split gc into unlink and reclaim phase - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/16f3595c0441d87dfa005c47d8f95be213afaa9e

Vendor Advisories for CVE-2026-23351(3)

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

Patch Availability(20)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-azure-6.17 (6.17.0-1015.15) @ questing2026-06-11ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1054.57.1) @ noble2026-06-11ubuntu
ubuntulinux-tools-oracle-edge (6.17.0-1014.14~24.04.1) @ noble2026-06-11ubuntu
ubuntulinux-tools-lowlatency-hwe-20.04-edge (5.15.0.178.188~20.04.1) @ focal2026-06-11ubuntu
ubuntulinux-tools-fips-6.8 (6.8.0-116.116+fips1) @ noble2026-06-11ubuntu
ubuntulinux-tools-nvidia-tegra-rt-6.8 (6.8.0-1024.24) @ noble2026-06-11ubuntu
ubuntulinux-tools-nvidia-tegra-igx-rt-5.15 (5.15.0.1049.51) @ jammy2026-06-11ubuntu
ubuntulinux-tools-nvidia-hwe-22.04-edge (6.8.0-1054.57~22.04.1) @ jammy2026-06-11ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1056.62) @ noble2026-06-11ubuntu
ubuntulinux-virtual-hwe-20.04-edge (5.15.0.179.189~20.04.1) @ focal2026-06-11ubuntu
ubuntulinux-tools-lowlatency-hwe-20.04-edge (5.15.0.178.150) @ jammy2026-06-11ubuntu
ubuntulinux-tools-azure-fips-5.15 (5.15.0.1114.99) @ jammy2026-06-11ubuntu
ubuntulinux-virtual-hwe-24.04 (6.17.0-29.29~24.04.1) @ noble2026-06-11ubuntu
ubuntulinux-virtual-6.8 (6.8.0-117.117) @ noble2026-06-11ubuntu
ubuntulinux-tools-intel-iot-realtime-5.15 (5.15.0.1099.103) @ jammy2026-06-11ubuntu
ubuntulinux-tools-gcp-edge (5.15.0.1108.117~20.04.1) @ focal2026-06-11ubuntu
ubuntulinux-tools-gcp-64k-6.17 (6.17.0-1018.19) @ questing2026-06-11ubuntu
ubuntulinux-tools-azure-fips-6.8 (6.8.0-1059.65+fips1) @ noble2026-06-11ubuntu
linuxKernel @ 5.10.253—osv
linuxKernel @ 6.1.167—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

(5 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 5.10.92-2 (53 versions)5.10.257-1—
linux-6.16.1.106-3~deb11u1 ... 6.1.164-1~deb11u1 (16 versions)6.1.170-1~deb11u1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (48 versions)6.1.170-1—
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 (117 versions)6.19.8-1—

Weakness Classification(1)

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

Additional Vendor Advisories

(24)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

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

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

Frequently asked(5)

What is CVE-2026-23351?
CVE-2026-23351 is a high vulnerability published on March 25, 2026. In the Linux kernel, the following vulnerability has been resolved: netfilter: nftsetpipapo: split gc into unlink and reclaim phase Yiming Qian reports Use-after-free in the pipapo set type: Under a large number of expired elements, commit-time GC can run for a very long time in a non-preemptible…
When was CVE-2026-23351 disclosed?
CVE-2026-23351 was first published in the National Vulnerability Database on March 25, 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-23351 actively exploited?
CVE-2026-23351 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.5% of all scored CVEs.
What is the CVSS score of CVE-2026-23351?
CVE-2026-23351 has a CVSS v4.0 base score of 7.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-23351?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-23351, 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-23351

Explore →

Is Your Infrastructure Affected by CVE-2026-23351?

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

Start Free Scan →Browse All CVEs