CVE-2025-21943gpio: aggregator: protect driver attr handlers against module unload
- 4.7MediumCVSS base score
- 0.17%Exploitation in 30 daysEPSS · top 94% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
In the Linux kernel, the following vulnerability has been resolved: gpio: aggregator: protect driver attr handlers against module unload Both new_device_store and delete_device_store touch module global resources (e.g. gpio_aggregator_lock). To prevent race conditions with module unload, a reference needs to be held. Add try_module_get() in these handlers. For new_device_store, this eliminates what appears to be the most dangerous scenario: if an id is allocated from gpio_aggregator_idr but platform_device_register has not yet been called or completed, a concurrent module unload could fail to unregister/delete the device, leaving behind a dangling platform device/GPIO forwarder. This can result in various issues. The following simple reproducer demonstrates these problems: #!/bin/bash while :; do # note: whether 'gpiochip0 0' exists or not does not matter. echo 'gpiochip0 0' > /sys/bus/platform/drivers/gpio-aggregator/new_device done & while :; do modprobe gpio-aggregator modprobe -r gpio-aggregator done & wait Starting with the following warning, several kinds of warnings will appear and the system may become unstable: ------------[ cut here ]------------ list_del corruption, ffff888103e2e980->next is LIST_POISON1 (dead000000000100) WARNING: CPU: 1 PID: 1327 at lib/list_debug.c:56 __list_del_entry_valid_or_report+0xa3/0x120 [...] RIP: 0010:__list_del_entry_valid_or_report+0xa3/0x120 [...] Call Trace: <TASK> ? __list_del_entry_valid_or_report+0xa3/0x120 ? __warn.cold+0x93/0xf2 ? __list_del_entry_valid_or_report+0xa3/0x120 ? report_bug+0xe6/0x170 ? __irq_work_queue_local+0x39/0xe0 ? handle_bug+0x58/0x90 ? exc_invalid_op+0x13/0x60 ? asm_exc_invalid_op+0x16/0x20 ? __list_del_entry_valid_or_report+0xa3/0x120 gpiod_remove_lookup_table+0x22/0x60 new_device_store+0x315/0x350 [gpio_aggregator] kernfs_fop_write_iter+0x137/0x1f0 vfs_write+0x262/0x430 ksys_write+0x60/0xd0 do_syscall_64+0x6c/0x180 entry_SYSCALL_64_after_hwframe+0x76/0x7e [...] </TASK> ---[ end trace 0000000000000000 ]---
Timeline
ID reserved
By Linux
- 3 months later
· 3 months later
Published
- 14 months later
· 14 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
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| CISA-ADPADP (enrichment) | 3.1 | Medium4.7 | CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H |
| NVDNVD · Modified | 3.1 | Medium4.7 | CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H |
- EPSS (exploitation in 30 days)
- 0.17% · top 94% of all CVEs (18 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: partial
The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 4.7.
Affected products
- affected 828546e24280f721350a7a0dcc92416e917b4382 – < fd6aa1f8cbe0979eb66ac32ebc231bf0b10a2117
- affected 828546e24280f721350a7a0dcc92416e917b4382 – < 807789018186cf508ceb3a1f8f02935cd195717b
- affected 828546e24280f721350a7a0dcc92416e917b4382 – < 9334c88fc2fbc6836b307d269fcc1744c69701c0
- affected 828546e24280f721350a7a0dcc92416e917b4382 – < d99dc8f7ea01ee1b21306e0eda8eb18a4af80db6
- affected 828546e24280f721350a7a0dcc92416e917b4382 – < 8fb07fb1bba91d45846ed8605c3097fe67a7d54c
- affected 828546e24280f721350a7a0dcc92416e917b4382 – < 56281a76b805b5ac61feb5d580139695a22f87f0
- affected 828546e24280f721350a7a0dcc92416e917b4382 – < 12f65d1203507f7db3ba59930fe29a3b8eee9945
- affected 5.8
- unaffected < 5.8
- unaffected 5.10.235 – ≤ 5.10.*
- unaffected 5.15.179 – ≤ 5.15.*
- unaffected 6.1.131 – ≤ 6.1.*
- unaffected 6.6.83 – ≤ 6.6.*
- unaffected 6.12.19 – ≤ 6.12.*
- unaffected 6.13.7 – ≤ 6.13.*
- unaffected 6.14 – ≤ *
References
References9
- https://git.kernel.org/stable/c/fd6aa1f8cbe0979eb66ac32ebc231bf0b10a2117 (opens in a new tab)
- https://git.kernel.org/stable/c/807789018186cf508ceb3a1f8f02935cd195717b (opens in a new tab)
- https://git.kernel.org/stable/c/9334c88fc2fbc6836b307d269fcc1744c69701c0 (opens in a new tab)
- https://git.kernel.org/stable/c/d99dc8f7ea01ee1b21306e0eda8eb18a4af80db6 (opens in a new tab)
- https://git.kernel.org/stable/c/8fb07fb1bba91d45846ed8605c3097fe67a7d54c (opens in a new tab)
- https://git.kernel.org/stable/c/56281a76b805b5ac61feb5d580139695a22f87f0 (opens in a new tab)
- https://git.kernel.org/stable/c/12f65d1203507f7db3ba59930fe29a3b8eee9945 (opens in a new tab)
- https://lists.debian.org/debian-lts-announce/2025/05/msg00045.html (opens in a new tab)
- https://lists.debian.org/debian-lts-announce/2025/05/msg00030.html (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2025-9378 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2025-21943)Record last updated .