Menu

Star on GitHub · 3.2k

CVE-2025-21767

5.5 · MEDIUM

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…

Published Feb 27, 2025CWE-667EPSS 0.18%

Overview

CVE-2025-21767 is a medium-severity vulnerability. It was published on February 27, 2025 and has a CVSS 3.1 base score of 5.5 (MEDIUM).

This vulnerability has a CVSS 3.1 base score of 5.5, rated MEDIUM. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

Technical 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

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2025-21767?

CVE-2025-21767 is a medium-severity vulnerability. It was published on February 27, 2025 and has a CVSS 3.1 base score of 5.5 (MEDIUM).

How severe is CVE-2025-21767?

This vulnerability has a CVSS 3.1 base score of 5.5, rated MEDIUM. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

How do I fix or remediate CVE-2025-21767?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2025-21767?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2025-21767 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related MEDIUM CVEs from 2025

View all