CVE-2022-49632: icmp: Fix a data-race around sysctl_icmp_errors_use_inbound_ifaddr.
In the Linux kernel, the following vulnerability has been resolved:
icmp: Fix a data-race around sysctl_icmp_errors_use_inbound_ifaddr.
While reading sysctl_icmp_errors_use_inbound_ifaddr, it can be changed
concurrently. Thus, we need to add READ_ONCE() to its reader.
Security readout for executives and security teams
Plain-English summary
CVE-2022-49632 is a Linux kernel ICMP data-race flaw. The main business risk is local availability impact, not data theft or privilege escalation. The CVE record rates it medium with high attack complexity and no confidentiality or integrity impact.
Executive priority
Handle through routine kernel patch management, with higher priority for shared Linux hosts where local users or workloads are less trusted. There is no source evidence of active exploitation, but availability impact justifies timely remediation.
Technical view
The kernel reads sysctl_icmp_errors_use_inbound_ifaddr while it may be changed concurrently. The resolved fix adds READ_ONCE() around the reader. The issue is classified as CWE-362 and has CVSS 3.1 score 4.7: local, high complexity, low privileges, availability impact only.
Likely exposure
Exposure is likely limited to Linux systems running affected kernel builds or downstream vendor kernels that have not incorporated the stable fixes. Internet exposure alone is not the key factor because the CVSS vector is local attack vector with low privileges required.
Exploitation context
The supplied sources do not show active exploitation, and KEV is false. The CVSS vector indicates exploitation requires local access, low privileges, and high complexity, with no user interaction. Do not treat this as remotely exploitable based on the provided evidence.
Researcher notes
The evidence is narrow: the CVE description and stable commit references identify a race on sysctl_icmp_errors_use_inbound_ifaddr fixed with READ_ONCE(). The bundle does not provide exploit details, downstream distro status, or a standalone mitigation besides applying fixed kernel code.
Mitigation direction
Apply Linux distribution kernel updates that include the stable fixes.
Check vendor kernel advisories for CVE-2022-49632 coverage.
Prioritize shared, multi-user, and container-host Linux systems.
Use normal maintenance windows where operational risk is low.
Avoid claiming remediation until the patched kernel is booted.
Validation and detection
Inventory Linux kernel versions across servers and appliances.
Map each kernel to vendor fixed builds or stable commits.
Confirm package changelogs or advisories reference this CVE or ICMP fix.
Verify systems rebooted into the updated kernel.
Document exceptions where vendor guidance is unavailable.
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.