[CVE-2026-72435][MODERATE REGULAR] netfilter: ipset: fix order of kfree_rcu() and rcu_assign_pointer() [ Upstream

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

CVE: CVE-2026-72435
Priority: MODERATE REGULAR
AL-KERNEL base severity: MODERATE
KPANIC flag: NO
Patch: netfilter: ipset: fix order of kfree_rcu() and rcu_assign_pointer() [ Upstream
Commit: c9787d7c24ffd83019f379455e1b97fb4f0f75eb
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=c9787d7c24ffd83019f379455e1b97fb4f0f75eb
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-72435
Analysis date: Sat, 15 Aug 2026 22:55:07 -0400
ActionableScore: 4
ActionableScore lower bound: 2
Actionable bucket: Borderline, manual review recommended. Not an Important candidate from patch evidence alone
Manual review required: YES

Summary:
An RCU lifetime ordering bug in netfilter ipset comment handling can leave a stale comment pointer visible after `kfree_rcu()`, creating a race-dependent UAF candidate that is most likely a local DoS but should receive manual review due to possible stale-object reuse.

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

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

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 REGULAR
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-72435	MODERATE	CHECK WITH IMPACT FROM ORIG NN MODERATE	Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:H';*CWE-416;CWE-362;*CWE-664;Other CVSS 'AV:L/AC:H/PR:H/UI:N/S:U/C:L/I:N/A:H';BEST CVSS score: '5.8';DESCR 'The ipset comment extension cleared an RCU protected comment pointer only after calling kfree_rcu on the old object. This creates a race window where an RCU reader can still observe the stale comment pointer after the object has already been queued for RCU freeing, which can lead to a use after free during later comment access. For the CVSS the PR:L is used in the paranoid score because CAP_NET_ADMIN or equivalent ipset control may be delegated to a less privileged container root or service account in some deployments. The issue is not directly network reachable and is triggered through local netfilter ipset control plane operations rather than packet traffic. Impact is at least local denial of service via kernel crash and in worst case may allow limited confidentiality or integrity impact due to stale RCU pointer reuse, so this should be reviewed manually.';YES REQUIRES MANUAL CHECK; ,and ActionableScore result is Borderline, manual review recommended. Not an Important candidate from patch evidence alone (with actual score 3)	YES	REMOTE SIMPLEFIX NETFILTER  DECREASED_TO_MODERATEREG_BASED_ON_ACTIONABLESCORELESSTHAN5	NO	NO	checked

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

ActionableScore=4
ActionableScoreLower=2

## 1. ActionableScore

* Conservative score: **2**
* Paranoid score: **4**
* Final recommended bucket: **Borderline, manual review recommended. Not an Important candidate from patch evidence alone**::

## 2. Signal breakdown

Conservative signals:

* Real lifetime corruption: **+1**. The ordering bug involves `kfree_rcu()` before clearing the published RCU pointer, creating a stale-pointer lifetime window.
* Memory corruption, weak or indirect corruption candidate: **+1**. This is an RCU UAF candidate, but the patch does not show attacker-controlled reclaim, writable stale access, callback dispatch, type confusion, or refcount takeover.
* Reliable kernel crash / strong DoS: **+1**. A stale comment pointer can plausibly crash the kernel if later dereferenced by an RCU reader.
* Hard or unreliable race / special timing required: **-1**. Exploitation depends on a narrow RCU ordering/race window.
* Requires CAP_NET_ADMIN in typical deployments: **-2**. Managing ipset comments normally requires netfilter control-plane privileges.

Conservative total: **2**

Paranoid additional interpretation:

* Broad/common subsystem exposure: **+1**. Netfilter/ipset is a common kernel firewall subsystem, even though this is a control-plane path and not packet processing.
* Reduced-privilege CAP_NET_ADMIN environments reduce the privilege penalty: **+1 effective uplift**. In containers or delegated network namespaces, CAP_NET_ADMIN may be available to a less trusted actor, so the full admin penalty may overstate required privilege.

Paranoid total: **4**

Not awarded:

* Remote reachable / network-triggerable: **+0**. This is not triggered by packet traffic directly.
* Strong LPE plausibility: **+0**. No demonstrated reclaim, object replacement, write primitive, callback control, or type confusion.
* Confidentiality / integrity impact: **+0 conservative**. Paranoid concern exists, but the race-UAF downgrade rule prevents treating this as proven C/I impact.
* Common networking packet path: **+0**. The affected path is ipset control-plane comment handling, not the packet-processing fast path.

## 3. Reachability analysis

The bug is reachable through local netfilter ipset management operations involving the comment extension. In typical host deployments this requires `CAP_NET_ADMIN`, so the conservative privilege model treats it as privileged local access. In containerized or delegated network namespace setups, a container root or service account may have enough netfilter capability without being full host root, which justifies the higher paranoid score.

The path is not directly network reachable. Incoming packets do not by themselves trigger the vulnerable ordering. Realistic exploitation would require the ability to modify or free ipset comment state while an RCU reader can still observe the old pointer.

Call-site confidence: **medium**. The patch shows the lifetime ordering bug directly, but not the reader call sites or a concrete crash trace.

## 4. Severity interpretation

This behaves like a **borderline actionable Moderate** rather than a clear Important issue. The technical class is meaningful because RCU stale-pointer bugs can become UAFs, and UAF-class issues should not be auto-closed without review. However, the patch only shows an ordering fix around `kfree_rcu()` and `rcu_assign_pointer()`, with no demonstrated attacker-controlled reclaim, write-after-free, type confusion, or privilege escalation primitive.

The realistic impact is most likely local DoS through a kernel crash. Theoretical memory corruption potential exists because stale RCU pointer reuse is possible, but the evidence does not support treating it as a strong LPE candidate.

## 5. One-sentence report phrase

An RCU lifetime ordering bug in netfilter ipset comment handling can leave a stale comment pointer visible after `kfree_rcu()`, creating a race-dependent UAF candidate that is most likely a local DoS but should receive manual review due to possible stale-object reuse.

## 6. Manual review recommendation

**MANUAL CHECK REQUIRED**

Reason: this is an RCU lifetime/UAF candidate in netfilter control-plane code. Even though the currently supported impact is mainly DoS and the score is not Important-class, UAF-class lifetime bugs should not be auto-closed without checking reader paths and possible object reuse.

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

Patch: netfilter: ipset: fix order of kfree_rcu() and rcu_assign_pointer() [ Upstream
Commit: c9787d7c24ffd83019f379455e1b97fb4f0f75eb
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=c9787d7c24ffd83019f379455e1b97fb4f0f75eb

Changed files:
  net/netfilter/ipset/ip_set_core.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=c9787d7c24ffd83019f379455e1b97fb4f0f75eb

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

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

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:H/UI:N/S:U/C:L/I:N/A:H
  The Best / paranoid CVSS vector: AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:H
  The Best / paranoid CVSS score: 5.8

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: 2
  Paranoid ActionableScore: 4

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: NO
Published priority for this report (same as in Subject): MODERATE REGULAR

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