The value of "size" comes from the user. When we add "start + size" it
could lead to an integer overflow bug.
It means we vmalloc() a lot more memory than we had intended. I believe
that on 64 bit systems vmalloc() can succeed even if we ask it to
allocate huge 4GB buffers. So we would get memory corruption and likely
a crash when we call ha->isp_ops->write_optrom() and ->read_optrom().
> From our CVE tracker, only Trusty and Zesty need this patch.
> This patch can fix the integer overflow problem in the
> qla2x00_sysfs_write_optrom_ctl function in drivers/scsi/qla2xxx/qla_attr.c
> Dan Carpenter (1):
> scsi: qla2xxx: Fix an integer overflow in sysfs code
> drivers/scsi/qla2xxx/qla_attr.c | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)