[CVE-2026-98841][MODERATE REGULAR] virt: vmgenid: set driver_data before registering notification handlers

[CVE-2026-98841][MODERATE REGULAR] virt: vmgenid: set driver_data before registering notification handlers

[AL-KERNEL]

CVE: CVE-2026-98841
Priority: MODERATE REGULAR
AL-KERNEL base severity: MODERATE
KPANIC flag: NO
Patch: virt: vmgenid: set driver_data before registering notification handlers
Commit: 538fe5efaa9704ad820ba34b4f9df135ca873d79
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=538fe5efaa9704ad820ba34b4f9df135ca873d79
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-98841
Analysis date: Mon, 19 Oct 2026 02:17:43 -0400
ActionableScore: 1
ActionableScore lower bound: unknown
Actionable bucket: Ordinary Moderate
Manual review required: NO

Summary:
An IRQ or ACPI notification arriving before vmgenid probe stores driver_data can dereference a NULL state pointer and panic the guest kernel, while no UAF, memory corruption, authorization bypass, or guest-to-host impact is established.

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

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

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

A detailed explanation of the methodology and priority rules is included
at the end of this message.

======================================================================
AL-KERNEL CLASSIFICATION RESULT
======================================================================

CVE-2026-98841	MODERATE	https://www.kernelcve.org/list/?q=CVE-2026-98841 CHECK WITH IMPACT FROM ORIG NN MODERATE | AEGIS IMPACT MODERATE_KPANIC AEGIS_AS=1 LEGACY=MODERATE RESULT=DIFF V39_AEGIS_ONE_STEP_UP=LOW->MODERATE TEMP_DISTANCE_MERGE_SKIP=AEGIS_LOW_ELIGIBLE_NO_POSITIVE_SIGNAL (final Legacy and Aegis differ; FINAL: MODERATE, Aegis: MODERATE_KPANIC)	Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H';CWE-362;CWE-665;**CWE-476;Other CVSS 'AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:H';BEST CVSS score: '4.7';DESCR 'The vmgenid probe paths register an IRQ or ACPI notification handler before storing the initialized state in driver_data. A notification arriving in this interval causes vmgenid_notify to dereference NULL driver_data and can panic the guest kernel. The Device Tree path can be triggered by a pending generation change during snapshot restoration or by activity on a shared IRQ line. The ACPI path has a narrower asynchronous notification window. For the CVSS the PR:L value is used in the paranoid score because snapshot restoration or VMM lifecycle operations may be delegated to a restricted operator or service account without full host administration. The base score uses PR:H because reliable notification injection normally requires control of the VMM or guest restoration process. The issue is not directly network reachable. The demonstrated impact is denial of service against the guest kernel. There is no UAF OOB access or write primitive supporting confidentiality integrity or privilege escalation impact. Automated impact decision path. The original SimpleNet classifier selected MODERATE_KPANIC. The primary LLM estimated paranoid CVSS 4.7 and the production ActionableScore returned 1 with recommendation Ordinary Moderate. The production rules then evaluated CVSS thresholds and ActionableScore thresholds. Recorded rule transitions were CVSS and initial triage stage MODERATE_KPANIC to MODERATE because the CVSS score, vector or bug class threshold rule was applied. ActionableScore thresholds stage MODERATE to LOW because the ActionableScore threshold rule was applied. final reconciliation stage LOW to MODERATE because the cross model evidence reconciliation rule was applied. The legacy KP specialist has no review artifact for this run. The legacy FD or DH downgrade specialist has no review artifact for this run. Exact triggered rule markers were DECREASED_TO_MODERATE_REGULAR_FROM_MODERATE7_BASED_ON_GUESSCVSS_AND_CIANNH and DECREASED_TO_LOW_FROM_MODERATE_BASED_ON_ACTIONABLESCORELESSTHAN3 and V39_AEGIS_ONE_STEP_UP and MANUAL_REVIEW_REQUIRED. The independent weaker Aegis shadow evaluated CVSS 4.4 and ActionableScore 1 with primitive class CLASS_C and manual review NO. Its independently reconciled impact was MODERATE_KPANIC. Cross model aggregation changed the production result under an enabled evidence gated merge rule. The final reported impact is MODERATE.';YES REQUIRES MANUAL CHECK; ,and ActionableScore result is Ordinary Moderate (with actual score 1)	MAYBE	OOB NULLPTR VIRT INIT ERRORPATH HARDWARE LINUS DECREASED_TO_MODERATE_REGULAR_FROM_MODERATE7_BASED_ON_GUESSCVSS_AND_CIANNH DECREASED_TO_LOW_FROM_MODERATE_BASED_ON_ACTIONABLESCORELESSTHAN3 V39_AEGIS_ONE_STEP_UP MANUAL_REVIEW_REQUIRED	-	-	checked

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

ActionableScore=1
PrimitiveClass=CLASS_C
RealUAF=NO
HostAdminRequired=UNKNOWN
NamespaceScopedPrivilege=NO
ImportantCandidate=NO
ManualReview=NO
AutoDowngradeAllowed=YES
RequiresHostUID0=UNKNOWN
AuthorizationDecisionBypass=NO
ProtectedResourceImpact=NONE
B4PendingReview=NO
B4PendingConfirmed=NO

1. ActionableScore

* Raw conservative score: 1
* Conservative score: 1
* Raw paranoid score: 1
* Paranoid score: 1
* No floor or cap was applied.
* Final recommended bucket: **Ordinary Moderate**::

2. Signal breakdown

Positive signals:

