Skip to main content
VulnerabilityPublished

CVE-2026-63977: Linux kernel · dpll: zl3073x: use __dpll_device_change_ntf() and remove change_work

Source GCVE Database

0
Authoritative record:CVE-2026-63977· High 7.8

Not known to be exploited · CVSS 7.8 High : upgrade to e7a33807fb3f87a855993474ac21684ce105927b or d733f519f6443540f8359461a34e3b0042099bbe soon.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score
7.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 2% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in e7a33807fb3f87a855993474ac21684ce105927b, d733f519f6443540f8359461a34e3b0042099bbe
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 19 Jul 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade Linux kernel to e7a33807fb3f87a855993474ac21684ce105927b or d733f519f6443540f8359461a34e3b0042099bbe.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 9363b4837659d1b7ee04cfa714373ce4b4b8269f, < e7a33807fb3f87a855993474ac21684ce105927b
Fixed in
  • e7a33807fb3f87a855993474ac21684ce105927b
LinuxLinuxAffected
  • ≥ 9363b4837659d1b7ee04cfa714373ce4b4b8269f, < d733f519f6443540f8359461a34e3b0042099bbe
Fixed in
  • d733f519f6443540f8359461a34e3b0042099bbe
LinuxLinuxAffected
  • =6.18
Fixed in–

AI-suggested

A fix has been implemented in the Linux kernel by removing the change_work mechanism and using __dpll_device_change_ntf() directly. Users should update to the Linux kernel version that includes this fix once available.

Description

In the Linux kernel, the following vulnerability has been resolved: dpll: zl3073x: use __dpll_device_change_ntf() and remove change_work The change_work was introduced to send device change notifications from DPLL device callbacks without deadlocking on dpll_lock, since the callbacks are already invoked under that lock. Now that __dpll_device_change_ntf() is exported for callers that already hold dpll_lock, use it directly and remove the change_work infrastructure entirely. This eliminates a race condition where change_work could be re-scheduled after cancel_work_sync() during device teardown, potentially causing the handler to dereference a freed or NULL dpll_dev pointer.

References

Community reviews

Loading reviews…