1. 26 1月, 2018 1 次提交
  2. 24 1月, 2018 1 次提交
  3. 11 1月, 2018 1 次提交
  4. 04 1月, 2018 1 次提交
  5. 29 12月, 2017 1 次提交
  6. 20 12月, 2017 1 次提交
  7. 19 12月, 2017 1 次提交
  8. 14 12月, 2017 1 次提交
  9. 09 12月, 2017 2 次提交
  10. 14 11月, 2017 1 次提交
  11. 11 11月, 2017 1 次提交
  12. 01 11月, 2017 1 次提交
  13. 27 10月, 2017 1 次提交
  14. 15 10月, 2017 3 次提交
  15. 11 10月, 2017 1 次提交
  16. 06 9月, 2017 2 次提交
  17. 29 8月, 2017 1 次提交
    • S
      cxgb4: Fix stack out-of-bounds read due to wrong size to t4_record_mbox() · 0f308686
      Stefano Brivio 提交于
      Passing commands for logging to t4_record_mbox() with size
      MBOX_LEN, when the actual command size is actually smaller,
      causes out-of-bounds stack accesses in t4_record_mbox() while
      copying command words here:
      
      	for (i = 0; i < size / 8; i++)
      		entry->cmd[i] = be64_to_cpu(cmd[i]);
      
      Up to 48 bytes from the stack are then leaked to debugfs.
      
      This happens whenever we send (and log) commands described by
      structs fw_sched_cmd (32 bytes leaked), fw_vi_rxmode_cmd (48),
      fw_hello_cmd (48), fw_bye_cmd (48), fw_initialize_cmd (48),
      fw_reset_cmd (48), fw_pfvf_cmd (32), fw_eq_eth_cmd (16),
      fw_eq_ctrl_cmd (32), fw_eq_ofld_cmd (32), fw_acl_mac_cmd(16),
      fw_rss_glb_config_cmd(32), fw_rss_vi_config_cmd(32),
      fw_devlog_cmd(32), fw_vi_enable_cmd(48), fw_port_cmd(32),
      fw_sched_cmd(32), fw_devlog_cmd(32).
      
      The cxgb4vf driver got this right instead.
      
      When we call t4_record_mbox() to log a command reply, a MBOX_LEN
      size can be used though, as get_mbox_rpl() will fill cmd_rpl up
      completely.
      
      Fixes: 7f080c3f ("cxgb4: Add support to enable logging of firmware mailbox commands")
      Signed-off-by: NStefano Brivio <sbrivio@redhat.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      0f308686
  18. 21 8月, 2017 1 次提交
  19. 09 8月, 2017 1 次提交
  20. 30 7月, 2017 1 次提交
  21. 21 7月, 2017 1 次提交
  22. 20 7月, 2017 1 次提交
  23. 24 6月, 2017 2 次提交
  24. 14 6月, 2017 1 次提交
  25. 10 6月, 2017 1 次提交
  26. 09 6月, 2017 1 次提交
  27. 03 6月, 2017 1 次提交
  28. 31 5月, 2017 2 次提交
  29. 22 5月, 2017 1 次提交
  30. 09 5月, 2017 1 次提交
  31. 23 3月, 2017 1 次提交
  32. 17 1月, 2017 1 次提交
  33. 14 1月, 2017 1 次提交
  34. 07 1月, 2017 1 次提交