CVE-2026-23095
BaseFortify
Publication date: 2026-02-04
Last updated on: 2026-04-03
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | 6.19 |
| linux | linux_kernel | 6.19 |
| linux | linux_kernel | 6.19 |
| linux | linux_kernel | 6.19 |
| linux | linux_kernel | 6.19 |
| linux | linux_kernel | From 5.11 (inc) to 5.15.199 (exc) |
| linux | linux_kernel | From 5.16 (inc) to 6.1.162 (exc) |
| linux | linux_kernel | From 6.2 (inc) to 6.6.122 (exc) |
| linux | linux_kernel | From 6.7 (inc) to 6.12.68 (exc) |
| linux | linux_kernel | From 6.13 (inc) to 6.18.8 (exc) |
| linux | linux_kernel | 6.19 |
| linux | linux_kernel | From 3.18 (inc) to 5.10.249 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-401 | The product does not sufficiently track and release allocated memory after it has been used, making the memory unavailable for reallocation and reuse. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a memory leak in the Linux kernel related to the Generic UDP Encapsulation (GUE) protocol handling. Specifically, when a GUE packet with an inner IP protocol number of 0 is processed, the function gue_udp_recv() returns a value that causes improper handling in ip_protocol_deliver_rcu(). This leads to a failure to properly release memory, resulting in a memory leak.
The issue arises because the code expects non-zero protocol numbers for resubmission, but protocol 0 is valid (used for IPv6 Hop-by-Hop Option). The fix involves dropping such packets to prevent the memory leak.
How can this vulnerability impact me? :
This vulnerability can cause a memory leak in the Linux kernel when processing certain network packets. Over time, this memory leak could lead to increased memory consumption, potentially degrading system performance or causing system instability.
In environments with high network traffic involving GUE packets with inner protocol 0, this could result in resource exhaustion, leading to denial of service or crashes.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability relates to a memory leak in the Linux kernel triggered by GUE packets with an inner protocol number 0. Detection would involve monitoring for memory leaks related to skb (socket buffer) allocations, especially those involving GUE packets with inner protocol 0.
Since the CVE description references a kmemleak report and a backtrace involving skb allocations, one way to detect this issue is to enable and monitor the Linux kernel's kmemleak feature, which tracks memory leaks.
Suggested commands include:
- Enable kmemleak: echo scan > /sys/kernel/debug/kmemleak
- Check for memory leaks: cat /sys/kernel/debug/kmemleak
- Monitor kernel logs for BUG or memory leak messages related to skb or GUE packets using: dmesg | grep -i skb
What immediate steps should I take to mitigate this vulnerability?
The vulnerability has been resolved by dropping GUE packets with inner protocol 0 to prevent the skb memory leak.
Immediate mitigation steps include:
- Update the Linux kernel to a version that includes the fix for this vulnerability.
- If updating immediately is not possible, consider filtering or dropping GUE packets with inner protocol 0 at the network level to prevent triggering the vulnerability.
- Enable kernel memory leak detection (kmemleak) to monitor for any related memory leaks.