[CVE-2026-43116][MODERATE 7.0] netfilter: ctnetlink: ensure safe access to master conntrack [ Upstream

[CVE-2026-43116][MODERATE 7.0] netfilter: ctnetlink: ensure safe access to master conntrack [ Upstream

[AL-KERNEL]

CVE: CVE-2026-43116
Priority: MODERATE 7.0
AL-KERNEL base severity: MODERATE
KPANIC flag: YES
Patch: netfilter: ctnetlink: ensure safe access to master conntrack [ Upstream
Commit: f338ced0473849c9f6ed0b77ca99f1aab5826787
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=f338ced0473849c9f6ed0b77ca99f1aab5826787
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-43116
Analysis date: Mon, 06 Jul 2026 14:27:18 -0400
ActionableScore: 5
ActionableScore lower bound: 4
Actionable bucket: Actionable Moderate at minimum
Manual review required: YES

Summary:
A race in netfilter ctnetlink expectation handling can leave exp master pointing to a freed master conntrack object, creating a local CAP_NET_ADMIN reachable UAF candidate that can cause kernel DoS and requires manual review for possible higher impact.

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

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

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-43116	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-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 race in netfilter ctnetlink expectation handling can allow exp master to be accessed after the master conntrack object has been removed. Holding a reference to the expectation object is not sufficient because the referenced master conntrack can disappear in parallel during cleanup, leaving a stale pointer and a possible use-after-free condition. For the CVSS the PR:L is used because practical triggering requires a local process with access to conntrack netlink operations such as expectation get delete or related control plane actions, but this does not necessarily require full host root in all container or delegated network administration deployments. The issue is not directly network reachable through packet traffic alone, although network activity may influence conntrack lifetime and race timing. Impact is at least local denial of service via kernel crash and in the paranoid case may allow confidentiality or integrity impact due to kernel use-after-free memory corruption. YES REQUIRES MANUAL CHECK';YES REQUIRES MANUAL CHECK; ,and ActionableScore result is Actionable Moderate at minimum (with actual score 5)	YES	REMOTE OOB LOCK NOMEMCHK NETFILTER SKB KPANIC  KPANIC DECREASED_TO_MODERATE70_BASED_ON_ACTIONABLESCORELOWERTHAN7	NO	NO	guess

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

ActionableScore=5
ActionableScoreLower=4

## 1. ActionableScore

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

## 2. Signal breakdown

Triggered signals:

* Local unprivileged or reduced-privilege trigger: +1
  ctnetlink expectation operations normally require CAP_NET_ADMIN, but this may be reachable from reduced-privilege contexts such as container root or user namespace plus network namespace setups where CAP_NET_ADMIN is delegated.

* Memory corruption, weak or indirect corruption candidate: +1
  The patch explicitly states that exp->master can become invalid after the master conntrack object goes away. This is a stale pointer / UAF candidate, but the patch does not show attacker-controlled reclaim, overwrite, callback hijack, or type confusion.

* Real lifetime corruption: +1
  The bug is a real lifetime issue involving expectation objects and master conntrack teardown. Holding a reference on the expectation does not protect the lifetime of exp->master.

* Reliable kernel crash / strong DoS: +1
  Dereferencing an invalid master conntrack pointer can plausibly crash the kernel or trigger serious kernel faults in conntrack expectation handling.

* Broad/default/common subsystem exposure: +1 in paranoid score
  Netfilter and conntrack are commonly deployed kernel networking components. The affected path is ctnetlink control plane rather than ordinary packet receive path, so this is counted only in the paranoid score.

Subtracted or not awarded:

* Hard or unreliable race / special timing required: -1 in conservative score
  The issue depends on racing expectation lookup/event handling with master conntrack teardown.

* Requires CAP_NET_ADMIN in typical deployments: not applied as full -2
  Full host-root is not necessarily required in all practical deployments because CAP_NET_ADMIN may be delegated into containers or network namespaces. This makes PR:L more appropriate than PR:H for practical triage.

* Strong LPE plausibility: not awarded
  The patch supports UAF concern, but does not show controlled reclaim, object replacement, arbitrary write, callback control, or refcount takeover.

* Confidentiality and integrity impact: not awarded in conservative score
  The realistic demonstrated impact is UAF/DoS. C/I are only a paranoid concern, not a demonstrated primitive.

## 3. Reachability analysis

The primary trigger is local ctnetlink control-plane access to conntrack expectation get/delete/event paths. It is not directly reachable from remote packet traffic alone, although network traffic and conntrack lifetime changes may influence the race timing.

In typical host deployments, modifying conntrack expectations requires CAP_NET_ADMIN. However, in containerized or namespace-enabled environments, a reduced-privilege actor may obtain CAP_NET_ADMIN in a network namespace without being full host root. That makes the practical privilege boundary weaker than ordinary PR:H.

The path is not a public Internet remote parser, but it belongs to a common networking subsystem. Realistic exploitation requires arranging expectation objects, master conntrack teardown, and the race window, so exploitation complexity is high.

Call-site confidence: high. The patch directly shows affected get/delete expectation paths, event reporting, and lock coverage around exp->master access.

## 4. Severity interpretation

This behaves more like an actionable Moderate kernel lifetime bug than an ordinary low-risk DoS. The conservative interpretation is a race-dependent UAF leading mainly to kernel crash, with no demonstrated reliable privilege escalation primitive.

The paranoid interpretation is still defensible at ActionableScore 5 because the stale pointer is in netfilter conntrack lifetime management, and UAF bugs in kernel networking control paths historically deserve manual review even when exploitability is not proven. It should not be promoted to a strong Important candidate without evidence of controlled reclaim, write-after-free, callback dispatch, type confusion, or refcount takeover.

## 5. One-sentence report phrase

A race in netfilter ctnetlink expectation handling can leave exp master pointing to a freed master conntrack object, creating a local CAP_NET_ADMIN reachable UAF candidate that can cause kernel DoS and requires manual review for possible higher impact.

## 6. Manual review recommendation

MANUAL CHECK REQUIRED

Reason: the patch explicitly fixes unsafe lifetime access to exp->master after master conntrack teardown. This is a real race-dependent UAF candidate in a common kernel networking subsystem, even though the currently supported impact is mainly DoS and reliable LPE is not demonstrated.

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

Patch: netfilter: ctnetlink: ensure safe access to master conntrack [ Upstream
Commit: f338ced0473849c9f6ed0b77ca99f1aab5826787
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=f338ced0473849c9f6ed0b77ca99f1aab5826787

Changed files:
  include/net/netfilter/nf_conntrack_core.h
  net/netfilter/nf_conntrack_ecache.c
  net/netfilter/nf_conntrack_expect.c
  net/netfilter/nf_conntrack_netlink.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=f338ced0473849c9f6ed0b77ca99f1aab5826787

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

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

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).