bug list: other potential buffer overflows

From: Dan Carpenter
Date: Thu Feb 25 2010 - 04:18:30 EST


Hi Kernel Janitors,

These are mostly bugs. Fixing them will gain you eternal glory and honour.

It's from some recent patches to smatch that I'll hopefully push later today.

regars,
dan carpenter

drivers/gpu/drm/drm_edid.c +1032 add_detailed_modes(35) warn: buffer overflow 'data->data.timings' 5 <= 5
drivers/infiniband/core/user_mad.c +655 ib_umad_reg_agent(46) error: buffer overflow 'umm' 4 <= 6
drivers/infiniband/core/user_mad.c +655 ib_umad_reg_agent(46) error: buffer overflow 'umm' 4 <= 7
drivers/media/common/tuners/qt1010.c +387 qt1010_init(67) error: buffer overflow 'i2c_data' 34 <= 34
drivers/net/s2io.c +5811 s2io_vpd_read(47) error: buffer overflow 'vpd_data' 256 <= 256
drivers/net/s2io.c +5812 s2io_vpd_read(48) error: buffer overflow 'vpd_data' 256 <= 257
drivers/net/s2io.c +5814 s2io_vpd_read(50) error: buffer overflow 'vpd_data' 256 <= 257
drivers/net/s2io.c +5814 s2io_vpd_read(50) warn: buffer overflow 'vpd_data' 256 <= 258
drivers/net/wan/lmc/lmc_main.c +1916 lmc_softreset(76) warn: buffer overflow 'sc->lmc_txring' 32 <= 32
drivers/net/wireless/iwlwifi/iwl3945-base.c +1930 iwl3945_init_hw_rates(6) error: buffer overflow 'iwl3945_rates' 12 <= 12
drivers/net/wireless/iwlwifi/iwl3945-base.c +1938 iwl3945_init_hw_rates(14) error: buffer overflow 'iwl3945_rates' 12 <= 12
drivers/net/wireless/iwlwifi/iwl-3945.c +188 iwl3945_hwrate_to_plcp_idx(5) error: buffer overflow 'iwl3945_rates' 12 <= 12
drivers/staging/arlan/arlan-proc.c +471 arlan_sysctl_info(66) warn: buffer overflow 'priva->card->_3' 13 <= 13
drivers/staging/comedi/drivers/cb_pcidda.c +311 cb_pcidda_attach(31) error: buffer overflow 'cb_pcidda_boards' 6 <= 9
drivers/staging/otus/hal/hpani.c +102 zfHpAniAttach(29) error: buffer overflow 'HpPriv->ani' 50 <= 59
drivers/staging/rt2860/common/cmm_wpa.c +414 RTMPToWirelessSta(54) error: buffer overflow 'pAd->TxSwQueue' 4 <= 4
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/