Vulnerability · Published Feb 27, 2025 · Assigned by Linux
CVE-2025-21767clocksource: Use migrate_disable() to avoid calling get_random_u32() in atomic context
Medium 5.5
In plain English
A medium-severity security flaw in Linux from Linux. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.2% (higher than 7% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.
Official 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 packages & fixed versions
| Ecosystem | Package | Fixed in | Advisory |
|---|---|---|---|
| Debian:12 | linux | 6.1.129-1 | DEBIAN-CVE-2025-21767 |
| Debian:13 | linux | 6.12.16-1 | DEBIAN-CVE-2025-21767 |
| Debian:14 | linux | 6.12.16-1 | DEBIAN-CVE-2025-21767 |
| Ubuntu:22.04:LTS | linux | 5.15.0-140.150 | UBUNTU-CVE-2025-21767 |
| Ubuntu:24.04:LTS | linux | 6.8.0-78.78 | USN-7703-1 |
| Ubuntu:24.04:LTS | linux | 6.8.0-78.78 | UBUNTU-CVE-2025-21767 |
| Ubuntu:22.04:LTS | linux-allwinner-5.19 | no fix listed | UBUNTU-CVE-2025-21767 |
| Ubuntu:22.04:LTS | linux-aws | 5.15.0-1084.91 | UBUNTU-CVE-2025-21767 |
| Ubuntu:24.04:LTS | linux-aws | 6.8.0-1035.37 | USN-7703-1 |
| Ubuntu:24.04:LTS | linux-aws | 6.8.0-1035.37 | UBUNTU-CVE-2025-21767 |
| Ubuntu:22.04:LTS | linux-aws-5.19 | no fix listed | UBUNTU-CVE-2025-21767 |
| Ubuntu:22.04:LTS | linux-aws-6.2 | no fix listed | UBUNTU-CVE-2025-21767 |
| Ubuntu:22.04:LTS | linux-aws-6.5 | no fix listed | UBUNTU-CVE-2025-21767 |
| Ubuntu:22.04:LTS | linux-aws-6.8 | 6.8.0-1035.37~22.04.1 | UBUNTU-CVE-2025-21767 |
| Ubuntu:22.04:LTS | linux-aws-6.8 | 6.8.0-1035.37~22.04.1 | USN-7703-2 |
| Ubuntu:22.04:LTS | linux-azure | 5.15.0-1089.98 | UBUNTU-CVE-2025-21767 |
| Ubuntu:24.04:LTS | linux-azure | 6.8.0-1034.39 | UBUNTU-CVE-2025-21767 |
| Ubuntu:22.04:LTS | linux-azure-5.19 | no fix listed | UBUNTU-CVE-2025-21767 |
| Ubuntu:24.04:LTS | linux-azure-6.11 | 6.11.0-1015.15~24.04.1 | UBUNTU-CVE-2025-21767 |
| Ubuntu:22.04:LTS | linux-azure-6.2 | no fix listed | UBUNTU-CVE-2025-21767 |
| Ubuntu:22.04:LTS | linux-azure-6.5 | no fix listed | UBUNTU-CVE-2025-21767 |
| Ubuntu:22.04:LTS | linux-azure-6.8 | 6.8.0-1034.39~22.04.1 | UBUNTU-CVE-2025-21767 |
| Ubuntu:22.04:LTS | linux-azure-fde | 5.15.0-1089.98.1 | UBUNTU-CVE-2025-21767 |
| Ubuntu:22.04:LTS | linux-azure-fde-5.19 | no fix listed | UBUNTU-CVE-2025-21767 |
| Ubuntu:22.04:LTS | linux-azure-fde-6.2 | no fix listed | UBUNTU-CVE-2025-21767 |
| Ubuntu:24.04:LTS | linux-azure-nvidia | 6.8.0-1022.23 | UBUNTU-CVE-2025-21767 |
| Ubuntu:22.04:LTS | linux-gcp | 5.15.0-1083.92 | UBUNTU-CVE-2025-21767 |
| Ubuntu:24.04:LTS | linux-gcp | 6.8.0-1036.38 | USN-7703-2 |
| Ubuntu:24.04:LTS | linux-gcp | 6.8.0-1036.38 | UBUNTU-CVE-2025-21767 |
| Ubuntu:22.04:LTS | linux-gcp-5.19 | no fix listed | UBUNTU-CVE-2025-21767 |
| Ubuntu:24.04:LTS | linux-gcp-6.11 | 6.11.0-1015.15~24.04.1 | UBUNTU-CVE-2025-21767 |
| Ubuntu:22.04:LTS | linux-gcp-6.2 | no fix listed | UBUNTU-CVE-2025-21767 |
| Ubuntu:22.04:LTS | linux-gcp-6.5 | no fix listed | UBUNTU-CVE-2025-21767 |
| Ubuntu:22.04:LTS | linux-gcp-6.8 | 6.8.0-1036.38~22.04.1 | USN-7703-2 |
| Ubuntu:22.04:LTS | linux-gcp-6.8 | 6.8.0-1036.38~22.04.1 | UBUNTU-CVE-2025-21767 |
| Ubuntu:22.04:LTS | linux-gke | 5.15.0-1081.87 | UBUNTU-CVE-2025-21767 |
| Ubuntu:24.04:LTS | linux-gke | 6.8.0-1032.36 | UBUNTU-CVE-2025-21767 |
| Ubuntu:24.04:LTS | linux-gke | 6.8.0-1032.36 | USN-7703-4 |
| Ubuntu:22.04:LTS | linux-gkeop | 5.15.0-1066.74 | UBUNTU-CVE-2025-21767 |
| Ubuntu:24.04:LTS | linux-gkeop | 6.8.0-1019.21 | USN-7703-2 |
| Ubuntu:24.04:LTS | linux-gkeop | 6.8.0-1019.21 | UBUNTU-CVE-2025-21767 |
| Ubuntu:22.04:LTS | linux-hwe-5.19 | no fix listed | UBUNTU-CVE-2025-21767 |
| Ubuntu:24.04:LTS | linux-hwe-6.11 | 6.11.0-26.26~24.04.1 | UBUNTU-CVE-2025-21767 |
| Ubuntu:22.04:LTS | linux-hwe-6.2 | no fix listed | UBUNTU-CVE-2025-21767 |
| Ubuntu:22.04:LTS | linux-hwe-6.5 | no fix listed | UBUNTU-CVE-2025-21767 |
| Ubuntu:22.04:LTS | linux-hwe-6.8 | 6.8.0-78.78~22.04.1 | USN-7703-4 |
| Ubuntu:22.04:LTS | linux-hwe-6.8 | 6.8.0-78.78~22.04.1 | UBUNTU-CVE-2025-21767 |
| Ubuntu:22.04:LTS | linux-ibm | 5.15.0-1076.79 | UBUNTU-CVE-2025-21767 |
| Ubuntu:24.04:LTS | linux-ibm | 6.8.0-1033.33 | USN-7703-2 |
| Ubuntu:24.04:LTS | linux-ibm | 6.8.0-1033.33 | UBUNTU-CVE-2025-21767 |
| Ubuntu:22.04:LTS | linux-ibm-6.8 | 6.8.0-1033.33~22.04.1 | UBUNTU-CVE-2025-21767 |
| Ubuntu:22.04:LTS | linux-ibm-6.8 | 6.8.0-1033.33~22.04.1 | USN-7703-2 |
| Ubuntu:24.04:LTS | linux-intel | no fix listed | UBUNTU-CVE-2025-21767 |
| Ubuntu:22.04:LTS | linux-intel-iot-realtime | no fix listed | UBUNTU-CVE-2025-21767 |
| Ubuntu:22.04:LTS | linux-intel-iotg | 5.15.0-1079.85 | UBUNTU-CVE-2025-21767 |
| Ubuntu:22.04:LTS | linux-kvm | 5.15.0-1080.85 | UBUNTU-CVE-2025-21767 |
| Ubuntu:22.04:LTS | linux-lowlatency | 5.15.0-140.150 | UBUNTU-CVE-2025-21767 |
| Ubuntu:24.04:LTS | linux-lowlatency | 6.8.0-78.78.1 | USN-7703-1 |
| Ubuntu:24.04:LTS | linux-lowlatency | 6.8.0-78.78.1 | UBUNTU-CVE-2025-21767 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-5.19 | no fix listed | UBUNTU-CVE-2025-21767 |
| Ubuntu:24.04:LTS | linux-lowlatency-hwe-6.11 | 6.11.0-1014.15~24.04.1 | UBUNTU-CVE-2025-21767 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.2 | no fix listed | UBUNTU-CVE-2025-21767 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.5 | no fix listed | UBUNTU-CVE-2025-21767 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.8 | 6.8.0-78.78.1~22.04.1 | USN-7703-1 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.8 | 6.8.0-78.78.1~22.04.1 | UBUNTU-CVE-2025-21767 |
| Ubuntu:22.04:LTS | linux-nvidia | 5.15.0-1078.79 | UBUNTU-CVE-2025-21767 |
| Ubuntu:24.04:LTS | linux-nvidia | 6.8.0-1035.38 | USN-7703-4 |
| Ubuntu:24.04:LTS | linux-nvidia | 6.8.0-1035.38 | UBUNTU-CVE-2025-21767 |
| Ubuntu:24.04:LTS | linux-nvidia-6.11 | 6.11.0-1010.10 | UBUNTU-CVE-2025-21767 |
| Ubuntu:22.04:LTS | linux-nvidia-6.2 | no fix listed | UBUNTU-CVE-2025-21767 |
| Ubuntu:22.04:LTS | linux-nvidia-6.5 | no fix listed | UBUNTU-CVE-2025-21767 |
| Ubuntu:22.04:LTS | linux-nvidia-6.8 | 6.8.0-1035.38~22.04.1 | UBUNTU-CVE-2025-21767 |
| Ubuntu:22.04:LTS | linux-nvidia-6.8 | 6.8.0-1035.38~22.04.1 | USN-7703-4 |
| Ubuntu:24.04:LTS | linux-nvidia-lowlatency | 6.8.0-1035.38.1 | USN-7703-4 |
| Ubuntu:24.04:LTS | linux-nvidia-lowlatency | 6.8.0-1035.38.1 | UBUNTU-CVE-2025-21767 |
| Ubuntu:22.04:LTS | linux-nvidia-tegra | 5.15.0-1037.37 | UBUNTU-CVE-2025-21767 |
| Ubuntu:24.04:LTS | linux-nvidia-tegra | 6.8.0-1009.9 | UBUNTU-CVE-2025-21767 |
| Ubuntu:22.04:LTS | linux-nvidia-tegra-igx | 5.15.0-1026.26 | UBUNTU-CVE-2025-21767 |
| Ubuntu:22.04:LTS | linux-oem-5.17 | no fix listed | UBUNTU-CVE-2025-21767 |
| Ubuntu:22.04:LTS | linux-oem-6.0 | no fix listed | UBUNTU-CVE-2025-21767 |
| Ubuntu:22.04:LTS | linux-oem-6.1 | no fix listed | UBUNTU-CVE-2025-21767 |
| Ubuntu:24.04:LTS | linux-oem-6.11 | 6.11.0-1022.22 | UBUNTU-CVE-2025-21767 |
| Ubuntu:22.04:LTS | linux-oem-6.5 | no fix listed | UBUNTU-CVE-2025-21767 |
| Ubuntu:24.04:LTS | linux-oem-6.8 | no fix listed | UBUNTU-CVE-2025-21767 |
| Ubuntu:22.04:LTS | linux-oracle | 5.15.0-1081.87 | UBUNTU-CVE-2025-21767 |
| Ubuntu:24.04:LTS | linux-oracle | 6.8.0-1032.33 | UBUNTU-CVE-2025-21767 |
| Ubuntu:24.04:LTS | linux-oracle | 6.8.0-1032.33 | USN-7703-3 |
| Ubuntu:22.04:LTS | linux-oracle-6.5 | no fix listed | UBUNTU-CVE-2025-21767 |
| Ubuntu:22.04:LTS | linux-oracle-6.8 | 6.8.0-1032.33~22.04.1 | USN-7703-3 |
| Ubuntu:22.04:LTS | linux-oracle-6.8 | 6.8.0-1032.33~22.04.1 | UBUNTU-CVE-2025-21767 |
| Ubuntu:22.04:LTS | linux-raspi | 5.15.0-1078.81 | UBUNTU-CVE-2025-21767 |
| Ubuntu:24.04:LTS | linux-raspi | 6.8.0-1035.39 | UBUNTU-CVE-2025-21767 |
| Ubuntu:24.04:LTS | linux-raspi | 6.8.0-1035.39 | USN-7703-4 |
| Ubuntu:24.04:LTS | linux-raspi-realtime | no fix listed | UBUNTU-CVE-2025-21767 |
| Ubuntu:22.04:LTS | linux-realtime | no fix listed | UBUNTU-CVE-2025-21767 |
| Ubuntu:24.04:LTS | linux-realtime | no fix listed | UBUNTU-CVE-2025-21767 |
| Ubuntu:22.04:LTS | linux-riscv | no fix listed | UBUNTU-CVE-2025-21767 |
| Ubuntu:24.04:LTS | linux-riscv | no fix listed | UBUNTU-CVE-2025-21767 |
| Ubuntu:22.04:LTS | linux-riscv-5.19 | no fix listed | UBUNTU-CVE-2025-21767 |
| Ubuntu:22.04:LTS | linux-riscv-6.5 | no fix listed | UBUNTU-CVE-2025-21767 |
| Ubuntu:22.04:LTS | linux-riscv-6.8 | 6.8.0-78.78~22.04.1 | UBUNTU-CVE-2025-21767 |
| Ubuntu:22.04:LTS | linux-starfive-5.19 | no fix listed | UBUNTU-CVE-2025-21767 |
| Ubuntu:22.04:LTS | linux-starfive-6.2 | no fix listed | UBUNTU-CVE-2025-21767 |
| Ubuntu:22.04:LTS | linux-starfive-6.5 | no fix listed | UBUNTU-CVE-2025-21767 |
| Ubuntu:24.04:LTS | linux-xilinx | 6.8.0-1017.18 | UBUNTU-CVE-2025-21767 |
| Ubuntu:22.04:LTS | linux-xilinx-zynqmp | 5.15.0-1050.54 | UBUNTU-CVE-2025-21767 |
Affected products (as reported)
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | d9b40ebd448e437ffbc65f013836f98252279a82 – before d9c217fadfcff7a8df58567517d1e4253f3fd2437560c02bdffb7c52d1457fa551b9e745d4b9e754 – before 60f54f0d4ea530950549a8263e6fdd70a40490a47560c02bdffb7c52d1457fa551b9e745d4b9e754 – before 852805b6cbdb69c298a8fc9fbe79994c95106e047560c02bdffb7c52d1457fa551b9e745d4b9e754 – before 8783ceeee797d9aa9cfe150690fb9d0bac8cc4597560c02bdffb7c52d1457fa551b9e745d4b9e754 – before cc3d79e7c806cb57d71c28a4a35e7d7fb3265faa7560c02bdffb7c52d1457fa551b9e745d4b9e754 – before 0fb534187d2355f6c8f995321e76d1ccd1262ac17560c02bdffb7c52d1457fa551b9e745d4b9e754 – before 6bb05a33337b2c842373857b63de5c9bf1ae2a09193e14e68e907b2a7a936a7726accbaa4df25a4d |
| Linux | Linux | 5.14 |
References
- https://git.kernel.org/stable/c/d9c217fadfcff7a8df58567517d1e4253f3fd243
- https://git.kernel.org/stable/c/60f54f0d4ea530950549a8263e6fdd70a40490a4
- https://git.kernel.org/stable/c/852805b6cbdb69c298a8fc9fbe79994c95106e04
- https://git.kernel.org/stable/c/8783ceeee797d9aa9cfe150690fb9d0bac8cc459
- https://git.kernel.org/stable/c/cc3d79e7c806cb57d71c28a4a35e7d7fb3265faa
- https://git.kernel.org/stable/c/0fb534187d2355f6c8f995321e76d1ccd1262ac1
- https://git.kernel.org/stable/c/6bb05a33337b2c842373857b63de5c9bf1ae2a09
- https://lists.debian.org/debian-lts-announce/2025/05/msg00030.html
- https://lists.debian.org/debian-lts-announce/2025/03/msg00028.html
- https://cert-portal.siemens.com/productcert/html/ssa-082556.html
- https://cert-portal.siemens.com/productcert/html/ssa-784472.html