[CVE-2026-97996][MODERATE REGULAR] virtio: fix use-after-free in unregister_virtio_device() [ Upstream

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

CVE: CVE-2026-97996
Priority: MODERATE REGULAR
AL-KERNEL base severity: MODERATE
KPANIC flag: NO
Patch: virtio: fix use-after-free in unregister_virtio_device() [ Upstream
Commit: 951cad50cba89e736afdee4a730e0e52f9245c9b
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=951cad50cba89e736afdee4a730e0e52f9245c9b
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-97996
Analysis date: Fri, 25 Sep 2026 06:45:52 -0400
ActionableScore: 4
ActionableScore lower bound: unknown
Actionable bucket: Borderline / manual review recommended
Manual review required: YES

Summary:
No one-sentence report phrase was found.

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

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

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-97996	MODERATE	https://www.kernelcve.org/list/?q=CVE-2026-97996 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-672;Other CVSS 'AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H';BEST CVSS score: '7';DESCR 'A use after free occurs in unregister_virtio_device because device_unregister can drop the final device reference and invoke a transport release callback before virtio_debug_device_exit reads dev debugfs_dir. The issue is confirmed by KASAN as an eight byte slab use after free read and affects virtio_mmio, virtio_vdpa, virtio_uml, mlxbf_tmfifo, and virtio_ccw when their removal paths hold no extra device reference. The immediate demonstrated impact is a local kernel crash or failure during device removal. Reuse of the freed slab object before debugfs cleanup may provide a stronger memory corruption condition because a stale debugfs_dir value is consumed by subsequent cleanup code. For the CVSS the PR:L in the paranoid score represents a reduced capability root account, service process, container environment, or delegated device management context that can initiate device removal without having unrestricted host control. The issue is not directly network reachable and normally requires local unbind, hot removal, or transport teardown. Impact is at least a local denial of service via kernel crash and in the worst defensible case may include confidentiality and integrity impact due to use after free memory reuse. Manual review is required to determine whether allocator reuse can turn the stale pointer consumption into a reliable privilege escalation primitive.';YES REQUIRES MANUAL CHECK; ,and ActionableScore result is Borderline / manual review recommended (with actual score 4)  SKIP CVE-2026-97996 UNKNOWN SKIP The Fixes patch not applied yet, so unlikely that actual: url YES  NO NO unknown 	MAYBE	READ DANGER VIRT INIT UAF HARDWARE DEBUGFS LINUS  DECREASED_TO_MODERATEREG_BASED_ON_FALSEPOSCHECKOFKP	-	-	checked

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

ActionableScore=4
PrimitiveClass=CLASS_B
RealUAF=YES
HostAdminRequired=UNKNOWN
NamespaceScopedPrivilege=UNKNOWN
ImportantCandidate=NO
ManualReview=RECOMMENDED
AutoDowngradeAllowed=YES

1. ActionableScore

* Raw conservative score: 3
* Conservative score: 4
* Raw paranoid score: 3
* Paranoid score: 4
* Applied conservative floor: 3 -> 4 under the real UAF floor because a freed structured object is actually dereferenced and host-admin-equivalent privilege is not established for every affected removal path.
* Applied paranoid floor: 3 -> 4 for the same reason. No additional paranoid point is justified by theoretical slab reuse alone.
* Final recommended bucket: **Borderline / manual review recommended**::

2. Signal breakdown

* +2 Real UAF. `device_unregister()` can drop the final reference and free the allocation containing `struct virtio_device`. `virtio_debug_device_exit()` then reads `dev->debugfs_dir` through the stale pointer.
* +1 Realistic kernel crash or strong DoS. KASAN confirms an eight-byte slab UAF read, and reuse of the freed allocation could supply an invalid pointer to debugfs cleanup.
* +0 Remote reachability. No network-triggered path is established.
* +0 Local unprivileged trigger. The reproducer uses sysfs unbind from `init/1`, and below-host-admin reachability is not established.
* +0 Structured stale-object leverage. The stale field is a pointer consumed by cleanup, but attacker-controlled reclaim, replacement contents, or another useful post-free operation is not demonstrated.
* +0 Concrete repeated release or refcount operation. `device_unregister()` may end the virtio object lifetime, but the later operation does not perform another put, free, or refcount mutation on that same `virtio_device`.
* +0 Paranoid repeated-refcount leverage. Withheld because there is no second lifetime mutation.
* +0 Weak or strong LPE leverage. Theoretical allocator reuse alone is insufficient.
* +0 Additional Availability. The same UAF crash is not counted twice.
* +0 Confidentiality or Integrity. No disclosure, controlled write, callback control, or attacker-shaped replacement object is established.
* No negative privilege penalty was applied because host-admin-equivalent privilege is not proven for every affected transport and removal mechanism.
* FLOOR 5 was not applied because this is a cleanup-time stale dereference without controlled reclaim, repeated lifetime mutation, or meaningful attacker influence over post-free contents.

3. Reachability analysis

The demonstrated trigger is unbinding a `virtio-uml` device through the driver removal path. Writing the relevant sysfs unbind control is ordinarily restricted, but the supplied evidence does not establish the complete privilege boundary for all affected transports or all hot-removal paths. Therefore `HostAdminRequired` remains `UNKNOWN`, and no speculative host-admin penalty is applied.

Affected transports include `virtio_mmio`, `virtio_vdpa`, `virtio_uml`, `mlxbf-tmfifo`, and `virtio_ccw`. `virtio_pci` is unaffected because its remove path holds an additional device reference. No complete attacker-created namespace path is shown, so `NamespaceScopedPrivilege` is `UNKNOWN`. No direct remote trigger, attacker-controlled firmware input, hard race, or unusual timing is required. The defect is an ordered teardown sequence rather than a race.

`CONFIG_VIRTIO_DEBUG` is relevant to the vulnerable debugfs cleanup path. KASAN is only needed to detect the reproduced UAF, not to create the underlying lifetime violation. Some affected transports require particular platform or virtualization configurations, but the evidence does not justify a rare-hardware penalty.

4. Primitive and severity interpretation

The exact primitive is a post-lifetime read from a freed allocation containing an embedded `struct virtio_device`. The stale path reads `dev->debugfs_dir` and passes the resulting pointer into recursive debugfs cleanup.

This is an active structured object rather than a fixed DMA buffer. However, the use occurs narrowly during unregister and cleanup. The demonstrated operation is an ordinary stale cleanup dereference:

`final put and release -> containing allocation freed -> stale field read during debugfs cleanup`

It is not a concrete repeated lifetime mutation:

`final put -> free -> second put or refcount mutation on the same virtio object`

Accordingly, this is `CLASS_B`, but constrained Class B. A real UAF exists, yet controlled reclaim, attacker-shaped replacement data, arbitrary read or write, callback influence, disclosure, and privilege escalation are not established. The immediate practical consequence is a diagnostic KASAN failure and potentially a kernel crash or failed device removal.

`ImportantCandidate=NO` because the evidence does not establish meaningful exploitation leverage beyond the cleanup-time stale-pointer use. `AutoDowngradeAllowed=YES` because no repeated release, controlled replacement, security-boundary bypass, or unresolved active-use primitive remains. Manual review is still recommended because the stale pointer enters `debugfs_remove_recursive()`, and surrounding allocator or transport behavior could change the practical consequence.

Likely operational severity is Moderate or borderline Moderate, not Important based on the supplied evidence.

5. One-sentence report phrase

A confirmed cleanup-time use-after-free occurs when virtio device unregister frees the embedded device before debugfs teardown reads its stale debugfs pointer, with kernel crash potential but no demonstrated controlled reclaim, repeated lifetime mutation, or privilege-escalation primitive.

6. Manual review recommendation

MANUAL CHECK RECOMMENDED

Review whether any affected transport permits below-host-admin removal and whether its release callback can enable attacker-influenced reuse before debugfs cleanup. Current evidence supports a constrained crash-capable UAF rather than an Important-grade exploitation primitive.

7. Call-site confidence

Call-site confidence: high

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

Patch: virtio: fix use-after-free in unregister_virtio_device() [ Upstream
Commit: 951cad50cba89e736afdee4a730e0e52f9245c9b
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=951cad50cba89e736afdee4a730e0e52f9245c9b

Changed files:
  drivers/virtio/virtio.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=951cad50cba89e736afdee4a730e0e52f9245c9b

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

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

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:L/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: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: unknown
  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).