In the Linux kernel, the following vulnerability has been resolved: i2c: ismt: Fix an out-of-bounds bug in ismt_access() When the driver does not check the data from the user, the variable 'data->block[0]' may be very large to cause an out-of-bounds bug. The following log can reveal it: [ 33.995542] i2c i2c-1: ioctl, cmd=0x720, arg=0x7ffcb3dc3a20 [ 33.995978] ismt_smbus 0000:00:05.0: I2C_SMBUS_BLOCK_DATA: WRITE [ 33.996475] ================================================================== [ 33.996995] BUG: KASAN: out-of-bounds in ismt_access.cold+0x374/0x214b [ 33.997473] Read of size 1844...
In the Linux kernel, the following vulnerability has been resolved: i2c: ismt: Fix an out-of-bounds bug in ismt_access() When the driver does not check the data from the user, the variable 'data->block[0]' may be very large to cause an out-of-bounds bug. The following log can reveal it: [ 33.995542] i2c i2c-1: ioctl, cmd=0x720, arg=0x7ffcb3dc3a20 [ 33.995978] ismt_smbus 0000:00:05.0: I2C_SMBUS_BLOCK_DATA: WRITE [ 33.996475] ================================================================== [ 33.996995] BUG: KASAN: out-of-bounds in ismt_access.cold+0x374/0x214b [ 33.997473] Read of size 1844...
Linux Linux, linux kernel의 현재 전체 버전이 공식 영향 범위(Linux Linux, linux kernel >= 13f35ac14cd0a9a1c4f0034c4c40d0ae98844ce9 < 4a7bb1d93addb2f67e36fed00a53cb7f270d7b7a, >= 13f35ac14cd0a9a1c4f0034c4c40d0ae98844ce9 < 03b7ef7a6c5ca1ff553470166b4919db88b810f6, >= 13f35ac14cd0a9a1c4f0034c4c40d0ae98844ce9 < bfe41d966c860a8ad4c735639d616da270c92735, >= 13f35ac14cd0a9a1c4f0034c4c40d0ae98844ce9 < cdcbae2c5003747ddfd14e29db9c1d5d7e7c44dd, >= 13f35ac14cd0a9a1c4f0034c4c40d0ae98844ce9 < 9ac541a0898e8ec187a3fa7024b9701cffae6bf2, >= 13f35ac14cd0a9a1c4f0034c4c40d0ae98844ce9 < 96c12fd0ec74641295e1c3c34dea3dce1b6c3422, >= 13f35ac14cd0a9a1c4f0034c4c40d0ae98844ce9 < a642469d464b2780a25a49b51ae56623c65eac34, >= 13f35ac14cd0a9a1c4f0034c4c40d0ae98844ce9 < 233348a04becf133283f0076e20b317302de21d9, >= 13f35ac14cd0a9a1c4f0034c4c40d0ae98844ce9 < 39244cc754829bf707dccd12e2ce37510f5b1f8d, >= 3.9, >= 3.9 < 4.9.337, >= 4.10 < 4.14.303, >= 4.15 < 4.19.270, >= 4.20 < 5.4.229, >= 5.5 < 5.10.163, >= 5.11 < 5.15.86, >= 5.16 < 6.0.16, >= 6.1 < 6.1.2)에 포함되는지 확인합니다. OS를 선택하면 해당 OS의 제품·패키지·KB·APAR 확인 명령만 표시됩니다.
조치방안
구조화된 수정 버전 값(4.9.337, 4.14.303, 4.19.270, 5.4.229, 5.10.163, 5.15.86, 6.0.16, 6.1.2)은 참고용입니다. 공급사 공식 보안 권고에서 제품·에디션·설치 방식별 수정 기준을 확인한 뒤 적용합니다.
조치 후 확인사항
패치 후 같은 명령으로 전체 버전을 다시 확인해 Linux Linux, linux kernel 4.9.337, 4.14.303, 4.19.270, 5.4.229, 5.10.163, 5.15.86, 6.0.16, 6.1.2 기준을 충족하는지 확인합니다. 이어서 메모리 손상 관련 오류·공격 흔적이 새로 발생하지 않는지 확인합니다.
