CVE-2025-21767

MediumCVSS 5.5/10Last modified Nov 5, 2026

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.

Metrics

CVSS 3.1 5.5/10CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Weakness enumeration

Affected software

VendorProductVersions
LinuxLinux>= d9b40ebd448e437ffbc65f013836f98252279a82, < d9c217fadfcff7a8df58567517d1e4253f3fd243; >= 7560c02bdffb7c52d1457fa551b9e745d4b9e754, < 60f54f0d4ea530950549a8263e6fdd70a40490a4; >= 7560c02bdffb7c52d1457fa551b9e745d4b9e754, < 852805b6cbdb69c298a8fc9fbe79994c95106e04; >= 7560c02bdffb7c52d1457fa551b9e745d4b9e754, < 8783ceeee797d9aa9cfe150690fb9d0bac8cc459; >= 7560c02bdffb7c52d1457fa551b9e745d4b9e754, < cc3d79e7c806cb57d71c28a4a35e7d7fb3265faa; >= 7560c02bdffb7c52d1457fa551b9e745d4b9e754, < 0fb534187d2355f6c8f995321e76d1ccd1262ac1; >= 7560c02bdffb7c52d1457fa551b9e745d4b9e754, < 6bb05a33337b2c842373857b63de5c9bf1ae2a09; 193e14e68e907b2a7a936a7726accbaa4df25a4d; 155d3c5d24ee13cafa6236b49fc02b240a511d59; >= 5.10.50, < 5.10.235; >= 5.12.17, < 5.13; >= 5.13.2, < 5.14
LinuxLinux5.14
SiemensSIMATIC S7-1500 CPU 1518-4 PN/DP MFP>= V3.1.5, < *
SiemensSIMATIC S7-1500 CPU 1518-4 PN/DP MFP>= V3.1.5, < *
SiemensSIMATIC S7-1500 CPU 1518F-4 PN/DP MFP>= V3.1.5, < *
SiemensSIMATIC S7-1500 CPU 1518F-4 PN/DP MFP>= V3.1.5, < *
SiemensSIMATIC S7-1500 TM MFP - GNU/Linux subsystem< *
SiemensSIPLUS S7-1500 CPU 1518-4 PN/DP MFP>= V3.1.5, < *

References

Timeline

Published
Feb 27, 2025
Last modified
Nov 5, 2026
NVD status
Modified

Related CVEs from 2025

CVE-2025-217685.5In the Linux kernel, the following vulnerability has been resolved: net: ipv6: fix dst ref loops in rpl, seg6 and ioam6 lwtunnels Some lwtCVE-2025-217695.5In the Linux kernel, the following vulnerability has been resolved: ptp: vmclock: Add .owner to vmclock_miscdev_fops Without the .owner fiCVE-2025-21776.5A vulnerability classified as critical was found in libzvbi up to 0.2.43. This vulnerability affects the function vbi_search_new of the fileCVE-2025-217705.5In the Linux kernel, the following vulnerability has been resolved: iommu: Fix potential memory leak in iopf_queue_remove_device() The iopCVE-2025-217715.5In the Linux kernel, the following vulnerability has been resolved: sched_ext: Fix incorrect autogroup migration detection scx_move_task()CVE-2025-217727.8In the Linux kernel, the following vulnerability has been resolved: partitions: mac: fix handling of bogus partition table Fix several issCVE-2025-217735.5In the Linux kernel, the following vulnerability has been resolved: can: etas_es58x: fix potential NULL pointer dereference on udev->serialCVE-2025-217745.5In the Linux kernel, the following vulnerability has been resolved: can: rockchip: rkcanfd_handle_rx_fifo_overflow_int(): bail out if skb cCVE-2025-217755.5In the Linux kernel, the following vulnerability has been resolved: can: ctucanfd: handle skb allocation failure If skb allocation fails, CVE-2025-217765.5In the Linux kernel, the following vulnerability has been resolved: USB: hub: Ignore non-compliant devices with too many configs or interfaCVE-2025-217775.5In the Linux kernel, the following vulnerability has been resolved: ring-buffer: Validate the persistent meta data subbuf array The meta dCVE-2025-217785.5In the Linux kernel, the following vulnerability has been resolved: tracing: Do not allow mmap() of persistent ring buffer When trying to
CVE-2025-21767: Medium severity, CVSS 5.5 | Vulnix