CVE-2026-74569

CVE CVE-2026-74569EUVD EUVD-2026-59634Published 2026-08-15T12:28:09.000ZLast changed 2026-08-19T16:39:11.000ZCVSS 9.8

What the advisory describes

In the Linux kernel, the following vulnerability has been resolved: netfilter: nf_conntrack_sip: widen NAT rewrite delta to s32 in sip_help_tcp() sip_help_tcp() stores the size change of each NAT-rewritten SIP message in s16 diff and accumulates it in s16 tdiff, but a single message can grow by more than S16_MAX while the packet stays under the 65535 enlarge_skb() limit: nf_nat_sip() rewrites every matching URI, and a long Contact list expands the message by tens of kilobytes. diff then wraps, and "datalen = datalen + diff - msglen" yields a huge unsigned datalen, so the next iteration's ct_sip_get_header() reads past the linearized skb tail. Widen diff, tdiff and the seq_adjust hook to s32. Both are bounded by the 65535 byte packet limit, and the seqadj core is already s32 (nf_ct_seqadj_set() takes s32), so no previously accepted input is rejected. BUG: KASAN: use-after-free in ct_sip_get_header (net/netfilter/nf_conntrack_sip.c:464) Read of size 1 at addr ffff888010800000 by task ksoftirqd/1/25 ct_sip_get_header (net/netfilter/nf_conntrack_sip.c:464) sip_help_tcp (net/netfilter/nf_conntrack_sip.c:1694) nf_confirm (net/netfilter/nf_conntrack_proto.c:183) nf_hook_slow (net/netfilter/core.c:619) ip6_output (net/ipv6/ip6_output.c:246) ip6_forward (net/ipv6/ip6_output.c:690) ipv6_rcv (net/ipv6/ip6_input.c:351) __netif_receive_skb_one_core (net/core/dev.c:6212) process_backlog (net/core/dev.c:6676) __napi_poll (net/core/dev.c:7735) net_rx_action (net/core/dev.c:7955) handle_softirqs (kernel/softirq.c:622) run_ksoftirqd (kernel/softirq.c:1076) ...

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 f5b321bd37fbec9188feb1f721ab46a5ac0b35da <1b0843f9e9b9b0b9b4b70d143b67e58163c85b2c; patch: 6.18.44; patch: 0; f5b321bd37fbec9188feb1f721ab46a5ac0b35da <ed1f9be6dc8e2e280b8725e44ccdc6e0cd38640d; patch: 5.15.216; f5b321bd37fbec9188feb1f721ab46a5ac0b35da <c97621a110e386b2dd69e276eb699e1d3cec581d; f5b321bd37fbec9188feb1f721ab46a5ac0b35da <ef5e2c6555d2bb52dfe0e4053a8c6193f9d83b64; patch: 6.1.183; patch: 7.2; f5b321bd37fbec9188feb1f721ab46a5ac0b35da <f74554e67ccf04d1fa71069e8c9afa2717e40716; patch: 6.12.103; f5b321bd37fbec9188feb1f721ab46a5ac0b35da <63eea41759fd682229c14e0a2205802b46d106f3; patch: 6.6.151; 2.6.34; f5b321bd37fbec9188feb1f721ab46a5ac0b35da <32d4abc8923b0d4046fd63ad6e4917872e44eb6d; patch: 5.10.265; patch: 7.1.8; f5b321bd37fbec9188feb1f721ab46a5ac0b35da <db3d0e0e5d4bc5ab4fe445b9f413d1b486508ca5

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

Does this concern one of your customers?

This page cannot answer that — it does not know your estate. Whoever has recorded their environments gets the answer the morning after publication, together with a paragraph they can forward to the customer unedited.

Try it for 28 days

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.