CVE-2026-68378 (GCVE-0-2026-68378)
Vulnerability from cvelistv5 – Published: 2026-08-10 12:03 – Updated: 2026-08-17 05:04| Vendor | Product | Version | CPE status | |
|---|---|---|---|---|
| Linux | Linux |
Affected:
40466ea1827c46c6435fab9b21b63b80733e2d07 , < 66fbe0499ef517ab161b96c49886a891851f6481
(git)
Affected: 58256a26bfb37a94738dd65618b1f31f460f8d91 , < 51c2fcc4cd2e4c52bd1970558f6e5356fdc51154 (git) Affected: 58256a26bfb37a94738dd65618b1f31f460f8d91 , < 4b3e6b9fdaeb40c6a2f7c41db3888b6ee628bdd2 (git) Affected: 58256a26bfb37a94738dd65618b1f31f460f8d91 , < d2e914a4a0d0f753dbae830264850d044026167c (git) |
guessed | |
| Linux | Linux |
Affected:
6.17
Unaffected: 0 , < 6.17 (semver) Unaffected: 6.18.42 , ≤ 6.18.* (semver) Unaffected: 7.1.6 , ≤ 7.1.* (semver) Unaffected: 7.2 , ≤ * (original_commit_for_fix) |
guessed |
{
"containers": {
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"drivers/dpll/dpll_netlink.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "66fbe0499ef517ab161b96c49886a891851f6481",
"status": "affected",
"version": "40466ea1827c46c6435fab9b21b63b80733e2d07",
"versionType": "git"
},
{
"lessThan": "51c2fcc4cd2e4c52bd1970558f6e5356fdc51154",
"status": "affected",
"version": "58256a26bfb37a94738dd65618b1f31f460f8d91",
"versionType": "git"
},
{
"lessThan": "4b3e6b9fdaeb40c6a2f7c41db3888b6ee628bdd2",
"status": "affected",
"version": "58256a26bfb37a94738dd65618b1f31f460f8d91",
"versionType": "git"
},
{
"lessThan": "d2e914a4a0d0f753dbae830264850d044026167c",
"status": "affected",
"version": "58256a26bfb37a94738dd65618b1f31f460f8d91",
"versionType": "git"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"drivers/dpll/dpll_netlink.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"status": "affected",
"version": "6.17"
},
{
"lessThan": "6.17",
"status": "unaffected",
"version": "0",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.18.*",
"status": "unaffected",
"version": "6.18.42",
"versionType": "semver"
},
{
"lessThanOrEqual": "7.1.*",
"status": "unaffected",
"version": "7.1.6",
"versionType": "semver"
},
{
"lessThanOrEqual": "*",
"status": "unaffected",
"version": "7.2",
"versionType": "original_commit_for_fix"
}
]
}
],
"cpeApplicability": [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.18.42",
"versionStartIncluding": "6.17",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "7.1.6",
"versionStartIncluding": "6.17",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "7.2",
"versionStartIncluding": "6.17",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
]
}
],
"descriptions": [
{
"lang": "en",
"value": "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."
}
],
"providerMetadata": {
"dateUpdated": "2026-08-17T05:04:24.219Z",
"orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"shortName": "Linux"
},
"references": [
{
"url": "https://git.kernel.org/stable/c/66fbe0499ef517ab161b96c49886a891851f6481"
},
{
"url": "https://git.kernel.org/stable/c/51c2fcc4cd2e4c52bd1970558f6e5356fdc51154"
},
{
"url": "https://git.kernel.org/stable/c/4b3e6b9fdaeb40c6a2f7c41db3888b6ee628bdd2"
},
{
"url": "https://git.kernel.org/stable/c/d2e914a4a0d0f753dbae830264850d044026167c"
}
],
"title": "dpll: fix NULL pointer dereference in dpll_msg_add_pin_ref_sync()",
"x_generator": {
"engine": "bippy-1.2.0"
}
}
},
"cveMetadata": {
"assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"assignerShortName": "Linux",
"cveId": "CVE-2026-68378",
"datePublished": "2026-08-10T12:03:56.590Z",
"dateReserved": "2026-07-30T09:28:09.387Z",
"dateUpdated": "2026-08-17T05:04:24.219Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2",
"vulnerability-lookup:meta": {
"epss": {
"cve": "CVE-2026-68378",
"date": "2026-11-21",
"epss": "0.00206",
"percentile": "0.1057"
},
"nvd": {
"cve": {
"affected": [
{
"affectedData": [
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"drivers/dpll/dpll_netlink.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "66fbe0499ef517ab161b96c49886a891851f6481",
"status": "affected",
"version": "40466ea1827c46c6435fab9b21b63b80733e2d07",
"versionType": "git"
},
{
"lessThan": "51c2fcc4cd2e4c52bd1970558f6e5356fdc51154",
"status": "affected",
"version": "58256a26bfb37a94738dd65618b1f31f460f8d91",
"versionType": "git"
},
{
"lessThan": "4b3e6b9fdaeb40c6a2f7c41db3888b6ee628bdd2",
"status": "affected",
"version": "58256a26bfb37a94738dd65618b1f31f460f8d91",
"versionType": "git"
},
{
"lessThan": "d2e914a4a0d0f753dbae830264850d044026167c",
"status": "affected",
"version": "58256a26bfb37a94738dd65618b1f31f460f8d91",
"versionType": "git"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"drivers/dpll/dpll_netlink.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"status": "affected",
"version": "6.17"
},
{
"lessThan": "6.17",
"status": "unaffected",
"version": "0",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.18.*",
"status": "unaffected",
"version": "6.18.42",
"versionType": "semver"
},
{
"lessThanOrEqual": "7.1.*",
"status": "unaffected",
"version": "7.1.6",
"versionType": "semver"
},
{
"lessThanOrEqual": "*",
"status": "unaffected",
"version": "7.2",
"versionType": "original_commit_for_fix"
}
]
}
],
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}
],
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "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": "CVE-2026-68378",
"lastModified": "2026-08-17T06:17:46.260",
"metrics": {},
"published": "2026-08-10T13:20:30.813",
"references": [
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/4b3e6b9fdaeb40c6a2f7c41db3888b6ee628bdd2"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/51c2fcc4cd2e4c52bd1970558f6e5356fdc51154"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/66fbe0499ef517ab161b96c49886a891851f6481"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/d2e914a4a0d0f753dbae830264850d044026167c"
}
],
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"vulnStatus": "Received"
}
},
"redhat_vex": {
"aggregate_severity": "Low",
"current_release_date": "2026-11-07T11:23:08+00:00",
"cve": "CVE-2026-68378",
"id": "CVE-2026-68378",
"initial_release_date": "2026-08-10T00:00:00+00:00",
"product_status:known_affected": "108",
"product_status:known_not_affected": "96",
"source": "Red Hat CSAF VEX",
"status": "final",
"title": "kernel: dpll: fix NULL pointer dereference in dpll_msg_add_pin_ref_sync()",
"url": "https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-68378.json",
"version": "3"
}
}
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
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.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
How durations are calculated
Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.
Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.
Loading timeline…
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.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.