CVE-2026-68416: Software Security Vulnerability Vulnerability

UNKNOWN
Advisory Identifier: GHSA-qpvq-4872-pr63
Share
Published
Advisory Summary

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

CVE Identifier CVE-2026-68416
GHSA Identifier GHSA-qpvq-4872-pr63
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-68416

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-68416, 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: fix double free and WARN_ON in add_mtd_device() error paths When device_register() or mtd_nvmem_add() fails inside add_mtd_device() for a partition, the error handling triggers mtd_release() via put_device() or device_unregister(). mtd_release() calls release_mtd_partition() which frees the mtd_info structure. However, callers such as mtd_add_partition() and add_mtd_partitions() also call free_partition() in their error paths, resulting in a double free. Additionally, release_mtd_partition() hits WARN_ON(!list_empty( &mtd->part.node)) because the partition node is still linked in the parent's partitions list when the release callback fires from the add_mtd_device() error path. Fix this by overriding dev->type and dev->release before put_device() in the error paths, so that device_release() invokes a no-op function instead of mtd_release(). For the mtd_nvmem_add() failure case, device_unregister() is replaced with device_del() to separate the device removal from the final kobject reference drop, allowing the override to take effect before put_device() is called. The callers' error paths (list_del + free_partition) remain the sole owners of mtd_info lifetime on add_mtd_device() failure, which is the expected contract. The normal partition teardown path is not affected: del_mtd_device() goes through kref_put() -> mtd_device_release() -> device_unregister() with dev->type still set to &mtd_devtype, so mtd_release() -> release_mtd_partition() continues to work correctly for the regular removal case.

References

NVD — CVE-2026-68416 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-68416
git.kernel.org/stable/c/820f983d64... WEB
https://git.kernel.org/stable/c/820f983d641937a787e841ee4b93501f69f5683e
git.kernel.org/stable/c/9d4af746af... WEB
https://git.kernel.org/stable/c/9d4af746af8ce27eefc2338b2feaa1e01f28b6c3
git.kernel.org/stable/c/e1e96aca1b... WEB
https://git.kernel.org/stable/c/e1e96aca1bdf391e2f49531c270ffc134e5b49a5
git.kernel.org/stable/c/f98ae09c72... WEB
https://git.kernel.org/stable/c/f98ae09c727dcf34f745c875661c64b642e4abfa
git.kernel.org/stable/c/ffe21a3545... WEB
https://git.kernel.org/stable/c/ffe21a3545b439e7b11578a701c22a847c149561

Frequently Asked Questions

What is CVE-2026-68416?
CVE-2026-68416 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-68416?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What CWE is associated with CVE-2026-68416?
CVE-2026-68416 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-68416?
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-qpvq-4872-pr63",
  "modified" : "2026-08-10T15:33:50Z",
  "published" : "2026-08-10T15:33:50Z",
  "aliases" : [ "CVE-2026-68416" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nmtd: fix double free and WARN_ON in add_mtd_device() error paths\n\nWhen device_register() or mtd_nvmem_add() fails inside\nadd_mtd_device() for a partition, the error handling triggers\nmtd_release() via put_device() or device_unregister(). mtd_release()\ncalls release_mtd_partition() which frees the mtd_info structure.\nHowever, callers such as mtd_add_partition() and add_mtd_partitions()\nalso call free_partition() in their error paths, resulting in a double\nfree.\n\nAdditionally, release_mtd_partition() hits WARN_ON(!list_empty(\n&mtd->part.node)) because the partition node is still linked in the\nparent's partitions list when the release callback fires from the\nadd_mtd_device() error path.\n\nFix this by overriding dev->type and dev->release before put_device()\nin the error paths, so that device_release() invokes a no-op function\ninstead of mtd_release(). For the mtd_nvmem_add() failure case,\ndevice_unregister() is replaced with device_del() to separate the\ndevice removal from the final kobject reference drop, allowing the\noverride to take effect before put_device() is called.\n\nThe callers' error paths (list_del + free_partition) remain the sole\nowners of mtd_info lifetime on add_mtd_device() failure, which is the\nexpected contract.\n\nThe normal partition teardown path is not affected: del_mtd_device()\ngoes through kref_put() -> mtd_device_release() -> device_unregister()\nwith dev->type still set to &mtd_devtype, so mtd_release() ->\nrelease_mtd_partition() continues to work correctly for the regular\nremoval case.",
  "severity" : [ ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-68416"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/820f983d641937a787e841ee4b93501f69f5683e"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/9d4af746af8ce27eefc2338b2feaa1e01f28b6c3"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/e1e96aca1bdf391e2f49531c270ffc134e5b49a5"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/f98ae09c727dcf34f745c875661c64b642e4abfa"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/ffe21a3545b439e7b11578a701c22a847c149561"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : null,
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-08-10T13:20:35Z"
  }
}