CVE-2025-38073: block: fix race between set_blocksize and read paths
block: fix race between setblocksize and read paths
Other sources
Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.
— NVD
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-hwe-6.14to a version that resolves this vulnerability.Fixed in 6.14.0-32.32~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
Event History
Frequently Asked Questions
What is the severity of CVE-2025-38073?
CVE-2025-38073 has been classified as a moderate severity vulnerability due to the potential for race conditions affecting block size operations.
How do I fix CVE-2025-38073?
To fix CVE-2025-38073, update your Linux kernel to the latest stable version that includes the fix for this vulnerability.
What are the potential impacts of CVE-2025-38073?
The potential impacts of CVE-2025-38073 include system instability and performance issues due to race conditions in block size handling.
Which versions of the Linux kernel are affected by CVE-2025-38073?
All versions of the Linux kernel prior to the fix that addresses CVE-2025-38073 are considered affected.
Is there a known exploit for CVE-2025-38073?
As of now, there are no publicly known exploits specifically targeting CVE-2025-38073.