Date: Mon, 22 May 2017 08:51:07 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 219356] Using AES-GCM with IPSEC with aesni module loaded panics FreeBSD 11 stable Message-ID: <bug-219356-8-rYS6t5KrTC@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-219356-8@https.bugs.freebsd.org/bugzilla/> References: <bug-219356-8@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219356 Andrey V. Elsukov <ae@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|freebsd-bugs@FreeBSD.org |ae@FreeBSD.org Status|New |In Progress --- Comment #4 from Andrey V. Elsukov <ae@FreeBSD.org> --- Created attachment 182793 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=182793&action=edit Proposed patch (untested) Thanks. The last trace is very helpful. Can you try this patch? It should be applicable to both stable/11 and head/. The problem triggered by error in crypto code. When AES-GCM fails authenticate decrypted data, it returns EBADMSG error code. This error code was handled incorrectly in new IPsec code and double free occurred for SA reference. This patch removed extra free(). -- You are receiving this mail because: You are the assignee for the bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-219356-8-rYS6t5KrTC>