LiveActive security incident?Get immediate response
CVE Record

CVE-2022-49634: sysctl: Fix data-races in proc_dou8vec_minmax().

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.

MediumCVSS 4.7Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel concurrency bug in sysctl handling. A local low-privileged user may be able to trigger a race condition that affects system availability. The sources do not show data theft, privilege escalation, or active exploitation evidence.

Executive priority

Treat as routine but real kernel hygiene. It is not internet-exploitable from the provided evidence, but availability impact matters on shared Linux infrastructure and should be addressed in normal kernel patch cycles.

Technical view

proc_dou8vec_minmax() could access a sysctl variable concurrently without basic READ_ONCE()/WRITE_ONCE() protection, creating a CWE-362 data race and possible load/store tearing. CVSS is 4.7: local attack vector, high complexity, low privileges, and high availability impact only.

Likely exposure

Exposure is mainly Linux systems running affected kernel versions or builds identified in the CVE metadata. Confirm against the exact deployed kernel and distribution backport status because source version ranges are limited and commit-based.

Exploitation context

The provided sources mark this as not in KEV and give no evidence of active exploitation. The CVSS vector requires local access, low privileges, and high attack complexity, with impact limited to availability.

Researcher notes

The core issue is unsynchronized sysctl access in proc_dou8vec_minmax(), fixed by READ_ONCE()/WRITE_ONCE() annotations. Evidence does not support exploitability beyond the CVSS local, high-complexity availability model.

Mitigation direction

  • Update to a kernel containing the referenced stable fixes.
  • Check Linux distribution advisories for backported fix status.
  • Prioritize multi-user, shared hosting, and container host environments.
  • Limit unnecessary local user access where patching is delayed.

Validation and detection

  • Inventory kernel versions across Linux fleets.
  • Compare deployed kernels with vendor fixed builds and referenced commits.
  • Check whether distributions have backported the stable fix.
  • Review exposure on systems allowing untrusted local users.
Prepared
Confidence
medium
Sources
6

Public sources used

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.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2022-49634 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
4.7 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

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.

1CVSS vectors
3Timeline events
1ADP providers
5Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

CVSS vector scores

1 official score

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.

ScoreVersionSeverityVectorExploitImpactSource
4.7CVSS 3.1MediumCVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H13.6CISA-ADP

Vulnerability scoring details

Base CVSS 3.1 score

4.7Medium
CVSS 3.1 vector shape for CVE-2022-49634Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
cvssV3_1other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux389dab6142d742f91010f38de0f1f2f440b97e1b, cb9444130662c6c13022579c861098f212db2562, cb9444130662c6c13022579c861098f212db2562, cb9444130662c6c13022579c861098f212db2562unaffected
LinuxLinux5.13, 0, 5.15.56, 5.18.13, 5.19affected
Weakness

CWE details

CWE-362

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.

Open CWE intelligenceSame-CWE CVEs