PoC Monitor
← All CVEs
CVE-2026-90008published 16 Sep 2026 10:33 UTCData: JSON · API

Linux

scsi: megaraid_sas: Limit NVMe request size to the PRP chain frame

In the Linux kernel, the following vulnerability has been resolved: scsi: megaraid_sas: Limit NVMe request size to the PRP chain frame megasas_make_prp_nvme() builds a command's PRP list in cmd->sg_frame, a DMA pool buffer of instance->max_chain_frame_sz bytes, spending one entry per NVMe page of the transfer plus one per page of the buffer for the chain pointer. The loop runs until the transfer is described and never checks the buffer bound. max_hw_sectors comes straight from the MDTS the firmware reports for the drive. On drives with a large MDTS the only thing keeping the list inside the buffer was the block layer default of 1280 KiB, which needs 320 entries, which fit into a 4 KiB frame as that holds 512. But since commit 9b8b84879d4a ("block: Increase BLK_DEF_MAX_SECTORS_CAP") that default is 4 MiB, and such a transfer needs 1025 entries, so the list runs a full page past the end of the frame: sd 1:0:1:0: [sdb] tag#630 page boundary ptr_sgl: 0x00000000ba62d13f BUG: unable to handle page fault for address: ff663bcb81e7c000 #PF: supervisor write access in kernel mode #PF: error_code(0x0002) - not-present page RIP: 0010:megasas_build_and_issue_cmd_fusion+0xeaa/0x1870 [megaraid_sas] If the page after the frame happens to be mapped, the overrun does not fault but silently corrupts the neighbouring pool entry, which is another in-flight command's PRP list. Cap max_hw_sectors at what the chain frame can describe, less one page for transfers that do not start on a page boundary and so need one entry more. This is the megaraid_sas counterpart of commit 04631f55afc5 ("scsi: mpt3sas: Limit NVMe request size to 2 MiB"), but derives the limit from max_chain_frame_sz rather than hardcoding it.

First public PoC None yetno public PoC found
Public PoCs00 on GitHub
CVSS7.8high · scored by CNA
CISA KEV Not listednot known exploited

Affected versions and mitigation

From the CVE record and the vendor's references.

Affected

Linux Linux
  • >= 9b8b84879d4adc506b0d3944e20b28d9f3f6994b, < 4bb34769ef44ab3770b89e4055de6af4a458bec9
  • >= 9b8b84879d4adc506b0d3944e20b28d9f3f6994b, < 4dd118d06dec9efe5065ac7897bdc18f404a3af4
  • >= 9b8b84879d4adc506b0d3944e20b28d9f3f6994b, < af8c27375733fb6a6df9fa484cda77cc3dd0cb80

Fixed in 4bb34769ef44ab3770b89e4055de6af4a458bec9, 4dd118d06dec9efe5065ac7897bdc18f404a3af4, af8c27375733fb6a6df9fa484cda77cc3dd0cb80

Linux Linux
  • 6.17

Fixed in 0, 6.18.51, 7.2.5, 7.3

Mitigation

Upgrade Linux to 4bb34769ef44ab3770b89e4055de6af4a458bec9 or 4dd118d06dec9efe5065ac7897bdc18f404a3af4 or af8c27375733fb6a6df9fa484cda77cc3dd0cb80 or later.

Upgrade Linux to 0 or 6.18.51 or 7.2.5 or 7.3 or later.

Timeline

Days relative to CVE publication
-2t=0+2+4+6+8CVE published16 Sep 2026 · t = 0

No public PoC found yet; not in CISA KEV.

PoC repositories

Found on GitHub.

No PoC repositories found yet.