CVE-2026-72251

CVE CVE-2026-72251EUVD EUVD-2026-59150Published 2026-08-15T05:54:39.000ZLast changed 2026-08-17T05:42:03.000ZCVSS 9.8

What the advisory describes

In the Linux kernel, the following vulnerability has been resolved: netfilter: nf_nat_sip: reload possible stale data pointer quoting sashiko: ------------------------------------------------------------------------ [..] noticed a potential memory bug and header corruption involving the SIP NAT helper. In net/netfilter/nf_nat_sip.c:nf_nat_sip(): if (skb_ensure_writable(skb, skb->len)) { nf_ct_helper_log(skb, ct, "cannot mangle packet"); return NF_DROP; } uh = (void *)skb->data + protoff; uh->dest = ct_sip_info->forced_dport; if (!nf_nat_mangle_udp_packet(skb, ct, ctinfo, protoff, 0, 0, NULL, 0)) { If a cloned or fragmented SKB is reallocated by skb_ensure_writable(), the old data buffer is freed. However, nf_nat_sip() fails to update *dptr to point to the new buffer. It also appears to use nf_nat_mangle_udp_packet() on what could be a TCP packet, which would overwrite the sequence number with a checksum update. ------------------------------------------------------------------------ nf_conntrack_sip linerizes skbs, hence no fragmented skb can be seen. But clones are possible, so rebuild dptr. Disable nf_nat_mangle_udp_packet() branch for TCP streams. It doesn't look like this can ever happen, else we should have received bug reports about this, so just check the conntrack is UDP and drop otherwise. The calling conntrack_sip set ->forced_dport for SIP_HDR_VIA_UDP messages, so I don't think this is ever expected to be true for a TCP stream.

Source: EUVD (ENISA), in the words of the advisory.

Products the advisory names

These come from the advisory itself, not from any check we performed.

• Linux — Linux 7266507d89991fa1e989283e4e032c6d9357fe26 <e38143c9b477f2968024c47c647dd4456a40aff1; 7266507d89991fa1e989283e4e032c6d9357fe26 <77e43bcb7ec177e293a5c3f1b91a2c5aebfb6c68; patch: 6.6.145; 7266507d89991fa1e989283e4e032c6d9357fe26 <2bcf2c5052fb5e73e255140ab43f056aef409c27; 3.9; patch: 5.10.261; patch: 6.1.178; 7266507d89991fa1e989283e4e032c6d9357fe26 <bded21a4bf9bf86a79148be735723a97ca9a7532; patch: 7.1.5; patch: 6.12.97; patch: 5.15.212; patch: 6.18.40; patch: 0; patch: 7.2; 7266507d89991fa1e989283e4e032c6d9357fe26 <0e76e3e886cc9ee027337d5ad39cb96f57b7bdc7; 7266507d89991fa1e989283e4e032c6d9357fe26 <57e4e29644ec054d7021d296407e7ddd844afea2; 7266507d89991fa1e989283e4e032c6d9357fe26 <eae9c6ccb5af69c713a65f8ae219f5c1aa32cd17; 7266507d89991fa1e989283e4e032c6d9357fe26 <dc11f26685aa850f237226f0f463647aea58ab7c

The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.

Carried in the product catalogue

An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.

• Linux — Linux

Patchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.