{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-68378 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-68378 is a vulnerability in Linux, published on 10 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-68378 and fix it if it is affected.\n\nWhat it is: CVE-2026-68378 is a vulnerability in Linux, published on 10 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-68378 in the wild and no public exploit code.\n\nAffected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-68378/ (Markdown: https://insights.sbomify.com/CVE-2026-68378/index.md)","id":"CVE-2026-68378","markdown":"https://insights.sbomify.com/CVE-2026-68378/index.md","name":"CVE-2026-68378","record":{"aliases":["BELL-CVE-2026-68378","DEBIAN-CVE-2026-68378","GHSA-j7r8-gfhw-6w5q","UBUNTU-CVE-2026-68378"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel","requires_auth":"low_privilege","summary":"A local attacker can trigger a kernel crash by unregistering shared DPLL pins, causing a NULL pointer dereference and denial of service.","user_interaction":"not_required","vuln_class":"null_dereference"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"dpll: fix NULL pointer dereference in dpll_msg_add_pin_ref_sync()","id":"CVE-2026-68378","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"tcp: fix TIME_WAIT socket reference leak on PSP policy failure","id":"CVE-2026-68379"},"packages":[],"prev":{"headline":"net/sched: act_tunnel_key: Defer dst_release to RCU callback","id":"CVE-2026-68377"},"products":["Linux"],"published":"2026-08-10","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-08-17","vendors":["Linux"]},"summary":"A local attacker can trigger a kernel crash by unregistering shared DPLL pins, causing a NULL pointer dereference and denial of service.","url":"https://insights.sbomify.com/CVE-2026-68378/"}