Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-52986netfilter: nf_conntrack_sip: don't use simple_strtoul

Description

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 <[email protected]>.

Timeline

  1. ID reserved

    By Linux

  2. · 15 days later

    Published

  3. · 5 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-52986, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1Critical9.8CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Modified3.1Critical9.8CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.63% · top 49% of all CVEs (17 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: yes · Technical impact: total
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Critical 9.8.

Affected products

  • Linux · Linux

    • affected 05e3ced297fe755093140e7487e292fb7603316e – < 8cd0358379570003659186706e077929d6930c40
    • affected 05e3ced297fe755093140e7487e292fb7603316e – < 9c6afcb1c3cbb2c0da65b8515ac14d7273872f84
    • affected 05e3ced297fe755093140e7487e292fb7603316e – < b3264c977e79d8a25778d4fd11520f00fea1329c
    • affected 05e3ced297fe755093140e7487e292fb7603316e – < ea2ecd29b8f4433e52607192ca91084f95787ca0
    • affected 05e3ced297fe755093140e7487e292fb7603316e – < 9f69c323ae0ab517e595c2cc74e0ae0d9d085611
    • affected 05e3ced297fe755093140e7487e292fb7603316e – < 7df9863bf538a626e8a684e59cb2c43eac0ef3c8
    • affected 05e3ced297fe755093140e7487e292fb7603316e – < 523762e3b6933fff81f01dfa3c60c0774044cdab
    • affected 05e3ced297fe755093140e7487e292fb7603316e – < 8cf6809cddcbe301aedfc6b51bcd4944d45795f6
  • Linux · Linux

    • affected 2.6.26
    • unaffected < 2.6.26
    • unaffected 5.10.258 – ≤ 5.10.*
    • unaffected 5.15.209 – ≤ 5.15.*
    • unaffected 6.1.175 – ≤ 6.1.*
    • unaffected 6.6.141 – ≤ 6.6.*
    • unaffected 6.12.91 – ≤ 6.12.*
    • unaffected 6.18.33 – ≤ 6.18.*
    • unaffected 7.0.10 – ≤ 7.0.*
    • unaffected 7.1 – ≤ *

References

References10

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-52986 badge
[![CVE-2026-52986](https://cveledger.app/badge/CVE-2026-52986.svg)](https://cveledger.app/cve/CVE-2026-52986)

Record last updated .