# CVE-2026-98088: scsi: mpt3sas: Avoid out-of-bounds cpumask_of_node() call in _base_assign_reply_queues()

> An out-of-bounds read in the mpt3sas driver can cause a kernel crash on systems without NUMA topology, leading to denial of service.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 25 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** AZL-104243, BELL-CVE-2026-98088, DEBIAN-CVE-2026-98088, GHSA-xp5x-f79f-mr26, UBUNTU-CVE-2026-98088

## What is CVE-2026-98088?

CVE-2026-98088 is a memory corruption vulnerability in Linux, published on 25 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In the Linux kernel, the following vulnerability has been resolved:

scsi: mpt3sas: Avoid out-of-bounds cpumask_of_node() call in _base_assign_reply_queues()

dev_to_node() can return NUMA_NO_NODE (-1) on systems without NUMA
topology information for the PCI device, such as single-socket boards
that don't expose device-to-node affinity. Passing -1 directly into
cpumask_of_node() indexes node_to_cpumask_map[-1], an out-of-bounds
array read caught by UBSAN:

  UBSAN: array-index-out-of-bounds in arch/x86/include/asm/topology.h:72:28
  index -1 is out of range for type 'cpumask *[1024]'

Fall back to cpu_online_mask when no NUMA node is available, rather than
assuming dev_to_node() always returns a valid node index.

## Which versions are affected by CVE-2026-98088?


## How do I fix CVE-2026-98088?

Apply the vendor's patch.

## Is CVE-2026-98088 being exploited?

There is no known exploitation of CVE-2026-98088 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-98088 and fix it if it is affected.

What it is: CVE-2026-98088 is a memory corruption vulnerability in Linux, published on 25 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-98088 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-98088/ (Markdown: https://insights.sbomify.com/CVE-2026-98088/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-98088
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-98088
- OSV: https://osv.dev/vulnerability/CVE-2026-98088

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-98088/
Summaries are generated and may contain mistakes; the official description above is the record.