DescriptionEugene Teo (Security Response)
2012-01-10 07:58:32 UTC
Commit 5b7c84066733c5dfb0e4016d939757b38de189e4 ('ipv4: correct IGMP behavior on v3 query during v2-compatibility mode') added yet another case for query parsing, which can result in max_delay = 0. Substitute a value of 1, as in the usual v3 case.
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=654876
code added in 2.6.36-rc8.
Upstream commit:
http://git.kernel.org/linus/a8c1f65c79cbbb2f7da782d4c9d15639a9b94b27
Acknowledgements:
Red Hat would like to thank Simon McVittie for reporting this issue.
Comment 3Eugene Teo (Security Response)
2012-01-10 08:09:35 UTC
Statement:
This issue did not affect the Linux kernel as shipped with Red Hat Enterprise Linux 4 as it did not backport the upstream commit 5b7c8406.
Comment 5Eugene Teo (Security Response)
2012-01-17 03:53:15 UTC
Commit 5b7c84066733c5dfb0e4016d939757b38de189e4 ('ipv4: correct IGMP behavior on v3 query during v2-compatibility mode') added yet another case for query parsing, which can result in max_delay = 0. Substitute a value of 1, as in the usual v3 case. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=654876 code added in 2.6.36-rc8. Upstream commit: http://git.kernel.org/linus/a8c1f65c79cbbb2f7da782d4c9d15639a9b94b27 Acknowledgements: Red Hat would like to thank Simon McVittie for reporting this issue.