CVE-2026-100079

Description

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.

Is your site exposed to CVE-2026-100079?

Run a free security scan — no signup, results in seconds.

EPSS — Exploit Prediction

0.0011

Probability of exploitation

0.01%

Percentile rank

EPSS estimates the probability that this vulnerability will be exploited in the wild within the next 30 days. A higher score means more likely to be exploited.

References

Other References

https://git.kernel.org/stable/c/1f44d001620fd3caa30619a9bc73e9d15555408b https://git.kernel.org/stable/c/62efee351566321ad72a4abaf6eb7d972590585d https://git.kernel.org/stable/c/7177c215e69658adbd2f2fc5b72e14be9208d2ba https://git.kernel.org/stable/c/eed73a65ab609b79d53de88cccc34b36dfe753c4 https://git.kernel.org/stable/c/fb7393519908befdc094be4ea913f582adbf2f7c

Frequently Asked Questions

What is CVE-2026-100079? +

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.

How do I check if I'm vulnerable to CVE-2026-100079? +

You can use Secably's free Website Scanner to check your website for known vulnerabilities. For infrastructure scanning, use the Port Scanner to identify exposed services that may be affected. Check the vendor advisories linked above for specific patch and version information.