https://vulnerability.circl.lu Contains only the most 10 recent sightings. http://www.rssboard.org/rss-specification python-feedgen en Tue, 20 Oct 2026 05:35:44 +0000 https://vulnerability.circl.lu/sighting/4548e324-3662-4057-8e09-8a992ee190c7/export {"uuid": "4548e324-3662-4057-8e09-8a992ee190c7", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-98386", "type": "seen", "source": "https://infosec.exchange/users/cve/statuses/117440653753491197", "content": "CVE-2026-98386 scsi: qla2xxx: Use memset_io() to clear QLAFX00 request ring slot In the Linux kernel, the following vulnerability has been resolved:\nscsi: qla2xxx: Use memset_io() to clear QLAFX00 request ring slot\nFor QLAFX00 the request ring is ioremapped device I/O memory(ha->iobase + req_que_off), not DMA-coherent RAM, which is why the restof the FX00 path accesses it through memcpy_toio() and the wrt_reg_*helpers. __qla2x00_alloc_iocbs() however zeroed the producer slot with aplain memset(). On architectures such as ARM64 a regular memset() mayemit unaligned or block-zeroing instructions (e.g. DC ZVA) that areinvalid on Device memory, leading to a synchronous external abort.\nUse memset_io() to clear the slot for QLAFX00, matching the I/Oaccessors used elsewhere on this ring. Other adapters keep the plainmemset() on their DMA-coherent rings. The zero-fill is retained for FX00because its IOCB builders (e.g. qlafx00_fxdisc_iocb()) copy only part ofthe entry and rely on the unused tail being pre-zeroed.\nhttps://www.cve.org/CVERecord?id=CVE-2026-98386https://git.kernel.org/stable/c/53eb96c244d150dfb8cc4b5b0492ab53755f3701https://git.kernel.org/stable/c/6ee6dfd922fafd508f6bde16de30dd2db796b7a7https://git.kernel.org/stable/c/e41d28d9a242c4005b7d01a7ee7769405a6a2c2ehttps://git.kernel.org/stable/c/626e44f3d8a924a97a3848a9fd45833947e081e9#kernel #Linux#CVE_2026_98386#bot", "creation_timestamp": "2026-10-14T18:22:43.550047Z"} {"uuid": "4548e324-3662-4057-8e09-8a992ee190c7", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-98386", "type": "seen", "source": "https://infosec.exchange/users/cve/statuses/117440653753491197", "content": "CVE-2026-98386 scsi: qla2xxx: Use memset_io() to clear QLAFX00 request ring slot In the Linux kernel, the following vulnerability has been resolved:\nscsi: qla2xxx: Use memset_io() to clear QLAFX00 request ring slot\nFor QLAFX00 the request ring is ioremapped device I/O memory(ha->iobase + req_que_off), not DMA-coherent RAM, which is why the restof the FX00 path accesses it through memcpy_toio() and the wrt_reg_*helpers. __qla2x00_alloc_iocbs() however zeroed the producer slot with aplain memset(). On architectures such as ARM64 a regular memset() mayemit unaligned or block-zeroing instructions (e.g. DC ZVA) that areinvalid on Device memory, leading to a synchronous external abort.\nUse memset_io() to clear the slot for QLAFX00, matching the I/Oaccessors used elsewhere on this ring. Other adapters keep the plainmemset() on their DMA-coherent rings. The zero-fill is retained for FX00because its IOCB builders (e.g. qlafx00_fxdisc_iocb()) copy only part ofthe entry and rely on the unused tail being pre-zeroed.\nhttps://www.cve.org/CVERecord?id=CVE-2026-98386https://git.kernel.org/stable/c/53eb96c244d150dfb8cc4b5b0492ab53755f3701https://git.kernel.org/stable/c/6ee6dfd922fafd508f6bde16de30dd2db796b7a7https://git.kernel.org/stable/c/e41d28d9a242c4005b7d01a7ee7769405a6a2c2ehttps://git.kernel.org/stable/c/626e44f3d8a924a97a3848a9fd45833947e081e9#kernel #Linux#CVE_2026_98386#bot", "creation_timestamp": "2026-10-14T18:22:43.550047Z"} https://vulnerability.circl.lu/sighting/4548e324-3662-4057-8e09-8a992ee190c7/export Wed, 14 Oct 2026 18:22:43 +0000