CVE-2022-49638: icmp: Fix data-races around sysctl.
In the Linux kernel, the following vulnerability has been resolved:
icmp: Fix data-races around sysctl.
While reading icmp sysctl variables, they can be changed concurrently.
So, we need to add READ_ONCE() to avoid data-races.
Security readout for executives and security teams
Plain-English summary
CVE-2022-49638 is a Linux kernel reliability issue in ICMP system settings. A local, low-privileged user could potentially trigger a race condition that affects availability. It is not listed as known exploited, and the public record points to kernel stable fixes rather than a standalone workaround.
Executive priority
Schedule remediation through normal kernel patch cycles, with higher priority for shared servers, developer workstations, and container hosts where untrusted users or workloads run locally. No source provided here supports emergency response for active exploitation.
Technical view
The issue is a CWE-362 data race around ICMP sysctl reads. ICMP sysctl variables may be changed concurrently while being read, so the kernel fix adds READ_ONCE() protections. CVSS 3.1 is 4.7 with local access, high attack complexity, low privileges, no confidentiality or integrity impact, and high availability impact.
Likely exposure
Exposure is mainly Linux systems running affected kernel versions or downstream builds without the stable fix. The CVE record lists affected Linux kernel versions/branches including 3.18 through 5.19-era entries. Distribution backports may change practical exposure, so validate against your OS vendor kernel advisory and package version.
Exploitation context
The CVSS vector indicates local access, low privileges, no user interaction, and high attack complexity. The source bundle does not show CISA KEV listing or other cited evidence of active exploitation. Treat this primarily as a local availability risk until vendor-specific advisories indicate otherwise.
Researcher notes
The public description is narrow: ICMP sysctl data-race fixed by READ_ONCE(). The affected-version data is kernel-centric and may not map directly to distribution package versions. Use the linked kernel stable commits and distro advisories for precise applicability.
Mitigation direction
Update to a vendor-supported kernel containing the referenced stable fixes.
Check your Linux distribution advisory for backported fix status.
Prioritize multi-user systems and hosts running untrusted local workloads.
Reboot if required to ensure the patched kernel is active.
Validation and detection
Inventory running kernel versions across Linux assets.
Compare installed kernel packages with vendor advisory fixed versions.
Confirm the active kernel changed after update and reboot.
Track exceptions where vendor guidance is not yet available.
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.