Bug 2550254 (CVE-2026-94453)

Summary:	CVE-2026-94453 libreswan: IKEv2 Use-After-Free bug when using IKE-over-TCP
Product:	[Other] Security Response	Reporter:	OSIDB Bzimport <bzimport>
Component:	vulnerability	Assignee:	Product Security DevOps Team <prodsec-dev>
Status:	NEW ---	QA Contact:
Severity:	high	Docs Contact:
Priority:	high
Version:	unspecified	CC:	akhatavk, aos-team-art-private, asdas, dpaolell, echaudro, fleitner, jdelft, jupierce, ktraynor, lgarciaa, mbiarnes, ppalepu, ppostler, prdhamdh, rhel-process-autobot, rkhan, sfaye, sghai, sidsharm, suppawar, vlaad, watson-tool-maintainers
Target Milestone:	---	Keywords:	Security
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	---
Doc Text:	A use-after-free flaw was found in Libreswan's IKE-over-TCP handling. When a TCP connection closes and additional packet processing occurs for the same connection tuple, the IKE daemon may access a previously freed interface endpoint object. A remote, unauthenticated attacker may exploit this flaw to cause the pluto daemon to crash and restart, resulting in denial of service.	Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	2550355
Bug Blocks:

Description OSIDB Bzimport 2026-10-13 07:50:19 UTC

IKE state is retained in memory after the client closes the connection storing a pointer to iface_endpoint inside ike_sa.sa->st_iface_endpoint. Once this invalid pointer is used, the daemon crashes. This can happen before the remote peer has authenticated itself. The option for IKE over TCP is not enabled by default. Only configurations that contain listen-tcp=yes are affected. Continued triggering of this vulnerability can lead to a denial of service. Remote code execution could be possible.

Vulnerable versions : 4.0 up to and including 5.4
Not vulnerable      : 5.4.1 and 5.3.3