CVE-2025-39866: fs: writeback: fix use-after-free in __mark_inode_dirty()
Published Sep 19, 2025
·Updated
fs: writeback: fix use-after-free in markinodedirty()
Affected Software
12 affected components
Linux Linux kernel
Microsoft azl3 kernel 6.6.96.2-2
Microsoft azl3 kernel 6.6.104.2-4
Linux Linux kernel>=4.2<5.10.247
Linux Linux kernel>=5.11<5.15.192
Linux Linux kernel>=5.16<6.1.151
Linux Linux kernel>=6.2<6.6.105
Linux Linux kernel>=6.7<6.12.46
Linux Linux kernel>=6.13<6.16.6
Linux Linux kernel=6.17-rc1
Linux Linux kernel=6.17-rc2
Debian Debian Linux=11.0
Event History
Sep 19, 2025
CVE Published
via MITRE·03:26 PM
Data Sourced
via MITRE·03:26 PM
DescriptionSeverity
Data Sourced
via Red Hat·04:03 PM
DescriptionSeverityAffected Software
Data Sourced
via NVD·04:15 PM
RemedyDescriptionSeverityWeaknessAffected Software
Sep 21, 2025
Data Sourced
via Microsoft·01:03 AM
DescriptionSeverityWeaknessAffected Software
Updated
via Microsoft·01:03 AM
DescriptionSeverity
Updated
via Microsoft·01:03 AM
Affected Software
Frequently Asked Questions
1
What is the severity of CVE-2025-39866?
CVE-2025-39866 is classified as a high severity vulnerability due to the potential for a use-after-free condition that can lead to memory corruption.
2
How do I fix CVE-2025-39866?
To fix CVE-2025-39866, ensure you update to the patched version of the Linux kernel that addresses this vulnerability.
3
What systems are affected by CVE-2025-39866?
CVE-2025-39866 affects the Linux kernel, specifically versions that have not yet applied the security patch for this vulnerability.
4
What are the implications of CVE-2025-39866?
The implications of CVE-2025-39866 include potential system crashes and unauthorized access to sensitive information due to memory corruption.
5
Is CVE-2025-39866 being actively exploited?
As of now, there are no confirmed reports of CVE-2025-39866 being actively exploited in the wild, but it is recommended to apply patches promptly.