CVE-2022-49633: icmp: Fix data-races around sysctl_icmp_echo_enable_probe.
In the Linux kernel, the following vulnerability has been resolved:
icmp: Fix data-races around sysctl_icmp_echo_enable_probe.
While reading sysctl_icmp_echo_enable_probe, it can be changed
concurrently. Thus, we need to add READ_ONCE() to its readers.
Security readout for executives and security teams
Plain-English summary
CVE-2022-49633 is a Linux kernel race condition in ICMP probe echo sysctl handling. A low-privileged local user may be able to trigger an availability impact under difficult conditions. It is not described as remotely exploitable, and the provided sources do not show active exploitation.
Executive priority
Treat as routine but real kernel patching work. It does not currently justify emergency response from the provided evidence, but shared Linux infrastructure should be updated promptly to reduce local denial-of-service risk.
Technical view
The bug is a CWE-362 data race around reads of sysctl_icmp_echo_enable_probe. The kernel fix adds READ_ONCE() for concurrent readers. CVSS is 4.7 with local access, high attack complexity, low privileges, no confidentiality or integrity impact, and high availability impact.
Likely exposure
Exposure is most relevant to Linux systems running affected kernel versions or downstream vendor kernels that include the vulnerable code and lack the stable fixes. Risk increases on multi-user hosts or environments allowing untrusted local code execution.
Exploitation context
The CVE is not in KEV, and the supplied sources do not claim public exploitation. The CVSS vector requires local access, low privileges, and high attack complexity, so this is mainly a local availability risk rather than a remote compromise path.
Researcher notes
The source evidence is limited to the CVE record and Linux stable commits. The root cause is a concurrent read of sysctl_icmp_echo_enable_probe without READ_ONCE(). No exploit details, operational mitigations, or affected distribution package lists are provided.
Mitigation direction
Apply vendor kernel updates that include the referenced Linux stable fixes.
Check distribution advisories for backported fixes before relying on version numbers alone.
Prioritize shared Linux hosts and systems running untrusted local workloads.
Monitor vendor guidance if immediate patching is not possible.
Validation and detection
Inventory Linux kernel versions and package release identifiers across affected hosts.
Confirm whether vendor kernels include the referenced stable commits or equivalent backports.
Review host roles for untrusted local users, containers, or workload execution.
Track remediation through normal kernel patch management evidence.
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.