CVE-2026-45868

Description

In the Linux kernel, the following vulnerability has been resolved: pinctrl: single: fix refcount leak in pcs_add_gpio_func() of_parse_phandle_with_args() returns a device_node pointer with refcount incremented in gpiospec.np. The loop iterates through all phandles but never releases the reference, causing a refcount leak on each iteration. Add of_node_put() calls to release the reference after extracting the needed arguments and on the error path when devm_kzalloc() fails. This bug was detected by our static analysis tool and verified by my code review.

Is your site exposed to CVE-2026-45868?

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

EPSS — Exploit Prediction

0.0021

Probability of exploitation

0.11%

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/191bfd5710d6a7f48ba4315d8d3e908dcc15243c https://git.kernel.org/stable/c/353353309b0f7afa407df29e455f9d15b5acc296 https://git.kernel.org/stable/c/3e3b28bb0b6ddc521a4fdd1c1ba0d35017a0796b https://git.kernel.org/stable/c/456a60d06c09a92680dc35fabca68024badcc28e https://git.kernel.org/stable/c/5b9e84d27e310f22c4ba45fedbc4f5baf43dd823 https://git.kernel.org/stable/c/7814b1431848854b56717086e2b61bea3c59753d https://git.kernel.org/stable/c/99cc7352156c65201c675f750e0e77c4c73d93f5 https://git.kernel.org/stable/c/e2e367e56bacb93ce5ac73f0b3297d5c83d38dd4

Frequently Asked Questions

What is CVE-2026-45868? +

In the Linux kernel, the following vulnerability has been resolved: pinctrl: single: fix refcount leak in pcs_add_gpio_func() of_parse_phandle_with_args() returns a device_node pointer with refcount incremented in gpiospec.np. The loop iterates through all phandles but never releases the reference, causing a refcount leak on each iteration. Add of_node_put() calls to release the reference after extracting the needed arguments and on the error path when devm_kzalloc() fails. This bug was detected by our static analysis tool and verified by my code review.

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

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.