Back

MEDIUM

sysctl: Fix data races in proc_douintvec_minmax().

Published Feb 26, 2025

Description

A sysctl variable is accessed concurrently, and there is always a chance of data-race. So, all readers and writers need some basic protection to avoid load/store-tearing.

This patch changes proc_douintvec_minmax() to use READ_ONCE() and WRITE_ONCE() internally to fix data-races on the sysctl side. For now, proc_douintvec_minmax() itself is tolerant to a data-race, but we still need to add annotations on the other subsystem's side.

Affected products

Remediation

Red Hat statement

The bug can lead to incorrect numerical value being read with sysctl for some specific cases if race condition happened (when both modifying this value and reading). The security impact is limited, because no known vectors of attack and no actual kernel panic or other fail. The bug actual only for Red Hat Enterprise Linux 8 and already fixed in Red Hat Enterprise Linux 9 and later versions. The bug could happen only for the case of reading (with in parallel modifying) of specific type of values "a vector of unsigned ints with min/max values" and the max impact could be incorrect values being read.

Weaknesses (1)

References (10)

Change history (0)

No recorded changes yet.

Sources
CVE.org / MITRE
Status PUBLISHED
Assigner Linux
Published Feb 26, 2025
Updated May 11, 2026
Reserved Feb 26, 2025
CISA Vulnrichment
Updated Oct 1, 2025
NVD
Status Modified
Modified Jun 17, 2026
Red Hat
Severity Low
Public date Feb 26, 2025
ENISA EUVD
Assigner Linux
Published Feb 26, 2025
Updated May 11, 2026
Exploited since n/a
EUVD-2022-54592