CVE-2025-40249
gpio: cdev: make sure the cdev fd is still active before emitting events
Reported by linux · Published December 4, 2025
In the Linux kernel, the following vulnerability has been resolved: gpio: cdev: make sure the cdev fd is still active before emitting events With the final call to fput() on a file descriptor, the release action may be deferred and scheduled on a work queue. The reference count of that descriptor is still zero and it must not be used. It's possible that a GPIO change, we want to notify the user-space about, happens AFTER the reference count on the file descriptor associated with the character device went down to zero but BEFORE the .release() callback was called from the workqueue and so BEFORE we unregistered from the notifier. Using the regular get_file() routine in this situation triggers the following warning: struct file::f_count incremented from zero; use-after-free condition present! So use the get_file_active() variant that will return NULL on file descriptors that have been or are being released.
EPSS 0.16% · 4.6th percentile
Fixed versions
Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.
| Package | Ecosystem | Fixed in |
|---|---|---|
| linux_kernel | linux | 6.18, 6.17.10 |
| Linux | Linux | dccc6daa8afa0f64c432e4c867f275747e3415e1, d4cd0902c156b2ca60fdda8cd8b5bcb4b0e9ed64, 6.13 |
Risk scores
Affected products
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | 40b7c49950bd56c984b1f6722f865b922879260e, 40b7c49950bd56c984b1f6722f865b922879260e |
| Linux | Linux | 6.13, 0, 6.17.10 |
| linux | linux_kernel | 6.13, 6.13 |
| Linux | Linux | 40b7c49950bd56c984b1f6722f865b922879260e, 6.13, 0 |
Timeline
- Dec 4, 2025 CVE Published
- Dec 5, 2025 EPSS Score (30 in total, the first dated here)
- Mar 29, 2026 Distribution Patch (129 in total, the first dated here)
- Mar 29, 2026 Security Advisory (136 in total, the first dated here)
- Jun 8, 2026 Coalition ESS Score
Query this with the API
The same record, from the CLI:
vulnetix vdb vuln CVE-2025-40249
vulnetix vdb fixes CVE-2025-40249
Or with curl, using the org id and key from your account page:
curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
"https://api.vdb.vulnetix.com/v2/vuln/CVE-2025-40249/fixes/registry"
The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart