[CVE-2026-68398][MODERATE 7.0] ppp: defer channel free to an RCU grace period to fix pppol2tp RX UAF [ Upstream

[CVE-2026-68398][MODERATE 7.0] ppp: defer channel free to an RCU grace period to fix pppol2tp RX UAF [ Upstream

[AL-KERNEL]

CVE: CVE-2026-68398
Priority: MODERATE 7.0
AL-KERNEL base severity: MODERATE
KPANIC flag: YES
Patch: ppp: defer channel free to an RCU grace period to fix pppol2tp RX UAF [ Upstream
Commit: 4bb84e964ff0fe0a171c965362de72f9820dbce9
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=4bb84e964ff0fe0a171c965362de72f9820dbce9
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-68398
Analysis date: Mon, 10 Aug 2026 12:15:55 -0400
ActionableScore: 5
ActionableScore lower bound: 4
Actionable bucket: Actionable Moderate at minimum
Manual review required: YES

Summary:
A local unprivileged user can race PPPoL2TP receive processing with channel teardown, causing `ppp_input()` to dereference a freed `struct channel`, resulting in a kernel UAF with realistic DoS impact and possible privilege-escalation concern requiring manual review.

======================================================================
ABOUT THIS REPORT
======================================================================

The original Linux kernel CVE announcement for CVE-2026-68398 is available here:
https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-68398

The original announcement does not normally provide a security severity
estimate, CVSS assessment, or enough information to determine whether the
reported kernel bug represents a practically relevant security issue.

This report was generated by AL-KERNEL, an AI-assisted Linux kernel
vulnerability analysis system developed by Alexander Larkin. It combines
an autonomous classifier with LLM-assisted technical analysis and a
separate ActionableScore mechanism.

The purpose of this report is to prioritize Linux kernel CVEs before
manual review, identify cases that require prompt investigation, and
support automatic closure of issues that are unlikely to have meaningful
security impact.

Published priority for this report: MODERATE 7.0
Manual review required: YES

A detailed explanation of the methodology and priority rules is included
at the end of this message.

======================================================================
AL-KERNEL CLASSIFICATION RESULT
======================================================================

CVE-2026-68398	MODERATE	CHECK WITH IMPACT FROM ORIG NN LOW	Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H';*CWE-416;CWE-362;CWE-667;Other CVSS 'AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:H';BEST CVSS score: '7';DESCR 'A use-after-free can occur in the PPPoL2TP receive path because pppol2tp_recv runs under rcu_read_lock and calls ppp_input while holding only an L2TP session reference, but the internal struct channel can be freed by ppp_release_channel with plain kfree on another CPU. A local unprivileged user can race packet receive processing with PPPoL2TP socket teardown for a bound but not attached and not bridged channel, leaving an in flight ppp_input to dereference freed channel memory. For the CVSS the PR:L is selected because reliable triggering requires a local user or process that can create and tear down the PPPoL2TP channel state. The issue is not pure AV:N because network packets drive the RX path, but local lifecycle control is needed for the free side of the race. Impact is at least a local denial of service via kernel crash, and in the worst case may allow privilege escalation due to kernel use-after-free memory corruption.';YES REQUIRES MANUAL CHECK; ,and ActionableScore result is Actionable Moderate at minimum (with actual score 5)	YES	INIT UAF NETWORK SKB HARDWARE KPANIC 	NO	NO	checked

======================================================================
ACTIONABLESCORE ANALYSIS
======================================================================

ActionableScore=5
ActionableScoreLower=4

## 1. ActionableScore

* Conservative score: 4
* Paranoid score: 5
* Final recommended bucket: **Actionable Moderate at minimum**

## 2. Signal breakdown

* Local unprivileged trigger: +1
  The commit explicitly states that the bug is reachable by an unprivileged user.

* Memory corruption, weak race-UAF primitive: +1
  This is a real use-after-free of `struct channel`, but it is race dependent and the patch does not demonstrate attacker-controlled reclaim, object replacement, type confusion, callback control, or arbitrary write.

* Real lifetime corruption: +1
  `ppp_release_channel()` could free `struct channel` with plain `kfree()` while `pppol2tp_recv()` still accesses it under RCU.

* Reliable kernel crash / strong DoS: +1
  An in-flight `ppp_input()` may dereference a freed channel, making kernel crash a realistic outcome.

* Weak LPE concern in paranoid score only: +1
  The patch comment says a late `ppp_input()` may still queue an skb on `pch->file.rq`, which implies possible stale writable object access. This is not enough for strong LPE, but it is enough to avoid auto-close.

* Hard race penalty: 0
  Although this is a race, the attacker can plausibly control both the PPPoL2TP lifecycle and receive-side activity, so I would not subtract by default.

## 3. Reachability analysis

The bug is locally reachable by an unprivileged user according to the commit message. The RX side is packet-driven through the L2TP UDP encapsulation path, but the free side requires local lifecycle control over the PPPoL2TP channel, so this should not be scored as purely remote/network-triggerable. Namespaces may affect practical reachability depending on PPP, L2TP, and socket permissions in the target product, but the provided patch text supports PR:L rather than PR:H. PPPoL2TP is not a universal default workload, but it is a normal kernel networking feature and should not be treated as rare hardware-only or legacy-only.

Call-site confidence: high. The commit provides the relevant call path and the patch directly changes the channel lifetime from plain `kfree()` to `call_rcu()`.

## 4. Severity interpretation

This is stronger than an ordinary Moderate because it is an unprivileged local kernel UAF in a receive path. Conservatively it behaves as a local DoS with weak memory-corruption potential because no reclaim or controlled replacement primitive is shown. Paranoid handling should keep it as Actionable Moderate at minimum because the stale object can be accessed after free and may receive queue operations before the RCU reader drains. It is not a clear Strong Important candidate without additional evidence of controlled reuse or exploitability, but it should not be auto-closed.

## 5. One-sentence report phrase

A local unprivileged user can race PPPoL2TP receive processing with channel teardown, causing `ppp_input()` to dereference a freed `struct channel`, resulting in a kernel UAF with realistic DoS impact and possible privilege-escalation concern requiring manual review.

## 6. Manual review recommendation

MANUAL CHECK REQUIRED

Reason: unprivileged local UAF plus possible stale writable queue access in a networking RX path. The conservative score is borderline, but the paranoid score reaches Actionable Moderate and should be reviewed manually.

======================================================================
UPSTREAM PATCH SUMMARY
======================================================================

Patch: ppp: defer channel free to an RCU grace period to fix pppol2tp RX UAF [ Upstream
Commit: 4bb84e964ff0fe0a171c965362de72f9820dbce9
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=4bb84e964ff0fe0a171c965362de72f9820dbce9

Changed files:
  drivers/net/ppp/ppp_generic.c

Diff excerpt:

Not included in this email. See the upstream URL for the full patch.

Full patch:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=4bb84e964ff0fe0a171c965362de72f9820dbce9

======================================================================
DETAILED REPORT METHODOLOGY
======================================================================

The original Linux kernel CVE announcement for CVE-2026-68398 can be found here:
https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-68398

The original CVE announcement normally does not include a security-level
estimate. In particular, it may not contain a CVSS assessment, an impact
level, or enough information to determine whether the reported bug is a
practically relevant security issue. One purpose of this parallel CVE list
is to provide that missing technical and prioritization information.

The original goal of the AL-KERNEL project was to prioritize Linux kernel
CVE analysis automatically before manual review. The system can also help
identify non-security issues that may be suitable for automatic closure.

This report was generated by AL-KERNEL, an AI-assisted Linux kernel
vulnerability analysis system developed by Alexander Larkin.

The first analysis stage combines an autonomous classifier with additional
LLM-based analysis. The autonomous classifier runs locally on a CPU and is
based on a backpropagation neural network. Together, these mechanisms
produce a technical vulnerability description, identify likely weakness
types, estimate CVSS severity, and provide input for ActionableScore.

Two CVSS estimates are retained because incomplete kernel vulnerability
information often permits more than one defensible interpretation:

  Conservative CVSS vector: AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:H
  The Best / paranoid CVSS vector: AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
  The Best / paranoid CVSS score: 7

The conservative vector represents a lower-impact interpretation.
The Best/paranoid vector intentionally represents a plausible upper-bound
interpretation and should not automatically be treated as demonstrated
real-world impact.

CVSS may also need to be adjusted for a particular Linux deployment,
because actual reachability, privileges, enabled kernel configuration,
hardware, namespaces, exposed device nodes, and other environmental
conditions can differ significantly between systems.

A separate ActionableScore mechanism evaluates practical remediation
urgency. Its analysis may include reachability, attack prerequisites,
subsystem exposure, memory-corruption characteristics, denial-of-service
reliability, and possible confidentiality, integrity, or
privilege-escalation impact.

  Conservative ActionableScore: 4
  Paranoid ActionableScore: 5

The final base severity is taken directly from the second tab-separated
field of the AL-KERNEL classification result. ActionableScore does not
replace or independently override that final AL-KERNEL decision, and
if ActionableScore adjusted impact level of ALKERNEL, then you would see
self-readable flags above like INCREASED_TO_HIGH_BASED_ON_ACTIONABLESCOREHIGHEREQTHAN7.

For an AL-KERNEL result of MODERATE, this report uses the following
additional presentation split:

  ActionableScore below 5   -> MODERATE REGULAR
  ActionableScore 5 or more -> MODERATE 7.0

The distinction between MODERATE REGULAR and MODERATE 7.0 makes it
possible to identify Moderate issues that should receive manual analysis
and fixes before lower-priority MODERATE REGULAR issues. In many cases,
MODERATE REGULAR fixes may wait for a later rebase or routine update.

There is one override in which MODERATE REGULAR becomes MODERATE 7.0
even when the ActionableScore is below 5. When the AL-KERNEL result
contains the KPANIC flag, a MODERATE result is always presented as
MODERATE 7.0. The KPANIC flag selected with few regexps without
usage of AI at all, so it helps to detect cases when Kernel Crash happens
and similar (to filter False-Negative results from the LLM usage).

KPANIC indicates that a reliable kernel crash, kernel panic, or similarly
serious kernel availability impact was identified by the classification
workflow.

AL-KERNEL base severity for this report: MODERATE
KPANIC detected for this report: YES
Published priority for this report (same as in Subject): MODERATE 7.0

These results are intended to support engineering triage. They are
machine-generated estimates, and cases marked for manual review should
be validated by a human security engineer before final disposition.
For more info read docs linked from here: https://kernelcve.org/
(and you can submit you own patch there to generate such a report
for non-existant CVE-id yet).

Note that in many cases this AI tool selects higher severity, than
real is (means you can expect Importants instead of Moderate 7.0 or
Moderates 7.0 instead of regular Moderates). If you see such cases,
please use reply email interface to add additional manual analyses
info to this particular CVE.
And please, please, let me know when you see Lows instead of Importants
or Important instead of Low (because particular for such cases I
need to tune this AI tool to make it better for this one and next similar).
My contact email for such notifications is alexanjelausa@gmail.com (and both
send reply to CVE record itself too and see "reply" button below for howto reply).