CVE-2026-23351
Last modified
CVE-2026-23351 is a high-severity vulnerability rated 7.8/10 on the CVSS scale. 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").. EPSS estimates a 0.12% chance of exploitation in the next 30 days.
Description
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").
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Linux | Linux Kernel | >= 5.6.1, < 5.10.253 | — |
| Linux | Linux Kernel | >= 5.11, < 5.15.203 | — |
| Linux | Linux Kernel | >= 5.16, < 6.1.167 | — |
| Linux | Linux Kernel | >= 6.2, < 6.6.130 | — |
| Linux | Linux Kernel | >= 6.7, < 6.12.77 | — |
| Linux | Linux Kernel | >= 6.13, < 6.18.17 | — |
| Linux | Linux Kernel | >= 6.19, < 6.19.7 | — |
| Linux | Linux Kernel | 5.6 | — |
| Linux | Linux Kernel | 7.0 | Rc1 |
References
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2026-23351?
How severe is CVE-2026-23351?
How do I fix CVE-2026-23351?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-23345In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-23346In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-23347In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-23348In the Linux kernel, the following vulnerability has been re…4.7
- CVE-2026-23349In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-23350In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-23352In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-23353In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-23354In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-23355In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-23356In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-23357In the Linux kernel, the following vulnerability has been re…5.5
Are you affected by CVE-2026-23351?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
