CVE-2026-23072: l2tp: Fix memleak in l2tp_udp_encap_recv().
Noroxi assessment
Priority: Monitor (action score 22/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.14% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 4d10edfd1475b69dbd4c47f34b61a3772ece83ca, 5cd158a88eef34e7b100cd9b963873d3b4e41b35, d4ce79e6dce2a4a49eebceea7b4caf5dc0f0ef3d.
Low priority for now. Upgrade to Linux Linux 4d10edfd1475b69dbd4c47f34b61a3772ece83ca, 5cd158a88eef34e7b100cd9b963873d3b4e41b35, d4ce79e6dce2a4a49eebceea7b4caf5dc0f0ef3d or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
In the Linux kernel, the following vulnerability has been resolved: l2tp: Fix memleak in l2tp_udp_encap_recv(). syzbot reported memleak of struct l2tp_session, l2tp_tunnel, sock, etc. [0] The cited commit moved down the validation of the protocol version in l2tp_udp_encap_recv(). The new place requires an extra error handling to avoid the memleak. Let's call l2tp_session_put() there. [0]: BUG: memory leak unreferenced object 0xffff88810a290200 (size 512): comm "syz.0.17", pid 6086, jiffies 4294944299 hex dump (first 32 bytes): 7d eb 04 0c 00 00 00 00 01 00 00 00 00 00 00 00 }............... 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ backtrace (crc babb6a4f): kmemleak_alloc_recursive include/linux/kmemleak.h:44 [inline] slab_post_alloc_hook mm/slub.c:4958 [inline] slab_alloc_node mm/slub.c:5263 [inline] __do_kmalloc_node mm/slub.c:5656 [inline] __kmalloc_noprof+0x3e0/0x660 mm/slub.c:5669 kmalloc_noprof include/linux/slab.h:961 [inline] kzalloc_noprof include/linux/slab.h:1094 [inline] l2tp_session_create+0x3a/0x3b0 net/l2tp/l2tp_core.c:1778 pppol2tp_connect+0x48b/0x920 net/l2tp/l2tp_ppp.c:755 __sys_connect_file+0x7a/0xb0 net/socket.c:2089 __sys_connect+0xde/0x110 net/socket.c:2108 __do_sys_connect net/socket.c:2114 [inline] __se_sys_connect net/socket.c:2111 [inline] __x64_sys_connect+0x1c/0x30 net/socket.c:2111 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xa4/0xf80 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f
- Published
- Feb 4, 2026
- Updated
- Jun 17, 2026
- EPSS
- 0.1% · 3th percentile
- CWE
- CWE-401
Report tools
Action score
22
Monitor
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel6.10 and later · before 6.12.68
- linux linux kernel6.13 and later · before 6.18.8
- linux linux kernel6.19
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 6.10affected
- 364798056f518b0bf2f17cd9eaf0dd4e856d7393 and later · before 5cd158a88eef34e7b100cd9b963873d3b4e41b35affected · git
- 364798056f518b0bf2f17cd9eaf0dd4e856d7393 and later · before d4ce79e6dce2a4a49eebceea7b4caf5dc0f0ef3daffected · git
- 364798056f518b0bf2f17cd9eaf0dd4e856d7393 and later · before 4d10edfd1475b69dbd4c47f34b61a3772ece83caaffected · git
- before 6.10not affected · semver
- 6.12.68 and later · up to and including 6.12.*not affected · semver
- 6.18.8 and later · up to and including 6.18.*not affected · semver
- 6.19 and laternot affected · original_commit_for_fix
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:13 | linux | before 6.12.69-1 | 6.12.69-1 |
| Debian:14 | linux | before 6.18.8-1 | 6.18.8-1 |
| openSUSE:Leap 16.0 | dtb-aarch64 | before 6.12.0-160000.28.1 | 6.12.0-160000.28.1 |
| openSUSE:Leap 16.0 | kernel-64kb | before 6.12.0-160000.28.1 | 6.12.0-160000.28.1 |
| openSUSE:Leap 16.0 | kernel-azure | before 6.12.0-160000.28.1 | 6.12.0-160000.28.1 |
| openSUSE:Leap 16.0 | kernel-default | before 6.12.0-160000.28.1 | 6.12.0-160000.28.1 |
| openSUSE:Leap 16.0 | kernel-default-base | before 6.12.0-160000.27.1.160000.2.8 | 6.12.0-160000.27.1.160000.2.8 |
| openSUSE:Leap 16.0 | kernel-docs | before 6.12.0-160000.28.1 | 6.12.0-160000.28.1 |
| openSUSE:Leap 16.0 | kernel-kvmsmall | before 6.12.0-160000.28.1 | 6.12.0-160000.28.1 |
| openSUSE:Leap 16.0 | kernel-obs-build | before 6.12.0-160000.28.1 | 6.12.0-160000.28.1 |
| openSUSE:Leap 16.0 | kernel-obs-qa | before 6.12.0-160000.28.1 | 6.12.0-160000.28.1 |
| openSUSE:Leap 16.0 | kernel-rt | before 6.12.0-160000.28.1 | 6.12.0-160000.28.1 |
| openSUSE:Leap 16.0 | kernel-source | before 6.12.0-160000.28.1 | 6.12.0-160000.28.1 |
| openSUSE:Leap 16.0 | kernel-syms | before 6.12.0-160000.28.1 | 6.12.0-160000.28.1 |
| openSUSE:Leap 16.0 | kernel-zfcpdump | before 6.12.0-160000.28.1 | 6.12.0-160000.28.1 |
| SUSE:Linux Micro 6.2 | gdk-pixbuf | before 2.42.12-160000.4.1 | 2.42.12-160000.4.1 |
| SUSE:Linux Micro 6.2 | kernel-64kb | before 6.12.0-160000.28.1 | 6.12.0-160000.28.1 |
| SUSE:Linux Micro 6.2 | kernel-default | before 6.12.0-160000.28.1 | 6.12.0-160000.28.1 |
| SUSE:Linux Micro 6.2 | kernel-default-base | before 6.12.0-160000.27.1.160000.2.8 | 6.12.0-160000.27.1.160000.2.8 |
| SUSE:Linux Micro 6.2 | kernel-rt | before 6.12.0-160000.28.1 | 6.12.0-160000.28.1 |
| SUSE:Linux Micro 6.2 | kernel-source | before 6.12.0-160000.28.1 | 6.12.0-160000.28.1 |
| SUSE:Linux Micro Extras 6.2 | kernel-obs-build | before 6.12.0-160000.28.1 | 6.12.0-160000.28.1 |
| SUSE:Linux Micro Extras 6.2 | kernel-syms | before 6.12.0-160000.28.1 | 6.12.0-160000.28.1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2026-23068Feb 4, 2026 · spi: spi-sprd-adi: Fix double free in probe error path31Monitor
- ← EarlierCVE-2026-23070Feb 4, 2026 · Octeontx2-af: Add proper checks for fwdata22Monitor
- Later →CVE-2026-23075Feb 4, 2026 · can: esd_usb: esd_usb_read_bulk_callback(): fix URB memory leak22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 4d10edfd1475b69dbd4c47f34b61a3772ece83ca | Vendor (CNA) |
| Linux Linux | 5cd158a88eef34e7b100cd9b963873d3b4e41b35 | Vendor (CNA) |
| Linux Linux | d4ce79e6dce2a4a49eebceea7b4caf5dc0f0ef3d | Vendor (CNA) |
| debian:linux | 6.12.69-1 · Debian:13 | Package registry (OSV) |
| opensuse:dtb-aarch64 | 6.12.0-160000.28.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-64kb | 6.12.0-160000.28.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-azure | 6.12.0-160000.28.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-default | 6.12.0-160000.28.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-default-base | 6.12.0-160000.27.1.160000.2.8 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-docs | 6.12.0-160000.28.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-kvmsmall | 6.12.0-160000.28.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-obs-build | 6.12.0-160000.28.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-obs-qa | 6.12.0-160000.28.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-rt | 6.12.0-160000.28.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-source | 6.12.0-160000.28.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:kernel-syms | 6.12.0-160000.28.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| suse:gdk-pixbuf | 2.42.12-160000.4.1 · SUSE:Linux Micro 6.2 | Package registry (OSV) |
| suse:kernel-64kb | 6.12.0-160000.28.1 · SUSE:Linux Micro 6.2 | Package registry (OSV) |
| suse:kernel-default | 6.12.0-160000.28.1 · SUSE:Linux Micro 6.2 | Package registry (OSV) |
| suse:kernel-default-base | 6.12.0-160000.27.1.160000.2.8 · SUSE:Linux Micro 6.2 | Package registry (OSV) |
| suse:kernel-obs-build | 6.12.0-160000.28.1 · SUSE:Linux Micro Extras 6.2 | Package registry (OSV) |
| suse:kernel-rt | 6.12.0-160000.28.1 · SUSE:Linux Micro 6.2 | Package registry (OSV) |
| suse:kernel-source | 6.12.0-160000.28.1 · SUSE:Linux Micro 6.2 | Package registry (OSV) |
| suse:kernel-syms | 6.12.0-160000.28.1 · SUSE:Linux Micro Extras 6.2 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-401 · Missing Release of Memory after Effective LifetimeCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.