First published: Tue Jan 10 2012(Updated: )
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. <a href="http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=654876">http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=654876</a> code added in 2.6.36-rc8. Upstream commit: <a href="http://git.kernel.org/linus/a8c1f65c79cbbb2f7da782d4c9d15639a9b94b27">http://git.kernel.org/linus/a8c1f65c79cbbb2f7da782d4c9d15639a9b94b27</a> Acknowledgements: Red Hat would like to thank Simon McVittie for reporting this issue.
Credit: security@debian.org security@debian.org
Affected Software | Affected Version | How to fix |
---|---|---|
Linux Linux kernel | <3.0.17 | |
Linux Linux kernel | >=3.1<3.1.9 | |
Linux Linux kernel | >=3.2<3.2.1 | |
Redhat Enterprise Linux Eus | =5.6 | |
debian/linux-2.6 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.