Linux vulnerability

In the Linux kernel, the following vulnerability has been resolved: usb: typec: ucsi: unregister debugfs entries on teardown ucsi_register() creates per-instance debugfs entries, but ucsi_unregister() keeps them around until ucsi_destroy(). Drivers like ucsi_glink that unregister/register the same UCSI instance across remoteproc restart then try to create an already existing debugfs directory and log: debugfs: 'pmic_glink.ucsi.0' already exists in 'ucsi' Unregister debugfs entries as part of ucsi_unregister(), and clear ucsi->debugfs after freeing it so repeated unregister paths remain safe.

Published 25 Sep 2026Updated 2 Oct 20265 sources
CVSS 5.5

What happened

In the Linux kernel, the following vulnerability has been resolved: usb: typec: ucsi: unregister debugfs entries on teardown ucsi_register() creates per-instance debugfs entries, but ucsi_unregister() keeps them around until ucsi_destroy(). Drivers like ucsi_glink that unregister/register the same UCSI instance across remoteproc restart then try to create an already existing debugfs directory and log: debugfs: 'pmic_glink.ucsi.0' already exists in 'ucsi' Unregister debugfs entries as part of ucsi_unregister(), and clear ucsi->debugfs after freeing it so repeated unregister paths remain safe.

Affected versions

Linux: df0383ffad64dc09954a60873c1e202b47f08d90 through before fb7393519908befdc094be4ea913f582adbf2f7c (git); df0383ffad64dc09954a60873c1e202b47f08d90 through before 7177c215e69658adbd2f2fc5b72e14be9208d2ba (git); df0383ffad64dc09954a60873c1e202b47f08d90 through before 1f44d001620fd3caa30619a9bc73e9d15555408b (git); df0383ffad64dc09954a60873c1e202b47f08d90 through before 62efee351566321ad72a4abaf6eb7d972590585d (git); df0383ffad64dc09954a60873c1e202b47f08d90 through before eed73a65ab609b79d53de88cccc34b36dfe753c4 (git); 6.6 Fixed: See vendor advisory.

Why it matters

Review the vendor advisory and exposure of the affected product to determine operational impact.

Detection & mitigation

  • Apply vendor-provided updates or mitigations.
  • Review affected product exposure and access logs.

Public PoC references

No public PoC reference has passed the current publication threshold.