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-2025-40030pinctrl: check the return value of pinmux_ops::get_function_name()

Description

In the Linux kernel, the following vulnerability has been resolved: pinctrl: check the return value of pinmux_ops::get_function_name() While the API contract in docs doesn't specify it explicitly, the generic implementation of the get_function_name() callback from struct pinmux_ops - pinmux_generic_get_function_name() - can fail and return NULL. This is already checked in pinmux_check_ops() so add a similar check in pinmux_func_name_to_selector() instead of passing the returned pointer right down to strcmp() where the NULL can get dereferenced. This is normal operation when adding new pinfunctions.

Timeline

  1. ID reserved

    By Linux

  2. · 7 months later

    Published

  3. · 7 months later

    Record updated

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

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Deferred.

EPSS (exploitation in 30 days)
0.23% · top 86% of all CVEs (16 Nov 2026)
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected f913cfce4ee49a3382a9ff95696f49a46e56e974 – < 1a7fc8fed2bb2e113604fde7a45432ace2056b97
    • affected f913cfce4ee49a3382a9ff95696f49a46e56e974 – < e7265dc4c670b89611bcf5fe33acf99bc0aa294f
    • affected f913cfce4ee49a3382a9ff95696f49a46e56e974 – < d77ef2f621cd1d605372c4c6ce667c496f6990c3
    • affected f913cfce4ee49a3382a9ff95696f49a46e56e974 – < ba7f7c2b2b3261e7def67018c38c69b626e0e66e
    • affected f913cfce4ee49a3382a9ff95696f49a46e56e974 – < 1a2ea887a5cd7d47bab599f733d89444df018b1a
    • affected f913cfce4ee49a3382a9ff95696f49a46e56e974 – < 688c688e0bf55824f4a38f8c2180046f089a3e3b
    • affected f913cfce4ee49a3382a9ff95696f49a46e56e974 – < b7e0535060a60cc99eafc19cc665d979714cd73a
    • affected f913cfce4ee49a3382a9ff95696f49a46e56e974 – < 4002ee98c022d671ecc1e4a84029e9ae7d8a5603
  • Linux · Linux

    • affected 4.19
    • unaffected < 4.19
    • unaffected 5.4.301 – ≤ 5.4.*
    • unaffected 5.10.246 – ≤ 5.10.*
    • unaffected 5.15.195 – ≤ 5.15.*
    • unaffected 6.1.156 – ≤ 6.1.*
    • unaffected 6.6.112 – ≤ 6.6.*
    • unaffected 6.12.53 – ≤ 6.12.*
    • unaffected 6.17.3 – ≤ 6.17.*
    • unaffected 6.18 – ≤ *

References

References8

Sources

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

Badge for a README or a ticket

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

Record last updated .