{"api_version":"1","generated_at":"2026-09-16T16:40:36+00:00","cve":"CVE-2026-90008","urls":{"html":"https://cve.report/CVE-2026-90008","api":"https://cve.report/api/cve/CVE-2026-90008.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-90008","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-90008"},"summary":{"title":"scsi: megaraid_sas: Limit NVMe request size to the PRP chain frame","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nscsi: megaraid_sas: Limit NVMe request size to the PRP chain frame\n\nmegasas_make_prp_nvme() builds a command's PRP list in cmd->sg_frame, a\nDMA pool buffer of instance->max_chain_frame_sz bytes, spending one\nentry per NVMe page of the transfer plus one per page of the buffer for\nthe chain pointer. The loop runs until the transfer is described and\nnever checks the buffer bound.\n\nmax_hw_sectors comes straight from the MDTS the firmware reports for the\ndrive. On drives with a large MDTS the only thing keeping the list\ninside the buffer was the block layer default of 1280 KiB, which needs\n320 entries, which fit into a 4 KiB frame as that holds 512. But since\ncommit 9b8b84879d4a (\"block: Increase BLK_DEF_MAX_SECTORS_CAP\") that\ndefault is 4 MiB, and such a transfer needs 1025 entries, so the list\nruns a full page past the end of the frame:\n\n  sd 1:0:1:0: [sdb] tag#630 page boundary ptr_sgl: 0x00000000ba62d13f\n  BUG: unable to handle page fault for address: ff663bcb81e7c000\n  #PF: supervisor write access in kernel mode\n  #PF: error_code(0x0002) - not-present page\n  RIP: 0010:megasas_build_and_issue_cmd_fusion+0xeaa/0x1870 [megaraid_sas]\n\nIf the page after the frame happens to be mapped, the overrun does not\nfault but silently corrupts the neighbouring pool entry, which is\nanother in-flight command's PRP list.\n\nCap max_hw_sectors at what the chain frame can describe, less one page\nfor transfers that do not start on a page boundary and so need one entry\nmore. This is the megaraid_sas counterpart of commit 04631f55afc5\n(\"scsi: mpt3sas: Limit NVMe request size to 2 MiB\"), but derives the\nlimit from max_chain_frame_sz rather than hardcoding it.","state":"PUBLISHED","assigner":"Linux","published_at":"2026-09-16 11:17:13","updated_at":"2026-09-16 15:18:24"},"problem_types":[],"metrics":[{"version":"3.1","source":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","type":"Secondary","score":"7.8","severity":"HIGH","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","data":{"version":"3.1","vectorString":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","baseScore":7.8,"baseSeverity":"HIGH","attackVector":"LOCAL","attackComplexity":"LOW","privilegesRequired":"LOW","userInteraction":"NONE","scope":"UNCHANGED","confidentialityImpact":"HIGH","integrityImpact":"HIGH","availabilityImpact":"HIGH"}},{"version":"3.1","source":"CNA","type":"DECLARED","score":"7.8","severity":"HIGH","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","data":{"baseScore":7.8,"baseSeverity":"HIGH","vectorString":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"}}],"references":[{"url":"https://git.kernel.org/stable/c/4dd118d06dec9efe5065ac7897bdc18f404a3af4","name":"https://git.kernel.org/stable/c/4dd118d06dec9efe5065ac7897bdc18f404a3af4","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/af8c27375733fb6a6df9fa484cda77cc3dd0cb80","name":"https://git.kernel.org/stable/c/af8c27375733fb6a6df9fa484cda77cc3dd0cb80","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/4bb34769ef44ab3770b89e4055de6af4a458bec9","name":"https://git.kernel.org/stable/c/4bb34769ef44ab3770b89e4055de6af4a458bec9","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-90008","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-90008","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 9b8b84879d4adc506b0d3944e20b28d9f3f6994b 4bb34769ef44ab3770b89e4055de6af4a458bec9 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 9b8b84879d4adc506b0d3944e20b28d9f3f6994b 4dd118d06dec9efe5065ac7897bdc18f404a3af4 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 9b8b84879d4adc506b0d3944e20b28d9f3f6994b af8c27375733fb6a6df9fa484cda77cc3dd0cb80 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 6.17","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.17 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.18.51 6.18.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.2.5 7.2.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.3-rc2 * original_commit_for_fix","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":null,"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"defaultStatus":"unaffected","product":"Linux","programFiles":["drivers/scsi/megaraid/megaraid_sas_base.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"4bb34769ef44ab3770b89e4055de6af4a458bec9","status":"affected","version":"9b8b84879d4adc506b0d3944e20b28d9f3f6994b","versionType":"git"},{"lessThan":"4dd118d06dec9efe5065ac7897bdc18f404a3af4","status":"affected","version":"9b8b84879d4adc506b0d3944e20b28d9f3f6994b","versionType":"git"},{"lessThan":"af8c27375733fb6a6df9fa484cda77cc3dd0cb80","status":"affected","version":"9b8b84879d4adc506b0d3944e20b28d9f3f6994b","versionType":"git"}]},{"defaultStatus":"affected","product":"Linux","programFiles":["drivers/scsi/megaraid/megaraid_sas_base.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"status":"affected","version":"6.17"},{"lessThan":"6.17","status":"unaffected","version":"0","versionType":"semver"},{"lessThanOrEqual":"6.18.*","status":"unaffected","version":"6.18.51","versionType":"semver"},{"lessThanOrEqual":"7.2.*","status":"unaffected","version":"7.2.5","versionType":"semver"},{"lessThanOrEqual":"*","status":"unaffected","version":"7.3-rc2","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"cpeMatch":[{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.18.51","versionStartIncluding":"6.17","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.2.5","versionStartIncluding":"6.17","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.3-rc2","versionStartIncluding":"6.17","vulnerable":true}],"negate":false,"operator":"OR"}]}],"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\nscsi: megaraid_sas: Limit NVMe request size to the PRP chain frame\n\nmegasas_make_prp_nvme() builds a command's PRP list in cmd->sg_frame, a\nDMA pool buffer of instance->max_chain_frame_sz bytes, spending one\nentry per NVMe page of the transfer plus one per page of the buffer for\nthe chain pointer. The loop runs until the transfer is described and\nnever checks the buffer bound.\n\nmax_hw_sectors comes straight from the MDTS the firmware reports for the\ndrive. On drives with a large MDTS the only thing keeping the list\ninside the buffer was the block layer default of 1280 KiB, which needs\n320 entries, which fit into a 4 KiB frame as that holds 512. But since\ncommit 9b8b84879d4a (\"block: Increase BLK_DEF_MAX_SECTORS_CAP\") that\ndefault is 4 MiB, and such a transfer needs 1025 entries, so the list\nruns a full page past the end of the frame:\n\n  sd 1:0:1:0: [sdb] tag#630 page boundary ptr_sgl: 0x00000000ba62d13f\n  BUG: unable to handle page fault for address: ff663bcb81e7c000\n  #PF: supervisor write access in kernel mode\n  #PF: error_code(0x0002) - not-present page\n  RIP: 0010:megasas_build_and_issue_cmd_fusion+0xeaa/0x1870 [megaraid_sas]\n\nIf the page after the frame happens to be mapped, the overrun does not\nfault but silently corrupts the neighbouring pool entry, which is\nanother in-flight command's PRP list.\n\nCap max_hw_sectors at what the chain frame can describe, less one page\nfor transfers that do not start on a page boundary and so need one entry\nmore. This is the megaraid_sas counterpart of commit 04631f55afc5\n(\"scsi: mpt3sas: Limit NVMe request size to 2 MiB\"), but derives the\nlimit from max_chain_frame_sz rather than hardcoding it."}],"metrics":[{"cvssV3_1":{"baseScore":7.8,"baseSeverity":"HIGH","vectorString":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"scenarios":[{"lang":"en","value":"AV:L - The overflow is in megaraid_sas while building NVMe PRP lists for SCSI commands from the local block layer (queuecommand → megasas_build_and_issue_cmd_fusion → megasas_make_prp_nvme); the HBA driver is not bound to the network stack.\nAC:L - On MegaRAID NVMe Fast Path with a firmware MDTS above the 4 KiB chain-frame capacity, a single 4 MiB I/O (the post-6.17 block-layer default) drives the unbounded PRP loop past cmd->sg_frame with no race or other condition outside the attacker’s control.\nPR:L - An unprivileged local user who can read or write a file or block device on the NVMe-backed volume can submit a large O_DIRECT or sequential I/O that the block layer issues as one request; the megaraid ioctl CAP_SYS_ADMIN check is not on this path.\nUI:N - The attacker triggers the overflow directly by submitting their own I/O; no separate victim action is required.\nS:U - The out-of-bounds write corrupts host-kernel DMA-pool memory of the same HBA; it is not a VM escape, IOMMU bypass, or other cross-authority impact.\nC:H - The write overruns the PRP chain frame into the neighbouring dma_pool object, another in-flight command’s PRP list, so DMA can be redirected to attacker-controlled buffers and disclose other I/O or kernel memory.\nI:H - This is an unbounded out-of-bounds write of DMA addresses past a fixed-size sg_frame, corrupting adjacent kernel/DMA-pool memory and enabling integrity violation and control-flow or DMA hijacking.\nA:H - When the page after the frame is unmapped the overrun causes a kernel page-fault oops in megasas_build_and_issue_cmd_fusion, as documented in the fix; neighbouring-command corruption can also panic or hang the host."}]}],"providerMetadata":{"dateUpdated":"2026-09-16T14:41:23.445Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/4bb34769ef44ab3770b89e4055de6af4a458bec9"},{"url":"https://git.kernel.org/stable/c/4dd118d06dec9efe5065ac7897bdc18f404a3af4"},{"url":"https://git.kernel.org/stable/c/af8c27375733fb6a6df9fa484cda77cc3dd0cb80"}],"title":"scsi: megaraid_sas: Limit NVMe request size to the PRP chain frame","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-90008","datePublished":"2026-09-16T10:33:16.772Z","dateReserved":"2026-09-11T19:38:34.781Z","dateUpdated":"2026-09-16T14:41:23.445Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-09-16 11:17:13","lastModifiedDate":"2026-09-16 15:18:24","problem_types":[],"metrics":{"cvssMetricV31":[{"source":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","type":"Secondary","cvssData":{"version":"3.1","vectorString":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","baseScore":7.8,"baseSeverity":"HIGH","attackVector":"LOCAL","attackComplexity":"LOW","privilegesRequired":"LOW","userInteraction":"NONE","scope":"UNCHANGED","confidentialityImpact":"HIGH","integrityImpact":"HIGH","availabilityImpact":"HIGH"},"exploitabilityScore":1.8,"impactScore":5.9}]},"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"90008","Ordinal":"1","Title":"scsi: megaraid_sas: Limit NVMe request size to the PRP chain fra","CVE":"CVE-2026-90008","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"90008","Ordinal":"1","NoteData":"In the Linux kernel, the following vulnerability has been resolved:\n\nscsi: megaraid_sas: Limit NVMe request size to the PRP chain frame\n\nmegasas_make_prp_nvme() builds a command's PRP list in cmd->sg_frame, a\nDMA pool buffer of instance->max_chain_frame_sz bytes, spending one\nentry per NVMe page of the transfer plus one per page of the buffer for\nthe chain pointer. The loop runs until the transfer is described and\nnever checks the buffer bound.\n\nmax_hw_sectors comes straight from the MDTS the firmware reports for the\ndrive. On drives with a large MDTS the only thing keeping the list\ninside the buffer was the block layer default of 1280 KiB, which needs\n320 entries, which fit into a 4 KiB frame as that holds 512. But since\ncommit 9b8b84879d4a (\"block: Increase BLK_DEF_MAX_SECTORS_CAP\") that\ndefault is 4 MiB, and such a transfer needs 1025 entries, so the list\nruns a full page past the end of the frame:\n\n  sd 1:0:1:0: [sdb] tag#630 page boundary ptr_sgl: 0x00000000ba62d13f\n  BUG: unable to handle page fault for address: ff663bcb81e7c000\n  #PF: supervisor write access in kernel mode\n  #PF: error_code(0x0002) - not-present page\n  RIP: 0010:megasas_build_and_issue_cmd_fusion+0xeaa/0x1870 [megaraid_sas]\n\nIf the page after the frame happens to be mapped, the overrun does not\nfault but silently corrupts the neighbouring pool entry, which is\nanother in-flight command's PRP list.\n\nCap max_hw_sectors at what the chain frame can describe, less one page\nfor transfers that do not start on a page boundary and so need one entry\nmore. This is the megaraid_sas counterpart of commit 04631f55afc5\n(\"scsi: mpt3sas: Limit NVMe request size to 2 MiB\"), but derives the\nlimit from max_chain_frame_sz rather than hardcoding it.","Type":"Description","Title":"scsi: megaraid_sas: Limit NVMe request size to the PRP chain fra"}]}}}