In the Linux kernel, the following vulnerability has been resolved: can: bcm: add locking for bcm_op runtime updates The CAN broadcast manager (CAN BCM) can send a sequence of CAN frames via hrtimer. The content and also the length of the sequence can be changed resp reduced at runtime where the 'currframe' counter is then set to zero. Although this appeared to be a safe operation the updates of 'currframe' can be triggered from user space and hrtimer context in bcm_can_tx(). Anderson Nascimento created a proof of concept that triggered a KASAN slab-out-of-bounds read access which can be pr...
In the Linux kernel, the following vulnerability has been resolved: can: bcm: add locking for bcm_op runtime updates The CAN broadcast manager (CAN BCM) can send a sequence of CAN frames via hrtimer. The content and also the length of the sequence can be changed resp reduced at runtime where the 'currframe' counter is then set to zero. Although this appeared to be a safe operation the updates of 'currframe' can be triggered from user space and hrtimer context in bcm_can_tx(). Anderson Nascimento created a proof of concept that triggered a KASAN slab-out-of-bounds read access which can be pr...
Linux Linux, linux kernel, debian linux의 현재 전체 버전이 공식 영향 범위(Linux Linux, linux kernel, debian linux >= ffd980f976e7fd666c2e61bf8ab35107efd11828 < 8f1c022541bf5a923c8d6fa483112c15250f30a4, >= ffd980f976e7fd666c2e61bf8ab35107efd11828 < 7595de7bc56e0e52b74e56c90f7e247bf626d628, >= ffd980f976e7fd666c2e61bf8ab35107efd11828 < fbd8fdc2b218e979cfe422b139b8f74c12419d1f, >= ffd980f976e7fd666c2e61bf8ab35107efd11828 < 2a437b86ac5a9893c902f30ef66815bf13587bf6, >= ffd980f976e7fd666c2e61bf8ab35107efd11828 < 76c84c3728178b2d38d5604e399dfe8b0752645e, >= ffd980f976e7fd666c2e61bf8ab35107efd11828 < cc55dd28c20a6611e30596019b3b2f636819a4c0, >= ffd980f976e7fd666c2e61bf8ab35107efd11828 < c4e8a172501e677ebd8ea9d9161d97dc4df56fbd, >= ffd980f976e7fd666c2e61bf8ab35107efd11828 < c2aba69d0c36a496ab4f2e81e9c2b271f2693fd7, >= 2.6.25, >= 2.6.25 < 5.4.294, >= 5.5 < 5.10.238, >= 5.11 < 5.15.185, >= 5.16 < 6.1.141, >= 6.2 < 6.6.93, >= 6.7 < 6.12.31, >= 6.13 < 6.14.9, 6.15, 11.0)에 포함되는지 확인합니다. OS를 선택하면 해당 OS의 제품·패키지·KB·APAR 확인 명령만 표시됩니다.
조치방안
제3자 참조와 수정 버전 값(5.4.294, 5.10.238, 5.15.185, 6.1.141, 6.6.93, 6.12.31, 6.14.9)은 보조 근거로만 사용하고, 공급사 공식 보안 권고에서 조치 기준을 재확인합니다.
조치 후 확인사항
패치 후 같은 명령으로 전체 버전을 다시 확인해 Linux Linux, linux kernel, debian linux 5.4.294, 5.10.238, 5.15.185, 6.1.141, 6.6.93, 6.12.31, 6.14.9 기준을 충족하는지 확인합니다. 이어서 메모리 손상 관련 오류·공격 흔적이 새로 발생하지 않는지 확인합니다.
