Skip to main content
VulnerabilityPublished Updated

CVE-2025-37928: Linux kernel · dm-bufio: don't schedule in atomic context

Affects Linux kernelSource GCVE Database

0
Compare

Public exploit available (Exploit-DB).

Data as of 5 Nov 2026, 22:03 UTC

Severity
High

Rated High by Threat Radar's AI analysis · No CVSS score from NVD or the CNA

Thin evidence

One scorer or none

Exploitation evidence

t = 0 is the CVE’s publication on cve.org

  1. Disclosed: evidence found.

    CVE published 20 May 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  4. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

Timeline

  1. CVE ID reserved

    by kernel.org

    , 34 days before disclosure

  2. CVE published

    on cve.org

    , t = 0

  3. First Exploit-DB entry (opens in a new tab)

    Parrot and DJI variants Drone OSes - Kernel Panic Exploit

    , 26 days after disclosure

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 5 Nov 2026.

What to do

AI-suggested

A fix for this issue has been implemented in the Linux kernel. Users and administrators should apply the official kernel updates that resolve this scheduling in atomic context bug in dm-bufio. Since this is a kernel-level issue, updating to the fixed kernel version is the recommended mitigation.

Description

CVE-2025-37928 is a vulnerability in the Linux kernel's dm-bufio component where a scheduling function is improperly called in an atomic context, causing a kernel BUG and potential system instability. This occurs when CONFIG_DEBUG_ATOMIC_SLEEP and try_verify_in_tasklet are enabled, leading to a sleeping function being invoked from an invalid context. The issue has been identified and resolved in the Linux kernel.

References

Community reviews

Loading reviews…