CVE-2025-21767

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

MEDIUM
5.5
CVSS Score
Published: February 27, 2025 at 02:18 AM UTC
Updated: October 15, 2026 at 02:17 AM UTC
4 products affected across 2 vendorsLinux KernelSIMATIC S7-1500 CPU 1518-4 Pn /dp MFP FirmwareSiplus S7-1500 CPU 1518-4 Pn /dp MFP Firmware

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM5.5
Exploit prediction
EPSS 0.2%

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

5.10.50 ≤ v < 5.10.2355.12.17 ≤ v < 5.135.13.2 ≤ v < 5.15.1795.16 ≤ v < 6.1.1296.13 ≤ v < 6.13.46.2 ≤ v < 6.6.796.7 ≤ v < 6.12.16155d3c5d24ee13cafa6236b49fc02b240a511d59193e14e68e907b2a7a936a7726accbaa4df25a4d5.10.505.12.175.13.25.146.146.14 rc17560c02bdffb7c52d1457fa551b9e745d4b9e754d9b40ebd448e437ffbc65f013836f98252279a82
Vendor states this is fixed in 0fb534187d2355f6c8f995321e76d1ccd1262ac1 (fixed)
Vendor states this is fixed in 60f54f0d4ea530950549a8263e6fdd70a40490a4 (fixed)
Vendor states this is fixed in 6bb05a33337b2c842373857b63de5c9bf1ae2a09 (fixed)
Vendor states this is fixed in 852805b6cbdb69c298a8fc9fbe79994c95106e04 (fixed)
Vendor states this is fixed in 8783ceeee797d9aa9cfe150690fb9d0bac8cc459 (fixed)
Vendor states this is fixed in cc3d79e7c806cb57d71c28a4a35e7d7fb3265faa (fixed)
Vendor states this is fixed in d9c217fadfcff7a8df58567517d1e4253f3fd243 (fixed)
Vendor states this is fixed in 5.10.235 (unaffected)
Affected range stops below 5.13, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 5.14 (unaffected)
Vendor states this is fixed in 5.15.179 (unaffected)
Vendor states this is fixed in 6.1.129 (unaffected)
Vendor states this is fixed in 6.12.16 (unaffected)
Vendor states this is fixed in 6.13.4 (unaffected)
Vendor states this is fixed in 6.14 (unaffected)
Vendor states this is fixed in 6.6.79 (unaffected)

References (11)

Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/0fb534187d2355f6c8f995321e76d1ccd1262ac1
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/60f54f0d4ea530950549a8263e6fdd70a40490a4
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/6bb05a33337b2c842373857b63de5c9bf1ae2a09
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/852805b6cbdb69c298a8fc9fbe79994c95106e04
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/8783ceeee797d9aa9cfe150690fb9d0bac8cc459
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/cc3d79e7c806cb57d71c28a4a35e7d7fb3265faa
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/d9c217fadfcff7a8df58567517d1e4253f3fd243
Source: af854a3a-2127-422b-91ae-364da2661108
https://lists.debian.org/debian-lts-announce/2025/03/msg00028.html

CVSS

Attack Vector
LOCAL
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-667

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card