CVE-2026-90008: Software Security Vulnerability Vulnerability

HIGH
Advisory Identifier: GHSA-hvj3-hrq6-8jr2
Share
CVSS 7.8
Published
Advisory Summary

CVE-2026-90008 is a HIGH (CVSS 7.8) security vulnerability vulnerability (General Security Weakness) affecting Software libraries in the Maven ecosystem. Remediation is available in the latest vendor maintenance releases.

CVE-2026-90008 at a Glance

CVE Identifier CVE-2026-90008
GHSA Identifier GHSA-hvj3-hrq6-8jr2
Severity HIGH
CVSS v3.1 Base Score 7.8
CWE Classification General Security Weakness
Affected Product Software
Package Ecosystem Maven
Published Date
Last Updated

Security Impact

CVSS: 7.8

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H).

Attack Vector Local (AV:L)
Attack Complexity Low (AC:L)
Privileges Required Low (PR:L)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality High (C:H)
Integrity High (I:H)
Availability High (A:H)

How to Fix CVE-2026-90008

To remediate this vulnerability, upgrade all affected Software dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

mvn dependency:tree

How to Check if You Are Affected

To determine whether your Java application is affected by CVE-2026-90008, inspect your build dependencies using the Maven Dependency Plugin:

mvn dependency:tree

Analyze the terminal output to locate any version of Software in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than the patched release), your application is affected.

Note: The mvn dependency:tree command inspects the resolved dependency graph declared in your project's POM files; it does not perform automated security scanning or inspect runtime dynamic classpaths. Always verify runtime container classpaths and shaded JARs.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under General Security Weakness. In Software, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

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.

References

NVD — CVE-2026-90008 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-90008
git.kernel.org/stable/c/4bb34769ef... WEB
https://git.kernel.org/stable/c/4bb34769ef44ab3770b89e4055de6af4a458bec9
git.kernel.org/stable/c/4dd118d06d... WEB
https://git.kernel.org/stable/c/4dd118d06dec9efe5065ac7897bdc18f404a3af4
git.kernel.org/stable/c/af8c273757... WEB
https://git.kernel.org/stable/c/af8c27375733fb6a6df9fa484cda77cc3dd0cb80

Frequently Asked Questions

What is CVE-2026-90008?
CVE-2026-90008 is a security vulnerability in Software classified as a security vulnerability vulnerability under General Security Weakness.
Which Software versions are affected?
Affected versions include releases prior to current release patches.
What version fixes CVE-2026-90008?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What is the CVSS score of CVE-2026-90008?
CVE-2026-90008 has a CVSS v3.1 base score of 7.8 (HIGH) with vector string CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H.
What CWE is associated with CVE-2026-90008?
CVE-2026-90008 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-90008?
Run the dependency tree command: 'mvn dependency:tree'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-hvj3-hrq6-8jr2",
  "modified" : "2026-09-16T15:31:06Z",
  "published" : "2026-09-16T12:30:45Z",
  "aliases" : [ "CVE-2026-90008" ],
  "details" : "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.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H"
  } ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-90008"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/4bb34769ef44ab3770b89e4055de6af4a458bec9"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/4dd118d06dec9efe5065ac7897bdc18f404a3af4"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/af8c27375733fb6a6df9fa484cda77cc3dd0cb80"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : "HIGH",
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-09-16T11:17:13Z"
  }
}