[CVE-2026-72493][MODERATE 7.0] net: serialize netif_running() check in enqueue_to_backlog() [ Upstream

[CVE-2026-72493][MODERATE 7.0] net: serialize netif_running() check in enqueue_to_backlog() [ Upstream

[AL-KERNEL]

CVE: CVE-2026-72493
Priority: MODERATE 7.0
AL-KERNEL base severity: MODERATE
KPANIC flag: NO
Patch: net: serialize netif_running() check in enqueue_to_backlog() [ Upstream
Commit: 2fface6e0bbd6314d1d9d071abf2c4d67548511c
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=2fface6e0bbd6314d1d9d071abf2c4d67548511c
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-72493
Analysis date: Sun, 16 Aug 2026 04:14:48 -0400
ActionableScore: 5
ActionableScore lower bound: 4
Actionable bucket: Actionable Moderate at minimum
Manual review required: YES

Summary:
A TOCTOU race in `enqueue_to_backlog()` can allow packets to escape backlog flushing during device unregister or netns exit, leading to a stale device-state use-after-free in core networking and a likely local kernel crash.

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

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

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-72493	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:H/I:H/A:H';*CWE-416;CWE-362;CWE-367;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 condition in enqueue_to_backlog can allow a packet to pass a lockless netif_running check before device close, then be queued after flush_all_backlogs has already finished during device unregistration or netns exit. This lets the packet escape backlog flushing and later reach code such as fib_rules_lookup with stale device related state, producing a KASAN slab use after free and a possible kernel crash. For the CVSS the PR:L is selected because reliable triggering requires local code execution with the ability to manipulate network namespaces or virtual network devices, commonly via CAP_NET_ADMIN inside a namespace. The issue is not directly network reachable from outside the host. Impact is at least local denial of service via kernel crash and in the paranoid case may allow confidentiality or integrity impact due to the UAF class, so it should be reviewed manually.';YES REQUIRES MANUAL CHECK; ,and ActionableScore result is Actionable Moderate at minimum (with actual score 5)	YES	REMOTE DANGER RACE UAF SKB HARDWARE SYZBOT PACKET  DECREASED_TO_MODERATEREG_BASED_ON_FALSEPOSCHECKOFKP	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

Conservative signals:

* **Memory corruption, weak primitive: +1**. The commit explicitly reports KASAN slab-use-after-free, but this is a race-dependent UAF without evidence of attacker-controlled reclaim, stale object replacement, write-after-free, callback control, or refcount takeover.
* **Real lifetime corruption: +1**. A packet can survive device unregister and backlog flushing, then later be processed with stale device-related state.
* **Reliable kernel crash / strong DoS: +1**. The observed failure is a KASAN UAF in `fib_rules_lookup()` and likely kernel crash or panic in affected configurations.
* **Broad/default/common subsystem: +1**. This is core networking code in `net/core/dev.c`.
* **Common networking core path or packet-processing path: +1**. `enqueue_to_backlog()` is part of the packet receive backlog path.
* **Hard or unreliable race / special timing required: -1**. The bug depends on a TOCTOU window between `netif_running()`, device close, backlog flushing, and later queueing.

Paranoid additional signal:

* **Local unprivileged trigger in some deployments: +1**. If unprivileged user namespaces are enabled, a local user may be able to create a network namespace and obtain namespace-scoped `CAP_NET_ADMIN` to manipulate virtual devices such as veth. This is deployment-dependent, so it is used only for the paranoid score.

Not awarded:

* **Remote reachable: +0**. The issue is in networking core code, but the trigger requires local device or namespace teardown behavior, not ordinary remote packets.
* **Privilege escalation plausible: +0**. UAF exists, but the patch does not show reclaim control, type confusion, write primitive, callback dispatch, or refcount abuse.
* **Confidentiality / Integrity impact: +0 conservative**. No concrete disclosure or write primitive is demonstrated.
* **Availability impact realistic: +0 extra**. DoS is already counted via reliable kernel crash.

Race-UAF downgrade rule applies. Conservative score is capped at **4** and paranoid score at **5**.

## 3. Reachability analysis

The realistic trigger is local. An attacker likely needs local code execution plus the ability to manipulate network namespaces or virtual network devices and trigger device unregister or netns exit while packets are being queued. In traditional host configurations this often maps to `CAP_NET_ADMIN`, but in containerized or user-namespace-enabled environments this may be reachable by a reduced-privilege user with namespace-scoped capabilities.

The affected code is in a default core networking path, but the vulnerable sequence requires a teardown race rather than normal packet reception. It is not directly network-triggerable from outside the host.

Call-site confidence: **high**, because the commit message describes the relevant call path, the race window, the stale packet escape, and the KASAN UAF location.

## 4. Severity interpretation

This is stronger than an ordinary Moderate because it is a real core-networking lifetime bug with a demonstrated KASAN slab-use-after-free. However, based on the supplied patch, it behaves more like an **Actionable Moderate** than a clear Important-class LPE, because exploitation evidence is limited to crash/UAF and no controlled reuse or write primitive is shown.

Theoretical memory corruption potential exists due to the UAF class. Realistic evidence currently supports local DoS and manual review, not confirmed privilege escalation.

## 5. One-sentence report phrase

A TOCTOU race in `enqueue_to_backlog()` can allow packets to escape backlog flushing during device unregister or netns exit, leading to a stale device-state use-after-free in core networking and a likely local kernel crash.

## 6. Manual review recommendation

**MANUAL CHECK REQUIRED**

Reason: this is a demonstrated KASAN slab-use-after-free in a core networking packet path. Even though the practical evidence points mainly to local DoS, UAF lifetime bugs in networking should not be auto-closed without manual review.

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

Patch: net: serialize netif_running() check in enqueue_to_backlog() [ Upstream
Commit: 2fface6e0bbd6314d1d9d071abf2c4d67548511c
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=2fface6e0bbd6314d1d9d071abf2c4d67548511c

Changed files:
  net/core/dev.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=2fface6e0bbd6314d1d9d071abf2c4d67548511c

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

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

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