sysctl: Fix data-races in proc_dou8vec_minmax().
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
sysctl: Fix data-races in proc_dou8vec_minmax().
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_dou8vec_minmax() to use READ_ONCE() and WRITE_ONCE() internally to fix data-races on the sysctl side. For now, proc_dou8vec_minmax() itself is tolerant to a data-race, but we still need to add annotations on the other subsystem's side.
From the CVE record · Linux
Concurrent access to a sysctl variable in the Linux kernel’s proc_dou8vec_minmax() can cause a data race and potential load/store tearing. The input does not specify an attacker action, access requirements, or user interaction.
Engineers running the Linux kernel should check their deployments; affected versions are not specified.