Unknown

CVE-2026-98386 — scsi: qla2xxx: Use memset_io() to clear QLAFX00 request ring slot

In the Linux kernel, the following vulnerability has been resolved: scsi: qla2xxx: Use memset_io() to clear QLAFX00 request ring slot For QLAFX00 the request ring is ioremapped device I/O memory (ha->iobase + req_que_off), not DMA-coherent RAM, which is why the rest of the FX00 path accesses it through memcpy_toio() and the wrt_reg_* helpers. __qla2x00_alloc_iocbs() however zeroed the producer slot with a plain memset(). On architectures such as ARM64 a regular memset() may emit unaligned or block-zeroing instructions (e.g. DC ZVA) that are invalid on Device memory, leading to a synchronous external abort. Use memset_io() to clear the slot for QLAFX00, matching the I/O accessors used elsewhere on this ring. Other adapters keep the plain memset() on their DMA-coherent rings. The zero-fill is retained for FX00 because its IOCB builders (e.g. qlafx00_fxdisc_iocb()) copy only part of the entry and rely on the unused tail being pre-zeroed.

Published Oct 14, 2026 · Updated Oct 14, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP · CNA: Linux

Low

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.

How the score was calculated

No scoring signals.

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation

Not confirmed

Not in CISA KEV — an absence of record, not proof it is unexploited.

EPSS FIRST

—

No EPSS score.

Affects

Linux

CVSS base

—

Score not published yet.

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

Identify exposed assets running the affected vendor/product/version combinations (Linux Linux).
No fix documented in the sources: reduce exposure and monitor the vendor advisory.
Search available logs for exploit probes, errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

Vendor	Product	Versions	Status	Source
Linux	Linux	≥ 8ae6d9c7eb1004bc134813287010d57a863ba13b and < 53eb96c244d150dfb8cc4b5b0492ab53755f3701≥ 8ae6d9c7eb1004bc134813287010d57a863ba13b and < 6ee6dfd922fafd508f6bde16de30dd2db796b7a7≥ 8ae6d9c7eb1004bc134813287010d57a863ba13b and < e41d28d9a242c4005b7d01a7ee7769405a6a2c2e≥ 8ae6d9c7eb1004bc134813287010d57a863ba13b and < 626e44f3d8a924a97a3848a9fd45833947e081e9version 3.10	Vulnerable	CVE Program (cve.org) e CISA ADP

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

Not enough vector or weakness data: use the affected application’s logs as a starting point.

application logs

Timeline

What happened to this CVE, newest first.

2026
Record published
Oct 14, 2026
Affected products added · linux/linux
Oct 14, 2026 · CVE Program (cve.org) e CISA ADP
Source status changed · → Received
Oct 14, 2026 · NIST National Vulnerability Database
Record created in this database
Oct 14, 2026 · Alertas do Telegram
CVE published
Oct 14, 2026 · Linux

Source activity

Repeated readings are counted rather than listed.

1× References added · Oct 14, 2026 – Oct 14, 2026
1× Official description updated · Oct 14, 2026 – Oct 14, 2026

References

4 on the record

git.kernel.org/stable/c/626e44f3d8a924a97a3848a9fd45833947e081e9
NIST National Vulnerability Database
git.kernel.org/stable/c/6ee6dfd922fafd508f6bde16de30dd2db796b7a7
NIST National Vulnerability Database
git.kernel.org/stable/c/53eb96c244d150dfb8cc4b5b0492ab53755f3701
NIST National Vulnerability Database
git.kernel.org/stable/c/e41d28d9a242c4005b7d01a7ee7769405a6a2c2e
NIST National Vulnerability Database

Elsewhere on this site

Linux
every CVE for this vendor

Related CVEs (same products)

Critical CVE-2026-99999 ipv4: validate checksum_start before completing checksum 9h
Unknown CVE-2026-98432 ipv4: free inet_opt and ireq_opt after an RCU grace period 9h
Unknown CVE-2026-98427 net/sched: codel: bound the dropping loop per dequeue call 1d
Unknown CVE-2026-98429 RDMA/efa: Keep EQ resources alive while IRQ is registered 1d
Unknown CVE-2026-98428 ALSA: usb: 6fire: Avoid embedded URBs 1d
Unknown CVE-2026-98430 RDMA/efa: Keep admin queues alive while IRQ is registered 1d

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No CVSS score published by NVD, the CNA, CISA or GitHub so far.
No FIRST EPSS score.
No fixed version, patch or mitigation documented.
No CISA SSVC assessment.
No CWE classification.
No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-98386 is "scsi: qla2xxx: Use memset_io() to clear QLAFX00 request ring slot", rated Unknown. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.