CVE-2022-49641

sysctl: Fix data races in proc_douintvec().

MEDIUM
4.7
CVSS Score
Published: February 26, 2025 at 02:23 AM UTC
Updated: June 17, 2026 at 05:18 AM UTC
1 product affected across 1 vendorLinux Kernel

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
MEDIUM4.7
Exploit prediction
EPSS 0.2%
SSVC
No known exploit

Description

In the Linux kernel, the following vulnerability has been resolved: sysctl: Fix data races in proc_douintvec(). 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() to use READ_ONCE() and WRITE_ONCE() internally to fix data-races on the sysctl side. For now, proc_douintvec() itself is tolerant to a data-race, but we still need to add annotations on the other subsystem's side.

Affected

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

v ≥ 4.4.24v ≥ 4.7.74.4.24 ≤ v < 4.54.7.7 ≤ v < 4.84.7.7 ≤ v < 5.10.1324.8 ≤ v < 5.10.1324.8 ≤ v < 5.15.564.8 ≤ v < 5.18.134.8 ≤ v < 5.195.11 ≤ v < 5.15.565.16 ≤ v < 5.18.134.4.244.7.75.19 rc15.19 rc25.19 rc35.19 rc45.19 rc55.19 rc670cd763eb1574cac07138be91f474a661e02d694e7d316a02f683864a12389f8808570e37fb90aa3f4cea51e9a3d536e2ca2b74a958f7c0b4ea733c3
Vendor states this is fixed in 4762b532ec9539755aab61445d5da6e1926ccb99 (fixed)
Vendor states this is fixed in 630c76850d554d7140232e71b5d1663e88cffb54 (fixed)
Vendor states this is fixed in d335db59f7fb3353f56e52371f1ee796ae9c8f09 (fixed)
Vendor states this is fixed in d5d54714e329f646bd7af4994fc427d88ee68936 (fixed)
Affected range stops below 4.5, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 4.8 (unaffected)
Vendor states this is fixed in 5.10.132 (unaffected)
Vendor states this is fixed in 5.15.56 (unaffected)
Vendor states this is fixed in 5.18.13 (unaffected)
Vendor states this is fixed in 5.19 (unaffected)

References (4)

Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/4762b532ec9539755aab61445d5da6e1926ccb99
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/630c76850d554d7140232e71b5d1663e88cffb54
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/d335db59f7fb3353f56e52371f1ee796ae9c8f09
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/d5d54714e329f646bd7af4994fc427d88ee68936

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

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

CVSS

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

Quick Info

StatusMODIFIED
CWE
CWE-362

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