* +1 Reliable kernel crash / strong DoS. An early Device Tree IRQ or asynchronous ACPI notification dereferences NULL `driver_data` in `vmgenid_notify()` and can panic the guest kernel.

Negative signals:

* No negative points. The ACPI window is narrow, but no race penalty is applied because the Device Tree path can receive an already-pending IRQ immediately after handler registration, making the faulty ordering more concrete than a purely low-probability race.

Material non-awarded signals:

* No UAF, OOB access, heap overwrite, repeated release, active-state corruption, or authorization bypass exists.
* No controlled reclaim, arbitrary write, disclosure, integrity modification, or privilege-escalation primitive is demonstrated.
* No direct network reachability is established.
* No local-unprivileged bonus is awarded because a guest user cannot ordinarily inject the vmgenid notification or control host snapshot restoration directly.
* No extra Availability point is awarded because it would double-count the same guest-kernel panic.
* V33, V32, B3-PENDING, B4-PENDING, B5-R, and KVM guest-to-host corruption rules do not apply.

3. Reachability analysis

The concrete trigger is an IRQ or ACPI notification arriving after handler registration but before `driver_data` assignment. The Device Tree case can occur when a VMM restores a snapshot with a pending generation-change notification. A device sharing the IRQ can also invoke the handler, although attacker control over such a device is not established. The ACPI path requires a notification in a narrower asynchronous window.

A guest-only attacker is not shown to control the complete sequence. A VMM process or virtualization-management service may control snapshot restoration and notification injection, but the supplied evidence does not establish whether that actor requires full host-administrator power or only delegated lifecycle permissions. Therefore `HostAdminRequired=UNKNOWN`. No user-namespace or network-namespace capability governs this path, so `NamespaceScopedPrivilege=NO`.

No special physical hardware is required, but the vulnerable state occurs during driver probe and normally requires snapshot restoration, a pending notification, or shared-IRQ activity.

4. Primitive and severity interpretation

The exact primitive is a NULL-pointer dereference caused by publishing a callback before publishing the callback state. The state object has already been initialized and has not been freed, so this is neither a UAF nor a stale-object lifetime violation.

The handler performs an ordinary invalid dereference before any useful attacker-controlled memory operation is established. This is therefore `CLASS_C`. The demonstrated consequence is a guest-kernel panic. Host corruption, guest-to-host impact, confidentiality loss, integrity loss, and privilege escalation are unsupported.

`ImportantCandidate=NO` because there is no independent corruption or security-boundary primitive beyond guest DoS. `AutoDowngradeAllowed=YES` because the behavior is a constrained initialization-order NULL dereference with no unresolved exploitation leverage.

5. One-sentence report phrase

An IRQ or ACPI notification arriving before vmgenid probe stores driver_data can dereference a NULL state pointer and panic the guest kernel, while no UAF, memory corruption, authorization bypass, or guest-to-host impact is established.

6. Manual review recommendation

NO MANUAL CHECK NEEDED

The patch establishes a bounded crash-only initialization-order defect, and no Important-preserving primitive or unresolved cross-boundary corruption chain remains.

7. Call-site confidence

Call-site confidence: high

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

Patch: virt: vmgenid: set driver_data before registering notification handlers
Commit: 538fe5efaa9704ad820ba34b4f9df135ca873d79
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=538fe5efaa9704ad820ba34b4f9df135ca873d79

Commit description:

Both probe paths register their notification handler before assigning
driver_data, which the handler dereferences.

In the devicetree path, the notification IRQ can fire as soon as
devm_request_irq() registers the handler: the interrupt may already be
pending at probe time, for example when a VMM injects the
generation-changed notification while restoring a guest from a snapshot
that was taken before the driver had probed (Firecracker does exactly
this on snapshot restore). The IRQ is also requested with IRQF_SHARED,
so another device sharing the line can trigger the handler just as
early. The handler then calls vmgenid_notify(), which dereferences the
still-NULL driver_data and panics:

  Unable to handle kernel NULL pointer dereference at virtual address 0000000000000010
  CPU: 0 UID: 0 PID: 1 Comm: swapper/0 Not tainted 6.18.38+ #1 PREEMPT(none)
  Hardware name: linux,dummy-virt (DT)
  pc : vmgenid_notify.isra.0+0x24/0x8c
  lr : vmgenid_of_irq_handler+0x14/0x34
  Call trace:
   vmgenid_notify.isra.0+0x24/0x8c (P)
   vmgenid_of_irq_handler+0x14/0x34
   __handle_irq_event_percpu+0x44/0x1bc
   handle_irq_event+0x4c/0xb4
   handle_fasteoi_irq+0xf8/0x1f8

The ACPI path has the same ordering problem: the handler is installed
with acpi_install_notify_handler() before driver_data is assigned.
ACPI notifications are dispatched asynchronously from a workqueue, so
the window is narrow, but a notification arriving between the two calls
hits the same NULL dereference.

Assign driver_data before registering the handlers. The state is fully
initialized at that point, so the handlers are safe to run. Should
registration fail, the probe error path leaves no dangling pointer
behind: the driver core clears driver_data in device_unbind_cleanup().

Fixes: 7b1bcd6 ("virt: vmgenid: add support for devicetree bindings")
Fixes: e076067 ("virt: vmgenid: change implementation to use a platform driver")
Cc: stable@vger.kernel.org
Signed-off-by: Zhichen Wang <wangzhichen@manus.ai>
Signed-off-by: Jason A. Donenfeld <Jason@zx2c4.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

Changed files:
  drivers/virt/vmgenid.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=538fe5efaa9704ad820ba34b4f9df135ca873d79

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

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

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

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