Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2025-21767clocksource: Use migrate_disable() to avoid calling get_random_u32() in atomic context

Description

In the Linux kernel, the following vulnerability has been resolved: clocksource: Use migrate_disable() to avoid calling get_random_u32() in atomic context The following bug report happened with a PREEMPT_RT kernel: BUG: sleeping function called from invalid context at kernel/locking/spinlock_rt.c:48 in_atomic(): 1, irqs_disabled(): 0, non_block: 0, pid: 2012, name: kwatchdog preempt_count: 1, expected: 0 RCU nest depth: 0, expected: 0 get_random_u32+0x4f/0x110 clocksource_verify_choose_cpus+0xab/0x1a0 clocksource_verify_percpu.part.0+0x6b/0x330 clocksource_watchdog_kthread+0x193/0x1a0 It is due to the fact that clocksource_verify_choose_cpus() is invoked with preemption disabled. This function invokes get_random_u32() to obtain random numbers for choosing CPUs. The batched_entropy_32 local lock and/or the base_crng.lock spinlock in driver/char/random.c will be acquired during the call. In PREEMPT_RT kernel, they are both sleeping locks and so cannot be acquired in atomic context. Fix this problem by using migrate_disable() to allow smp_processor_id() to be reliably used without introducing atomic context. preempt_disable() is then called after clocksource_verify_choose_cpus() but before the clocksource measurement is being run to avoid introducing unexpected latency.

Timeline

  1. ID reserved

    By Linux

  2. · 2 months later

    Published

  3. · 21 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2025-21767, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.18% · top 93% of all CVEs (15 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected d9b40ebd448e437ffbc65f013836f98252279a82 – < d9c217fadfcff7a8df58567517d1e4253f3fd243
    • affected 7560c02bdffb7c52d1457fa551b9e745d4b9e754 – < 60f54f0d4ea530950549a8263e6fdd70a40490a4
    • affected 7560c02bdffb7c52d1457fa551b9e745d4b9e754 – < 852805b6cbdb69c298a8fc9fbe79994c95106e04
    • affected 7560c02bdffb7c52d1457fa551b9e745d4b9e754 – < 8783ceeee797d9aa9cfe150690fb9d0bac8cc459
    • affected 7560c02bdffb7c52d1457fa551b9e745d4b9e754 – < cc3d79e7c806cb57d71c28a4a35e7d7fb3265faa
    • affected 7560c02bdffb7c52d1457fa551b9e745d4b9e754 – < 0fb534187d2355f6c8f995321e76d1ccd1262ac1
    • affected 7560c02bdffb7c52d1457fa551b9e745d4b9e754 – < 6bb05a33337b2c842373857b63de5c9bf1ae2a09
    • affected 193e14e68e907b2a7a936a7726accbaa4df25a4d
    • affected 155d3c5d24ee13cafa6236b49fc02b240a511d59
    • affected 5.10.50 – < 5.10.235
    • affected 5.12.17 – < 5.13
    • affected 5.13.2 – < 5.14
  • Linux · Linux

    • affected 5.14
    • unaffected < 5.14
    • unaffected 5.10.235 – ≤ 5.10.*
    • unaffected 5.15.179 – ≤ 5.15.*
    • unaffected 6.1.129 – ≤ 6.1.*
    • unaffected 6.6.79 – ≤ 6.6.*
    • unaffected 6.12.16 – ≤ 6.12.*
    • unaffected 6.13.4 – ≤ 6.13.*
    • unaffected 6.14 – ≤ *

References

References11

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2025-21767 badge
[![CVE-2025-21767](https://cveledger.app/badge/CVE-2025-21767.svg)](https://cveledger.app/cve/CVE-2025-21767)

Record last updated .