In the Linux kernel, the following vulnerability has been resolved: dm cache policy smq: fix missing locks in invalidating cache blocks In passthrough mode, the policy invalidate_mapping operation is called simultaneously from multiple workers, thus it should be protected by a lock. Otherwise, we might end up with data races on the allocated blocks counter, or even use-after-free issues with internal data structures when doing concurrent writes. Note that the existing FIXME in smq_invalidate_mapping() doesn't affect passthrough mode since migration tasks don't exist there, but would need at...
In the Linux kernel, the following vulnerability has been resolved: dm cache policy smq: fix missing locks in invalidating cache blocks In passthrough mode, the policy invalidate_mapping operation is called simultaneously from multiple workers, thus it should be protected by a lock. Otherwise, we might end up with data races on the allocated blocks counter, or even use-after-free issues with internal data structures when doing concurrent writes. Note that the existing FIXME in smq_invalidate_mapping() doesn't affect passthrough mode since migration tasks don't exist there, but would need at...
Linux Linux, linux kernel의 현재 전체 버전이 공식 영향 범위(Linux Linux, linux kernel >= b29d4986d0da1a27cd35917cdb433672f5c95d7f < 4991b5a08751e2e82488fb93ae08849b6aea10d9, >= b29d4986d0da1a27cd35917cdb433672f5c95d7f < 1b2bec4a7dcf5f00b7a1cbeeec8997841d783513, >= b29d4986d0da1a27cd35917cdb433672f5c95d7f < 9a5fdfb9e57ec3a8ad2b8fce5e5ffa42d53b130e, >= b29d4986d0da1a27cd35917cdb433672f5c95d7f < ac5ee99443891bdb161f5539606a66a1b5e72542, >= b29d4986d0da1a27cd35917cdb433672f5c95d7f < 93627a29d4b66d4a2def938dfb8610cc80ae454b, >= b29d4986d0da1a27cd35917cdb433672f5c95d7f < c348ae47d8e65f06429fa41adce9ad986b696766, >= b29d4986d0da1a27cd35917cdb433672f5c95d7f < 2b62d0611c9af14a16bddf22df2612b4f40eb5a1, >= b29d4986d0da1a27cd35917cdb433672f5c95d7f < 2d1f7b65f5deedd2e6b09fdc6ea27f8375f24b45, >= 4.12, >= 4.12 < 5.10.258, >= 5.11 < 5.15.209, >= 5.16 < 6.1.175, >= 6.2 < 6.6.141, >= 6.7 < 6.12.91, >= 6.13 < 6.18.33, >= 6.19 < 7.0.10)에 포함되는지 확인합니다. OS를 선택하면 해당 OS의 제품·패키지·KB·APAR 확인 명령만 표시됩니다.
조치방안
제3자 참조와 수정 버전 값(5.10.258, 5.15.209, 6.1.175, 6.6.141, 6.12.91, 6.18.33, 7.0.10)은 보조 근거로만 사용하고, 공급사 공식 보안 권고에서 조치 기준을 재확인합니다.
조치 후 확인사항
패치 후 같은 명령으로 전체 버전을 다시 확인해 Linux Linux, linux kernel 5.10.258, 5.15.209, 6.1.175, 6.6.141, 6.12.91, 6.18.33, 7.0.10 기준을 충족하는지 확인합니다. 이어서 메모리 손상 관련 오류·공격 흔적이 새로 발생하지 않는지 확인합니다.
