CVEvulnerability

CVE-2025-21694

5.5 MEDIUM Published 2025-02-12 Modified 2026-10-15 Official page ↗
Status
Modified
Published
2025-02-12
Last modified
2026-10-15
Assigner
416baaa9-dc9f-4396-8d5f-8c081fb06d67
CVSS 3.1 ([email protected])
5.5 MEDIUM — CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
CVSS 3.1 (134c704f-9b21-4f2e-91b3-4a467353bcc0)
5.5 MEDIUM — CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Description

In the Linux kernel, the following vulnerability has been resolved: fs/proc: fix softlockup in __read_vmcore (part 2) Since commit 5cbcb62dddf5 ("fs/proc: fix softlockup in __read_vmcore") the number of softlockups in __read_vmcore at kdump time have gone down, but they still happen sometimes. In a memory constrained environment like the kdump image, a softlockup is not just a harmless message, but it can interfere with things like RCU freeing memory, causing the crashdump to get stuck. The second loop in __read_vmcore has a lot more opportunities for natural sleep points, like scheduling out while waiting for a data write to happen, but apparently that is not always enough. Add a cond_resched() to the second loop in __read_vmcore to (hopefully) get rid of the softlockups.

Affected configurations

• linux linux kernel (>= 4.19.317 < 4.20) • linux linux kernel (>= 5.4.279 < 5.4.290) • linux linux kernel (>= 5.10.221 < 5.10.234) • linux linux kernel (>= 5.15.162 < 5.15.177) • linux linux kernel (>= 6.1.95 < 6.1.127) • linux linux kernel (>= 6.6.35 < 6.6.74) • linux linux kernel (>= 6.9.6 < 6.12.11) • linux linux kernel 6.13

References