CVE-2025-22064: netfilter: nf_tables: don't unregister hook when table is dormant
In the Linux kernel, the following vulnerability has been resolved:
netfilter: nf_tables: don't unregister hook when table is dormant
When nf_tables_updchain encounters an error, hook registration needs to
be rolled back.
This should only be done if the hook has been registered, which won't
happen when the table is flagged as dormant (inactive).
Just move the assignment into the registration block.
Security readout for executives and security teams
Plain-English summary
This is a Linux kernel netfilter/nf_tables bug involving incorrect rollback when updating a chain on a dormant table. The public bundle does not provide CVSS, impact class, or exploit details, so business urgency should be driven by kernel exposure and vendor patch availability.
Executive priority
Treat as a kernel maintenance priority, not an emergency based on the supplied evidence. Prioritize patch tracking for Linux infrastructure where nftables is operationally important, and escalate only if vendor advisories add severity, exploitability, or active exploitation evidence.
Technical view
The fix prevents nf_tables from unregistering a hook during nf_tables_updchain error rollback when the table is dormant and the hook was never registered. The issue is in Linux kernel netfilter/nf_tables logic and is addressed by Linux stable commits listed in the CVE references.
Likely exposure
Exposure is limited to systems running affected Linux kernel versions with nf_tables/netfilter present. Internet-facing firewalls, container hosts, and Linux servers using nftables deserve inventory attention, but the provided sources do not define required privileges, impact, or reachable attack paths.
Exploitation context
The bundle marks KEV as false and provides no cited evidence of active exploitation or public weaponization. It also does not state whether exploitation is local, remote, or requires nftables administration capability.
Researcher notes
Key missing evidence: CVSS, CWE, impact, exploit prerequisites, and complete version-range semantics. The safest source-grounded conclusion is that this is a logic bug fixed in stable Linux branches; validation should focus on kernel provenance and whether distro backports include the fix.
Mitigation direction
Apply Linux kernel updates containing the referenced stable fixes.
Check distribution advisories for backported fixes before relying on version numbers alone.
Prioritize hosts using nftables, firewalls, routers, and container infrastructure.
If no vendor update is available, follow vendor guidance for interim risk reduction.
Validation and detection
Inventory running kernel versions across Linux assets.
Confirm whether nftables or netfilter-dependent services are in use.
Verify vendor kernel packages include one of the referenced stable fixes.
After updating, confirm systems boot into the fixed kernel.
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.
cve · low confidence lookup
CVE-2025-22064 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
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.
0CVSS vectors
3Timeline events
0ADP providers
6Source links
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
CVE publishedCVE Program
The CVE record was published.
Apr 16, 2025, 14:12 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.