CVE-2026-90251: Software Security Vulnerability Vulnerability

UNKNOWN
Advisory Identifier: GHSA-hmjm-jgv8-x76g
Share
Published
Advisory Summary

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

CVE-2026-90251 at a Glance

CVE Identifier CVE-2026-90251
GHSA Identifier GHSA-hmjm-jgv8-x76g
Severity N/A
CVSS v3.1 Base Score N/A
CWE Classification General Security Weakness
Affected Product Software
Package Ecosystem Maven
Published Date
Last Updated

How to Fix CVE-2026-90251

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-90251, 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: Bluetooth: MSFT: validate evt_prefix_len against the response length read_supported_features() only checks that the response covers the fixed part of struct msft_rp_read_supported_features, which is 11 bytes: if (skb->len < sizeof(*rp)) { bt_dev_err(hdev, "MSFT supported features length mismatch"); goto failed; } evt_prefix[] is a flexible array member and rp->evt_prefix_len is an unvalidated u8 taken straight out of that response, so msft->evt_prefix = kmemdup(rp->evt_prefix, rp->evt_prefix_len, GFP_KERNEL); copies up to 255 bytes from a reply that may have carried none of them. What is copied is data the controller never sent, and it is then used to match incoming vendor events in msft_vendor_evt(). This is not an out-of-bounds access. An skb data allocation always has at least SKB_DATA_ALIGN(sizeof(struct skb_shared_info)) bytes past the payload, which is more than the 255 byte maximum, so the read stays inside the allocation and KASAN does not report it. It is still a read of bytes the host was never given, with the length fully controlled by the controller. Reject a response that is too short for the prefix it declares. Verified with an emulated controller over /dev/vhci on a KASAN kernel, with vhci made to advertise an MSFT opcode the way btintel, btqca, btmtk and btrtl do unconditionally. A reply of exactly 11 bytes declaring evt_prefix_len = 255 reaches kmemdup and copies 255 bytes ("skb->len=11 evt_prefix_len=255", with the copied buffer dumped); since the reply ends at the fixed part, all 255 come from past the end of the response. No KASAN report is produced, as expected from the allocation slack described above. With this patch the response is rejected with "MSFT event prefix length mismatch" and msft->evt_prefix is left unset.

References

NVD — CVE-2026-90251 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-90251
git.kernel.org/stable/c/0079e1a944... WEB
https://git.kernel.org/stable/c/0079e1a944634ab2dc1c7cdec1144486d096407e
git.kernel.org/stable/c/21f539c59e... WEB
https://git.kernel.org/stable/c/21f539c59ed330b671d75fd119c5f659ff92fbd1
git.kernel.org/stable/c/52b1b3b4d4... WEB
https://git.kernel.org/stable/c/52b1b3b4d403cbda1b70ce2385e1a71f166a87ba
git.kernel.org/stable/c/620c2631cf... WEB
https://git.kernel.org/stable/c/620c2631cff490d14d0b9d56f185cc745806d6d7
git.kernel.org/stable/c/63562cfaea... WEB
https://git.kernel.org/stable/c/63562cfaea8a650fdb31ee8de21c32e3600be642
git.kernel.org/stable/c/7c2658023d... WEB
https://git.kernel.org/stable/c/7c2658023d839b651368a5b8b781bf9a817647cb
git.kernel.org/stable/c/dce783a10e... WEB
https://git.kernel.org/stable/c/dce783a10e70f013410f5b583a29fc3286899629
git.kernel.org/stable/c/e804d54a5a... WEB
https://git.kernel.org/stable/c/e804d54a5a99d99250490e68093eff7190472e6f

Frequently Asked Questions

What is CVE-2026-90251?
CVE-2026-90251 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-90251?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What CWE is associated with CVE-2026-90251?
CVE-2026-90251 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-90251?
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-hmjm-jgv8-x76g",
  "modified" : "2026-09-17T18:31:57Z",
  "published" : "2026-09-17T18:31:57Z",
  "aliases" : [ "CVE-2026-90251" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: MSFT: validate evt_prefix_len against the response length\n\nread_supported_features() only checks that the response covers the fixed\npart of struct msft_rp_read_supported_features, which is 11 bytes:\n\n\tif (skb->len < sizeof(*rp)) {\n\t\tbt_dev_err(hdev, \"MSFT supported features length mismatch\");\n\t\tgoto failed;\n\t}\n\nevt_prefix[] is a flexible array member and rp->evt_prefix_len is an\nunvalidated u8 taken straight out of that response, so\n\n\tmsft->evt_prefix = kmemdup(rp->evt_prefix, rp->evt_prefix_len,\n\t\t\t\t   GFP_KERNEL);\n\ncopies up to 255 bytes from a reply that may have carried none of them.\nWhat is copied is data the controller never sent, and it is then used to\nmatch incoming vendor events in msft_vendor_evt().\n\nThis is not an out-of-bounds access. An skb data allocation always has\nat least SKB_DATA_ALIGN(sizeof(struct skb_shared_info)) bytes past the\npayload, which is more than the 255 byte maximum, so the read stays\ninside the allocation and KASAN does not report it. It is still a read\nof bytes the host was never given, with the length fully controlled by\nthe controller.\n\nReject a response that is too short for the prefix it declares.\n\nVerified with an emulated controller over /dev/vhci on a KASAN kernel,\nwith vhci made to advertise an MSFT opcode the way btintel, btqca, btmtk\nand btrtl do unconditionally. A reply of exactly 11 bytes declaring\nevt_prefix_len = 255 reaches kmemdup and copies 255 bytes\n(\"skb->len=11 evt_prefix_len=255\", with the copied buffer dumped); since\nthe reply ends at the fixed part, all 255 come from past the end of the\nresponse. No KASAN report is produced, as expected from the allocation\nslack described above. With this patch the response is rejected with\n\"MSFT event prefix length mismatch\" and msft->evt_prefix is left unset.",
  "severity" : [ ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-90251"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/0079e1a944634ab2dc1c7cdec1144486d096407e"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/21f539c59ed330b671d75fd119c5f659ff92fbd1"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/52b1b3b4d403cbda1b70ce2385e1a71f166a87ba"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/620c2631cff490d14d0b9d56f185cc745806d6d7"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/63562cfaea8a650fdb31ee8de21c32e3600be642"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/7c2658023d839b651368a5b8b781bf9a817647cb"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/dce783a10e70f013410f5b583a29fc3286899629"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/e804d54a5a99d99250490e68093eff7190472e6f"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : null,
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-09-17T17:17:21Z"
  }
}