CVE-2026-52986

In the Linux kernel, the following vulnerability has been resolved: netfilter: nf_conntrack_sip: don't use simple_strtoul Replace unsafe port parsing in epaddr_len(), ct_sip_parse_header_uri(), and ct_sip_parse_request() with a new sip_parse_port() helper that validates each digit against the buffer limit, eliminating the use of simple_strtoul() which assumes NUL-terminated strings. The previous code dereferenced pointers without bounds checks after sip_parse_addr() and relied on simple_strtoul() on non-NUL-terminated skb data. A port that reaches the buffer limit without a trailing character is also rejected as malformed. Also get rid of all simple_strtoul() usage in conntrack, prefer a stricter version instead. There are intentional changes: - Bail out if number is > UINT_MAX and indicate a failure, same for too long sequences. While we do accept 05535 as port 5535, we will not accept e.g. 'sip:10.0.0.1:005060'. While its syntactically valid under RFC 3261, we should restrict this to not waste cycles when presented with malformed packets with 64k '0' characters. - Force base 10 in ct_sip_parse_numerical_param(). This is used to fetch 'expire=' and 'rports='; both are expected to use base-10. - In nf_nat_sip.c, only accept the parsed value if its within the 1k-64k range. - epaddr_len now returns 0 if the port is invalid, as it already does for invalid ip addresses. This is intentional. nf_conntrack_sip performs lots of guesswork to find the right parts of the message to parse. Being stricter could break existing setups. Connection tracking helpers are designed to allow traffic to pass, not to block it. Based on an earlier patch from Jenny Guanni Qu <qguanni@gmail.com>.

• CWE-476

• https://git.kernel.org/stable/c/523762e3b6933fff81f01dfa3c60c0774044cdabPatch
• https://git.kernel.org/stable/c/7df9863bf538a626e8a684e59cb2c43eac0ef3c8Patch
• https://git.kernel.org/stable/c/8cd0358379570003659186706e077929d6930c40Patch
• https://git.kernel.org/stable/c/8cf6809cddcbe301aedfc6b51bcd4944d45795f6Patch
• https://git.kernel.org/stable/c/9c6afcb1c3cbb2c0da65b8515ac14d7273872f84Patch
• https://git.kernel.org/stable/c/9f69c323ae0ab517e595c2cc74e0ae0d9d085611Patch
• https://git.kernel.org/stable/c/b3264c977e79d8a25778d4fd11520f00fea1329cPatch
• https://git.kernel.org/stable/c/ea2ecd29b8f4433e52607192ca91084f95787ca0Patch

Published

Jun 24, 2026

Last Modified

Jul 14, 2026

Status

Analyzed

• How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
• Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
• PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
• AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.

• CVE-2026-52980In the Linux kernel, the following vulnerability has been re…5.5
• CVE-2026-52981In the Linux kernel, the following vulnerability has been re…7.5
• CVE-2026-52982In the Linux kernel, the following vulnerability has been re…9.8
• CVE-2026-52983In the Linux kernel, the following vulnerability has been re…7.5
• CVE-2026-52984In the Linux kernel, the following vulnerability has been re…5.5
• CVE-2026-52985In the Linux kernel, the following vulnerability has been re…5.5
• CVE-2026-52987In the Linux kernel, the following vulnerability has been re…7.8
• CVE-2026-52988In the Linux kernel, the following vulnerability has been re…7.1
• CVE-2026-52989In the Linux kernel, the following vulnerability has been re…9.8
• CVE-2026-5299ICMPv6 PvD protocol dissector crash in Wireshark 4.6.0 to 4.…5.5
• CVE-2026-52990In the Linux kernel, the following vulnerability has been re…5.5
• CVE-2026-52991In the Linux kernel, the following vulnerability has been re…7.8