Independent & educational platform Not a government body. No link or affiliation with any government organisation. Made for learning only. Test only systems you own or are authorised to test. Become a Partner or Sponsor → Full disclaimer

CVE-2025-21767

medium

In the Linux kernel, the following vulnerability has been resolved: clocksource: Use migrate_disable() to avoid calling get_random_u32() in atomic context Th…

Vendor / product: Linux — linux kernel

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.

CVSS
5.5
5.5 (CVSS v3.1)
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Severity source: NVD CVSS v3.1 (nvd@nist.gov)
Timeline (UTC)
Published: 2025-02-27 03:15
Modified: 2026-11-05 21:17
NVD status: Modified
Last synced 1 week ago
Verified against the source API 2026-11-05 21:23 UTC
Exploitation
Not listed in CISA KEV (as of last catalog sync)
Absence from KEV does not mean a CVE is not exploited. Exploitation status: unknown (no authoritative evidence in our sources).

Affected products

linux / linux_kernel ≥5.10.50 <5.10.235, ≥5.12.17 <5.13, ≥5.13.2 <5.15.179, ≥5.16 <6.1.129, ≥6.2 <6.6.79, ≥6.7 <6.12.16

Weakness classification (CWE)

Source: NVD / CISA. “NVD-CWE-Other” and “NVD-CWE-noinfo” mean NVD could not assign a specific weakness.

Mitigation & advisories

Patch / mitigation: https://git.kernel.org/stable/c/0fb534187d2355f6c8f995321e76d1ccd1262ac1
Patch / mitigation: https://git.kernel.org/stable/c/60f54f0d4ea530950549a8263e6fdd70a40490a4
Patch / mitigation: https://git.kernel.org/stable/c/6bb05a33337b2c842373857b63de5c9bf1ae2a09
Patch / mitigation: https://git.kernel.org/stable/c/852805b6cbdb69c298a8fc9fbe79994c95106e04
Patch / mitigation: https://git.kernel.org/stable/c/8783ceeee797d9aa9cfe150690fb9d0bac8cc459
Patch / mitigation: https://git.kernel.org/stable/c/cc3d79e7c806cb57d71c28a4a35e7d7fb3265faa
Patch / mitigation: https://git.kernel.org/stable/c/d9c217fadfcff7a8df58567517d1e4253f3fd243

References

Data sources

NVD CVE API 2.0 — fetched 2026-11-05 21:23 UTC · record ↗

Learn the basics

Understanding CVEs and CVSS Scores

Related CVEs