Skip to main content
VulnerabilityPublished Updated

CVE-2026-53349: Linux kernel · netfilter: nf_conntrack: destroy stale expectfn expectations on unregister

Source GCVE Database

0

Not known to be exploited · CVSS 5.5 Medium.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score
5.5Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 1% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 1 Jul 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

AI-suggested

A fix has been implemented in the Linux kernel to properly destroy stale expectations during NAT helper module unregistering, preventing use-after-free crashes. Users should update to a Linux kernel version that includes this fix. Since this requires kernel module unloading privileges, limiting CAP_SYS_MODULE access reduces risk. Patch status is not explicitly stated here; check the vendor or Linux kernel advisories for the fixed kernel versions and apply updates accordingly.

Description

A vulnerability in the Linux kernel's netfilter nf_conntrack subsystem could cause a use-after-free condition when NAT helpers unregister while expectations still exist. This occurs because stale pointers to module code remain in the expectation table after module removal, leading to kernel crashes when those pointers are dereferenced. The issue requires CAP_SYS_MODULE privileges to exploit and is considered a robustness flaw rather than a direct attack vector.

References

Community reviews

Loading reviews…