๐Ÿ” CVE Alert

CVE-2025-38349

UNKNOWN 0.0

eventpoll: don't decrement ep refcount while still holding the ep mutex

CVSS Score
0.0
EPSS Score
0.0%
EPSS Percentile
0th

In the Linux kernel, the following vulnerability has been resolved: eventpoll: don't decrement ep refcount while still holding the ep mutex Jann Horn points out that epoll is decrementing the ep refcount and then doing a mutex_unlock(&ep->mtx); afterwards. That's very wrong, because it can lead to a use-after-free. That pattern is actually fine for the very last reference, because the code in question will delay the actual call to "ep_free(ep)" until after it has unlocked the mutex. But it's wrong for the much subtler "next to last" case when somebody *else* may also be dropping their reference and free the ep while we're still using the mutex. Note that this is true even if that other user is also using the same ep mutex: mutexes, unlike spinlocks, can not be used for object ownership, even if they guarantee mutual exclusion. A mutex "unlock" operation is not atomic, and as one user is still accessing the mutex as part of unlocking it, another user can come in and get the now released mutex and free the data structure while the first user is still cleaning up. See our mutex documentation in Documentation/locking/mutex-design.rst, in particular the section [1] about semantics: "mutex_unlock() may access the mutex structure even after it has internally released the lock already - so it's not safe for another context to acquire the mutex and assume that the mutex_unlock() context is not using the structure anymore" So if we drop our ep ref before the mutex unlock, but we weren't the last one, we may then unlock the mutex, another user comes in, drops _their_ reference and releases the 'ep' as it now has no users - all while the mutex_unlock() is still accessing it. Fix this by simply moving the ep refcount dropping to outside the mutex: the refcount itself is atomic, and doesn't need mutex protection (that's the whole _point_ of refcounts: unlike mutexes, they are inherently about object lifetimes).

Vendor linux
Product linux
Ecosystems
Industries
Technology
Published Jul 18, 2025
Last Updated May 11, 2026
Stay Ahead of the Next One

Get instant alerts for linux linux

Be the first to know when new unknown vulnerabilities affecting linux linux are published โ€” delivered to Slack, Telegram or Discord.

Get Free Alerts โ†’ Free ยท No credit card ยท 60 sec setup

Affected Versions

Linux / Linux
58c9b016e12855286370dfb704c08498edbc857a < 521e9ff0b67c66a17d6f9593dfccafaa984aae4c 58c9b016e12855286370dfb704c08498edbc857a < 6dee745bd0aec9d399df674256e7b1ecdb615444 58c9b016e12855286370dfb704c08498edbc857a < 605c18698ecfa99165f36b7f59d3ed503e169814 58c9b016e12855286370dfb704c08498edbc857a < 8c2e52ebbe885c7eeaabd3b7ddcdc1246fc400d2
Linux / Linux
6.4

References

NVD โ†— CVE.org โ†— EPSS Data โ†—
git.kernel.org: https://git.kernel.org/stable/c/521e9ff0b67c66a17d6f9593dfccafaa984aae4c git.kernel.org: https://git.kernel.org/stable/c/6dee745bd0aec9d399df674256e7b1ecdb615444 git.kernel.org: https://git.kernel.org/stable/c/605c18698ecfa99165f36b7f59d3ed503e169814 git.kernel.org: https://git.kernel.org/stable/c/8c2e52ebbe885c7eeaabd3b7ddcdc1246fc400d2 project-zero.issues.chromium.org: https://project-zero.issues.chromium.org/issues/430541637