[CVE-2026-68323][MODERATE 7.0] tipc: serialize udp bearer replicast list updates [ Upstream

[AL-KERNEL <alkernel@kernelcve.org>]

CVE: CVE-2026-68323
Priority: MODERATE 7.0
AL-KERNEL base severity: MODERATE
KPANIC flag: YES
Patch: tipc: serialize udp bearer replicast list updates [ Upstream
Commit: d70c81001df9320d3445e664428a1d408b5ba896
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=d70c81001df9320d3445e664428a1d408b5ba896
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-68323
Analysis date: Mon, 10 Aug 2026 20:25:28 -0400
ActionableScore: 5
ActionableScore lower bound: 4
Actionable bucket: Strong Important candidate / Actionable Moderate at minimum**:: Actionable Moderate at minimum. Strong Important candidate only if manual review confirms controllable UAF reuse or stronger corruption.
Manual review required: YES

Summary:
A race in the TIPC UDP replicast path allows concurrent softirq list_add_rcu() and workqueue list_del_rcu() operations on the bearer peer list, causing kernel list corruption and a reliable kernel BUG, with practical triggering possible from an unprivileged user namespace.

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

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

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-68323	MODERATE	CHECK WITH IMPACT FROM ORIG NN IMPORTANT	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-362;CWE-667;*CWE-416;Other CVSS 'AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H';BEST CVSS score: '7';DESCR 'A race in the TIPC UDP replicast path can corrupt the bearer replicast peer list because tipc_udp_rcast_add() can run from the UDP encapsulation receive softirq while cleanup_bearer() deletes the same list from a workqueue. The two writers were not serialized, so concurrent list_add_rcu() and list_del_rcu() operations can produce list corruption, kernel BUG, and potentially stale RCU list state during bearer teardown. For the CVSS the PR:L value is used for the paranoid score because the bearer can be enabled from an unprivileged user namespace and TIPv2 generic netlink operations lack GENL_ADMIN_PERM, so reliable triggering does not require full host administrator privileges. The issue is mainly local or namespace reachable, although UDP packets can participate once a TIPC UDP bearer exists. Impact is at least denial of service via kernel crash and should be reviewed manually because the bug class is a race with kernel list corruption and possible use-after-free style behavior.';YES REQUIRES MANUAL CHECK; ,and ActionableScore result is Strong Important candidate / Actionable Moderate at minimum (with actual score 5)	YES	REMOTE OOB LOCK INIT TIPC RACE LEAK NETWORK LINUS IPV6 KPANIC  KPANIC DECREASED_TO_MODERATE70_BASED_ON_ACTIONABLESCORELOWERTHAN7	NO	NO	checked

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

ActionableScore=5
ActionableScoreLower=4

## 1. ActionableScore

* Conservative score: 4
* Paranoid score: 5
* Final recommended bucket: **Strong Important candidate / Actionable Moderate at minimum**:: Actionable Moderate at minimum. Strong Important candidate only if manual review confirms controllable UAF reuse or stronger corruption.

## 2. Signal breakdown

Triggered signals:

* Local unprivileged trigger: +1
  The commit states that the TIPC bearer can be enabled from an unprivileged user namespace because TIPv2 generic netlink ops lack GENL_ADMIN_PERM.

* Memory corruption, weak or indirect corruption candidate: +1
  The bug corrupts a kernel linked list through unsynchronized list_add_rcu() and list_del_rcu(). This is real corruption, but the patch does not show controlled overwrite, controlled reclaim, callback control, or arbitrary write.

* Real lifetime corruption: +1
  The race involves RCU list deletion and teardown. The commit also describes an entry being added after cleanup_bearer() emptied the list, creating stale lifetime behavior when the bearer is freed.

* Reliable kernel crash / strong DoS: +1
  The commit includes a concrete list_del corruption report followed by kernel BUG at lib/list_debug.c.

Paranoid-only additional signal:

* Availability impact realistic: +1
  The crash is a host kernel BUG in a network subsystem path and can plausibly be triggered repeatedly once the local namespace and bearer setup are available.

Not awarded:

* Remote reachable / network-triggerable: +0
  UDP packets can participate after a TIPC UDP bearer exists, but reliable triggering requires local or namespace-level setup. This is not a plain AV:N remote service bug.

* Privilege escalation plausible: +0
  There is possible UAF-style concern, but no demonstrated attacker-controlled reclaim, object replacement, write-after-free, callback dispatch, or refcount takeover.

* Strong generic memory corruption: +0
  The primitive is list corruption and stale RCU/lifetime state, not a shown arbitrary write or controlled UAF reuse primitive.

* Hard race penalty: 0
  This is a race, but it is between realistic softirq receive and workqueue cleanup paths and has an observed BUG trace. I would not subtract unless later testing shows it is extremely unreliable.

## 3. Reachability analysis

The main trigger requires local ability to create or manipulate a TIPC UDP bearer. The important reachability detail is that this can be done from an unprivileged user namespace according to the commit message, because the relevant TIPv2 generic netlink operations do not require GENL_ADMIN_PERM. That makes PR effectively low in practical triage terms, not full host root.

The issue is not purely remote. Network traffic can participate through the UDP encapsulation receive path once the bearer exists, but the attacker needs local namespace or control-plane setup to create the vulnerable state. TIPC is not as broadly exposed as TCP/IP or netfilter packet processing, but this should not be auto-closed because the affected path combines namespace reachability, kernel list corruption, RCU lifetime behavior, and a demonstrated kernel BUG.

## 4. Severity interpretation

This is stronger than an ordinary Moderate DoS because it is not just a WARN or validation failure. The patch fixes unsynchronized mutation of an RCU-protected kernel list and a teardown window where new entries could be added after cleanup.

Realistically demonstrated impact is kernel crash / DoS. Theoretical memory corruption impact exists because kernel list corruption and RCU lifetime mistakes can sometimes become exploitable, but the patch does not show a controlled reuse or arbitrary write primitive. Therefore the conservative result is borderline manual review, while the paranoid result is Actionable Moderate.

## 5. One-sentence report phrase

A race in the TIPC UDP replicast path allows concurrent softirq list_add_rcu() and workqueue list_del_rcu() operations on the bearer peer list, causing kernel list corruption and a reliable kernel BUG, with practical triggering possible from an unprivileged user namespace.

## 6. Manual review recommendation

MANUAL CHECK REQUIRED

Reason: the bug has observed kernel list corruption, RCU/lifetime teardown behavior, and unprivileged user namespace reachability. The current evidence supports DoS, but the corruption class is serious enough that it should not be auto-closed without human review for possible UAF reuse or stronger exploitation primitives.

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

Patch: tipc: serialize udp bearer replicast list updates [ Upstream
Commit: d70c81001df9320d3445e664428a1d408b5ba896
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=d70c81001df9320d3445e664428a1d408b5ba896

Changed files:
  lib/list_debug.c
  net/tipc/udp_media.c
  kernel/workqueue.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=d70c81001df9320d3445e664428a1d408b5ba896

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

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

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:N/I:N/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).