{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-90008 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-90008 is a high-severity memory corruption vulnerability in Linux, published on 16 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-90008 and fix it if it is affected.\n\nWhat it is: CVE-2026-90008 is a high-severity memory corruption vulnerability in Linux, published on 16 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-90008 in the wild and no public exploit code.\n\nAffected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-90008/ (Markdown: https://insights.sbomify.com/CVE-2026-90008/index.md)","id":"CVE-2026-90008","markdown":"https://insights.sbomify.com/CVE-2026-90008/index.md","name":"CVE-2026-90008","record":{"aliases":["BELL-CVE-2026-90008","DEBIAN-CVE-2026-90008","GHSA-hvj3-hrq6-8jr2","UBUNTU-CVE-2026-90008"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service","data_modify"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel driver","requires_auth":"low_privilege","summary":"A buffer overflow in the megaraid_sas driver allows attackers to corrupt kernel memory, causing crashes or data integrity issues.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":7.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[],"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-\u003esg_frame, a\nDMA pool buffer of instance-\u003emax_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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"scsi: megaraid_sas: Limit NVMe request size to the PRP chain frame","id":"CVE-2026-90008","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"scsi: bsg: Fix TOCTOU in io_uring passthrough command setup","id":"CVE-2026-90009"},"packages":[],"prev":{"headline":"scsi: pm8001: Use rollback index when freeing MSI-X vectors","id":"CVE-2026-90007"},"products":["Linux"],"published":"2026-09-16","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-19","vendors":["Linux"]},"summary":"A buffer overflow in the megaraid_sas driver allows attackers to corrupt kernel memory, causing crashes or data integrity issues.","url":"https://insights.sbomify.com/CVE-2026-90008/"}