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-38632pinmux: fix race causing mux_owner NULL with active mux_usecount

Description

In the Linux kernel, the following vulnerability has been resolved: pinmux: fix race causing mux_owner NULL with active mux_usecount commit 5a3e85c3c397 ("pinmux: Use sequential access to access desc->pinmux data") tried to address the issue when two client of the same gpio calls pinctrl_select_state() for the same functionality, was resulting in NULL pointer issue while accessing desc->mux_owner. However, issue was not completely fixed due to the way it was handled and it can still result in the same NULL pointer. The issue occurs due to the following interleaving: cpu0 (process A) cpu1 (process B) pin_request() { pin_free() { mutex_lock() desc->mux_usecount--; //becomes 0 .. mutex_unlock() mutex_lock(desc->mux) desc->mux_usecount++; // becomes 1 desc->mux_owner = owner; mutex_unlock(desc->mux) mutex_lock(desc->mux) desc->mux_owner = NULL; mutex_unlock(desc->mux) This sequence leads to a state where the pin appears to be in use (`mux_usecount == 1`) but has no owner (`mux_owner == NULL`), which can cause NULL pointer on next pin_request on the same pin. Ensure that updates to mux_usecount and mux_owner are performed atomically under the same lock. Only clear mux_owner when mux_usecount reaches zero and no new owner has been assigned.

Timeline

  1. ID reserved

    By Linux

  2. · 4 months later

    Published

  3. · 15 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

CVSS scores of CVE-2025-38632, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.1Medium4.7CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.15% · top 96% of all CVEs (15 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected d25e45dcf8e32062f7935e4ba154869043812ab6 – < 8434dec94e73cad527341d6280895191d949a702
    • affected 2da32aed4a97ca1d70fb8b77926f72f30ce5fb4b – < 9b2a3e7189028aa7c4d53a84364f2ea9fb209787
    • affected c11e2ec9a780f54982a187ee10ffd1b810715c85 – < 9ea3f6b9a67be3476e331ce51cac316c2614a564
    • affected 5a3e85c3c397c781393ea5fb2f45b1f60f8a4e6e – < b7bd6e3971eb7f0e34d2fdce1b18b08094e0c804
    • affected 5a3e85c3c397c781393ea5fb2f45b1f60f8a4e6e – < 22b585cbd67d14df3b91529d1b990661c300faa9
    • affected 5a3e85c3c397c781393ea5fb2f45b1f60f8a4e6e – < 0b075c011032f88d1cfde3b45d6dcf08b44140eb
    • affected 6.6.66 – < 6.6.102
    • affected 6.12.5 – < 6.12.42
  • Linux · Linux

    • affected 6.13
    • unaffected < 6.13
    • unaffected 6.6.102 – ≤ 6.6.*
    • unaffected 6.12.42 – ≤ 6.12.*
    • unaffected 6.15.10 – ≤ 6.15.*
    • unaffected 6.16.1 – ≤ 6.16.*
    • unaffected 6.17 – ≤ *

References

References6

Sources

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

Badge for a README or a ticket

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

Record last updated .