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 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.

Package Linux Kernel
Published 2025-02-27
Last modified 2026-05-12
CVSS version 3.1
Patch available
Yes

CVSS 3.1 score

5.5

out of 10
Medium
Attack Vector
Local
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
High
Vector string
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Weakness type

CWE-667

CVE-2025-21767 is a Improper Locking vulnerability

What is Improper Locking?

The product does not properly acquire or release a lock, which can lead to unexpected behaviour. Learn more on MITRE CWE

Affected versions

Linux kernel versions 5.10.50, 5.12.17, 5.13.2, 5.14 and later are affected. Fixed in 5.10.235, 5.15.179, 6.1.129, 6.6.79, 6.12.16, 6.13.4, 6.14 and their respective stable series.

Affected from
≥ 5.10.50 ≥ 5.12.17 ≥ 5.13.2 ≥ 5.14
Fixed in
✓ 5.10.235 5.10.x ✓ 5.15.179 5.15.x ✓ 6.1.129 6.1.x ✓ 6.6.79 6.6.x ✓ 6.12.16 6.12.x ✓ 6.13.4 6.13.x ✓ 6.14

References

The following references provide additional information about CVE-2025-21767 including vendor advisories, patch commits, exploit details, and third-party analysis. Links are sourced from the NIST NVD database.

7 patch commits total View all on NVD

Frequently asked questions

  • What is CVE-2025-21767?

    CVE-2025-21767 is a Medium severity Linux kernel vulnerability with a CVSS score of 5.5 out of 10 , classified as an Improper Locking flaw (CWE-667) . It affects Linux kernel versions from 5.10.50 onward and has been patched in 5.10.235, 5.15.179, 6.1.129 and others. CVE-2025-21767 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.

  • What is the CVSS score for CVE-2025-21767?

    CVE-2025-21767 has a CVSS score of 5.5 out of 10, rated Medium severity (CVSS 3.1). The vector string is CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H .

  • Is there a patch available for CVE-2025-21767?

    Yes — CVE-2025-21767 has been patched. Fixed versions include 5.10.235, 5.15.179, 6.1.129 and others. If you are running Linux kernel 5.10.50 or later up to the fix versions, apply the relevant patch for your kernel branch.

  • Is CVE-2025-21767 actively exploited?

    No — CVE-2025-21767 has not been confirmed as actively exploited. It is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.

  • What is Improper Locking (CWE-667)?

    The product does not properly acquire or release a lock, which can lead to unexpected behaviour. View CWE-667 on MITRE CWE →

Back to
All CVEs
View on
NVD / NIST