In the Linux kernel, the following vulnerability has been resolved: fs/jfs: Add validity check for db_maxag and db_agpref Both db_maxag and db_agpref are used as the index of the db_agfree array, but there is currently no validity check for db_maxag and db_agpref, which can lead to errors. The following is related bug reported by Syzbot: UBSAN: array-index-out-of-bounds in fs/jfs/jfs_dmap.c:639:20 index 7936 is out of range for type 'atomic_t[128]' Add checking that the values of db_maxag and db_agpref are valid indexes for the db_agfree array.
In the Linux kernel, the following vulnerability has been resolved: fs/jfs: Add validity check for db_maxag and db_agpref Both db_maxag and db_agpref are used as the index of the db_agfree array, but there is currently no validity check for db_maxag and db_agpref, which can lead to errors. The following is related bug reported by Syzbot: UBSAN: array-index-out-of-bounds in fs/jfs/jfs_dmap.c:639:20 index 7936 is out of range for type 'atomic_t[128]' Add checking that the values of db_maxag and db_agpref are valid indexes for the db_agfree array.
Linux Linux, linux kernel의 현재 전체 버전이 공식 영향 범위(Linux Linux, linux kernel >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < a0649e2dd4a3595b5595a29d0064d047c2fae2fb, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < ce15b0f1a431168f07b1cc6c9f71206a2db5c809, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 32bd8f1cbcf8b663e29dd1f908ba3a129541a11b, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < c6c8863fb3f57700ab583d875adda04caaf2278a, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 1f74d336990f37703a8eee77153463d65b67f70e, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 5013f8269887642cca784adc8db9b5f0b771533f, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < dca403bb035a565bb98ecc1dda5d30f676feda40, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 2323de34a3ae61a9f9b544c18583f71cea86721f, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 64933ab7b04881c6c18b21ff206c12278341c72e, >= 2.6.12, < 4.14.331, >= 4.15 < 4.19.300, >= 4.20 < 5.4.262, >= 5.5 < 5.10.202, >= 5.11 < 5.15.140, >= 5.16 < 6.1.64, >= 6.2 < 6.5.13, >= 6.6 < 6.6.3)에 포함되는지 확인합니다. OS를 선택하면 해당 OS의 제품·패키지·KB·APAR 확인 명령만 표시됩니다.
조치방안
구조화된 수정 버전 값(4.14.331, 4.19.300, 5.4.262, 5.10.202, 5.15.140, 6.1.64, 6.5.13, 6.6.3)은 참고용입니다. 공급사 공식 보안 권고에서 제품·에디션·설치 방식별 수정 기준을 확인한 뒤 적용합니다.
조치 후 확인사항
패치 후 같은 명령으로 전체 버전을 다시 확인해 Linux Linux, linux kernel 4.14.331, 4.19.300, 5.4.262, 5.10.202, 5.15.140, 6.1.64, 6.5.13, 6.6.3 기준을 충족하는지 확인합니다. 이어서 메모리 손상 관련 오류·공격 흔적이 새로 발생하지 않는지 확인합니다.
