An out-of-bounds write vulnerability was found in the Linux kernel s SLIMpro I2C device driver. The flaw lies in the xgene_slimpro_i2c_xfer() function. Quoting the upstream commit below: The data->block[0] variable comes from user and is a number between 0-255. Without proper check, the variable may be very large to cause an out-of-bounds when performing memcpy in slimpro_i2c_blkwr. Upstream fix:https://github.com/torvalds/linux/commit/92fbb6d1296f
An out-of-bounds write vulnerability was found in the Linux kernel s SLIMpro I2C device driver. The flaw lies in the xgene_slimpro_i2c_xfer() function. Quoting the upstream commit below: The data->block[0] variable comes from user and is a number between 0-255. Without proper check, the variable may be very large to cause an out-of-bounds when performing memcpy in slimpro_i2c_blkwr. Upstream fix:https://github.com/torvalds/linux/commit/92fbb6d1296f
An out-of-bounds write vulnerability was found in the Linux kernel s SLIMpro I2C device driver. The flaw liesin the xgene_slimpro_i2c_xfer() function. Quoting the upstream commit below: The data->block[0]variable comes from userand isa number between 0-255. Without propercheck, the variable may be very large to cause an out-of-bounds when performing memcpy in slimpro_i2c_blkwr. Upstream fix:https://github.com/torvalds/linux/commit/92fbb6d1296f
An out-of-bounds write vulnerability was found in the Linux kernel s SLIMpro I2C device driver. The userspace data->block[0] variable was not capped to a number between 0-255 and was used as the size of amemcpy, possibly writingbeyondthe end of dma_buffer. This flaw couldallow a local privileged user to crash the system or potentially achieve code execution.
An out-of-bounds write vulnerability was found in the Linux kernel s SLIMpro I2C device driver. The userspace data->block[0] variable was not capped to a number between 0-255 and was used as the size of a memcpy, possibly writing beyond the end of dma_buffer. This flaw could allow a local privileged user to crash the system or potentially achieve code execution.
An out-of-bounds write vulnerability was found in the Linux kernel s SLIMpro I2C device driver. The userspace data->block[0] variable was not capped to a number between 0-255 and was used as the size of a memcpy, possibly writing beyond the end of dma_buffer. This flaw could allow a local privileged user to crash the system or potentially achieve code execution.
An out-of-bounds write vulnerability was found in the Linux kernel s SLIMpro I2C device driver. The userspace data->block[0] variable was not capped to a number between 0-255 and was used as the size of a memcpy, possibly writing beyond the end of dma_buffer. This flaw could allow a local privileged user to crash the system or potentially achieve code execution.
An out-of-bounds write vulnerability was found in the Linux kernel s SLIMpro I2C device driver. The userspace data->block[0] variable was not capped to a number between 0-255 and was used as the size of a memcpy, possibly writing beyond the end of dma_buffer. This flaw could allow a local privileged user to crash the system or potentially achieve code execution.
An out-of-bounds write vulnerability was found in the Linux kernel s SLIMpro I2C device driver. The userspace data->block[0] variable was not capped to a number between 0-255 and was used as the size of a memcpy, possibly writing beyond the end of dma_buffer. This flaw could allow a local privileged user to crash the system or potentially achieve code execution.
An out-of-bounds write vulnerability was found in the Linux kernel s SLIMpro I2C device driver. The userspace data->block[0] variable was not capped to a number between 0-255 and was used as the size of a memcpy, possibly writing beyond the end of dma_buffer. This flaw could allow a local privileged user to crash the system or potentially achieve code execution.
An out-of-bounds write vulnerability was found in the Linux kernel s SLIMpro I2C device driver. The userspace data->block[0] variable was not capped to a number between 0-255 and was used as the size of a memcpy, possibly writing beyond the end of dma_buffer. This flaw could allow a local privileged user to crash the system or potentially achieve code execution.
An out-of-bounds write vulnerability was found in the Linux kernel s SLIMpro I2C device driver. The userspace data->block[0] variable was not capped to a number between 0-255 and was used as the size of a memcpy, possibly writing beyond the end of dma_buffer. This flaw could allow a local privileged user to crash the system or potentially achieve code execution.
An out-of-bounds write vulnerability was found in the Linux kernel s SLIMpro I2C device driver. The userspace data->block[0] variable was not capped to a number between 0-255 and was used as the size of a memcpy, possibly writing beyond the end of dma_buffer. This flaw could allow a local privileged user to crash the system or potentially achieve code execution.
An out-of-bounds write vulnerability was found in the Linux kernel s SLIMpro I2C device driver. The userspace data->block[0] variable was not capped to a number between 0-255 and was used as the size of a memcpy, possibly writing beyond the end of dma_buffer. This flaw could allow a local privileged user to crash the system or potentially achieve code execution.
An out-of-bounds write vulnerability was found in the Linux kernel s SLIMpro I2C device driver. The userspace data->block[0] variable was not capped to a number between 0-255 and was used as the size of a memcpy, possibly writing beyond the end of dma_buffer. This flaw could allow a local privileged user to crash the system or potentially achieve code execution.
An out-of-bounds write vulnerability was found in the Linux kernel s SLIMpro I2C device driver. The userspace data->block[0] variable was not capped to a number between 0-255 and was used as the size of a memcpy, possibly writing beyond the end of dma_buffer. This flaw could allow a local privileged user to crash the system or potentially achieve code execution.
An out-of-bounds write vulnerability was found in the Linux kernel s SLIMpro I2C device driver. The userspace data->block[0] variable was not capped to a number between 0-255 and was used as the size of a memcpy, possibly writing beyond the end of dma_buffer. This flaw could allow a local privileged user to crash the system or potentially achieve code execution.
An out-of-bounds write vulnerability was found in the Linux kernel s SLIMpro I2C device driver. The userspace data->block[0] variable was not capped to a number between 0-255 and was used as the size of a memcpy, possibly writing beyond the end of dma_buffer. This flaw could allow a local privileged user to crash the system or potentially achieve code execution.
An out-of-bounds write vulnerability was found in the Linux kernel s SLIMpro I2C device driver. The userspace data->block[0] variable was not capped to a number between 0-255 and was used as the size of a memcpy, possibly writing beyond the end of dma_buffer. This flaw could allow a local privileged user to crash the system or potentially achieve code execution.
An out-of-bounds write vulnerability was found in the Linux kernel s SLIMpro I2C device driver. The userspace data->block[0] variable was not capped to a number between 0-255 and was used as the size of a memcpy, possibly writing beyond the end of dma_buffer. This flaw could allow a local privileged user to crash the system or potentially achieve code execution.
An out-of-bounds write vulnerability was found in the Linux kernel s SLIMpro I2C device driver. The userspace data->block[0] variable was not capped to a number between 0-255 and was used as the size of a memcpy, possibly writing beyond the end of dma_buffer. This flaw could allow a local privileged user to crash the system or potentially achieve code execution.
An out-of-bounds write vulnerability was found in the Linux kernel s SLIMpro I2C device driver. The userspace data->block[0] variable was not capped to a number between 0-255 and was used as the size of a memcpy, possibly writing beyond the end of dma_buffer. This flaw could allow a local privileged user to crash the system or potentially achieve code execution.
An out-of-bounds write vulnerability was found in the Linux kernel s SLIMpro I2C device driver. The userspace data->block[0] variable was not capped to a number between 0-255 and was used as the size of a memcpy, possibly writing beyond the end of dma_buffer. This flaw could allow a local privileged user to crash the system or potentially achieve code execution.
An out-of-bounds write vulnerability was found in the Linux kernel s SLIMpro I2C device driver. The userspace data->block[0] variable was not capped to a number between 0-255 and was used as the size of a memcpy, possibly writing beyond the end of dma_buffer. This flaw could allow a local privileged user to crash the system or potentially achieve code execution.
An out-of-bounds write vulnerability was found in the Linux kernel s SLIMpro I2C device driver. The userspace data->block[0] variable was not capped to a number between 0-255 and was used as the size of a memcpy, possibly writing beyond the end of dma_buffer. This flaw could allow a local privileged user to crash the system or potentially achieve code execution.
An out-of-bounds write vulnerability was found in the Linux kernel s SLIMpro I2C device driver. The userspace data->block[0] variable was not capped to a number between 0-255 and was used as the size of a memcpy, possibly writing beyond the end of dma_buffer. This flaw could allow a local privileged user to crash the system or potentially achieve code execution.
An out-of-bounds write vulnerability was found in the Linux kernel s SLIMpro I2C device driver. The userspace data->block[0] variable was not capped to a number between 0-255 and was used as the size of a memcpy, possibly writing beyond the end of dma_buffer. This flaw could allow a local privileged user to crash the system or potentially achieve code execution.
An out-of-bounds write vulnerability was found in the Linux kernel s SLIMpro I2C device driver. The userspace data->block[0] variable was not capped to a number between 0-255 and was used as the size of a memcpy, possibly writing beyond the end of dma_buffer. This flaw could allow a local privileged user to crash the system or potentially achieve code execution.
An out-of-bounds write vulnerability was found in the Linux kernel s SLIMpro I2C device driver. The userspace data->block[0] variable was not capped to a number between 0-255 and was used as the size of a memcpy, possibly writing beyond the end of dma_buffer. This flaw could allow a local privileged user to crash the system or potentially achieve code execution.
An out-of-bounds write vulnerability was found in the Linux kernel s SLIMpro I2C device driver. The userspace data->block[0] variable was not capped to a number between 0-255 and was used as the size of a memcpy, possibly writing beyond the end of dma_buffer. This flaw could allow a local privileged user to crash the system or potentially achieve code execution.
An out-of-bounds write vulnerability was found in the Linux kernel s SLIMpro I2C device driver. The userspace data->block[0] variable was not capped to a number between 0-255 and was used as the size of a memcpy, possibly writing beyond the end of dma_buffer. This flaw could allow a local privileged user to crash the system or potentially achieve code execution.
An out-of-bounds write vulnerability was found in the Linux kernel s SLIMpro I2C device driver. The userspace data->block[0] variable was not capped to a number between 0-255 and was used as the size of a memcpy, possibly writing beyond the end of dma_buffer. This flaw could allow a local privileged user to crash the system or potentially achieve code execution.
An out-of-bounds write vulnerability was found in the Linux kernel s SLIMpro I2C device driver. The userspace data->block[0] variable was not capped to a number between 0-255 and was used as the size of a memcpy, possibly writing beyond the end of dma_buffer. This flaw could allow a local privileged user to crash the system or potentially achieve code execution.
An out-of-bounds write vulnerability was found in the Linux kernel s SLIMpro I2C device driver. The userspace data->block[0] variable was not capped to a number between 0-255 and was used as the size of a memcpy, possibly writing beyond the end of dma_buffer. This flaw could allow a local privileged user to crash the system or potentially achieve code execution.
An out-of-bounds write vulnerability was found in the Linux kernel s SLIMpro I2C device driver. The userspace data->block[0] variable was not capped to a number between 0-255 and was used as the size of a memcpy, possibly writing beyond the end of dma_buffer. This flaw could allow a local privileged user to crash the system or potentially achieve code execution.
An out-of-bounds write vulnerability was found in the Linux kernel s SLIMpro I2C device driver. The userspace data->block[0] variable was not capped to a number between 0-255 and was used as the size of a memcpy, possibly writing beyond the end of dma_buffer. This flaw could allow a local privileged user to crash the system or potentially achieve code execution.
An out-of-bounds write vulnerability was found in the Linux kernel s SLIMpro I2C device driver. The userspace data->block[0] variable was not capped to a number between 0-255 and was used as the size of a memcpy, possibly writing beyond the end of dma_buffer. This flaw could allow a local privileged user to crash the system or potentially achieve code execution.
An out-of-bounds write vulnerability was found in the Linux kernel s SLIMpro I2C device driver. The userspace data->block[0] variable was not capped to a number between 0-255 and was used as the size of a memcpy, possibly writing beyond the end of dma_buffer. This flaw could allow a local privileged user to crash the system or potentially achieve code execution.
An out-of-bounds write vulnerability was found in the Linux kernel s SLIMpro I2C device driver. The userspace data->block[0] variable was not capped to a number between 0-255 and was used as the size of a memcpy, possibly writing beyond the end of dma_buffer. This flaw could allow a local privileged user to crash the system or potentially achieve code execution.
An out-of-bounds write vulnerability was found in the Linux kernel s SLIMpro I2C device driver. The userspace data->block[0] variable was not capped to a number between 0-255 and was used as the size of a memcpy, possibly writing beyond the end of dma_buffer. This flaw could allow a local privileged user to crash the system or potentially achieve code execution.
An out-of-bounds write vulnerability was found in the Linux kernel s SLIMpro I2C device driver. The userspace data->block[0] variable was not capped to a number between 0-255 and was used as the size of a memcpy, possibly writing beyond the end of dma_buffer. This flaw could allow a local privileged user to crash the system or potentially achieve code execution.
An out-of-bounds write vulnerability was found in the Linux kernel s SLIMpro I2C device driver. The userspace data->block[0] variable was not capped to a number between 0-255 and was used as the size of a memcpy, possibly writing beyond the end of dma_buffer. This flaw could allow a local privileged user to crash the system or potentially achieve code execution.
An out-of-bounds write vulnerability was found in the Linux kernel s SLIMpro I2C device driver. The userspace data->block[0] variable was not capped to a number between 0-255 and was used as the size of a memcpy, possibly writing beyond the end of dma_buffer. This flaw could allow a local privileged user to crash the system or potentially achieve code execution.
An out-of-bounds write vulnerability was found in the Linux kernel s SLIMpro I2C device driver. The userspace data->block[0] variable was not capped to a number between 0-255 and was used as the size of a memcpy, possibly writing beyond the end of dma_buffer. This flaw could allow a local privileged user to crash the system or potentially achieve code execution.
An out-of-bounds write vulnerability was found in the Linux kernel s SLIMpro I2C device driver. The userspace data->block[0] variable was not capped to a number between 0-255 and was used as the size of a memcpy, possibly writing beyond the end of dma_buffer. This flaw could allow a local privileged user to crash the system or potentially achieve code execution.
An out-of-bounds write vulnerability was found in the Linux kernel s SLIMpro I2C device driver. The userspace data->block[0] variable was not capped to a number between 0-255 and was used as the size of a memcpy, possibly writing beyond the end of dma_buffer. This flaw could allow a local privileged user to crash the system or potentially achieve code execution.
An out-of-bounds write vulnerability was found in the Linux kernel s SLIMpro I2C device driver. The userspace data->block[0] variable was not capped to a number between 0-255 and was used as the size of a memcpy, possibly writing beyond the end of dma_buffer. This flaw could allow a local privileged user to crash the system or potentially achieve code execution.
An out-of-bounds write vulnerability was found in the Linux kernel s SLIMpro I2C device driver. The userspace data->block[0] variable was not capped to a number between 0-255 and was used as the size of a memcpy, possibly writing beyond the end of dma_buffer. This flaw could allow a local privileged user to crash the system or potentially achieve code execution.
An out-of-bounds write vulnerability was found in the Linux kernel s SLIMpro I2C device driver. The userspace data->block[0] variable was not capped to a number between 0-255 and was used as the size of a memcpy, possibly writing beyond the end of dma_buffer. This flaw could allow a local privileged user to crash the system or potentially achieve code execution.
An out-of-bounds write vulnerability was found in the Linux kernel s SLIMpro I2C device driver. The userspace data->block[0] variable was not capped to a number between 0-255 and was used as the size of a memcpy, possibly writing beyond the end of dma_buffer. This flaw could allow a local privileged user to crash the system or potentially achieve code execution.
An out-of-bounds write vulnerability was found in the Linux kernel s SLIMpro I2C device driver. The userspace data->block[0] variable was not capped to a number between 0-255 and was used as the size of a memcpy, possibly writing beyond the end of dma_buffer. This flaw could allow a local privileged user to crash the system or potentially achieve code execution.
An out-of-bounds write vulnerability was found in the Linux kernel s SLIMpro I2C device driver. The userspace data->block[0] variable was not capped to a number between 0-255 and was used as the size of a memcpy, possibly writing beyond the end of dma_buffer. This flaw could allow a local privileged user to crash the system or potentially achieve code execution.
An out-of-bounds write vulnerability was found in the Linux kernel s SLIMpro I2C device driver. The userspace data->block[0] variable was not capped to a number between 0-255 and was used as the size of a memcpy, possibly writing beyond the end of dma_buffer. This flaw could allow a local privileged user to crash the system or potentially achieve code execution.
An out-of-bounds write vulnerability was found in the Linux kernel s SLIMpro I2C device driver. The userspace data->block[0] variable was not capped to a number between 0-255 and was used as the size of a memcpy, possibly writing beyond the end of dma_buffer. This flaw could allow a local privileged user to crash the system or potentially achieve code execution.
An out-of-bounds write vulnerability was found in the Linux kernel s SLIMpro I2C device driver. The userspace data->block[0] variable was not capped to a number between 0-255 and was used as the size of a memcpy, possibly writing beyond the end of dma_buffer. This flaw could allow a local privileged user to crash the system or potentially achieve code execution.
An out-of-bounds write vulnerability was found in the Linux kernel s SLIMpro I2C device driver. The userspace data->block[0] variable was not capped to a number between 0-255 and was used as the size of a memcpy, possibly writing beyond the end of dma_buffer. This flaw could allow a local privileged user to crash the system or potentially achieve code execution.
An out-of-bounds write vulnerability was found in the Linux kernel s SLIMpro I2C device driver. The userspace data->block[0] variable was not capped to a number between 0-255 and was used as the size of a memcpy, possibly writing beyond the end of dma_buffer. This flaw could allow a local privileged user to crash the system or potentially achieve code execution.
An out-of-bounds write vulnerability was found in the Linux kernel s SLIMpro I2C device driver. The userspace data->block[0] variable was not capped to a number between 0-255 and was used as the size of a memcpy, possibly writing beyond the end of dma_buffer. This flaw could allow a local privileged user to crash the system or potentially achieve code execution.
An out-of-bounds write vulnerability was found in the Linux kernel s SLIMpro I2C device driver. The userspace data->block[0] variable was not capped to a number between 0-255 and was used as the size of a memcpy, possibly writing beyond the end of dma_buffer. This flaw could allow a local privileged user to crash the system or potentially achieve code execution.
An out-of-bounds write vulnerability was found in the Linux kernel s SLIMpro I2C device driver. The userspace data->block[0] variable was not capped to a number between 0-255 and was used as the size of a memcpy, possibly writing beyond the end of dma_buffer. This flaw could allow a local privileged user to crash the system or potentially achieve code execution.
An out-of-bounds write vulnerability was found in the Linux kernel s SLIMpro I2C device driver. The userspace data->block[0] variable was not capped to a number between 0-255 and was used as the size of a memcpy, possibly writing beyond the end of dma_buffer. This flaw could allow a local privileged user to crash the system or potentially achieve code execution.
An out-of-bounds write vulnerability was found in the Linux kernel s SLIMpro I2C device driver. The userspace data->block[0] variable was not capped to a number between 0-255 and was used as the size of a memcpy, possibly writing beyond the end of dma_buffer. This flaw could allow a local privileged user to crash the system or potentially achieve code execution.
An out-of-bounds write vulnerability was found in the Linux kernel s SLIMpro I2C device driver. The userspace data->block[0] variable was not capped to a number between 0-255 and was used as the size of a memcpy, possibly writing beyond the end of dma_buffer. This flaw could allow a local privileged user to crash the system or potentially achieve code execution.
An out-of-bounds write vulnerability was found in the Linux kernel s SLIMpro I2C device driver. The userspace data->block[0] variable was not capped to a number between 0-255 and was used as the size of a memcpy, possibly writing beyond the end of dma_buffer. This flaw could allow a local privileged user to crash the system or potentially achieve code execution.
An out-of-bounds write vulnerability was found in the Linux kernel s SLIMpro I2C device driver. The userspace data->block[0] variable was not capped to a number between 0-255 and was used as the size of a memcpy, possibly writing beyond the end of dma_buffer. This flaw could allow a local privileged user to crash the system or potentially achieve code execution.
An out-of-bounds write vulnerability was found in the Linux kernel s SLIMpro I2C device driver. The userspace data->block[0] variable was not capped to a number between 0-255 and was used as the size of a memcpy, possibly writing beyond the end of dma_buffer. This flaw could allow a local privileged user to crash the system or potentially achieve code execution.
An out-of-bounds write vulnerability was found in the Linux kernel s SLIMpro I2C device driver. The userspace data->block[0] variable was not capped to a number between 0-255 and was used as the size of a memcpy, possibly writing beyond the end of dma_buffer. This flaw could allow a local privileged user to crash the system or potentially achieve code execution.
An out-of-bounds write vulnerability was found in the Linux kernel s SLIMpro I2C device driver. The userspace data->block[0] variable was not capped to a number between 0-255 and was used as the size of a memcpy, possibly writing beyond the end of dma_buffer. This flaw could allow a local privileged user to crash the system or potentially achieve code execution.
An out-of-bounds write vulnerability was found in the Linux kernel s SLIMpro I2C device driver. The userspace data->block[0] variable was not capped to a number between 0-255 and was used as the size of a memcpy, possibly writing beyond the end of dma_buffer. This flaw could allow a local privileged user to crash the system or potentially achieve code execution.
An out-of-bounds write vulnerability was found in the Linux kernel s SLIMpro I2C device driver. The userspace data->block[0] variable was not capped to a number between 0-255 and was used as the size of a memcpy, possibly writing beyond the end of dma_buffer. This flaw could allow a local privileged user to crash the system or potentially achieve code execution.
An out-of-bounds write vulnerability was found in the Linux kernel s SLIMpro I2C device driver. The userspace data->block[0] variable was not capped to a number between 0-255 and was used as the size of a memcpy, possibly writing beyond the end of dma_buffer. This flaw could allow a local privileged user to crash the system or potentially achieve code execution.
An out-of-bounds write vulnerability was found in the Linux kernel s SLIMpro I2C device driver. The userspace data->block[0] variable was not capped to a number between 0-255 and was used as the size of a memcpy, possibly writing beyond the end of dma_buffer. This flaw could allow a local privileged user to crash the system or potentially achieve code execution.
An out-of-bounds write vulnerability was found in the Linux kernel s SLIMpro I2C device driver. The userspace data->block[0] variable was not capped to a number between 0-255 and was used as the size of a memcpy, possibly writing beyond the end of dma_buffer. This flaw could allow a local privileged user to crash the system or potentially achieve code execution.
An out-of-bounds write vulnerability was found in the Linux kernel s SLIMpro I2C device driver. The userspace data->block[0] variable was not capped to a number between 0-255 and was used as the size of a memcpy, possibly writing beyond the end of dma_buffer. This flaw could allow a local privileged user to crash the system or potentially achieve code execution.
An out-of-bounds write vulnerability was found in the Linux kernel s SLIMpro I2C device driver. The userspace data->block[0] variable was not capped to a number between 0-255 and was used as the size of a memcpy, possibly writing beyond the end of dma_buffer. This flaw could allow a local privileged user to crash the system or potentially achieve code execution.
An out-of-bounds write vulnerability was found in the Linux kernel s SLIMpro I2C device driver. The userspace data->block[0] variable was not capped to a number between 0-255 and was used as the size of a memcpy, possibly writing beyond the end of dma_buffer. This flaw could allow a local privileged user to crash the system or potentially achieve code execution.
Anout-of-boundswritevulnerabilitywasfoundintheLinuxkernelsSLIMproI2Cdevice driver. The userspace data->block[0] variable was not capped to a number between 0-255 and was usedas the size of a memcpy, possibly writing beyond the end of dma_buffer. This flaw could allow a local privileged user to crash the system or potentially achieve code execution.
An out-of-bounds write vulnerability was found in the Linux kernel s SLIMpro I2C device driver. The userspace data->block[0] variable was not capped to a number between 0-255 and was used as the size of a memcpy, possibly writing beyond the end of dma_buffer. This flaw could allow a local privileged user to crash the system or potentially achieve code execution.
An out-of-bounds write vulnerability was found in the Linux kernel sSLIMpro I2C device driver. The userspace data->block[0] variable was not capped to anumber between 0-255 and was usedas the size of amemcpy, possibly writing beyond the end of dma_buffer. This flaw could allow alocal privileged user to crash the system or potentially achieve code execution.
An out-of-bounds write vulnerability was found in the Linux kernel s SLIMpro I2C device driver. The userspace data->block[0] variable was not capped to a number between 0-255 and was used as the size of a memcpy, possibly writing beyond the end of dma_buffer. This flaw could allow a local privileged user to crash the system or potentially achieve code execution.
An out-of-bounds write vulnerability was found in the Linux kernels SLIMpro I2C device driver. The userspace data->block[0] variable was not capped toa number between 0-255 and was usedas the size ofa memcpy, possibly writing beyond the end of dma_buffer. This flaw could allowa local privileged user to crash the system or potentially achieve codeexecution.
An out-of-bounds write vulnerability was found in the Linux kernel s SLIMpro I2C device driver. The userspace data->block[0] variable was not capped to a number between 0-255 and was used as the size of a memcpy, possibly writing beyond the end of dma_buffer. This flaw could allow a local privileged user to crash the system or potentially achieve code execution.
An out-of-bounds write vulnerability was found in the Linux kernel sSLIMpro I2C device driver. The userspace data->block[0] variable was not capped to anumber between 0-255 and was usedas the size of amemcpy, possibly writing beyond the end of dma_buffer. This flaw could allow alocal privileged user to crash the system or potentially achieve code execution.
An out-of-bounds write vulnerability was found in the Linux kernel s SLIMpro I2C device driver. The userspace data->block[0] variable was not capped to a number between 0-255 and was used as the size of a memcpy, possibly writing beyond the end of dma_buffer. This flaw could allow a local privileged user to crash the system or potentially achieve code execution.
An out-of-bounds write vulnerability was found in the Linux kernels SLIMpro I2C device driver. The userspace data->block[0] variable was not capped toa number between 0-255 and was usedas the size ofa memcpy, possibly writing beyond the end of dma_buffer. This flaw could allowa local privileged user to crash the system or potentially achieve codeexecution.
An out-of-bounds write vulnerability was found in the Linux kernel s SLIMpro I2C device driver. The userspace data->block[0] variable was not capped to a number between 0-255 and was used as the size of a memcpy, possibly writing beyond the end of dma_buffer. This flaw could allow a local privileged user to crash the system or potentially achieve code execution.
An out-of-bounds write vulnerability was found in the Linux kernel sSLIMpro I2C device driver. The userspace data->block[0] variable was not capped to anumber between 0-255 and was usedas the size of amemcpy, possibly writing beyond the end of dma_buffer. This flaw could allow alocal privileged user to crash the system or potentially achieve code execution.
An out-of-bounds write vulnerability was found in the Linux kernel s SLIMpro I2C device driver. The userspace data->block[0] variable was not capped to a number between 0-255 and was used as the size of a memcpy, possibly writing beyond the end of dma_buffer. This flaw could allow a local privileged user to crash the system or potentially achieve code execution.
An out-of-bounds write vulnerability was found in the Linux kernels SLIMpro I2C device driver. The userspace data->block[0] variable was not capped toa number between 0-255 and was usedas the size ofa memcpy, possibly writing beyond the end of dma_buffer. This flaw could allowa local privileged user to crash the system or potentially achieve codeexecution.
An out-of-bounds write vulnerability was found in the Linux kernel s SLIMpro I2C device driver. The userspace data->block[0] variable was not capped to a number between 0-255 and was used as the size of a memcpy, possibly writing beyond the end of dma_buffer. This flaw could allow a local privileged user to crash the system or potentially achieve code execution.
An out-of-bounds write vulnerability was found in the Linux kernel sSLIMpro I2C device driver. The userspace data->block[0] variable was not capped to anumber between 0-255 and was usedas the size of amemcpy, possibly writing beyond the end of dma_buffer. This flaw could allow alocal privileged user to crash the system or potentially achieve code execution.
An out-of-bounds write vulnerability was found in the Linux kernel s SLIMpro I2C device driver. The userspace data->block[0] variable was not capped to a number between 0-255 and was used as the size of a memcpy, possibly writing beyond the end of dma_buffer. This flaw could allow a local privileged user to crash the system or potentially achieve code execution.
An out-of-bounds write vulnerability was found in the Linux kernels SLIMpro I2C device driver. The userspace data->block[0] variable was not capped toa number between 0-255 and was usedas the size ofa memcpy, possibly writing beyond the end of dma_buffer. This flaw could allowa local privileged user to crash the system or potentially achieve codeexecution.
An out-of-bounds write vulnerability was found in the Linux kernel s SLIMpro I2C device driver. The userspace data->block[0] variable was not capped to a number between 0-255 and was used as the size of a memcpy, possibly writing beyond the end of dma_buffer. This flaw could allow a local privileged user to crash the system or potentially achieve code execution.
An out-of-bounds write vulnerability was found in the Linux kernel sSLIMpro I2C device driver. The userspace data->block[0] variable was not capped to anumber between 0-255 and was usedas the size of amemcpy, possibly writing beyond the end of dma_buffer. This flaw could allow alocal privileged user to crash the system or potentially achieve code execution.
An out-of-bounds write vulnerability was found in the Linux kernel s SLIMpro I2C device driver. The userspace data->block[0] variable was not capped to a number between 0-255 and was used as the size of a memcpy, possibly writing beyond the end of dma_buffer. This flaw could allow a local privileged user to crash the system or potentially achieve code execution.
An out-of-bounds write vulnerability was found in the Linux kernels SLIMpro I2C device driver. The userspace data->block[0] variable was not capped toa number between 0-255 and was usedas the size ofa memcpy, possibly writing beyond the end of dma_buffer. This flaw could allowa local privileged user to crash the system or potentially achieve codeexecution.
An out-of-bounds write vulnerability was found in the Linux kernel s SLIMpro I2C device driver. The userspace data->block[0] variable was not capped to a number between 0-255 and was used as the size of a memcpy, possibly writing beyond the end of dma_buffer. This flaw could allow a local privileged user to crash the system or potentially achieve code execution.
An out-of-bounds write vulnerability was found in the Linux kernel sSLIMpro I2C device driver. The userspace data->block[0] variable was not capped to anumber between 0-255 and was usedas the size of amemcpy, possibly writing beyond the end of dma_buffer. This flaw could allow alocal privileged user to crash the system or potentially achieve code execution.
An out-of-bounds write vulnerability was found in the Linux kernel s SLIMpro I2C device driver. The userspace data->block[0] variable was not capped to a number between 0-255 and was used as the size of a memcpy, possibly writing beyond the end of dma_buffer. This flaw could allow a local privileged user to crash the system or potentially achieve code execution.
An out-of-bounds write vulnerability was found in the Linux kernels SLIMpro I2C device driver. The userspace data->block[0] variable was not capped toa number between 0-255 and was usedas the size ofa memcpy, possibly writing beyond the end of dma_buffer. This flaw could allowa local privileged user to crash the system or potentially achieve codeexecution.
An out-of-bounds write vulnerability was found in the Linux kernel s SLIMpro I2C device driver. The userspace data->block[0] variable was not capped to a number between 0-255 and was used as the size of a memcpy, possibly writing beyond the end of dma_buffer. This flaw could allow a local privileged user to crash the system or potentially achieve code execution.
An out-of-bounds write vulnerability was found in the Linux kernel sSLIMpro I2C device driver. The userspace data->block[0] variable was not capped to anumber between 0-255 and was usedas the size of amemcpy, possibly writing beyond the end of dma_buffer. This flaw could allow alocal privileged user to crash the system or potentially achieve code execution.
An out-of-bounds write vulnerability was found in the Linux kernel s SLIMpro I2C device driver. The userspace data->block[0] variable was not capped to a number between 0-255 and was used as the size of a memcpy, possibly writing beyond the end of dma_buffer. This flaw could allow a local privileged user to crash the system or potentially achieve code execution.
An out-of-bounds write vulnerability was found in the Linux kernels SLIMpro I2C device driver. The userspace data->block[0] variable was not capped toa number between 0-255 and was usedas the size ofa memcpy, possibly writing beyond the end of dma_buffer. This flaw could allowa local privileged user to crash the system or potentially achieve codeexecution.
An out-of-bounds write vulnerability was found in the Linux kernel s SLIMpro I2C device driver. The userspace data->block[0] variable was not capped to a number between 0-255 and was used as the size of a memcpy, possibly writing beyond the end of dma_buffer. This flaw could allow a local privileged user to crash the system or potentially achieve code execution.
An out-of-bounds write vulnerability was found in the Linux kernel s SLIMpro I2C device driver. The userspace data->block[0] variable was not capped to a number between 0-255 and was usedas the size of a memcpy, possibly writing beyond the end of dma_buffer. This flaw could allow a local privileged user to crash the system or potentially achieve code execution.
An out-of-bounds write vulnerability was found in the Linux kernel s SLIMpro I2C device driver. The userspace data->block[0] variable was not capped to a number between 0-255 and was used as the size of a memcpy, possibly writing beyond the end of dma_buffer. This flaw could allow a local privileged user to crash the system or potentially achieve code execution.
An out-of-bounds write vulnerability was found in the Linux kernel s SLIMpro I2C device driver. The userspace data->block[0] variable was not capped to a number between 0-255 and was usedas the size of a memcpy, possibly writing beyond the end of dma_buffer. This flaw could allow a local privileged user to crash the system or potentially achieve code execution.
An out-of-bounds write vulnerability was found in the Linux kernel s SLIMpro I2C device driver. The userspace data->block[0] variable was not capped to a number between 0-255 and was used as the size of a memcpy, possibly writing beyond the end of dma_buffer. This flaw could allow a local privileged user to crash the system or potentially achieve code execution.
An out-of-bounds write vulnerability was found in the Linux kernel sSLIMpro I2C device driver. The userspace data->block[0] variable was not capped to anumber between 0-255 and was usedas the size of amemcpy, possibly writing beyond the end of dma_buffer. This flaw could allow alocal privileged user to crash the system or potentially achieve code execution.
An out-of-bounds write vulnerability was found in the Linux kernel s SLIMpro I2C device driver. The userspace data->block[0] variable was not capped to a number between 0-255 and was used as the size of a memcpy, possibly writing beyond the end of dma_buffer. This flaw could allow a local privileged user to crash the system or potentially achieve code execution.
An out-of-bounds write vulnerability was found in the Linux kernels SLIMpro I2C device driver. The userspace data->block[0] variable was not capped toa number between 0-255 and was usedas the size ofa memcpy, possibly writing beyond the end of dma_buffer. This flaw could allowa local privileged user to crash the system or potentially achieve codeexecution.
An out-of-bounds write vulnerability was found in the Linux kernel s SLIMpro I2C device driver. The userspace data->block[0] variable was not capped to a number between 0-255 and was used as the size of a memcpy, possibly writing beyond the end of dma_buffer. This flaw could allow a local privileged user to crash the system or potentially achieve code execution.
An out-of-bounds write vulnerability was found in the Linux kernel sSLIMpro I2C device driver. The userspace data->block[0] variable was not capped to anumber between 0-255 and was usedas the size of amemcpy, possibly writing beyond the end of dma_buffer. This flaw could allow alocal privileged user to crash the system or potentially achieve code execution.
An out-of-bounds write vulnerability was found in the Linux kernel s SLIMpro I2C device driver. The userspace data->block[0] variable was not capped to a number between 0-255 and was used as the size of a memcpy, possibly writing beyond the end of dma_buffer. This flaw could allow a local privileged user to crash the system or potentially achieve code execution.
An out-of-bounds write vulnerability was found in the Linux kernels SLIMpro I2C device driver. The userspace data->block[0] variable was not capped toa number between 0-255 and was usedas the size ofa memcpy, possibly writing beyond the end of dma_buffer. This flaw could allowa local privileged user to crash the system or potentially achieve codeexecution.
An out-of-bounds write vulnerability was found in the Linux kernel s SLIMpro I2C device driver. The userspace data->block[0] variable was not capped to a number between 0-255 and was used as the size of a memcpy, possibly writing beyond the end of dma_buffer. This flaw could allow a local privileged user to crash the system or potentially achieve code execution.
An out-of-bounds write vulnerability was found in the Linux kernel sSLIMpro I2C device driver. The userspace data->block[0] variable was not capped to anumber between 0-255 and was usedas the size of amemcpy, possibly writing beyond the end of dma_buffer. This flaw could allow alocal privileged user to crash the system or potentially achieve code execution.
An out-of-bounds write vulnerability was found in the Linux kernel s SLIMpro I2C device driver. The userspace data->block[0] variable was not capped to a number between 0-255 and was used as the size of a memcpy, possibly writing beyond the end of dma_buffer. This flaw could allow a local privileged user to crash the system or potentially achieve code execution.
An out-of-bounds write vulnerability was found in the Linux kernels SLIMpro I2C device driver. The userspace data->block[0] variable was not capped toa number between 0-255 and was usedas the size ofa memcpy, possibly writing beyond the end of dma_buffer. This flaw could allowa local privileged user to crash the system or potentially achieve codeexecution.
An out-of-bounds write vulnerability was found in the Linux kernel s SLIMpro I2C device driver. The userspace data->block[0] variable was not capped to a number between 0-255 and was used as the size of a memcpy, possibly writing beyond the end of dma_buffer. This flaw could allow a local privileged user to crash the system or potentially achieve code execution.
An out-of-bounds write vulnerability was found in the Linux kernel sSLIMpro I2C device driver. The userspace data->block[0] variable was not capped to anumber between 0-255 and was usedas the size of amemcpy, possibly writing beyond the end of dma_buffer. This flaw could allow alocal privileged user to crash the system or potentially achieve code execution.
An out-of-bounds write vulnerability was found in the Linux kernel s SLIMpro I2C device driver. The userspace data->block[0] variable was not capped to a number between 0-255 and was used as the size of a memcpy, possibly writing beyond the end of dma_buffer. This flaw could allow a local privileged user to crash the system or potentially achieve code execution.
An out-of-bounds write vulnerability was found in the Linux kernels SLIMpro I2C device driver. The userspace data->block[0] variable was not capped toa number between 0-255 and was usedas the size ofa memcpy, possibly writing beyond the end of dma_buffer. This flaw could allowa local privileged user to crash the system or potentially achieve codeexecution.
An out-of-bounds write vulnerability was found in the Linux kernel s SLIMpro I2C device driver. The userspace data->block[0] variable was not capped to a number between 0-255 and was used as the size of a memcpy, possibly writing beyond the end of dma_buffer. This flaw could allow a local privileged user to crash the system or potentially achieve code execution.
An out-of-bounds write vulnerability was found in the Linux kernel sSLIMpro I2C device driver. The userspace data->block[0] variable was not capped to anumber between 0-255 and was usedas the size of amemcpy, possibly writing beyond the end of dma_buffer. This flaw could allow alocal privileged user to crash the system or potentially achieve code execution.
An out-of-bounds write vulnerability was found in the Linux kernel s SLIMpro I2C device driver. The userspace data->block[0] variable was not capped to a number between 0-255 and was used as the size of a memcpy, possibly writing beyond the end of dma_buffer. This flaw could allow a local privileged user to crash the system or potentially achieve code execution.
An out-of-bounds write vulnerability was found in the Linux kernels SLIMpro I2C device driver. The userspace data->block[0] variable was not capped toa number between 0-255 and was usedas the size ofa memcpy, possibly writing beyond the end of dma_buffer. This flaw could allowa local privileged user to crash the system or potentially achieve codeexecution.
An out-of-bounds write vulnerability was found in the Linux kernel s SLIMpro I2C device driver. The userspace data->block[0] variable was not capped to a number between 0-255 and was used as the size of a memcpy, possibly writing beyond the end of dma_buffer. This flaw could allow a local privileged user to crash the system or potentially achieve code execution.
An out-of-bounds write vulnerability was found in the Linux kernel sSLIMpro I2C device driver. The userspace data->block[0] variable was not capped to anumber between 0-255 and was usedas the size of amemcpy, possibly writing beyond the end of dma_buffer. This flaw could allow alocal privileged user to crash the system or potentially achieve code execution.
An out-of-bounds write vulnerability was found in the Linux kernel s SLIMpro I2C device driver. The userspace data->block[0] variable was not capped to a number between 0-255 and was used as the size of a memcpy, possibly writing beyond the end of dma_buffer. This flaw could allow a local privileged user to crash the system or potentially achieve code execution.
An out-of-bounds write vulnerability was found in the Linux kernels SLIMpro I2C device driver. The userspace data->block[0] variable was not capped toa number between 0-255 and was usedas the size ofa memcpy, possibly writing beyond the end of dma_buffer. This flaw could allowa local privileged user to crash the system or potentially achieve codeexecution.
An out-of-bounds write vulnerability was found in the Linux kernel s SLIMpro I2C device driver. The userspace data->block[0] variable was not capped to a number between 0-255 and was used as the size of a memcpy, possibly writing beyond the end of dma_buffer. This flaw could allow a local privileged user to crash the system or potentially achieve code execution.
An out-of-bounds write vulnerability was found in the Linux kernel s SLIMpro I2C device driver. The userspace data->block[0] variable was not capped to a number between 0-255 and was usedas the size of a memcpy, possibly writing beyond the end of dma_buffer. This flaw could allow a local privileged user to crash the system or potentially achieve code execution.
An out-of-bounds write vulnerability was found in the Linux kernel s SLIMpro I2C device driver. The userspace data->block[0] variable was not capped to a number between 0-255 and was used as the size of a memcpy, possibly writing beyond the end of dma_buffer. This flaw could allow a local privileged user to crash the system or potentially achieve code execution.
An out-of-bounds write vulnerability was found in the Linux kernel s SLIMpro I2C device driver. The userspace data->block[0] variable was not capped to a number between 0-255 and was usedas the size of a memcpy, possibly writing beyond the end of dma_buffer. This flaw could allow a local privileged user to crash the system or potentially achieve code execution.
An out-of-bounds write vulnerability was found in the Linux kernel s SLIMpro I2C device driver. The userspace data->block[0] variable was not capped to a number between 0-255 and was used as the size of a memcpy, possibly writing beyond the end of dma_buffer. This flaw could allow a local privileged user to crash the system or potentially achieve code execution.
An out-of-bounds write vulnerability was found in the Linux kernel sSLIMpro I2C device driver. The userspace data->block[0] variable was not capped to anumber between 0-255 and was usedas the size of amemcpy, possibly writing beyond the end of dma_buffer. This flaw could allow alocal privileged user to crash the system or potentially achieve code execution.
An out-of-bounds write vulnerability was found in the Linux kernel s SLIMpro I2C device driver. The userspace data->block[0] variable was not capped to a number between 0-255 and was used as the size of a memcpy, possibly writing beyond the end of dma_buffer. This flaw could allow a local privileged user to crash the system or potentially achieve code execution.
An out-of-bounds write vulnerability was found in the Linux kernels SLIMpro I2C device driver. The userspace data->block[0] variable was not capped toa number between 0-255 and was usedas the size ofa memcpy, possibly writing beyond the end of dma_buffer. This flaw could allowa local privileged user to crash the system or potentially achieve codeexecution.
An out-of-bounds write vulnerability was found in the Linux kernel s SLIMpro I2C device driver. The userspace data->block[0] variable was not capped to a number between 0-255 and was used as the size of a memcpy, possibly writing beyond the end of dma_buffer. This flaw could allow a local privileged user to crash the system or potentially achieve code execution.
An out-of-bounds write vulnerability was found in the Linux kernel sSLIMpro I2C device driver. The userspace data->block[0] variable was not capped to anumber between 0-255 and was usedas the size of amemcpy, possibly writing beyond the end of dma_buffer. This flaw could allow alocal privileged user to crash the system or potentially achieve code execution.
An out-of-bounds write vulnerability was found in the Linux kernel s SLIMpro I2C device driver. The userspace data->block[0] variable was not capped to a number between 0-255 and was used as the size of a memcpy, possibly writing beyond the end of dma_buffer. This flaw could allow a local privileged user to crash the system or potentially achieve code execution.
An out-of-bounds write vulnerability was found in the Linux kernels SLIMpro I2C device driver. The userspace data->block[0] variable was not capped toa number between 0-255 and was usedas the size ofa memcpy, possibly writing beyond the end of dma_buffer. This flaw could allowa local privileged user to crash the system or potentially achieve codeexecution.
