From: Jason Gunthorpe > Sent: 27 May 2015 00:30 > sctp_v4_map_v6 was subtly writing and reading from members > of a union in a way the clobbered data it needed to read before > it read it. > > Zeroing the v6 flowinfo overwrites the v4 sin_addr with 0, meaning > that every place that calls sctp_v4_map_v6 gets ::ffff:0.0.0.0 as the > result. > > Reorder things to guarantee correct behaviour no matter what the > union layout is. > > This impacts user space clients that open an IPv6 SCTP socket and > receive IPv4 connections. Prior to 299ee user space would see a > sockaddr with AF_INET and a correct address, after 299ee the sockaddr > is AF_INET6, but the address is wrong. > > Fixes: 299ee123e198 (sctp: Fixup v4mapped behaviour to comply with Sock API) ... > This bugfix should be a candidate for -stable Anyone know off-hand which kernel releases are affected? I'm going to have to note this in the release notes for one of our products. David -- To unsubscribe from this list: send the line "unsubscribe linux-sctp" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
