CVE-2026-31427 netfilter: nf_conntrack_sip: fix use of uninitialized rtp_addr in process_sdp

Medium 5.5 Published Updated

An attacker can cause the Linux kernel to leak stack memory or corrupt SIP session data by sending crafted SDP packets with no active media lines.

Exploited in the wild
Not known
Login needed
Any signed-in user
Attackable
Local or same network only
Victim action needed
Not needed
Fix
Available

What is CVE-2026-31427?

CVE-2026-31427 is a medium-severity vulnerability in Linux kernel, published on 13 Apr 2026. It can only be exploited from the same machine or local network, with no action from the victim.

Official description

In the Linux kernel, the following vulnerability has been resolved:

netfilter: nf_conntrack_sip: fix use of uninitialized rtp_addr in process_sdp

process_sdp() declares union nf_inet_addr rtp_addr on the stack and passes it to the nf_nat_sip sdp_session hook after walking the SDP media descriptions. However rtp_addr is only initialized inside the media loop when a recognized media type with a non-zero port is found.

If the SDP body contains no m= lines, only inactive media sections (m=audio 0 ...) or only unrecognized media types, rtp_addr is never assigned. Despite that, the function still calls hooks->sdp_session() with &rtp_addr, causing nf_nat_sdp_session() to format the stale stack value as an IP address and rewrite the SDP session owner and connection lines with it.

With CONFIG_INIT_STACK_ALL_ZERO (default on most distributions) this results in the session-level o= and c= addresses being rewritten to 0.0.0.0 for inactive SDP sessions. Without stack auto-init the rewritten address is whatever happened to be on the stack.

Fix this by pre-initializing rtp_addr from the session-level connection address (caddr) when available, and tracking via a have_rtp_addr flag whether any valid address was established. Skip the sdp_session hook entirely when no valid address exists.

Weakness: CWE-908

Which versions are affected by CVE-2026-31427?

It affects 1 product.

Products include Linux kernel.

How do I fix CVE-2026-31427?

Apply the vendor's patch.

Is CVE-2026-31427 being exploited?

There is no known exploitation of CVE-2026-31427 in the wild and no public exploit code.

All Linux kernel vulnerabilities

Sources

Also known as AZL-82709, BELL-CVE-2026-31427, DEBIAN-CVE-2026-31427, GHSA-w9rr-8fx7-936w, ROOT-OS-DEBIAN-11-CVE-2026-31427, ROOT-OS-DEBIAN-12-CVE-2026-31427 and 4 more.

Is CVE-2026-31427 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free