CVE-2022-49640: sysctl: Fix data races in proc_douintvec_minmax().
In the Linux kernel, the following vulnerability has been resolved:
sysctl: Fix data races in proc_douintvec_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_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.
Security readout for executives and security teams
Plain-English summary
CVE-2022-49640 is a Linux kernel race condition in sysctl handling. It is not described as remotely exploitable and requires local low-privileged access with high attack complexity. The main security concern is availability, not data theft or privilege escalation. There is no cited evidence of active exploitation.
Executive priority
Treat as a moderate Linux maintenance issue. It does not justify emergency response based on current sources, but should be included in routine kernel patching, with higher priority for shared or multi-user Linux environments.
Technical view
The issue is a CWE-362 data race in proc_douintvec_minmax(). Concurrent sysctl reads and writes lacked READ_ONCE()/WRITE_ONCE() protection, creating possible load/store tearing. CVSS is 4.7: local, high complexity, low privileges, no user interaction, no confidentiality or integrity impact, high availability impact.
Likely exposure
Exposure is limited to systems running affected Linux kernel versions or downstream kernels without the referenced stable fixes. Risk is most relevant where untrusted local users can interact with sysctl-controlled kernel behavior. Distribution backports may change apparent version exposure.
Exploitation context
The source bundle marks this CVE as not in CISA KEV. No provided source states active exploitation. Exploitation would require local access and high-complexity timing against a kernel data race. The public description does not provide a complete exploit path.
Researcher notes
The public record describes the fix and race condition, but not a proven exploit technique. The affected-version data is kernel-specific and may not directly match distribution package versions. Validate using vendor backport status rather than upstream version numbers alone.
Mitigation direction
Apply Linux kernel updates from your distribution or vendor that include the referenced stable fixes.
Verify whether your vendor backported the READ_ONCE()/WRITE_ONCE() fix into older kernel packages.
Prioritize shared Linux hosts where low-privileged local users are present.
If no vendor advisory exists, track upstream stable commits and request vendor confirmation.
Validation and detection
Inventory Linux kernel versions across servers, appliances, and images.
Map installed kernels to vendor advisories or the referenced upstream stable commits.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-362: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-362 · source CWE mapping
Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')
Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.