{"id":"CVE-2026-68378","summary":"dpll: fix NULL pointer dereference in dpll_msg_add_pin_ref_sync()","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-\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'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-\u003epin_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.","modified":"2026-08-18T03:30:46.799805749Z","published":"2026-08-10T12:03:56.590Z","database_specific":{"osv_generated_from":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/68xxx/CVE-2026-68378.json","cna_assigner":"Linux"},"references":[{"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"},{"type":"ADVISORY","url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/68xxx/CVE-2026-68378.json"},{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-68378"},{"type":"PACKAGE","url":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"}],"affected":[{"ranges":[{"type":"GIT","repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","events":[{"introduced":"40466ea1827c46c6435fab9b21b63b80733e2d07"},{"fixed":"66fbe0499ef517ab161b96c49886a891851f6481"}]},{"type":"GIT","repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","events":[{"introduced":"58256a26bfb37a94738dd65618b1f31f460f8d91"},{"fixed":"51c2fcc4cd2e4c52bd1970558f6e5356fdc51154"},{"fixed":"4b3e6b9fdaeb40c6a2f7c41db3888b6ee628bdd2"},{"fixed":"d2e914a4a0d0f753dbae830264850d044026167c"}]}],"database_specific":{"source":"https://storage.googleapis.com/osv-test-cve-osv-conversion/osv-output/CVE-2026-68378.json"}},{"package":{"name":"Kernel","ecosystem":"Linux"},"ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"6.17.0"},{"fixed":"6.18.42"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.19.0"},{"fixed":"7.1.6"}]}],"database_specific":{"source":"https://storage.googleapis.com/osv-test-cve-osv-conversion/osv-output/CVE-2026-68378.json"}}],"schema_version":"1.9.0"}