CVE-2022-49920: netfilter: nf_tables: netlink notifier might race to release objects
In the Linux kernel, the following vulnerability has been resolved:
netfilter: nf_tables: netlink notifier might race to release objects
commit release path is invoked via call_rcu and it runs lockless to
release the objects after rcu grace period. The netlink notifier handler
might win race to remove objects that the transaction context is still
referencing from the commit release path.
Call rcu_barrier() to ensure pending rcu callbacks run to completion
if the list of transactions to be destroyed is not empty.
Security readout for executives and security teams
Plain-English summary
CVE-2022-49920 is a Linux kernel race condition in netfilter nf_tables. A local low-privileged user could potentially trigger a kernel availability failure. The public record rates it medium severity, with high attack complexity and no confidentiality or integrity impact identified.
Executive priority
Treat as routine but important kernel maintenance. Prioritize shared systems, multi-user servers, and environments where local users are less trusted. No source indicates active exploitation, but availability impact can still disrupt critical workloads.
Technical view
The issue is CWE-362 in nf_tables transaction cleanup. A netlink notifier can race with the RCU-based commit release path and remove objects still referenced by a transaction context. The kernel fix calls rcu_barrier() when pending transaction destruction exists, ensuring RCU callbacks complete before release continues.
Likely exposure
Exposure is most relevant to Linux systems running affected kernel versions with netfilter nf_tables present. The CVE data lists affected Linux kernel versions including 5.12, 5.15.78, 6.0.8, and 6.1, but distro-specific backport status is not provided.
Exploitation context
The CVSS vector requires local access, low privileges, no user interaction, and high attack complexity. Impact is availability only. The source bundle does not indicate public exploitation, and KEV status is false.
Researcher notes
The public record is concise and kernel-focused. It identifies the race and fix approach, but does not provide distro matrices, exploit evidence, or operational mitigations beyond applying fixed kernel code. Validate exposure through vendor backport information, not version numbers alone.
Mitigation direction
Check your Linux distribution or vendor advisory for patched kernel packages.
Prioritize kernel updates that include the referenced stable commits.
Reboot systems after kernel updates where required by your platform.
If immediate patching is blocked, reduce unnecessary local user access.
Validation and detection
Inventory Linux kernel versions across servers, endpoints, and appliances.
Confirm whether vendor kernels include the referenced stable fixes or backports.
Identify systems using affected kernel branches listed in the CVE data.
Track remediation through package management or kernel build records.
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.