[CVE-2026-98544][MODERATE 7.0] bna: prevent IOC timer rearm during teardown [ Upstream

[CVE-2026-98544][MODERATE 7.0] bna: prevent IOC timer rearm during teardown [ Upstream

[AL-KERNEL]

CVE: CVE-2026-98544
Priority: MODERATE 7.0
AL-KERNEL base severity: MODERATE
KPANIC flag: YES
Patch: bna: prevent IOC timer rearm during teardown [ Upstream
Commit: 28e32ace754b57534ef0ca0fb99bcbea5b13ba2a
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=28e32ace754b57534ef0ca0fb99bcbea5b13ba2a
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-98544
Analysis date: Fri, 23 Oct 2026 19:46:23 -0400
ActionableScore: 3
ActionableScore lower bound: unknown
Actionable bucket: Borderline / manual review recommended
Manual review required: YES

Summary:
Mutually rearming BNA IOC timers can execute after free_netdev releases the driver context, causing a teardown use after free and potential kernel crash, although no remote or below host admin trigger and no controlled exploitation primitive are currently established.

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

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

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-98544	MODERATE	https://www.kernelcve.org/list/?q=CVE-2026-98544 CHECK WITH IMPACT FROM ORIG NN MODERATE | AEGIS IMPACT MODERATE_KPANIC AEGIS_AS=4 LEGACY=MODERATE_KPANIC RESULT=SAME V39_AEGIS_ONE_STEP_UP=MODERATE->MODERATE_KPANIC (final reconciliation agrees; DECISION: both MODERATE_KPANIC)	Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:L/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H';*CWE-416;CWE-362;CWE-667;Other CVSS 'AV:L/AC:H/PR:H/UI:N/S:U/C:L/I:L/A:H';BEST CVSS score: '6.4';DESCR 'A race during bna driver teardown can leave IOC timer callbacks active after free_netdev has released the struct bnad object. The sem_timer and iocpf_timer callbacks can rearm each other, so timer_delete_sync on individual timers does not prevent a sibling callback from scheduling a timer again. A later bnad_iocpf_timeout callback can access bnad and take bnad_bna_lock after the underlying allocation has been freed, creating a use after free condition. The immediate result may be a kernel crash, while reuse of the freed allocation creates a plausible risk of confidentiality or integrity impact that requires manual analysis. For the CVSS the PR:H reflects that reliable triggering normally requires administrative control over PCI driver removal, unbind, or a failing probe teardown path. AC:H reflects the timer and teardown race window. The issue is not directly network reachable even though it affects an Ethernet driver. Impact is at least a local denial of service via kernel crash and in the worst case may include confidentiality or integrity impact due to use after free. YES REQUIRES MANUAL CHECK Automated impact decision path. The original SimpleNet classifier selected MODERATE_KPANIC. The primary LLM estimated paranoid CVSS 6.4 and the production ActionableScore returned 3 with recommendation Borderline / manual review recommended. The production rules then evaluated CVSS thresholds and ActionableScore thresholds. Recorded rule transitions were ActionableScore thresholds stage MODERATE_KPANIC to MODERATE because the ActionableScore threshold rule was applied. final reconciliation stage MODERATE to MODERATE_KPANIC 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_MODERATEREG_BASED_ON_ACTIONABLESCORELESSTHAN4 and V39_AEGIS_ONE_STEP_UP and MANUAL_REVIEW_REQUIRED. The independent weaker Aegis shadow evaluated CVSS 1.9 and ActionableScore 4 with primitive class CLASS_B and manual review REQUIRED. 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_KPANIC.';YES REQUIRES MANUAL CHECK; ,and ActionableScore result is Borderline / manual review recommended (with actual score 3)	MAYBE	REMOTE INIT UAF NETWORK TIMER TEST  DECREASED_TO_MODERATEREG_BASED_ON_ACTIONABLESCORELESSTHAN4 KPANIC V39_AEGIS_ONE_STEP_UP MANUAL_REVIEW_REQUIRED	-	-	checked

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

ActionableScore=3
PrimitiveClass=CLASS_B
RealUAF=YES
HostAdminRequired=UNKNOWN
NamespaceScopedPrivilege=NO
ImportantCandidate=NO
ManualReview=RECOMMENDED
AutoDowngradeAllowed=YES
RequiresHostUID0=UNKNOWN
AuthorizationDecisionBypass=NO
ProtectedResourceImpact=NONE
B4PendingReview=NO
B4PendingConfirmed=NO

1. ActionableScore

* Raw conservative score: 3
* Conservative score: 3
* Raw paranoid score: 3
* Paranoid score: 3
* No floor or cap was applied.
* Final recommended bucket: **Borderline / manual review recommended**::

2. Signal breakdown

Positive signals:

* +2 Real UAF. A live IOC timer callback can execute after `free_netdev()` has released the containing `struct bnad`.
* +1 Realistic kernel crash. `bnad_iocpf_timeout()` accesses the freed object and attempts to acquire `bnad->bna_lock`, which can cause an invalid atomic operation, Oops, or panic.

Negative signals:

* No negative privilege score. Host-admin control is plausible for PCI removal or driver unbind, but the complete trigger also includes probe failure and disable timeout paths. The supplied evidence does not prove which actor can reliably produce the full sequence.
* No race penalty. The defect involves asynchronous ordering, but the commit does not establish that the vulnerable timing is narrow or difficult to reproduce once `bnad_ioceth_disable()` times out and a callback remains live.
* No rare-hardware penalty. Matching BNA hardware is required, but the supplied evidence does not establish a physical attacker requirement or provide enough deployment evidence to justify a numeric rarity penalty.

Important non-awarded signals:

* Controlled reclaim or attacker-shaped replacement contents are not demonstrated.
* Arbitrary or directed kernel write is not demonstrated.
* Structured stale-object leverage is not awarded. The visible stale operation acquires a lock in the freed driver context but does not consume attacker-influenced pointers, lengths, callbacks, or ownership fields.
* The atomic lock operation may modify freed storage, but its target and value are constrained and no useful corruption chain is established. It is not scored separately from the UAF.
* Remote reachability is not established merely because this is an Ethernet driver.
* Extra Availability is not awarded because the same potential kernel crash is already counted.
* Confidentiality, integrity, LPE, and callback hijacking are not awarded.

Repeated-release assessment:

* No first release of a separately referenced object followed by reuse of the exact dangling reference is shown.
* No second `put`, `release`, `free`, or refcount mutation exists.
* Concrete repeated release/refcount +1 was not awarded.
* Paranoid repeated-refcount leverage +1 was not awarded.
* FLOOR 5 was not applicable.

Special profiles:

* B5-R is not applicable. There is no retry-accumulated heap OOB write.
* B3-PENDING is not applicable. There is no shared-backing or file-backed write.
* V33 and V34 are not applicable. No attacker-controlled networking metadata corruption is involved.
* B4-PENDING is not applicable. No authorization decision changes from DENY to ALLOW.

3. Reachability analysis

The vulnerable paths are PCI probe failure cleanup and `bnad_pci_remove()`. Driver unbind or PCI removal normally involves host-global device management, but the supplied material does not prove that administrative removal is the only way to reach the vulnerable sequence. Probe failure, IOC disable timeout, device failure, or recovery behavior may also participate.

No ordinary local-user, delegated service, container, network-namespace, or remote-packet trigger is established. PCI device lifecycle operations are not namespace-scoped, and an attacker-created user or network namespace does not provide control over this host-owned device.

The affected BNA device and driver must be present. The timer callback must remain live after `bnad_ioceth_disable()` and execute after the containing netdev allocation is freed. The mutually rearming timers make this sequence technically concrete, but attacker control and practical repeatability remain unresolved.

4. Primitive and severity interpretation

The exact primitive is an asynchronous post-teardown use-after-free of a fixed driver context. `sem_timer` and `iocpf_timer` can rearm each other, while `timer_delete_sync()` waits only for the callback associated with the timer being deleted. Consequently, a sibling callback can restore a timer after it was individually deleted.

The stale object is a structured `struct bnad`, but the demonstrated stale use is narrow and teardown-specific. The callback accesses the freed object and acquires its spinlock. This is stronger than a NULL dereference but does not establish controlled reclaim, attacker-directed replacement, useful pointer traversal, or callback dispatch through reclaimed data.

This is CLASS_B because an actual lifetime violation exists. The demonstrated consequence is kernel crash or corruption of the stale lock state. Privilege escalation and broader confidentiality or integrity effects remain theoretical.

ImportantCandidate is NO because the supplied evidence shows a constrained teardown UAF without meaningful attacker-controlled reuse or an independent security-boundary primitive. AutoDowngradeAllowed is YES because no unresolved strong exploitation mechanism is established. Manual review remains recommended to verify whether firmware behavior, device recovery, or an exposed management operation can provide a repeatable below-host-admin trigger.

5. One-sentence report phrase

Mutually rearming BNA IOC timers can execute after free_netdev releases the driver context, causing a teardown use after free and potential kernel crash, although no remote or below host admin trigger and no controlled exploitation primitive are currently established.

6. Manual review recommendation

MANUAL CHECK RECOMMENDED

Verify practical trigger permissions, timer behavior after IOC disable timeout, allocator reuse around `free_netdev()`, and whether device or firmware recovery can invoke the complete sequence without host-administrator control.

7. Call-site confidence

Call-site confidence: high

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

Patch: bna: prevent IOC timer rearm during teardown [ Upstream
Commit: 28e32ace754b57534ef0ca0fb99bcbea5b13ba2a
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=28e32ace754b57534ef0ca0fb99bcbea5b13ba2a

Changed files:
  drivers/net/ethernet/brocade/bna/bnad.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=28e32ace754b57534ef0ca0fb99bcbea5b13ba2a

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

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

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

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