CVE-2025-21767

clocksource: Use migrate_disable() to avoid calling get_random_u32() in atomic context

State
Published
Severity
Not scored
Published
Feb 27, 2025
Updated
Oct 15, 2026
Reserved
Dec 29, 2024

Read the record on cve.org

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.

Scores

The record has no CVSS score.

Weaknesses

The record names no weakness.

Affected Products

ProductVersions
LinuxLinux
  • d9b40ebd448e437ffbc65f013836f98252279a82 to before d9c217fadfcff7a8df58567517d1e4253f3fd243Affected
  • 7560c02bdffb7c52d1457fa551b9e745d4b9e754 to before 60f54f0d4ea530950549a8263e6fdd70a40490a4Affected
  • 7560c02bdffb7c52d1457fa551b9e745d4b9e754 to before 852805b6cbdb69c298a8fc9fbe79994c95106e04Affected
  • 7560c02bdffb7c52d1457fa551b9e745d4b9e754 to before 8783ceeee797d9aa9cfe150690fb9d0bac8cc459Affected
  • 7560c02bdffb7c52d1457fa551b9e745d4b9e754 to before cc3d79e7c806cb57d71c28a4a35e7d7fb3265faaAffected
  • 7560c02bdffb7c52d1457fa551b9e745d4b9e754 to before 0fb534187d2355f6c8f995321e76d1ccd1262ac1Affected
  • 7560c02bdffb7c52d1457fa551b9e745d4b9e754 to before 6bb05a33337b2c842373857b63de5c9bf1ae2a09Affected
  • 193e14e68e907b2a7a936a7726accbaa4df25a4dAffected
  • 155d3c5d24ee13cafa6236b49fc02b240a511d59Affected
  • 5.10.50 to before 5.10.235Affected
  • 5.12.17 to before 5.13Affected
  • 5.13.2 to before 5.14Affected
LinuxLinux
  • 5.14Affected
  • before 5.14Not affected
  • 5.10.235 through 5.10.*Not affected
  • 5.15.179 through 5.15.*Not affected
  • 6.1.129 through 6.1.*Not affected
  • 6.6.79 through 6.6.*Not affected
  • 6.12.16 through 6.12.*Not affected
  • 6.13.4 through 6.13.*Not affected
  • 6.14 and laterNot affected

References

Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.