CVE-2025-21715: In the Linux kernel, the following vulnerability has been resolved: net: davicom: fix UAF in dm9000_drv_remove dm is netdev private data and it cann...

Description

In the Linux kernel, the following vulnerability has been resolved: net: davicom: fix UAF in dm9000_drv_remove dm is netdev private data and it cannot be used after free_netdev() call. Using dm after free_netdev() can cause UAF bug. Fix it by moving free_netdev() at the end of the function. This is similar to the issue fixed in commit ad297cd2db89 ("net: qcom/emac: fix UAF in emac_remove"). This bug is detected by our static analysis tool.

Metrics

CVSS 3.1

7.8/10

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

EPSS Probability

0.20%

10.1th percentile

Probability of exploitation in the next 30 days. Learn more

Weakness Enumeration

CWE-416

Affected Software

Vendor	Product	Versions
Linux	Linux Kernel	>= 4.4.262, < 4.5
Linux	Linux Kernel	>= 4.9.262, < 4.10
Linux	Linux Kernel	>= 4.14.226, < 4.15
Linux	Linux Kernel	>= 4.19.181, < 4.20
Linux	Linux Kernel	>= 5.4.106, < 5.4.291
Linux	Linux Kernel	>= 5.10.24, < 5.10.235
Linux	Linux Kernel	>= 5.11.7, < 5.15.179
Linux	Linux Kernel	>= 5.16, < 6.1.129
Linux	Linux Kernel	>= 6.2, < 6.6.76
Linux	Linux Kernel	>= 6.7, < 6.12.13
Linux	Linux Kernel	>= 6.13, < 6.13.2

References

Timeline

Published: Feb 27, 2025
Last Modified: Jun 17, 2026
Status: Modified

Frequently Asked Questions

What is CVE-2025-21715?

In the Linux kernel, the following vulnerability has been resolved: net: davicom: fix UAF in dm9000_drv_remove dm is netdev private data and it cannot be used after free_netdev() call. Using dm after free_netdev() can cause UAF bug. Fix it by moving free_netdev() at the end of the function. This is similar to the issue fixed in commit ad297cd2db89 ("net: qcom/emac: fix UAF in emac_remove"). This bug is detected by our static analysis tool.

How severe is CVE-2025-21715?

CVE-2025-21715 has a CVSS score of 7.8/10 (HIGH severity). The EPSS model estimates a 0.20% probability of exploitation in the next 30 days.

How do I fix CVE-2025-21715?

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.