Skip to content
Noroxi
CVE.org (no NVD analysis yet)· CNA Linux

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

Noroxi assessment

Priority: Monitor (action score 0/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.21% (FIRST EPSS).
  • Fixed version: Linux Linux 0eca1d7a4dac793224e6e295e29e00245e96cf16, 2df8c8630904794100189fa3d70598642e1877ce, 337026cf8149dcfedacd60d6d7081bff10ee5cd4; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 Release Notes; azl3 kernel 6.6.159.1-1 on Azure Linux 3.0 6.6.161.1-1.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 0eca1d7a4dac793224e6e295e29e00245e96cf16, 2df8c8630904794100189fa3d70598642e1877ce, 337026cf8149dcfedacd60d6d7081bff10ee5cd4; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 Release Notes; azl3 kernel 6.6.159.1-1 on Azure Linux 3.0 6.6.161.1-1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

—No exploit Fix available
Published
Oct 14, 2026
Updated
Oct 30, 2026
EPSS
0.2% · 12th percentile
CWE
—

Report tools

JSON

Action score

0

Monitor

Low priority for now.

CVSS
0 / 40 · —
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-98386

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 3.10affected
    • 8ae6d9c7eb1004bc134813287010d57a863ba13b and later · before 0eca1d7a4dac793224e6e295e29e00245e96cf16affected · git
    • 8ae6d9c7eb1004bc134813287010d57a863ba13b and later · before 337026cf8149dcfedacd60d6d7081bff10ee5cd4affected · git
    • 8ae6d9c7eb1004bc134813287010d57a863ba13b and later · before 6e8f1144d06cfd8cf8c346066efd8f572b28f768affected · git
    • 8ae6d9c7eb1004bc134813287010d57a863ba13b and later · before 2df8c8630904794100189fa3d70598642e1877ceaffected · git
    • 8ae6d9c7eb1004bc134813287010d57a863ba13b and later · before 53eb96c244d150dfb8cc4b5b0492ab53755f3701affected · git
    • 8ae6d9c7eb1004bc134813287010d57a863ba13b and later · before 6ee6dfd922fafd508f6bde16de30dd2db796b7a7affected · git
    • 8ae6d9c7eb1004bc134813287010d57a863ba13b and later · before e41d28d9a242c4005b7d01a7ee7769405a6a2c2eaffected · git
    • 8ae6d9c7eb1004bc134813287010d57a863ba13b and later · before 626e44f3d8a924a97a3848a9fd45833947e081e9affected · git
    • before 3.10not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxfrom 0—
Debian:12linux-6.12before 6.12.113-1~deb12u16.12.113-1~deb12u1
Debian:13linuxbefore 6.12.113-16.12.113-1
Debian:14linuxbefore 7.2.7-17.2.7-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2026-98384Oct 9, 2026 · bpf: Fix out-of-bounds read of sk_protocol in bpf_sock_destroy()
    0Monitor
  • ← EarlierCVE-2026-98385Oct 12, 2026 · sched/cache: Decouple sched_cache_group from mm to fix UAF
    31Monitor
  • Later →CVE-2026-98387Oct 14, 2026 · s390/crypto: Fix skcipher_walk return code handling in aes_s390
    0Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux0eca1d7a4dac793224e6e295e29e00245e96cf16Vendor (CNA)
Linux Linux2df8c8630904794100189fa3d70598642e1877ceVendor (CNA)
Linux Linux337026cf8149dcfedacd60d6d7081bff10ee5cd4Vendor (CNA)
Linux Linux53eb96c244d150dfb8cc4b5b0492ab53755f3701Vendor (CNA)
Linux Linux626e44f3d8a924a97a3848a9fd45833947e081e9Vendor (CNA)
Linux Linux6e8f1144d06cfd8cf8c346066efd8f572b28f768Vendor (CNA)
Linux Linux6ee6dfd922fafd508f6bde16de30dd2db796b7a7Vendor (CNA)
Linux Linuxe41d28d9a242c4005b7d01a7ee7769405a6a2c2eVendor (CNA)
azl3 kernel 6.6.157.1-1 on Azure Linux 3.0Release NotesMicrosoft (MSRC)
azl3 kernel 6.6.159.1-1 on Azure Linux 3.06.6.161.1-1 · Release NotesMicrosoft (MSRC)
debian:linux6.12.113-1 · Debian:13Package registry (OSV)
debian:linux7.2.7-1 · Debian:14Package registry (OSV)
debian:linux-6.126.12.113-1~deb12u1 · Debian:12Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

  1. Published
  2. Fix recordedsame day
  3. TodayNov 7, 2026+24 d
EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

Technical details

No CVSS vector for this record, so attack conditions can't be derived.

Weakness class (CWE)

—

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Exploit maturity— → none
  2. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (7 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records