CVE-2023-53619: netfilter: conntrack: Avoid nf_ct_helper_hash uses after free
In the Linux kernel, the following vulnerability has been resolved:
netfilter: conntrack: Avoid nf_ct_helper_hash uses after free
If nf_conntrack_init_start() fails (for example due to a
register_nf_conntrack_bpf() failure), the nf_conntrack_helper_fini()
clean-up path frees the nf_ct_helper_hash map.
When built with NF_CONNTRACK=y, further netfilter modules (e.g:
netfilter_conntrack_ftp) can still be loaded and call
nf_conntrack_helpers_register(), independently of whether nf_conntrack
initialized correctly. This accesses the nf_ct_helper_hash dangling
pointer and causes a uaf, possibly leading to random memory corruption.
This patch guards nf_conntrack_helper_register() from accessing a freed
or uninitialized nf_ct_helper_hash pointer and fixes possible
uses-after-free when loading a conntrack module.
Security readout for executives and security teams
Plain-English summary
A Linux netfilter cleanup flaw can leave a pointer referencing freed memory. If connection tracking fails during startup and a helper module is loaded afterward, the kernel may corrupt memory. Successful abuse could compromise system confidentiality, integrity, or availability, but the required failure sequence limits likely exposure.
Executive priority
Schedule expedited remediation for affected multi-user, container-hosting, or otherwise locally accessible Linux systems. Prioritize hosts showing conntrack initialization failures or using helper modules. Treat this as high-priority maintenance rather than a confirmed active incident because exploitation evidence is absent and the triggering state is specific.
Technical view
When nf_conntrack_init_start() fails, its cleanup path frees nf_ct_helper_hash. With NF_CONNTRACK built in, later loading a conntrack helper module can reach nf_conntrack_helper_register() and use the dangling pointer. The stable fix prevents access when the hash is freed or uninitialized. CVSS 3.1 is 7.8: local access, low complexity, low privileges, no user interaction.
Likely exposure
Exposure requires an affected Linux kernel with NF_CONNTRACK enabled, failed connection-tracking initialization, and subsequent conntrack helper-module loading. The bundle lists several affected releases through 6.5, but its version representation is ambiguous for distribution kernels. Internet reachability alone is insufficient; verify each vendor kernel against the applicable stable fix.
Exploitation context
The supplied CVSS vector describes a local, low-privilege attack context. However, the source bundle does not explain how an attacker reliably induces every prerequisite. The CVE is not marked as KEV, and the provided sources contain no evidence of active exploitation or a public exploit.
Researcher notes
The essential state transition is failed conntrack initialization, cleanup of nf_ct_helper_hash, then later helper registration through another module. Assessment should distinguish vulnerable source lineage from distribution backports. The bundle provides eight branch-specific stable commits but does not identify downstream package mappings, reliable triggering conditions, public proof-of-concept availability, or observed exploitation.
Mitigation direction
Upgrade to a vendor-supported kernel containing the applicable referenced stable fix.
Follow distribution guidance because the bundle does not map fixes to downstream package versions.
After conntrack initialization failure, avoid loading helper modules until rebooting into a confirmed fixed kernel.
Validation and detection
Record each running kernel release and vendor build, then compare it with vendor security guidance.
Confirm whether affected systems build NF_CONNTRACK into the kernel.
Review kernel logs for conntrack initialization or register_nf_conntrack_bpf failures.
Identify systems that load FTP or other conntrack helper modules.
After updating, verify the fixed kernel is running and test required netfilter functionality.
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-2023-53619 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.
1CVSS vectors
3Timeline events
0ADP providers
9Source links
CVSS vector scores
1 official score
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.