CVE-2022-49631: raw: Fix a data-race around sysctl_raw_l3mdev_accept.
In the Linux kernel, the following vulnerability has been resolved:
raw: Fix a data-race around sysctl_raw_l3mdev_accept.
While reading sysctl_raw_l3mdev_accept, 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-49631 is a Linux kernel race condition in raw networking sysctl handling. A low-privileged local user could potentially cause an availability impact, but the published CVSS rates exploitation as high complexity. There is no supplied evidence of active exploitation.
Executive priority
Treat as a routine kernel availability-risk patch, not an emergency, unless the environment has many untrusted local users or shared workloads. Bundle evidence supports medium severity and no confirmed active exploitation.
Technical view
The issue is CWE-362: sysctl_raw_l3mdev_accept could be read while being changed concurrently. Kernel stable fixes add READ_ONCE() around the reader. CVSS 3.1 is 4.7: local access, high attack complexity, low privileges, no confidentiality or integrity impact, high availability impact.
Likely exposure
Exposure is mainly unpatched Linux systems on affected kernel branches identified by the CVE metadata. Risk is most relevant where local low-privileged users can run code on the host. Distribution backports may change exact exposure, so validate against vendor kernel advisories.
Exploitation context
The bundle does not show KEV listing or other evidence of active exploitation. The CVSS vector indicates local, high-complexity exploitation requiring low privileges and no user interaction, with impact limited to availability.
Researcher notes
The fix is narrow: a reader of sysctl_raw_l3mdev_accept needed READ_ONCE() because the value can change concurrently. The source bundle does not provide a reproducer, affected distribution matrix, or exploit confirmation.
Mitigation direction
Apply kernel updates that include the referenced stable fixes.
Check Linux distribution advisories for backported fixes and package-specific version mapping.
Prioritize multi-user hosts and systems allowing local shell or workload execution.
Use normal change control and reboot processes required for kernel remediation.
Validation and detection
Identify running kernel versions across Linux hosts.
Map kernel packages to vendor advisories for CVE-2022-49631.
Confirm installed kernels include the relevant stable fix commits or vendor backports.
Review exposure of multi-user and shared workload systems first.
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.