Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-45868pinctrl: single: fix refcount leak in pcs_add_gpio_func()

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.

Timeline

  1. ID reserved

    By Linux

  2. · 14 days later

    Published

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-45868, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.16% · top 95% of all CVEs (14 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected a1a277eb76b3507df7c41774048a644aa4dfd096 – < 191bfd5710d6a7f48ba4315d8d3e908dcc15243c
    • affected a1a277eb76b3507df7c41774048a644aa4dfd096 – < 3e3b28bb0b6ddc521a4fdd1c1ba0d35017a0796b
    • affected a1a277eb76b3507df7c41774048a644aa4dfd096 – < 456a60d06c09a92680dc35fabca68024badcc28e
    • affected a1a277eb76b3507df7c41774048a644aa4dfd096 – < 99cc7352156c65201c675f750e0e77c4c73d93f5
    • affected a1a277eb76b3507df7c41774048a644aa4dfd096 – < 7814b1431848854b56717086e2b61bea3c59753d
    • affected a1a277eb76b3507df7c41774048a644aa4dfd096 – < e2e367e56bacb93ce5ac73f0b3297d5c83d38dd4
    • affected a1a277eb76b3507df7c41774048a644aa4dfd096 – < 5b9e84d27e310f22c4ba45fedbc4f5baf43dd823
    • affected a1a277eb76b3507df7c41774048a644aa4dfd096 – < 353353309b0f7afa407df29e455f9d15b5acc296
  • Linux · Linux

    • affected 3.10
    • unaffected < 3.10
    • unaffected 5.10.252 – ≤ 5.10.*
    • unaffected 5.15.202 – ≤ 5.15.*
    • unaffected 6.1.165 – ≤ 6.1.*
    • unaffected 6.6.128 – ≤ 6.6.*
    • unaffected 6.12.75 – ≤ 6.12.*
    • unaffected 6.18.14 – ≤ 6.18.*
    • unaffected 6.19.4 – ≤ 6.19.*
    • unaffected 7.0 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-45868 badge
[![CVE-2026-45868](https://cveledger.app/badge/CVE-2026-45868.svg)](https://cveledger.app/cve/CVE-2026-45868)

Record last updated .