CVE-2025-38140: dm: limit swapping tables for devices with zone write plugs
dm: limit swapping tables for devices with zone write plugs
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
ubuntu/linux-aws-6.14to a version that resolves this vulnerability.Fixed in 6.14.0-1013.13~24.04.1 - Upgrade
Upgrade
ubuntu/linux-azure-nvidia-6.14to a version that resolves this vulnerability.Fixed in 6.14.0-1007.7 - Upgrade
Upgrade
ubuntu/linux-gcp-6.14to a version that resolves this vulnerability.Fixed in 6.14.0-1016.17~24.04.1 - Upgrade
Upgrade
ubuntu/linux-oem-6.14to a version that resolves this vulnerability.Fixed in 6.14.0-1012.12 - Upgrade
Upgrade
ubuntu/linux-oracle-6.14to a version that resolves this vulnerability.Fixed in 6.14.0-1013.13~24.04.1 - Upgrade
Upgrade
ubuntu/linux-riscv-6.14to a version that resolves this vulnerability.Fixed in 6.14.0-32.32.1~24.04.1 - Upgrade
Upgrade
ubuntu/linux-realtime-6.14to a version that resolves this vulnerability.Fixed in 6.14.0-1012.12~24.04.1 - Compensating control
For devices that already have zone write plug resources allocated, disallow table reloads that change zoned settings; permit switching only to another zoned table that also emulates zone append.
Event History
Frequently Asked Questions
What is the severity of CVE-2025-38140?
CVE-2025-38140 has been classified with a medium severity due to its potential impact on device zone handling in the Linux kernel.
How do I fix CVE-2025-38140?
To address CVE-2025-38140, update your Linux kernel to the latest patched version that resolves this vulnerability.
Which versions of the Linux kernel are affected by CVE-2025-38140?
CVE-2025-38140 affects specific versions of the Linux kernel that utilize device zone management.
What are the potential consequences of CVE-2025-38140?
The consequences of CVE-2025-38140 include possible data corruption or unexpected behavior during disk operations with zoned devices.
Is CVE-2025-38140 actively exploited in the wild?
As of now, there is no public information indicating that CVE-2025-38140 is actively exploited in the wild.