CVE-2026-71401 SUSE CVE debrief

Who should care

Users of wicked DHCPv4 client, particularly those with untrusted networks, should verify and apply patches. Affected operators should review their deployments and assign owners for follow-up. Security teams should plan vendor-supported updates or mitigations through normal change control where exposure is confirmed.

Technical summary

The ni_capture_inspect_udp_header() function in wicked's DHCPv4 packet capture code does not verify the IP total length field before subtracting the header length, leading to an out-of-bounds read past the receive buffer. This can cause the wickedd-dhcp4 daemon to crash depending on the process memory layout. No information disclosure has been demonstrated. The issue affects wicked up to and including version 0.6.80.

Defensive priority

Medium-priority vulnerability in wicked DHCPv4 client; verify and apply vendor patches.

Recommended defensive actions

• Verify wicked version and apply patches if necessary
• Review process memory layout for potential impact
• Monitor for potential exploitation attempts
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
• Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance
• Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed
• Check relevant monitoring, detection, and logs for exposed assets that need extra review

Evidence notes

Integer underflow in wicked DHCPv4 packet capture code; verify patches and process memory layout impact. The issue affects wicked up to and including version 0.6.80. Users should verify their versions and apply patches if necessary. Defensive verification tasks include reviewing process memory layout for potential impact and monitoring for potential exploitation attempts.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.