CVE-2026-68213: Software Security Vulnerability Vulnerability
HIGHCVE-2026-68213 is a HIGH (CVSS 7.8) security vulnerability vulnerability (CWE-401: Missing Release of Memory after Effective Lifetime) affecting Software libraries in the Maven ecosystem. The weakness occurs when the product does not sufficiently track and release allocated memory after it has been used, making the memory unavailable for reallocation and reuse.. Remediation is available in the latest vendor maintenance releases.
CVE-2026-68213 at a Glance
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).
How to Fix CVE-2026-68213
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:treeHow to Check if You Are Affected
To determine whether your Java application is affected by CVE-2026-68213, inspect your build dependencies using the Maven Dependency Plugin:
mvn dependency:treeAnalyze 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 CWE-401: Missing Release of Memory after Effective Lifetime, where the product does not sufficiently track and release allocated memory after it has been used, making the memory unavailable for reallocation and reuse. 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-68213?
Which Software versions are affected?
What version fixes CVE-2026-68213?
What is the CVSS score of CVE-2026-68213?
What CWE is associated with CVE-2026-68213?
How can I check Maven dependencies for CVE-2026-68213?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-rjmw-6r45-2xm2",
"modified" : "2026-08-19T18:32:11Z",
"published" : "2026-08-10T15:33:41Z",
"aliases" : [ "CVE-2026-68213" ],
"details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nmedia: rtl2832_sdr: Return queued buffers on start_streaming() failure\n\nThe vb2 framework hands buffers to the driver via buf_queue() before\ncalling start_streaming(). If start_streaming() returns an error\nwithout first returning those buffers via vb2_buffer_done(),\nvb2_start_streaming() fires WARN_ON(owned_by_drv_count) and the queued\nbuffers leak.\n\nrtl2832_sdr_start_streaming() had multiple error paths that hit this\ntrap: two direct early returns (-ENODEV, -ERESTARTSYS), plus six\n`goto err` paths covering subdev s_power, tuner setup, ADC setup,\nstream-buffer allocation, urb allocation, and urb submission failures.\nNone of them returned the queued buffers.\n\nThe original function had no distinct success exit and fell straight\nthrough into the err label, which previously only did mutex_unlock and\n\"return ret\". Adding queued-buffer cleanup at err must therefore be\npaired with an explicit success return; otherwise every successful\nstart would also drain the buffer queue and kill streaming. Add that\nsuccess return, then add rtl2832_sdr_cleanup_queued_bufs() at the err\nlabel and before each early return.\n\nThe cleanup helper takes a vb2_buffer_state argument so that the\nstart_streaming error paths can pass VB2_BUF_STATE_QUEUED (as\nexpected by userspace on start_streaming failure) while stop_streaming\nkeeps its existing VB2_BUF_STATE_ERROR semantics.\n\nThis mirrors the uvcvideo fix in commit 4cf3b6fd54eb (\"media: uvcvideo:\nReturn queued buffers on start_streaming() failure\").\n\nThe err label still does not roll back power_ctrl(), frontend_ctrl(),\nthe POWER_ON flag, or stream/URB allocations that may have happened\nbefore the failing step. Those are pre-existing leaks of a different\nclass and are not addressed here.",
"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-68213"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/0b08c0403cf672a121ace4eff647a9b240bd4e1b"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/33ca0aab6f4bd90921fc1395478f38f72c4d19af"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/465dc8e71d2db2ed603e749fa71392bcdccf07eb"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/772f2550fe32357557d3b2f88e02f7cf477f0789"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/894e83509c66910112b9eaeaa8cd66cd9806db91"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/a248273f8af6e630a03e823274385725974009b5"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/fc0b18782aab4e35078efe72863df8eab46560a8"
}, {
"type" : "WEB",
"url" : "https://git.kernel.org/stable/c/fd1e11fc3849169285e48b2d4ec441614ad2ea74"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-401" ],
"severity" : "HIGH",
"github_reviewed" : false,
"github_reviewed_at" : null,
"nvd_published_at" : "2026-08-10T13:20:09Z"
}
}