Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
The Linux kernel pinmux subsystem is affected in several version ranges, including all of 6.13 and earlier releases before their listed fixes. A race between two callers using the same GPIO pin can leave the pin marked in use with no owner, which can cause a NULL pointer issue on a later pin request. The source gives few details on what access an attacker would need. Upgrade to 6.6.102 or later, 6.12.42 or later, 6.15.10 or later, or 6.16.1 or later, depending on your series. No fix is listed for the 6.13 series.
Not analysed yet
We haven’t published our own analysis of this CVE. If a person reviews it, this page will say what’s affected and what has to be true for it to matter.
Severity and exploitation
No source has published a CVSS score for this record yet.
- CISA KEV Not listed.
- EPSS 0.0015, the 4th percentile, on 20 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 22 Aug 2025, 16:00 UTC Confirmed by the CVE List
- 22 Aug 2025, 16:15 UTC Confirmed by NVD
Sources
References from the CNA
- git.kernel.org/stable/c/8434dec94e73cad527341d6280895191d949a702
- git.kernel.org/stable/c/9b2a3e7189028aa7c4d53a84364f2ea9fb209787
- git.kernel.org/stable/c/9ea3f6b9a67be3476e331ce51cac316c2614a564
- git.kernel.org/stable/c/b7bd6e3971eb7f0e34d2fdce1b18b08094e0c804
- git.kernel.org/stable/c/22b585cbd67d14df3b91529d1b990661c300faa9
- git.kernel.org/stable/c/0b075c011032f88d1cfde3b45d6dcf08b44140eb