CVE-2026-23457: netfilter: nf_conntrack_sip: fix Content-Length u32 truncation in sip_help_tcp()
In the Linux kernel, the following vulnerability has been resolved:
netfilter: nf_conntrack_sip: fix Content-Length u32 truncation in sip_help_tcp()
sip_help_tcp() parses the SIP Content-Length header with
simple_strtoul(), which returns unsigned long, but stores the result in
unsigned int clen. On 64-bit systems, values exceeding UINT_MAX are
silently truncated before computing the SIP message boundary.
For example, Content-Length 4294967328 (2^32 + 32) is truncated to 32,
causing the parser to miscalculate where the current message ends. The
loop then treats trailing data in the TCP segment as a second SIP
message and processes it through the SDP parser.
Fix this by changing clen to unsigned long to match the return type of
simple_strtoul(), and reject Content-Length values that exceed the
remaining TCP payload length.
Security readout for executives and security teams
Plain-English summary
A remotely supplied oversized SIP Content-Length can be truncated by Linux’s netfilter SIP connection-tracking code. This can make the kernel misidentify message boundaries and process trailing network data incorrectly. The supplied CVSS score is 8.6, with availability identified as the greatest potential impact.
Executive priority
Treat this as a high-priority patching issue for systems actively processing untrusted SIP traffic, especially network infrastructure whose failure would disrupt communications. Absence from KEV and lack of cited exploitation evidence do not justify emergency-wide shutdowns, but exposed systems should enter the next expedited maintenance cycle.
Technical view
On 64-bit systems, sip_help_tcp() parsed Content-Length as unsigned long but stored it in unsigned int. Values above UINT_MAX could wrap before boundary calculation, causing subsequent TCP payload bytes to be treated as another SIP message and passed to the SDP parser. The stable fix preserves the wider type and rejects lengths exceeding the remaining payload.
Likely exposure
Likely exposure is limited to affected Linux kernels where the nf_conntrack_sip TCP helper is active and processes attacker-controlled SIP traffic. The bundle does not establish distribution defaults, appliance configurations, or vendor backport status. Consequently, kernel version strings alone may not reliably determine vulnerability.
Exploitation context
The CVSS vector describes network access, low complexity, no required privileges, and no user interaction. However, this CVE is not listed in KEV, and the supplied sources provide no evidence of active exploitation or a public proof of concept. Reachability of the vulnerable SIP-processing path remains essential.
Researcher notes
The demonstrated defect is an integer-width mismatch followed by incorrect SIP boundary handling. The fix changes clen to unsigned long and validates it against remaining TCP payload length. The bundle does not establish the precise downstream failure mode, affected distribution packages, a public exploit, or observed attacks; those points require vendor-specific confirmation.
Mitigation direction
Upgrade to a vendor-supported kernel release containing the applicable stable fix or documented backport.
Verify distribution and appliance advisories because packaged version numbers may not reveal backported fixes.
Prioritize reachable SIP gateways, firewalls, and other systems that process untrusted SIP-over-TCP traffic.
If patching is delayed, consult vendor guidance; the supplied sources name no supported interim workaround.
Validation and detection
Inventory kernel builds and determine whether the nf_conntrack_sip TCP helper is configured and active.
Confirm the installed source package contains the applicable stable fix or a vendor-documented equivalent backport.
Map network paths capable of delivering untrusted SIP-over-TCP traffic to the helper.
After updating, verify the running kernel changed and repeat the configuration and reachability checks.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2026-23457 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
1ADP providers
11Source links
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.