CVE-2025-38411
HighIn the Linux kernel, the following vulnerability has been resolved: netfs: Fix double put of request If a netfs request finishes during the pause loop, it will have the ref that belongs to the IN_PROGRESS flag removed at that point - however, if it then goes to the final wait loop, that will *also* put the ref because it sees that the IN_PROGRESS flag is clear and incorrectly assumes that this happened when it called the collector. In fact, since IN_PROGRESS is clear, we shouldn't call the collector again since it's done all the cleanup, such as calling ->ki_complete(). Fix this by making netfs_collect_in_app() just return, indicating that we're done if IN_PROGRESS is removed.
CVSS 3.1 score
7.8
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Weakness type
CWE-415CVE-2025-38411 is classified as CWE-415
See CWE-415 on MITRE CWE for full details on this weakness type.
Affected versions
Linux kernel versions
6.15.3
and later are affected. Fixed in
6.15.6
and their respective stable series.
References
2 totalFrequently asked questions
-
What is CVE-2025-38411?
CVE-2025-38411 is a High severity Linux kernel vulnerability with a CVSS score of 7.8 out of 10 . It affects Linux kernel versions from 6.15.3 onward and has been patched in 6.15.6. CVE-2025-38411 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.
-
What is the CVSS score for CVE-2025-38411?
CVE-2025-38411 has a CVSS score of 7.8 out of 10, rated High severity (CVSS 3.1). The vector string is
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. -
Is there a patch available for CVE-2025-38411?
Yes. CVE-2025-38411 has been patched. Fixed versions include 6.15.6. If you are running Linux kernel 6.15.3 or later up to the fix versions, apply the relevant patch for your kernel branch.
-
Is CVE-2025-38411 actively exploited?
No. CVE-2025-38411 has not been confirmed as actively exploited. It is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.