[CVE-2026-74684][MODERATE 7.0] net: tap: set skb->dev before parsing virtio net header in tap_get_user_xdp()

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

CVE: CVE-2026-74684
Priority: MODERATE 7.0
AL-KERNEL base severity: MODERATE
KPANIC flag: YES
Patch: net: tap: set skb->dev before parsing virtio net header in tap_get_user_xdp()
Commit: 8b444b126cd8e4473e652f529753ed4dd1360a9c
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=8b444b126cd8e4473e652f529753ed4dd1360a9c
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-74684
Analysis date: Sat, 22 Aug 2026 16:33:48 -0400
ActionableScore: 5
ActionableScore lower bound: 4
Actionable bucket: Actionable Moderate at minimum
Manual review required: YES

Summary:
A NULL pointer dereference in the tap/vhost XDP transmit path allows a guest or adjacent virtual network endpoint to crash the host kernel by causing virtio-net header parsing before `skb->dev` is initialized.

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

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

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-74684	MODERATE	CHECK WITH IMPACT FROM ORIG NN LOW	Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:A/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:H';**CWE-476;*CWE-20;CWE-754;Other CVSS 'AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H';BEST CVSS score: '7.4';DESCR 'A NULL-pointer dereference in the Linux tap/vhost XDP transmit path can occur because tap_get_user_xdp() parses the virtio net header before assigning skb dev. A guest or adjacent virtual network endpoint can trigger this when the vhost TX path passes an XDP buffer with a GSO virtio net header and protocol value zero, causing dev_parse_header_protocol() to dereference a NULL skb dev pointer and crash the host kernel. For the CVSS the PR:N is used for the paranoid score because no privileges on the vulnerable host are required, although practical triggering requires access to a guest or virtual network path using tap and vhost. The issue is not Internet remote and is better modeled as adjacent or guest-to-host reachable. Impact is denial of service via host kernel crash. No direct confidentiality or integrity impact is assigned because the observed primitive is a NULL pointer dereference rather than UAF, OOB access, or arbitrary write.';YES REQUIRES MANUAL CHECK; ,and ActionableScore result is Actionable Moderate at minimum (with actual score 5)	YES	LOCK DANGER NULLPTR SIMPLEFIX NETWORK SKB KERNEL_PANIC_PLUS_UAF HARDWARE KPANIC PACKET 	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 score:

* Guest or adjacent virtual network trigger without host privileges: +1
  The attacker does not need privileges on the vulnerable host, but needs access to a guest or virtual networking path using tap and vhost.

* Reliable kernel crash / strong DoS: +1
  The commit explicitly describes a NULL pointer dereference in `dev_parse_header_protocol()` leading to a crash.

* Availability impact realistic: +1
  The crash is in host kernel networking code and can affect the whole host, not only the guest process.

* Common virtualization networking datapath: +1
  tap/vhost/virtio-net is a common Linux virtualization networking path.

* Specific runtime conditions required: -1
  Triggering requires the vhost TX path, XDP buffer handling, a GSO virtio-net header, and protocol set to zero.

Paranoid delta:

* Cross-boundary host impact from guest or adjacent virtual endpoint: +1
  A guest-controlled or adjacent virtual network packet path can crash the host kernel, so it should not be auto-closed as an ordinary local NULL dereference.

Not awarded:

* No generic memory corruption: +0
  The primitive shown is NULL pointer dereference, not UAF, OOB write, double-free, type confusion, or arbitrary write.

* No privilege escalation plausible: +0
  The patch does not show reclaim, overwrite, callback control, refcount abuse, or another LPE-relevant primitive.

* No confidentiality or integrity impact: +0
  There is no supported read disclosure or write corruption primitive.

## 3. Reachability analysis

The bug is reachable through the Linux tap/vhost XDP transmit path when a virtio-net header is parsed before `skb->dev` is assigned. A guest or adjacent virtual network endpoint may trigger it if the host uses tap/vhost with the affected XDP path and receives a GSO virtio-net header with protocol zero.

This is not Internet-remote in the normal sense. It is better modeled as adjacent or guest-to-host reachable. The attacker generally needs access to a VM or virtual network path backed by tap/vhost, but does not need privileges on the vulnerable host.

Namespaces do not materially reduce the concern if the affected path is exposed through a VM or delegated virtual networking setup. The affected subsystem is common in virtualization deployments, but the exact trigger requires specific packet/header conditions.

Call-site confidence: high, because the patch and commit message directly show the ordering bug and the downstream NULL dereference path.

## 4. Severity interpretation

This behaves above an ordinary Moderate because it is a host-kernel crash reachable from a virtualization networking boundary. It does not reach Strong Important based on the supplied evidence because the demonstrated primitive is a NULL pointer dereference only.

The realistic impact is denial of service through host kernel crash. The theoretical memory-corruption potential is low because there is no UAF, stale object reuse, OOB access, controlled overwrite, or object confusion shown by the patch.

## 5. One-sentence report phrase

A NULL pointer dereference in the tap/vhost XDP transmit path allows a guest or adjacent virtual network endpoint to crash the host kernel by causing virtio-net header parsing before `skb->dev` is initialized.

## 6. Manual review recommendation

MANUAL CHECK REQUIRED

Reason: this is a guest-to-host or adjacent virtual networking crash path in host kernel code. Even though the primitive is only NULL dereference and does not support C/I or LPE, the host-impacting virtualization boundary makes it actionable and unsuitable for auto-close.

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

Patch: net: tap: set skb->dev before parsing virtio net header in tap_get_user_xdp()
Commit: 8b444b126cd8e4473e652f529753ed4dd1360a9c
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=8b444b126cd8e4473e652f529753ed4dd1360a9c

Commit description:

The commit 4f61f13 ("net: tap: NULL pointer derefence in
dev_parse_header_protocol when skb->dev is null") fixed a crash in
tap_get_user() by assigning skb->dev before calling tun_vnet_hdr_to_skb().
This is required because virtio_net_hdr_to_skb() may invoke
dev_parse_header_protocol(), which dereferences skb->dev. Without the
assignment, a NULL pointer dereference can occur.

However, tap_get_user_xdp() still parses the virtio-net header before
assigning skb->dev. When the vhost TX path passes an XDP buffer containing
a GSO virtio-net header but the protocol is set to zero on purpose,
tun_vnet_hdr_to_skb() can reach dev_parse_header_protocol() while skb->dev
is still NULL, resulting in a crash.

Fix this by looking up the tap device and assigning skb->dev before calling
tun_vnet_hdr_to_skb(), matching the ordering already used in
tap_get_user(). Preserve the existing RCU read-side critical section across
dev_queue_xmit().

Fixes: 924a9bc ("net: check if protocol extracted by virtio_net_hdr_set_proto is correct")
Cc: stable@vger.kernel.org
Signed-off-by: Dongli Zhang <dongli.zhang@oracle.com>
Reviewed-by: Willem de Bruijn <willemb@google.com>
Acked-by: Michael S. Tsirkin <mst@redhat.com>
Link: https://patch.msgid.link/20260802224612.264563-1-dongli.zhang@oracle.com
Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

Changed files:
  drivers/net/tap.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=8b444b126cd8e4473e652f529753ed4dd1360a9c

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

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

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

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