From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-99766: scsi: aic79xx: Fix NULL pointer dereference in device reset
Date: Fri, 20 Nov 2026 06:52:32 +0100 [thread overview]
Message-ID: <2026112026-CVE-2026-99766-df08@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
scsi: aic79xx: Fix NULL pointer dereference in device reset
Since commit c67e63800446 ("scsi: aic79xx: Do not reference SCSI command
when resetting device") the device reset SCB has no SCSI command, but
ahd_linux_dev_reset() still sets its residual, and ahd_abort_scbs(), which
completes it, sets its status. Seen on an AIC-7902 when a failing disk
triggered a device reset, which killed the SCSI error handler:
BUG: kernel NULL pointer dereference, address: 0000009c
EIP: ahd_linux_dev_reset.cold+0xee/0x26e
Add NULL command checks to the accessors in aic79xx_osm.h. Also skip
autosense for an SCB without a command and complete it with ahd_done()
right away: the REQUEST SENSE path can clear SCB_DEVICE_RESET, after which
ahd_done() would dereference the missing command.
The Linux kernel CVE team has assigned CVE-2026-99766 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.7 with commit c67e63800446f9c72e362fe6f5e0c623fbe2e394 and fixed in 6.12.118 with commit 8eba199dce256eaa2ee3da460588f2ba5494a4d5
Issue introduced in 6.7 with commit c67e63800446f9c72e362fe6f5e0c623fbe2e394 and fixed in 6.18.64 with commit 856e3bf320c777b4676d58166745d1c96670574e
Issue introduced in 6.7 with commit c67e63800446f9c72e362fe6f5e0c623fbe2e394 and fixed in 7.3.5 with commit dab8971b78d13d0aaca40e96feb6188b85d3c752
Issue introduced in 6.7 with commit c67e63800446f9c72e362fe6f5e0c623fbe2e394 and fixed in 7.4-rc2 with commit f057a8bfeb6ff89c65e95540b8700a53c66d4a31
Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.
Unaffected versions might change over time as fixes are backported to
older supported kernel versions. The official CVE entry at
https://cve.org/CVERecord/?id=CVE-2026-99766
will be updated if fixes are backported, please check that for the most
up to date information about this issue.
Affected files
==============
The file(s) affected by this issue are:
drivers/scsi/aic7xxx/aic79xx_core.c
drivers/scsi/aic7xxx/aic79xx_osm.h
Mitigation
==========
The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes. Individual
changes are never tested alone, but rather are part of a larger kernel
release. Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all. If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
https://git.kernel.org/stable/c/8eba199dce256eaa2ee3da460588f2ba5494a4d5
https://git.kernel.org/stable/c/856e3bf320c777b4676d58166745d1c96670574e
https://git.kernel.org/stable/c/dab8971b78d13d0aaca40e96feb6188b85d3c752
https://git.kernel.org/stable/c/f057a8bfeb6ff89c65e95540b8700a53c66d4a31
reply other threads:[~2026-11-20 6:01 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2026112026-CVE-2026-99766-df08@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cve@kernel.org \
--cc=gregkh@kernel.org \
--cc=linux-cve-announce@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.