Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

Description

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.

Timeline

  1. ID reserved

    By Linux

  2. · 19 days later

    Published

  3. · 16 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.22% · top 88% of all CVEs (16 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected 8ae6d9c7eb1004bc134813287010d57a863ba13b – < 0eca1d7a4dac793224e6e295e29e00245e96cf16
    • affected 8ae6d9c7eb1004bc134813287010d57a863ba13b – < 337026cf8149dcfedacd60d6d7081bff10ee5cd4
    • affected 8ae6d9c7eb1004bc134813287010d57a863ba13b – < 6e8f1144d06cfd8cf8c346066efd8f572b28f768
    • affected 8ae6d9c7eb1004bc134813287010d57a863ba13b – < 2df8c8630904794100189fa3d70598642e1877ce
    • affected 8ae6d9c7eb1004bc134813287010d57a863ba13b – < 53eb96c244d150dfb8cc4b5b0492ab53755f3701
    • affected 8ae6d9c7eb1004bc134813287010d57a863ba13b – < 6ee6dfd922fafd508f6bde16de30dd2db796b7a7
    • affected 8ae6d9c7eb1004bc134813287010d57a863ba13b – < e41d28d9a242c4005b7d01a7ee7769405a6a2c2e
    • affected 8ae6d9c7eb1004bc134813287010d57a863ba13b – < 626e44f3d8a924a97a3848a9fd45833947e081e9
  • Linux · Linux

    • affected 3.10
    • unaffected < 3.10
    • unaffected 5.10.273 – ≤ 5.10.*
    • unaffected 5.15.224 – ≤ 5.15.*
    • unaffected 6.1.191 – ≤ 6.1.*
    • unaffected 6.6.160 – ≤ 6.6.*
    • unaffected 6.12.112 – ≤ 6.12.*
    • unaffected 6.18.53 – ≤ 6.18.*
    • unaffected 7.2.7 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-98386 badge
[![CVE-2026-98386](https://cveledger.app/badge/CVE-2026-98386.svg)](https://cveledger.app/cve/CVE-2026-98386)

Record last updated .