Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

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… (CVE-2026-63918)

0
Medium
Published: 07/19/2026 (07/19/2026, 18:31:46 UTC)
Source: GCVE Database

Description

A use-after-free vulnerability in the Linux kernel's L2TP subsystem was resolved by changing the reference counting method in the l2tp_session_get_by_ifname() function. The issue arises because this function used a plain refcount increment that could succeed on a zero refcount, leading to a stale pointer being returned. This inconsistency was fixed by using refcount_inc_not_zero(), matching other session getters and preventing use-after-free conditions.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 07/19/2026, 20:07:33 UTC

Technical Analysis

The vulnerability in the Linux kernel's L2TP code involves the l2tp_session_get_by_ifname() function returning a pointer to a session whose reference count has dropped to zero. The function used refcount_inc() which does not prevent incrementing a zero refcount, potentially causing a use-after-free when the session memory is freed after the RCU grace period. Other session getters use refcount_inc_not_zero() to avoid this race condition. The fix replaces refcount_inc() with refcount_inc_not_zero() in the ifname getter, restoring consistency and preventing the use-after-free scenario.

Potential Impact

If exploited, this vulnerability could lead to a use-after-free condition in the kernel, potentially causing kernel crashes or memory corruption. However, the session memory is held live during the RCU read section, and the actual free happens after the grace period, which may limit exploitation. No known exploits are reported in the wild.

Mitigation Recommendations

Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. The fix involves changing the reference counting method in the kernel source code. Until an official patch is available, users should monitor vendor advisories for updates. No other specific mitigations are indicated.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Gcve Source
db.gcve.eu
Osv Id
GHSA-9qwr-gw6x-fmgj
Osv Schema Version
1.4.0
Aliases
["CVE-2026-63918"]
Ecosystems
[]
Database Specific Severity
null
Cvss Version
null

Threat ID: 6a5d27ab2a4a8d598912f246

Added to database: 07/19/2026, 19:38:19 UTC

Last enriched: 07/19/2026, 20:07:33 UTC

Last updated: 07/20/2026, 13:17:22 UTC

Views: 12

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses