CVE-2025-21966: dm-flakey: Fix memory corruption in optional corrupt_bio_byte feature
Published Apr 1, 2025
·Updated
dm-flakey: Fix memory corruption in optional corruptbiobyte feature
Affected Software
12 affected componentsFixes available
Linux Kernel
Linux Linux kernel>=6.5<6.6.84
Linux Linux kernel>=6.7<6.12.20
Linux Linux kernel>=6.13<6.13.8
Linux Linux kernel=6.14-rc1
Linux Linux kernel=6.14-rc2
Linux Linux kernel=6.14-rc3
Linux Linux kernel=6.14-rc4
Linux Linux kernel=6.14-rc5
Linux Linux kernel=6.14-rc6
Microsoft azl3 kernel 6.6.85.1-2
Microsoft azl3 kernel 6.6.82.1-1
Event History
Apr 1, 2025
CVE Published
via MITRE·03:47 PM
Data Sourced
via MITRE·03:47 PM
DescriptionSeverity
Data Sourced
via Red Hat·04:02 PM
DescriptionSeverityAffected Software
Data Sourced
via NVD·04:15 PM
RemedyDescriptionSeverityWeaknessAffected Software
May 5, 2025
Data Sourced
via Microsoft·07:00 AM
DescriptionSeverityWeaknessAffected Software
Frequently Asked Questions
1
What is the severity of CVE-2025-21966?
CVE-2025-21966 is classified as a potential risk due to memory corruption issues in the Linux kernel.
2
How do I fix CVE-2025-21966?
To fix CVE-2025-21966, update your Linux kernel to the latest version that includes the patch for this vulnerability.
3
What systems are affected by CVE-2025-21966?
CVE-2025-21966 affects the Linux kernel, specifically systems using the dm-flakey module.
4
What problems does CVE-2025-21966 cause?
CVE-2025-21966 can lead to memory corruption, potentially impacting system stability and security.
5
Is there a workaround for CVE-2025-21966?
There are no known workarounds for CVE-2025-21966; applying the kernel update is the recommended solution.