Red Hat Bugzilla – Bug 643290
sysctl: bad user of proc_doulongvec_minmax() can oops the kernel
Last modified: 2013-09-29 22:20:30 EDT
Description of problem: When proc_doulongvec_minmax() is used with an array of longs, and no min/max check requested (.extra1 or .extra2 being NULL), we dereference a NULL pointer for the second element of the array. Additional info: We need to backport the following two patches: commit 27b3d80a7b6adcf069b5e869e4efcc3a79f88a91 Author: Eric Dumazet <eric.dumazet@gmail.com> Date: Thu Oct 7 12:59:29 2010 -0700 and this one: http://www.spinics.net/lists/netdev/msg143210.html
Thank you for your bug report. This issue was evaluated for inclusion in the current release of Red Hat Enterprise Linux. Unfortunately, we are unable to address this request in the current release. Because we are in the final stage of Red Hat Enterprise Linux 6 development, only significant, release-blocking issues involving serious regressions and data corruption can be considered. If you believe this issue meets the release blocking criteria as defined and communicated to you by your Red Hat Support representative, please ask your representative to file this issue as a blocker for the current release. Otherwise, ask that it be evaluated for inclusion in the next minor release of Red Hat Enterprise Linux.
Patch(es) available on kernel-2.6.32-83.el6
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHSA-2011-0542.html