cve.bz

CVE-2025-37906 linux linux kernel: Race Condition

4.7 mediumEPSS 0.2%Fix available

Medium (4.7) in linux linux kernel. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.

On this page
In the Linux kernel, the following vulnerability has been resolved: ublk: fix race between io_uring_cmd_complete_in_task and ublk_cancel_cmd ublk_cancel_cmd() calls io_uring_cmd_done() to complete uring_cmd, but we may have scheduled task work via io_uring_cmd_complete_in_task() for dispatching request, then kernel crash can be triggered. Fix it by not trying to canceling the command if ublk block request is started.

Severity

CVSS 3.1

4.7 medium
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS
0.2% (unchanged from 0.2% a week ago; 0.1% 30 days ago) estimated probability of exploitation activity in the next 30 days; 8th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CWE
CWE-362 Concurrent Execution using Shared Resource with Improper Synchronization (Race Condition)
OWASP Top 10
A06:2025 Insecure Design
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2025-37906 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2025-37906?via=ask-ai-copy and https://cve.bz/cve/CVE-2025-37906?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2025-37906 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Linux6.7 and later

Fixed in

ProductRelease lineFixed in
Linux6.126.12.114
Linux6.146.14.6
Linuxlater releases6.15

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12linux-6.126.12.115-2~deb12u1DEBIAN-CVE-2025-37906
Debian13linux6.12.115-2DEBIAN-CVE-2025-37906
Debian14linux6.16.3-1DEBIAN-CVE-2025-37906
Ubuntu16.04:LTSlinux-hwe-edgeno fix listedUBUNTU-CVE-2025-37906
Ubuntu18.04:LTSlinux-gcp, linux-hwe, linux-oem and 12 moreno fix listedUBUNTU-CVE-2025-37906
Ubuntu20.04:LTSlinux-gke, linux-gkeop, linux-riscv and 26 moreno fix listedUBUNTU-CVE-2025-37906
Ubuntu22.04:LTSlinux-riscv, linux-aws-6.2, linux-aws-6.5 and 40 moreno fix listedUBUNTU-CVE-2025-37906
Ubuntu24.04:LTSlinux, linux-aws, linux-gcp and 25 moreno fix listedUBUNTU-CVE-2025-37906
Ubuntu24.04:LTSlinux-aws-6.14, linux-oracle-6.146.14.0-1009.9~24.04.1UBUNTU-CVE-2025-37906 USN-7665-2
Ubuntu24.04:LTSlinux-gcp-6.146.14.0-1011.11~24.04.1UBUNTU-CVE-2025-37906
Ubuntu24.04:LTSlinux-nvidia-tegra6.8.0-1035.38UBUNTU-CVE-2025-37906 USN-8781-1
Ubuntu24.04:LTSlinux-oem-6.146.14.0-1007.7UBUNTU-CVE-2025-37906 USN-7650-1
Ubuntu24.04:LTSlinux-riscv-6.146.14.0-24.24.1~24.04.1UBUNTU-CVE-2025-37906
Ubuntu25.04linux6.14.0-24.24USN-7649-1
Ubuntu25.04linux-aws6.14.0-1009.9USN-7649-2
11 more for Ubuntu in the JSON and on Ubuntu's page.
Alpaquita25linux-lts6.12.115-r0BELL-CVE-2025-37906
Alpaquitastreamlinux-lts6.18.35-r1BELL-CVE-2025-37906

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · Alpaquita.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

A moderate-severity race condition was found in the Linux kernel's ublk subsystem, which implements userspace block devices on top of io_uring. When a ublk command is canceled via ublk_cancel_cmd(), which calls io_uring_cmd_done() to complete the uring command, while task work for dispatching the block request has already been scheduled through io_uring_cmd_complete_in_task(), the race can trigger a kernel crash. A local user able to run a ublk userspace driver could use this flaw to cause a denial of service (kernel crash). Red Hat rates this flaw as Moderate severity (CVSS 3.1: 4.1, AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:H) because exploitation requires local access with high privileges and high attack complexity, and the impact is limited to system availability. This differs from the upstream CVEORG score of 7.8, which assumes low attack complexity, low privileges, and confidentiality and integrity impacts that Red Hat's assessment does not support. In Red Hat's product scope, only the Red Hat Enterprise Linux 10 kernel is affected, and the fix is currently deferred to a future update; the residual risk is a local denial of service that requires an actor with high privileges able to drive a ublk device. Red Hat Enterprise Linux 6, 7, 8, and 9, Red Hat In-Vehicle OS, and Hosted OpenShift Clusters are marked not affected because the vulnerable code is not present in those products.

Red Hat's mitigation

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 10kernelFix deferred
Red Hat Enterprise Linux 6kernelNot affected
Red Hat Enterprise Linux 7kernelNot affected
Red Hat Enterprise Linux 7kernel-rtNot affected
Red Hat Enterprise Linux 8kernelNot affected
Red Hat Enterprise Linux 8kernel-rtNot affected
Red Hat Enterprise Linux 9kernelNot affected
Red Hat Enterprise Linux 9kernel-rtNot affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2025-37906.

Attack patterns (CAPEC)

  • CAPEC-26 Leveraging Race Conditions Likelihood: High · Severity: High
  • CAPEC-29 Leveraging Time-of-Check and Time-of-Use (TOCTOU) Race Conditions Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON