CVE-2022-49641: sysctl: Fix data races in proc_douintvec().
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.
Security readout for executives and security teams
Plain-English summary
CVE-2022-49641 is a Linux kernel data-race issue in sysctl handling. A local, low-privileged user could potentially trigger an availability impact under difficult conditions. There is no source-provided evidence of active exploitation or remote attack exposure.
Executive priority
Treat as routine-to-moderate Linux kernel maintenance. Prioritize environments with local untrusted users or dense shared workloads. It does not currently justify emergency action absent vendor escalation or exploitation evidence.
Technical view
The issue is a CWE-362 race in proc_douintvec(), where concurrent sysctl variable access lacked READ_ONCE()/WRITE_ONCE() protection, risking load/store tearing. CVSS 3.1 is 4.7: local attack vector, high complexity, low privileges, no user interaction, availability impact only.
Likely exposure
Exposure is limited to systems running affected Linux kernel versions or downstream builds containing the vulnerable sysctl code. Network-only attackers are not indicated by the CVSS vector. Confirm exposure through kernel version, vendor backport status, and referenced stable commits.
Exploitation context
The provided sources do not report public exploitation or CISA KEV listing. Exploitation requires local access, low privileges, and high-complexity timing conditions. Impact is modeled as availability loss, not confidentiality or integrity compromise.
Researcher notes
The record describes a resolved kernel race, not a detailed exploit path. The affected-version data in the supplied bundle is limited and should be reconciled with distro advisories because vendors often backport kernel fixes without changing major version numbers.
Mitigation direction
Check your Linux distribution’s advisory for CVE-2022-49641.
Update to a vendor kernel containing the referenced stable fixes.
Prioritize shared multi-user systems and container hosts for review.
If updates are delayed, monitor for unexplained kernel instability.
Validation and detection
Inventory Linux kernel versions across servers and endpoints.
Compare installed kernels with vendor fixed versions or backport notes.
Review whether referenced stable commits are included in your kernel source package.
Confirm no affected custom kernels remain in production.
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.