LiveActive security incident?Get immediate response
CVE Record

CVE-2022-49639: cipso: Fix data-races around sysctl.

In the Linux kernel, the following vulnerability has been resolved: cipso: Fix data-races around sysctl. While reading cipso sysctl variables, they can be changed concurrently. So, we need to add READ_ONCE() to avoid data-races.

MediumCVSS 4.7Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2022-49639 is a Linux kernel race condition in CIPSO sysctl handling. A local user could potentially trigger an availability impact under difficult conditions. It is not marked in CISA KEV, and the provided sources do not show active exploitation. Business urgency is moderate, mainly for systems allowing local user access on affected kernels.

Executive priority

Treat as a routine but important Linux kernel maintenance item. It is not a confirmed internet-facing or actively exploited issue in the provided sources, but local availability impact on shared systems can still affect operations.

Technical view

The Linux kernel CIPSO code read sysctl variables while they could be changed concurrently. The fix adds READ_ONCE() to avoid data races. The CVSS 3.1 vector is 4.7: local attack, high complexity, low privileges, no user interaction, unchanged scope, availability impact only. CWE is CWE-362.

Likely exposure

Exposure applies to Linux systems running affected kernel versions listed in the CVE record. The issue is in CIPSO sysctl code; the provided sources do not fully define which configurations are practically reachable. Prioritize multi-user Linux hosts and systems using CIPSO/NetLabel-related functionality.

Exploitation context

The CVSS vector indicates exploitation requires local access, low privileges, and high attack complexity. Impact is availability only, with no stated confidentiality or integrity impact. CISA KEV status is false, and the supplied sources do not report public exploitation.

Researcher notes

Evidence is limited to the CVE record and upstream stable commits. The CVE describes a data race fixed by READ_ONCE() around CIPSO sysctl reads. No exploit details, operational indicators, or distribution-specific fixed package versions are provided in the source bundle.

Mitigation direction

  • Update to a vendor-supported kernel containing the referenced stable fixes.
  • Check Linux distribution advisories for backported fixes for CVE-2022-49639.
  • Prioritize remediation on multi-user or shared Linux systems.
  • If immediate patching is not possible, reduce unnecessary local user access.

Validation and detection

  • Inventory Linux kernel versions across servers, endpoints, and appliances.
  • Compare installed kernels with vendor advisories for CVE-2022-49639.
  • Confirm deployed kernels include the relevant upstream stable fix commits.
  • Review whether CIPSO or NetLabel-related functionality is enabled or required.
Prepared
Confidence
high
Sources
10

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-49639 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
9Source 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-49639Attack 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
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux446fda4f26822b2d42ab3396aafcedf38a9ff2b6, 446fda4f26822b2d42ab3396aafcedf38a9ff2b6, 446fda4f26822b2d42ab3396aafcedf38a9ff2b6, 446fda4f26822b2d42ab3396aafcedf38a9ff2b6, 446fda4f26822b2d42ab3396aafcedf38a9ff2b6, 446fda4f26822b2d42ab3396aafcedf38a9ff2b6, 446fda4f26822b2d42ab3396aafcedf38a9ff2b6, 446fda4f26822b2d42ab3396aafcedf38a9ff2b6unaffected
LinuxLinux2.6.19, 0, 4.9.324, 4.14.289, 4.19.253, 5.4.207, 5.10.132, 5.15.56, 5.18.13, 5.19affected
Weakness

CWE details

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.