CVE-2025-40315

UnknownEPSS 0.17%

Last modified

CVE-2025-40315 is a vulnerability of currently unknown severity. In the Linux kernel, the following vulnerability has been resolved: usb: gadget: f_fs: Fix epfile null pointer access after ep enable. A race condition occurs when ffs_func_eps_enable() runs concurrently with ffs_data_reset(). The ffs_data_clear() called in ffs_data_reset() sets ffs->epfiles to NULL before resetting ffs->eps_count to 0, leading to a NULL pointer dereference when accessing epfile->ep in ffs_func_eps_enable() after successful usb_ep_enable(). The ffs->epfiles pointer is set to NULL in both ffs_data_clear() and ffs_data_close() functions, and its modification is protected by the spinlock ffs->eps_lock. EPSS estimates a 0.17% chance of exploitation in the next 30 days.

Description

In the Linux kernel, the following vulnerability has been resolved: usb: gadget: f_fs: Fix epfile null pointer access after ep enable. A race condition occurs when ffs_func_eps_enable() runs concurrently with ffs_data_reset(). The ffs_data_clear() called in ffs_data_reset() sets ffs->epfiles to NULL before resetting ffs->eps_count to 0, leading to a NULL pointer dereference when accessing epfile->ep in ffs_func_eps_enable() after successful usb_ep_enable(). The ffs->epfiles pointer is set to NULL in both ffs_data_clear() and ffs_data_close() functions, and its modification is protected by the spinlock ffs->eps_lock. And the whole ffs_func_eps_enable() function is also protected by ffs->eps_lock. Thus, add NULL pointer handling for ffs->epfiles in the ffs_func_eps_enable() function to fix issues

Metrics

EPSS Probability
0.17%

6.5th percentile

Probability of exploitation in the next 30 days. Learn more

Affected Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= c9fc422c9a43e3d58d246334a71f3390401781dc, < b00d2572c16e8e59e979960d3383c2ae9cebd195; >= 0042178a69eb77a979e36a50dcce9794a3140ef8, < 1c0dbd240be3f87cac321b14e17979b7e9cb6a8f; >= 72a8aee863af099d4434314c4536d6c9a61dcf3c, < 9ec40fba7357df2d36f4c2e2f3b9b1a4fba0a272; >= ebe2b1add1055b903e2acd86b290a85297edc0b3, < c53e90563bc148e4e0ad09fe130ba2246d426ea6; >= ebe2b1add1055b903e2acd86b290a85297edc0b3, < fc1141a530dfc91f0ee19b7f422a2d24829584bc; >= ebe2b1add1055b903e2acd86b290a85297edc0b3, < d62b808d5c68a931ad0849a00a5e3be3dd7e0019; >= ebe2b1add1055b903e2acd86b290a85297edc0b3, < 30880e9df27332403dd638a82c27921134b3630b; >= ebe2b1add1055b903e2acd86b290a85297edc0b3, < cfd6f1a7b42f62523c96d9703ef32b0dbc495ba4; 32048f4be071f9a6966744243f1786f45bb22dc2; cfe5f6fd335d882bcc829a1c8a7d462a455c626e; 3e078b18753669615301d946297bafd69294ad2c; >= 5.4.180, < 5.4.302; >= 5.10.101, < 5.10.247; >= 5.15.24, < 5.15.197; >= 4.14.267, < 4.15; >= 4.19.230, < 4.20; >= 5.16.10, < 5.17
LinuxLinux5.17

References

Timeline

Published
Last Modified
Status
Deferred

Frequently Asked Questions

What is CVE-2025-40315?
In the Linux kernel, the following vulnerability has been resolved: usb: gadget: f_fs: Fix epfile null pointer access after ep enable. A race condition occurs when ffs_func_eps_enable() runs concurrently with ffs_data_reset(). The ffs_data_clear() called in ffs_data_reset() sets ffs->epfiles to NULL before resetting ffs->eps_count to 0, leading to a NULL pointer dereference when accessing epfile->ep in ffs_func_eps_enable() after successful usb_ep_enable(). The ffs->epfiles pointer is set to NULL in both ffs_data_clear() and ffs_data_close() functions, and its modification is protected by the spinlock ffs->eps_lock. And the whole ffs_func_eps_enable() function is also protected by ffs->eps_lock. Thus, add NULL pointer handling for ffs->epfiles in the ffs_func_eps_enable() function to fix issues
How severe is CVE-2025-40315?
Severity scoring for CVE-2025-40315 is pending analysis. The EPSS model estimates a 0.17% probability of exploitation in the next 30 days.
How do I fix CVE-2025-40315?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2025

Are you affected by CVE-2025-40315?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST