CVE-2026-68378: Software Security Vulnerability Vulnerability

UNKNOWN
Advisory Identifier: GHSA-j7r8-gfhw-6w5q
Share
Published
Advisory Summary

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

CVE Identifier CVE-2026-68378
GHSA Identifier GHSA-j7r8-gfhw-6w5q
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-68378

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-68378, 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: dpll: fix NULL pointer dereference in dpll_msg_add_pin_ref_sync() When a dpll_pin is shared across multiple dpll_device instances and those devices are being unregistered (e.g. during driver module removal), a NULL pointer dereference can occur in dpll_msg_add_pin_ref_sync(). This happens under the following conditions: - A pin is registered with two or more dpll devices (dpll_A, dpll_B) - The pin has ref_sync pairs with other pins - During unregistration of dpll_A's pins, a ref_sync partner pin is unregistered first, removing it from dpll_A->pin_refs - But since the partner pin is still registered with dpll_B, its dpll_refs is not empty, so dpll_pin_ref_sync_pair_del() does NOT run and the partner stays in the pin's ref_sync_pins xarray - When the pin itself is then unregistered from dpll_A, the delete notification calls dpll_msg_add_pin_ref_sync() which finds the partner in ref_sync_pins, passes dpll_pin_available() (partner is still registered with dpll_B), but dpll_pin_on_dpll_priv(dpll_A, partner) returns NULL because partner was already removed from dpll_A->pin_refs - The NULL priv pointer is passed to the driver's ref_sync_get callback, which dereferences it BUG: kernel NULL pointer dereference, address: 0000000000000034 Oops: Oops: 0000 [#1] SMP NOPTI RIP: 0010:zl3073x_dpll_input_pin_ref_sync_get+0x73/0x80 [zl3073x] Call Trace: dpll_msg_add_pin_ref_sync+0xb8/0x200 dpll_cmd_pin_get_one+0x3b6/0x4b0 dpll_pin_event_send+0x72/0x140 __dpll_pin_unregister+0x5a/0x2b0 dpll_pin_unregister+0x49/0x70 Fix this by skipping ref_sync pins whose priv pointer cannot be resolved for the current dpll device.

References

NVD — CVE-2026-68378 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-68378
git.kernel.org/stable/c/4b3e6b9fda... WEB
https://git.kernel.org/stable/c/4b3e6b9fdaeb40c6a2f7c41db3888b6ee628bdd2
git.kernel.org/stable/c/51c2fcc4cd... WEB
https://git.kernel.org/stable/c/51c2fcc4cd2e4c52bd1970558f6e5356fdc51154
git.kernel.org/stable/c/66fbe0499e... WEB
https://git.kernel.org/stable/c/66fbe0499ef517ab161b96c49886a891851f6481
git.kernel.org/stable/c/d2e914a4a0... WEB
https://git.kernel.org/stable/c/d2e914a4a0d0f753dbae830264850d044026167c

Frequently Asked Questions

What is CVE-2026-68378?
CVE-2026-68378 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-68378?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What CWE is associated with CVE-2026-68378?
CVE-2026-68378 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-68378?
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-j7r8-gfhw-6w5q",
  "modified" : "2026-08-10T15:33:48Z",
  "published" : "2026-08-10T15:33:48Z",
  "aliases" : [ "CVE-2026-68378" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\ndpll: fix NULL pointer dereference in dpll_msg_add_pin_ref_sync()\n\nWhen a dpll_pin is shared across multiple dpll_device instances and\nthose devices are being unregistered (e.g. during driver module removal),\na NULL pointer dereference can occur in dpll_msg_add_pin_ref_sync().\n\nThis happens under the following conditions:\n - A pin is registered with two or more dpll devices (dpll_A, dpll_B)\n - The pin has ref_sync pairs with other pins\n - During unregistration of dpll_A's pins, a ref_sync partner pin is\n   unregistered first, removing it from dpll_A->pin_refs\n - But since the partner pin is still registered with dpll_B, its\n   dpll_refs is not empty, so dpll_pin_ref_sync_pair_del() does NOT\n   run and the partner stays in the pin's ref_sync_pins xarray\n - When the pin itself is then unregistered from dpll_A, the delete\n   notification calls dpll_msg_add_pin_ref_sync() which finds the\n   partner in ref_sync_pins, passes dpll_pin_available() (partner is\n   still registered with dpll_B), but dpll_pin_on_dpll_priv(dpll_A,\n   partner) returns NULL because partner was already removed from\n   dpll_A->pin_refs\n - The NULL priv pointer is passed to the driver's ref_sync_get\n   callback, which dereferences it\n\n BUG: kernel NULL pointer dereference, address: 0000000000000034\n Oops: Oops: 0000 [#1] SMP NOPTI\n RIP: 0010:zl3073x_dpll_input_pin_ref_sync_get+0x73/0x80 [zl3073x]\n Call Trace:\n  dpll_msg_add_pin_ref_sync+0xb8/0x200\n  dpll_cmd_pin_get_one+0x3b6/0x4b0\n  dpll_pin_event_send+0x72/0x140\n  __dpll_pin_unregister+0x5a/0x2b0\n  dpll_pin_unregister+0x49/0x70\n\nFix this by skipping ref_sync pins whose priv pointer cannot be resolved\nfor the current dpll device.",
  "severity" : [ ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-68378"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/4b3e6b9fdaeb40c6a2f7c41db3888b6ee628bdd2"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/51c2fcc4cd2e4c52bd1970558f6e5356fdc51154"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/66fbe0499ef517ab161b96c49886a891851f6481"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/d2e914a4a0d0f753dbae830264850d044026167c"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : null,
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-08-10T13:20:30Z"
  }
}