* [CVE-2026-89849][MODERATE REGULAR] scsi: qla2xxx: Reject non-SCSI SRB on status IOCB fast path
@ 2026-09-16 13:09 21% AL-KERNEL
0 siblings, 0 replies; 1+ results
From: AL-KERNEL @ 2026-09-16 13:09 UTC (permalink / raw)
To: kernel-cve
CVE: CVE-2026-89849
Priority: MODERATE REGULAR
AL-KERNEL base severity: MODERATE
KPANIC flag: NO
Patch: scsi: qla2xxx: Reject non-SCSI SRB on status IOCB fast path
Commit: 9204fb0888374083be74f799049649a17eab4191
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=9204fb0888374083be74f799049649a17eab4191
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-89849
Analysis date: Wed, 16 Sep 2026 09:09:10 -0400
ActionableScore: 4
ActionableScore lower bound: 3
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-89849 is available here:
https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-89849
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-89849 MODERATE https://www.kernelcve.org/list/?q=CVE-2026-89849 CHECK WITH IMPACT FROM ORIG NN MODERATE Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:A/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:H';CWE-843;CWE-824;**CWE-476;Other CVSS 'AV:A/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H';BEST CVSS score: '6.4';DESCR 'A wild pointer dereference in the qla2xxx status IOCB fast path can occur because qla2x00_status_entry may treat a non-SCSI SRB as SRB_SCSI_CMD. The srb union overlays the SCSI command pointer with other command layouts, so sp u scmd cmd can become a non-NULL garbage pointer and bypass NULL checks. A malicious or faulty Fibre Channel device, fabric component, firmware path, or a local actor able to submit the relevant non-SCSI commands may trigger an unexpected STATUS_TYPE IOCB for a non-SCSI handle. For the CVSS the PR:N is used for the paranoid adjacent-fabric scenario because no victim host account is required when the trigger is supplied by an external storage fabric peer. The issue is adjacent network reachable rather than Internet reachable because qla2xxx is used on Fibre Channel SAN fabrics. Impact is at least denial of service via kernel crash and in worst case may allow limited confidentiality or integrity impact due to a kernel wild pointer dereference, so manual review is recommended.';YES REQUIRES MANUAL CHECK; ,and ActionableScore result is Borderline / manual review recommended (with actual score 4) YES SIMPLEFIX HARDWARE LINUS TEST NO NO checked
======================================================================
ACTIONABLESCORE ANALYSIS
======================================================================
ActionableScore=4
ActionableScoreLower=3
PrimitiveClass=CLASS_C
RealUAF=NO
HostAdminRequired=UNKNOWN
NamespaceScopedPrivilege=NO
ImportantCandidate=NO
ManualReview=RECOMMENDED
AutoDowngradeAllowed=YES
1. ActionableScore
* Raw conservative score: 3
* Conservative score: 3. No floor or cap applied.
* Raw paranoid score: 4
* Paranoid score: 4. No floor or cap applied.
* Final recommended bucket: **Borderline / manual review recommended**::
2. Signal breakdown
Conservative signals:
* +1 Weak / indirect corruption candidate. `qla2x00_status_entry()` can treat a non-SCSI SRB as `SRB_SCSI_CMD`, causing wrong union-field interpretation and a wild pointer dereference through `sp->u.scmd.cmd`.
* +1 Firmware-mediated external influence. The trigger depends on firmware delivering an unexpected `STATUS_TYPE` IOCB for a non-SCSI handle, so this is not direct Internet or ordinary packet reachability.
* +1 Reliable kernel crash / strong DoS. A non-NULL garbage pointer can bypass NULL checks and be dereferenced in the SCSI fast path.
Paranoid additional signal:
* +1 Weak LPE concern. The bug is more than a plain NULL dereference because it is a semantic mismatch between SRB layouts and can make kernel code consume a non-SCSI union member as a SCSI command pointer. This remains weak because no controlled reclaim, arbitrary write, callback control, or privilege-escalation chain is established.
Important non-awarded signals:
* RealUAF not awarded. No freed object or stale post-lifetime object use is established.
* Concrete repeated release/refcount not awarded. No first release, surviving exact dangling reference, and second lifetime mutation are shown.
* Strong exploitation leverage not awarded. There is no controlled replacement, attacker-shaped reclaimed object, arbitrary kernel read/write, or callback/function-pointer influence.
* Direct remote reachability not awarded. Fibre Channel fabric or firmware mediation is material.
* Confidentiality and integrity are not awarded in the conservative score. The patch supports wild pointer dereference and crash, but not a disclosure path or unauthorized modification primitive.
* Extra Availability not awarded. The same crash is already counted once.
* Hardware rarity penalty not applied. qla2xxx is hardware-specific, but the evidence does not prove rare physical-only attacker access as the limiting factor.
3. Reachability analysis
The vulnerable path is in the qla2xxx interrupt/status completion path for Fibre Channel storage adapters. The immediate trigger described by the commit is firmware delivering an unexpected `STATUS_TYPE` IOCB for a non-SCSI handle. A malicious or faulty Fibre Channel device, fabric component, or firmware path could plausibly influence this condition, but this is firmware-mediated adjacent-fabric exposure rather than direct network reachability.
A local actor might contribute by submitting relevant non-SCSI commands if they have access to the appropriate storage management or passthrough interfaces, but the supplied evidence does not establish that an ordinary unprivileged local user can complete the trigger. Host-admin-equivalent privilege is also not positively established for every plausible trigger path because the adjacent-fabric scenario does not require a victim host account. Therefore `HostAdminRequired=UNKNOWN`.
Namespace-scoped privilege is not relevant from the supplied evidence. No user namespace or network namespace based complete trigger chain is established. Prior setup likely includes an affected qla2xxx HBA and Fibre Channel SAN configuration, but no scoring penalty is applied solely because the bug is in a hardware driver. No race or narrow timing requirement is established.
4. Primitive and severity interpretation
The exact primitive is a type/semantic confusion in an active status completion path. A non-SCSI SRB can enter code that assumes `SRB_SCSI_CMD`, and the `srb` union causes `sp->u.scmd.cmd` to be interpreted from another command layout. If that value is non-NULL garbage, existing NULL checks do not stop later dereference.
This is not an active structured UAF and not fixed stale storage. It is an invalid structured-object interpretation leading to a wild pointer dereference. The demonstrated consequence is kernel crash / DoS. The speculative consequence is limited C/I impact if the wrongly interpreted pointer can ever be meaningfully influenced, but the patch does not establish controlled target selection, controlled reclaim, arbitrary write, or LPE.
PrimitiveClass is `CLASS_C` because the demonstrated behavior is primarily invalid-state / wild dereference crash behavior without an independently useful corruption primitive. `ImportantCandidate=NO` because the evidence does not establish Class A or strong Class B exploitation leverage. `AutoDowngradeAllowed=YES` because no unresolved UAF, repeated lifetime mutation, authorization bypass, COW violation, controlled corruption, or boundary-bypass primitive remains established. Operationally this is a borderline Moderate driver DoS issue that merits human review due to the wild pointer dereference and adjacent storage-fabric exposure, but it is not a strong Important candidate from the supplied evidence.
5. One-sentence report phrase
A qla2xxx status IOCB handling bug can reinterpret a non-SCSI SRB as a SCSI command and dereference a garbage command pointer, allowing a faulty or malicious Fibre Channel firmware or fabric path to crash the host kernel.
6. Manual review recommendation
MANUAL CHECK RECOMMENDED
Reason: the issue is not a plain resource leak or harmless warning, and it involves wild pointer dereference in an interrupt completion path. However, no UAF, arbitrary write, controlled replacement, disclosure path, or demonstrated privilege escalation is established.
7. Call-site confidence
Call-site confidence: high
======================================================================
UPSTREAM PATCH SUMMARY
======================================================================
Patch: scsi: qla2xxx: Reject non-SCSI SRB on status IOCB fast path
Commit: 9204fb0888374083be74f799049649a17eab4191
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=9204fb0888374083be74f799049649a17eab4191
Commit description:
qla2x00_status_entry() filters out non-TYPE_SRB entries and the
SRB_NVME_CMD, SRB_BIDI_CMD and SRB_TM_CMD types, then falls through to a
SCSI fast path that assumes the command is an SRB_SCSI_CMD. The first
thing on that path, qla_chk_edif_rx_sa_delete_pending(), and the
subsequent handling both evaluate GET_CMD_SP(sp), i.e. sp->u.scmd.cmd.
The srb u union overlays the SCSI command pointer with other command
layouts (bsg_job, iocb_cmd). If firmware delivers an unexpected
STATUS_TYPE IOCB for a non-SCSI handle, sp->u.scmd.cmd can read as a
non-NULL garbage pointer, bypassing the NULL checks in
qla_chk_edif_rx_sa_delete_pending() and at the cp == NULL test, and
leading to a wild pointer dereference.
Reject any SRB whose type is not SRB_SCSI_CMD before entering the fast
path. The outstanding_cmds slot is left untouched so a genuinely
non-SCSI command still completes through its proper handler.
Fixes: dd30706 ("scsi: qla2xxx: edif: Add key update")
Cc: [email protected]
Reported-by: Sashiko <[email protected]>
Signed-off-by: Nilesh Javali <[email protected]>
Link: https://patch.msgid.link/[email protected]
Signed-off-by: Martin K. Petersen (Oracle) <[email protected]>
Signed-off-by: Greg Kroah-Hartman <[email protected]>
Changed files:
drivers/scsi/qla2xxx/qla_dbg.c
drivers/scsi/qla2xxx/qla_isr.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=9204fb0888374083be74f799049649a17eab4191
======================================================================
DETAILED REPORT METHODOLOGY
======================================================================
The original Linux kernel CVE announcement for CVE-2026-89849 can be found here:
https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-89849
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:H/PR:N/UI:N/S:U/C:N/I:N/A:H
The Best / paranoid CVSS vector: AV:A/AC:H/PR:N/UI:N/S:U/C:L/I:L/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: 3
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 [email protected] (and both
send reply to CVE record itself too and see "reply" button below for howto reply).
^ permalink raw reply [relevance 21%]
Results 1-1 of 1 | reverse | sort options + mbox downloads above
-- links below jump to the message on this page --
2026-09-16 13:09 21% [CVE-2026-89849][MODERATE REGULAR] scsi: qla2xxx: Reject non-SCSI SRB on status IOCB fast path AL-KERNEL
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox