GHSA-J7R8-GFHW-6W5Q
Vulnerability from github – Published: 2026-08-10 15:33 – Updated: 2026-08-10 15:33In 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.
{
"affected": [],
"aliases": [
"CVE-2026-68378"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-08-10T13:20:30Z",
"severity": null
},
"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\u0027s pins, a ref_sync partner pin is\n unregistered first, removing it from dpll_A-\u003epin_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\u0027s 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-\u003epin_refs\n - The NULL priv pointer is passed to the driver\u0027s 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.",
"id": "GHSA-j7r8-gfhw-6w5q",
"modified": "2026-08-10T15:33:48Z",
"published": "2026-08-10T15:33:48Z",
"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"
}
],
"schema_version": "1.4.0",
"severity": []
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.