CVE-2026-63918: l2tp: use refcount_inc_not_zero in l2tp_session_get_by_ifname
Noroxi assessment
Priority: Monitor (action score 31/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.16% (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 05f95729ca844704d15e49ce14868af4b403b32b, 782d60a6596aee9b29c2eecfa70033899278bf65, 947013fd7c8c35dd5856557b215840098a3f67f8.
Low priority for now. Upgrade to Linux Linux 05f95729ca844704d15e49ce14868af4b403b32b, 782d60a6596aee9b29c2eecfa70033899278bf65, 947013fd7c8c35dd5856557b215840098a3f67f8 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: use refcount_inc_not_zero in l2tp_session_get_by_ifname A reader in l2tp_session_get_by_ifname() can return a pointer to a session whose refcount has reached zero. The getter takes its reference with plain refcount_inc(), but every other session getter in the same file (l2tp_v2_session_get, l2tp_v3_session_get, and the corresponding _get_next variants) uses refcount_inc_not_zero() because the IDR/RCU lookup can race with refcount_dec_and_test() -> l2tp_session_free() -> kfree_rcu(). The ifname getter is the only outlier; the inconsistency was raised on-list after 979c017803c4 ("l2tp: use list_del_rcu in l2tp_session_unhash"). A reader inside rcu_read_lock_bh() that matches session->ifname can be preempted between the strcmp() and the refcount_inc(). If the last reference drops on another CPU in that window, the reader's refcount_inc() runs on a counter that has reached zero. refcount_t catches the addition-on-zero, prints "refcount_t: addition on 0; use-after-free", saturates the counter, and returns the saturated pointer to the caller. Session memory is held live by the in-flight RCU read section, but the kfree_rcu() callback queued from l2tp_session_free() will free it once the grace period closes; a caller that dereferences the returned session past that point hits a slab-use-after-free. On PREEMPT_RT local_bh_disable() is a per-CPU sleeping lock and the preemption window is real; on stock PREEMPT kernels local_bh_disable() is a preempt_count increment that closes the cross-CPU race in practice (see below). Use refcount_inc_not_zero() and continue the list walk on failure, matching the other session getters in the file. The ifname getter is the only session getter in net/l2tp/ that still uses the bare refcount_inc() pattern; this change restores file-internal consistency. The success path is unchanged.
- Published
- Jul 19, 2026
- Updated
- Oct 30, 2026
- EPSS
- 0.1% · 5th percentile
- CWE
- CWE-416
Report tools
Action score
31
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 7.8
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
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.
Is your version affected? Check itNoroxi 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 |
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.12affected
- abe7a1a7d0b69e63b1bca5f9531023a52336784f and later · before ee80455feffb9cb62b5b58715cabeff495e666b2affected · git
- abe7a1a7d0b69e63b1bca5f9531023a52336784f and later · before 947013fd7c8c35dd5856557b215840098a3f67f8affected · git
- abe7a1a7d0b69e63b1bca5f9531023a52336784f and later · before 782d60a6596aee9b29c2eecfa70033899278bf65affected · git
- abe7a1a7d0b69e63b1bca5f9531023a52336784f and later · before 05f95729ca844704d15e49ce14868af4b403b32baffected · git
- before 6.12not affected · semver
- 6.12.93 and later · up to and including 6.12.*not affected · semver
- 6.18.35 and later · up to and including 6.18.*not affected · semver
- 7.0.12 and later · up to and including 7.0.*not affected · semver
- 7.1 and laternot affected · original_commit_for_fix
Affected versions · NVD (4)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel6.12 and later · before 6.12.93
- linux linux kernel6.13 and later · before 6.18.35
- linux linux kernel6.19 and later · before 7.0.12
- linux linux kernel7.1
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:10 | kernel | before 6.12.0-211.63.1.el10_2 | 6.12.0-211.63.1.el10_2 |
| AlmaLinux:10 | kernel-64k | before 6.12.0-211.63.1.el10_2 | 6.12.0-211.63.1.el10_2 |
| AlmaLinux:10 | kernel-64k-core | before 6.12.0-211.63.1.el10_2 | 6.12.0-211.63.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug | before 6.12.0-211.63.1.el10_2 | 6.12.0-211.63.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-core | before 6.12.0-211.63.1.el10_2 | 6.12.0-211.63.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-devel | before 6.12.0-211.63.1.el10_2 | 6.12.0-211.63.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-devel-matched | before 6.12.0-211.63.1.el10_2 | 6.12.0-211.63.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-modules | before 6.12.0-211.63.1.el10_2 | 6.12.0-211.63.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-modules-core | before 6.12.0-211.63.1.el10_2 | 6.12.0-211.63.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-modules-extra | before 6.12.0-211.63.1.el10_2 | 6.12.0-211.63.1.el10_2 |
| AlmaLinux:10 | kernel-64k-devel | before 6.12.0-211.63.1.el10_2 | 6.12.0-211.63.1.el10_2 |
| AlmaLinux:10 | kernel-64k-devel-matched | before 6.12.0-211.63.1.el10_2 | 6.12.0-211.63.1.el10_2 |
| AlmaLinux:10 | kernel-64k-modules | before 6.12.0-211.63.1.el10_2 | 6.12.0-211.63.1.el10_2 |
| AlmaLinux:10 | kernel-64k-modules-core | before 6.12.0-211.63.1.el10_2 | 6.12.0-211.63.1.el10_2 |
| AlmaLinux:10 | kernel-64k-modules-extra | before 6.12.0-211.63.1.el10_2 | 6.12.0-211.63.1.el10_2 |
| AlmaLinux:10 | kernel-abi-stablelists | before 6.12.0-211.63.1.el10_2 | 6.12.0-211.63.1.el10_2 |
| AlmaLinux:10 | kernel-core | before 6.12.0-211.63.1.el10_2 | 6.12.0-211.63.1.el10_2 |
| AlmaLinux:10 | kernel-cross-headers | before 6.12.0-211.63.1.el10_2 | 6.12.0-211.63.1.el10_2 |
| AlmaLinux:10 | kernel-debug | before 6.12.0-211.63.1.el10_2 | 6.12.0-211.63.1.el10_2 |
| AlmaLinux:10 | kernel-debug-core | before 6.12.0-211.63.1.el10_2 | 6.12.0-211.63.1.el10_2 |
| AlmaLinux:10 | kernel-debug-devel | before 6.12.0-211.63.1.el10_2 | 6.12.0-211.63.1.el10_2 |
| AlmaLinux:10 | kernel-debug-devel-matched | before 6.12.0-211.63.1.el10_2 | 6.12.0-211.63.1.el10_2 |
| AlmaLinux:10 | kernel-debug-modules | before 6.12.0-211.63.1.el10_2 | 6.12.0-211.63.1.el10_2 |
| AlmaLinux:10 | kernel-debug-modules-core | before 6.12.0-211.63.1.el10_2 | 6.12.0-211.63.1.el10_2 |
+96
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-63916Jul 19, 2026 · HID: wacom: Fix OOB write in wacom_hid_set_device_mode()35Monitor
- ← EarlierCVE-2026-63917Jul 19, 2026 · ip6: vti: Use ip6_tnl.net in vti6_changelink().35Monitor
- Later →CVE-2026-63919Jul 19, 2026 · xfrm: input: hold netns during deferred transport reinjection35Monitor
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 | 05f95729ca844704d15e49ce14868af4b403b32b | Vendor (CNA) |
| Linux Linux | 782d60a6596aee9b29c2eecfa70033899278bf65 | Vendor (CNA) |
| Linux Linux | 947013fd7c8c35dd5856557b215840098a3f67f8 | Vendor (CNA) |
| Linux Linux | ee80455feffb9cb62b5b58715cabeff495e666b2 | Vendor (CNA) |
| almalinux:kernel | 6.12.0-211.63.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k | 6.12.0-211.63.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-core | 6.12.0-211.63.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug | 6.12.0-211.63.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug-core | 6.12.0-211.63.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug-devel | 6.12.0-211.63.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug-devel-matched | 6.12.0-211.63.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules | 6.12.0-211.63.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules-core | 6.12.0-211.63.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules-extra | 6.12.0-211.63.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-devel | 6.12.0-211.63.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-devel-matched | 6.12.0-211.63.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| debian:linux | 6.12.94-1 · Debian:13 | Package registry (OSV) |
| red hat:kernel-64k-debug-debuginfo | 0:6.12.0-211.63.1.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:kernel-64k-debug-devel | 0:6.12.0-211.63.1.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:kernel-64k-debug-devel-matched | 0:6.12.0-211.63.1.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:kernel-64k-debuginfo | 0:6.12.0-211.63.1.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:kernel-64k-devel | 0:6.12.0-211.63.1.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:kernel-64k-devel-matched | 0:6.12.0-211.63.1.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:kernel-debug-debuginfo | 0:6.12.0-211.63.1.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:kernel-debug-devel | 0:6.12.0-211.63.1.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:kernel-debug-devel-matched | 0:6.12.0-211.63.1.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:kernel-debuginfo | 0:6.12.0-211.63.1.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:kernel-debuginfo-common-aarch64 | 0:6.12.0-211.63.1.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:kernel-modules-internal | 0:6.12.0-211.63.1.el10_2 · Red Hat:shadow_migration_toolkit:10::el10 | 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.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Not on record for this CVE: patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
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
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-416 · Use After FreeCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-secondary
Root cause
After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.
The bug in code
The whole CWE-416 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
free(dev->buf);
/* ... another thread is still running ... */
process(dev->buf);Fixed
lock(&dev->lock);
free(dev->buf);
dev->buf = NULL;
unlock(&dev->lock);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 (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (3 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.