CVE-2025-21694

fs/proc: fix softlockup in __read_vmcore (part 2)

MEDIUM
5.5
CVSS Score
Published: February 12, 2025 at 01:27 PM UTC
Updated: October 15, 2026 at 02:17 AM UTC
15 products affected across 2 vendorsLinux KernelSIMATIC S7-1500 CPU 1518-4 Pn /dp MFP FirmwareSiplus S7-1500 CPU 1518-4 Pn /dp MFP Firmware

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM5.5
Exploit prediction
EPSS 0.2%
SSVC
No known exploit

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

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

4.19.317 ≤ v < 4.205.10.221 ≤ v < 5.10.2345.15.162 ≤ v < 5.15.1775.4.279 ≤ v < 5.4.2906.1.95 ≤ v < 6.1.1276.6.35 ≤ v < 6.6.746.9.6 ≤ v < 6.12.114.19.3175.10.2215.15.1625.4.279518fbd644dabb6aedbdd4939c6c9cc1bf651459f5cbcb62dddf5346077feb82b7b0c9254222d34456.1.956.136.13 rc16.13 rc26.13 rc36.13 rc46.13 rc56.13 rc66.13 rc76.6.356.9.670c1835e776c8447c1aca87ddb38cfe764fe756a7bdf1d550ddfcd9ab797087421f77b7aceddc8a7803d5a33d5ffdc2d86dcc0cfa01655a330612cdba373ad833a6bfe4bc6cedcf7e56a99cc6fd9a193e1b160a50c756e0efbea290b9bf5117cb80e8c4be8780e8a0e25dc4c3927f611ec8970d26c0c7369
Vendor states this is fixed in 649b266606bc413407ce315f710c8ce8a88ee30a (fixed)
Vendor states this is fixed in 65c367bd9d4f43513c7f837df5753bea9561b836 (fixed)
Vendor states this is fixed in 80828540dad0757b6337c6561d49c81038f38d87 (fixed)
Vendor states this is fixed in 80da29deb88a3a907441fc35bb7bac309f31e713 (fixed)
Vendor states this is fixed in 84c4ed15626574c9ac6c1039ba9c137a77bcc7f2 (fixed)
Vendor states this is fixed in a5a2ee8144c3897d37403a69118c3e3dc5713958 (fixed)
Vendor states this is fixed in cbc5dde0a461240046e8a41c43d7c3b76d5db952 (fixed)
Affected range stops below 4.20, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 5.10.234 (unaffected)
Vendor states this is fixed in 5.15.177 (unaffected)
Vendor states this is fixed in 5.4.290 (unaffected)
Vendor states this is fixed in 6.1.127 (unaffected)
Vendor states this is fixed in 6.10 (unaffected)
Vendor states this is fixed in 6.12.11 (unaffected)
Vendor states this is fixed in 6.13 (unaffected)
Vendor states this is fixed in 6.6.74 (unaffected)
v < V3.2
Affected range stops below V3.2, so it looks safe — our inference, not a vendor statement
v < V3.2
Affected range stops below V3.2, so it looks safe — our inference, not a vendor statement
v < V3.2
Affected range stops below V3.2, so it looks safe — our inference, not a vendor statement
v < V3.2
Affected range stops below V3.2, so it looks safe — our inference, not a vendor statement
v < V3.2
Affected range stops below V3.2, so it looks safe — our inference, not a vendor statement
v < V3.2
Affected range stops below V3.2, so it looks safe — our inference, not a vendor statement
v < V3.2
Affected range stops below V3.2, so it looks safe — our inference, not a vendor statement
v < V3.2
Affected range stops below V3.2, so it looks safe — our inference, not a vendor statement
v < V3.2
Affected range stops below V3.2, so it looks safe — our inference, not a vendor statement

References (12)

Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/649b266606bc413407ce315f710c8ce8a88ee30a
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/65c367bd9d4f43513c7f837df5753bea9561b836
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/80828540dad0757b6337c6561d49c81038f38d87
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/80da29deb88a3a907441fc35bb7bac309f31e713
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/84c4ed15626574c9ac6c1039ba9c137a77bcc7f2
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/a5a2ee8144c3897d37403a69118c3e3dc5713958
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/cbc5dde0a461240046e8a41c43d7c3b76d5db952
Source: af854a3a-2127-422b-91ae-364da2661108
https://lists.debian.org/debian-lts-announce/2025/03/msg00001.html

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

5.5MEDIUMCISA-ADP
Attack Vector
LOCAL
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusMODIFIED
CWE
NVD-CWE-noinfo

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card