CVE-2022-49630: tcp: Fix a data-race around sysctl_tcp_ecn_fallback.
In the Linux kernel, the following vulnerability has been resolved:
tcp: Fix a data-race around sysctl_tcp_ecn_fallback.
While reading sysctl_tcp_ecn_fallback, 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
This is a Linux kernel race condition in TCP ECN fallback handling. A local low-privileged user may be able to trigger an availability impact, but the source data rates exploitation as high complexity and does not indicate data theft or integrity loss.
Executive priority
Handle through normal kernel patch governance, with priority for shared Linux hosts. This is not supported as internet-remote or actively exploited in the provided evidence, but availability impact makes delayed patching undesirable.
Technical view
The issue is a CWE-362 data race around reads of sysctl_tcp_ecn_fallback. The resolved kernel change adds READ_ONCE() to prevent concurrent modification from being read unsafely. CVSS is 4.7 with local attack vector, low privileges, high complexity, and high availability impact.
Likely exposure
Systems running affected Linux kernel versions or vendor kernels that have not backported the referenced stable fixes may be exposed. Exposure is mainly relevant where untrusted local users or workloads exist.
Exploitation context
The provided sources do not show active exploitation, and the CVE is not marked KEV. The CVSS vector indicates local access, low privileges, no user interaction, and high attack complexity.
Researcher notes
Focus analysis on kernel versions carrying the TCP ECN fallback sysctl code path and whether READ_ONCE() is present in the reader. The affected-version data is sparse, so distro backport verification is essential.
Mitigation direction
Apply Linux kernel or distro updates that include the referenced stable fixes.
Confirm whether your vendor kernel backports the READ_ONCE() fix.
Reboot into the patched kernel when required by your update process.
If no update is available, check vendor guidance for supported mitigations.
Validation and detection
Inventory Linux kernel versions across servers, endpoints, and container hosts.
Compare running kernels against vendor advisories and fixed stable commits.
Confirm patched systems are booted into the updated kernel.
Prioritize validation on multi-user and workload-hosting Linux systems.
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.