{
  "affected": [
    {
      "ecosystem_specific": {
        "urgency": "not yet assigned"
      },
      "package": {
        "ecosystem": "Debian:12",
        "name": "linux"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "6.1.176-1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "ecosystem_specific": {
        "urgency": "not yet assigned"
      },
      "package": {
        "ecosystem": "Debian:13",
        "name": "linux"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "6.12.94-1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "ecosystem_specific": {
        "urgency": "not yet assigned"
      },
      "package": {
        "ecosystem": "Debian:14",
        "name": "linux"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "7.0.13-1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "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-\u003eexpectfn (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-\u003eexpectfn into freed module text.  When the expected connection arrives, init_conntrack() invokes exp-\u003eexpectfn(), 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 -\u003eexpectfn 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.",
  "id": "DEBIAN-CVE-2026-53349",
  "modified": "2026-09-14T16:47:29.175158484Z",
  "published": "2026-07-01T14:16:43.003Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://security-tracker.debian.org/tracker/CVE-2026-53349"
    }
  ],
  "severity": [
    {
      "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H",
      "type": "CVSS_V3"
    }
  ],
  "upstream": [
    "CVE-2026-53349"
  ]
}