CVE-2026-93048: Software Security Vulnerability Vulnerability

UNKNOWN
Advisory Identifier: GHSA-2p6r-8jww-x7j3
Share
Published
Advisory Summary

CVE-2026-93048 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-93048 at a Glance

CVE Identifier CVE-2026-93048
GHSA Identifier GHSA-2p6r-8jww-x7j3
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-93048

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-93048, 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: mtd: part: reject MTDPART_OFS_RETAIN in mtd_add_partition() mtd_add_partition() does not reject the special offset value MTDPART_OFS_RETAIN (-3), which leads to a WARN_ON in add_mtd_device() when called through the BLKPG ioctl on NAND devices. The RETAIN value depends on cur_offset being the end of the previous partition, but in the dynamic partition path cur_offset equals the offset argument itself, causing undefined behavior. Commit 5daa7b21496a ("mtd: prepare partition add and del functions for ioctl requests") introduced mtd_add_partition() and correctly rejected MTDPART_OFS_APPEND (-1) and MTDPART_OFS_NXTBLK (-2), since those special offsets rely on cur_offset tracking the previous partition's end. However, commit 1a31368bf92e ("mtd: add a flags for partitions which should just leave smth. after them") later added MTDPART_OFS_RETAIN (-3) for the static partition table path without updating mtd_add_partition() to also reject this value. With offset=-3 passed via BLKPG, the RETAIN size calculation in allocate_partition() underflows (parent_size - 0xFFFFFFFFFFFFFFFD = parent_size + 3). If the underflow result does not appear to leave enough space, allocate_partition() jumps to out_register via goto, skipping erasesize initialization. This results in erasesize=0, which triggers: WARN_ON((!mtd->erasesize || !master->_erase) && !(mtd->flags & MTD_NO_ERASE)) in add_mtd_device(). If the underflow result appears to leave enough space, a bogus partition size is calculated, but the "out of reach" sanity check catches the invalid offset and creates a disabled empty partition (offset=0, size=0) instead of returning an error. Fix this by adding MTDPART_OFS_RETAIN to the rejection list in mtd_add_partition(), consistent with the existing handling of APPEND and NXTBLK.

References

NVD — CVE-2026-93048 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-93048
git.kernel.org/stable/c/181c1bff94... WEB
https://git.kernel.org/stable/c/181c1bff940e7d3e34ca485d37e3cdbfe409203c
git.kernel.org/stable/c/398aca2f90... WEB
https://git.kernel.org/stable/c/398aca2f90122d5abbabff1079deaeb885fe9e40
git.kernel.org/stable/c/6aaab2ace3... WEB
https://git.kernel.org/stable/c/6aaab2ace3f7b55733d904e5549acf8405f03642
git.kernel.org/stable/c/701c3ae727... WEB
https://git.kernel.org/stable/c/701c3ae7273e1adc20db5d97c42e0139b479f16b
git.kernel.org/stable/c/a536eb57be... WEB
https://git.kernel.org/stable/c/a536eb57be58442b19398b2783071007ecfb1735
git.kernel.org/stable/c/b759d5bb62... WEB
https://git.kernel.org/stable/c/b759d5bb6265419344ee9729fd0dc07ad85719d8
git.kernel.org/stable/c/c645f6dd1a... WEB
https://git.kernel.org/stable/c/c645f6dd1af2ecc70fd3578e141f2f71fa9e4eff
git.kernel.org/stable/c/e204e5c49a... WEB
https://git.kernel.org/stable/c/e204e5c49a012f99638633fdbd773e3c86260053

Frequently Asked Questions

What is CVE-2026-93048?
CVE-2026-93048 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-93048?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What CWE is associated with CVE-2026-93048?
CVE-2026-93048 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-93048?
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-2p6r-8jww-x7j3",
  "modified" : "2026-09-17T18:32:08Z",
  "published" : "2026-09-17T18:32:08Z",
  "aliases" : [ "CVE-2026-93048" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nmtd: part: reject MTDPART_OFS_RETAIN in mtd_add_partition()\n\nmtd_add_partition() does not reject the special offset value\nMTDPART_OFS_RETAIN (-3), which leads to a WARN_ON in\nadd_mtd_device() when called through the BLKPG ioctl on NAND\ndevices. The RETAIN value depends on cur_offset being the end of\nthe previous partition, but in the dynamic partition path\ncur_offset equals the offset argument itself, causing undefined\nbehavior.\n\nCommit 5daa7b21496a (\"mtd: prepare partition add and del functions\nfor ioctl requests\") introduced mtd_add_partition() and correctly\nrejected MTDPART_OFS_APPEND (-1) and MTDPART_OFS_NXTBLK (-2),\nsince those special offsets rely on cur_offset tracking the\nprevious partition's end. However, commit 1a31368bf92e (\"mtd: add a flags\nfor partitions which should just leave smth. after them\")\nlater added MTDPART_OFS_RETAIN (-3) for the static\npartition table path without updating mtd_add_partition() to\nalso reject this value.\n\nWith offset=-3 passed via BLKPG, the RETAIN size calculation in\nallocate_partition() underflows (parent_size - 0xFFFFFFFFFFFFFFFD\n= parent_size + 3). If the underflow result does not appear to\nleave enough space, allocate_partition() jumps to out_register via\ngoto, skipping erasesize initialization. This results in\nerasesize=0, which triggers:\n\nWARN_ON((!mtd->erasesize || !master->_erase) &&\n\t\t!(mtd->flags & MTD_NO_ERASE))\n\nin add_mtd_device(). If the underflow result appears to leave\nenough space, a bogus partition size is calculated, but the\n\"out of reach\" sanity check catches the invalid offset and\ncreates a disabled empty partition (offset=0, size=0) instead\nof returning an error.\n\nFix this by adding MTDPART_OFS_RETAIN to the rejection list in\nmtd_add_partition(), consistent with the existing handling of\nAPPEND and NXTBLK.",
  "severity" : [ ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-93048"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/181c1bff940e7d3e34ca485d37e3cdbfe409203c"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/398aca2f90122d5abbabff1079deaeb885fe9e40"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/6aaab2ace3f7b55733d904e5549acf8405f03642"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/701c3ae7273e1adc20db5d97c42e0139b479f16b"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/a536eb57be58442b19398b2783071007ecfb1735"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/b759d5bb6265419344ee9729fd0dc07ad85719d8"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/c645f6dd1af2ecc70fd3578e141f2f71fa9e4eff"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/e204e5c49a012f99638633fdbd773e3c86260053"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : null,
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-09-17T17:17:58Z"
  }
}