UBUNTU-CVE-2026-53349 (CVE-2026-53349)

Vulnerability from osv_ubuntu – Published: 2026-07-01 14:16 – Updated: 2026-11-19 04:01 – Source website
VLAI
Details

In the Linux kernel, the following vulnerability has been resolved: netfilter: nf_conntrack: destroy stale expectfn expectations on unregister NAT helpers such as nf_nat_h323 store a raw pointer to module text in exp->expectfn (e.g. ip_nat_q931_expect). nf_ct_helper_expectfn_unregister() only unlinks the callback descriptor and never walks the expectation table, so an expectation pending at module removal survives with a dangling exp->expectfn into freed module text. When the expected connection arrives, init_conntrack() invokes exp->expectfn(), now a stale pointer into the unloaded module. Reproduced on a KASAN build by loading the H.323 helpers, creating a Q.931 expectation, unloading nf_nat_h323, then connecting to the expected port: Oops: int3: 0000 [#1] SMP KASAN NOPTI RIP: 0010:0xffffffffa06102d1 init_conntrack.isra.0 (net/netfilter/nf_conntrack_core.c:1862) nf_conntrack_in (net/netfilter/nf_conntrack_core.c:2049) ipv4_conntrack_local (net/netfilter/nf_conntrack_proto.c:223) nf_hook_slow (net/netfilter/core.c:619) __ip_local_out (net/ipv4/ip_output.c:120) __tcp_transmit_skb (net/ipv4/tcp_output.c:1715) tcp_connect (net/ipv4/tcp_output.c:4374) tcp_v4_connect (net/ipv4/tcp_ipv4.c:345) __sys_connect (net/socket.c:2167) Modules linked in: nf_conntrack_h323 [last unloaded: nf_nat_h323] Reaching the dangling state requires CAP_SYS_MODULE in the initial user namespace to remove a NAT helper that still has live expectations, so this is a robustness fix; leaving an expectation pointing at freed text is wrong regardless. Add nf_ct_helper_expectfn_destroy(), which walks the expectation table and drops every expectation whose ->expectfn matches the descriptor being torn down. Call it from each NAT helper's exit path after the existing RCU grace period, so no expectation outlives the code it points at and no extra synchronize_rcu() is introduced. With the fix, the same reproducer runs to completion without the Oops.

Severity
References
https://ubuntu.com/security/CVE-2026-53349 REPORT
https://www.cve.org/CVERecord?id=CVE-2026-53349 REPORT
https://git.kernel.org/linus/c3009418f9fa1dcb3eb8… REPORT
https://git.kernel.org/stable/c/29d8cc44bbdf7b83a… REPORT
https://git.kernel.org/stable/c/9d017671dcfcec233… REPORT
https://git.kernel.org/stable/c/bf8c0b5dd203be94c… REPORT
https://git.kernel.org/stable/c/c3009418f9fa1dcb3… REPORT
https://git.kernel.org/stable/c/f92c90a2a3e6ff6f9… REPORT
https://git.kernel.org/stable/c/fbfde85308b99938a… REPORT
https://ubuntu.com/security/notices/USN-8726-1 ADVISORY
https://ubuntu.com/security/notices/USN-8727-1 ADVISORY
https://ubuntu.com/security/notices/USN-8728-1 ADVISORY
https://ubuntu.com/security/notices/USN-8760-1 ADVISORY
https://ubuntu.com/security/notices/USN-8726-2 ADVISORY
https://ubuntu.com/security/notices/USN-8726-3 ADVISORY
https://ubuntu.com/security/notices/USN-8800-1 ADVISORY
https://ubuntu.com/security/notices/USN-8760-2 ADVISORY
https://ubuntu.com/security/notices/USN-8728-2 ADVISORY
https://ubuntu.com/security/notices/USN-8726-4 ADVISORY
https://ubuntu.com/security/notices/USN-8728-3 ADVISORY
https://ubuntu.com/security/notices/USN-8903-1 ADVISORY
https://ubuntu.com/security/notices/USN-8905-1 ADVISORY
https://ubuntu.com/security/notices/USN-8906-1 ADVISORY
https://ubuntu.com/security/notices/USN-8904-1 ADVISORY
https://ubuntu.com/security/notices/USN-8903-2 ADVISORY
https://ubuntu.com/security/notices/USN-8905-2 ADVISORY
https://ubuntu.com/security/notices/USN-9002-1 ADVISORY
https://ubuntu.com/security/notices/USN-9025-1 ADVISORY
https://ubuntu.com/security/notices/USN-9066-1 ADVISORY

Loading 1.1 MB of JSON…



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline

Sightings and recorded dates, grouped by day · UTC

JSON
How durations are calculated

Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.

Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.

Events included in the timeline

Loading timeline…


    Loading…

    Loading…

    Loading…

    Related by attack behaviour

    Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.