CVE-2026-68203: Software Security Vulnerability Vulnerability
UNKNOWNCVE-2026-68203 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-68203 at a Glance
How to Fix CVE-2026-68203
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.
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-68203, 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
References
Frequently Asked Questions
What is CVE-2026-68203?
Which Software versions are affected?
What version fixes CVE-2026-68203?
What CWE is associated with CVE-2026-68203?
How can I check Maven dependencies for CVE-2026-68203?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-m883-8hm9-jvgx",
"modified" : "2026-08-10T15:33:40Z",
"published" : "2026-08-10T15:33:40Z",
"aliases" : [ "CVE-2026-68203" ],
"details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nmedia: vivid: fix cleanup bugs in vivid_init()\n\nWhen platform_device_register() fails in vivid_init(), the embedded\nstruct device in vivid_pdev has already been initialized by\ndevice_initialize(), but the failure path jumps to free_output_strings\nwithout dropping the device reference for the current platform device:\n\n vivid_init()\n -> platform_device_register(&vivid_pdev)\n -> device_initialize(&vivid_pdev.dev)\n -> setup_pdev_dma_masks(&vivid_pdev)\n -> platform_device_add(&vivid_pdev)\n\nThis leads to a reference leak when platform_device_register() fails.\nFix this by calling platform_device_put() before jumping to the common\ncleanup path.\n\nAlso, the unreg_driver label incorrectly calls\nplatform_driver_register() instead of platform_driver_unregister(),\nwhich breaks cleanup when workqueue creation fails after successful\ndriver registration. Fix that as well.\n\nThe reference leak was identified by a static analysis tool I developed\nand confirmed by manual review. The incorrect cleanup call was found\nduring code inspection.",
"severity" : [ ],
"affected" : [ ],
"references" : [ {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-68203"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/1349af7f87df57940619f5b87990b799dac9ed8a"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/4385092a86b94e1f332db35a3766108978c0722f"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/6d51ad8f1c50c50d1abcc97fd243179967184c6a"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/a07c179a92e949172ca52f6d4a13202ea88cd4b7"
} ],
"database_specific" : {
"cwe_ids" : [ ],
"severity" : null,
"github_reviewed" : false,
"github_reviewed_at" : null,
"nvd_published_at" : "2026-08-10T13:20:07Z"
}
}