In the Linux kernel, the following vulnerability has been resolved: i2c: i801: Don't generate an interrupt on bus reset Now that the i2c-i801 driver supports interrupts, setting the KILL bit in a attempt to recover from a timed out transaction triggers an interrupt. Unfortunately, the interrupt handler (i801_isr) is not prepared for this situation and will try to process the interrupt as if it was signaling the end of a successful transaction. In the case of a block transaction, this can result in an out-of-range memory access. This condition was reproduced several times by syzbot: https://...
In the Linux kernel, the following vulnerability has been resolved: i2c: i801: Don't generate an interrupt on bus reset Now that the i2c-i801 driver supports interrupts, setting the KILL bit in a attempt to recover from a timed out transaction triggers an interrupt. Unfortunately, the interrupt handler (i801_isr) is not prepared for this situation and will try to process the interrupt as if it was signaling the end of a successful transaction. In the case of a block transaction, this can result in an out-of-range memory access. This condition was reproduced several times by syzbot: https://...
Linux Linux, linux kernel의 현재 전체 버전이 공식 영향 범위(Linux Linux, linux kernel >= 636752bcb5177a301d0266270661581de8624828 < f9469082126cebb7337db3992d143f5e4edfe629, >= 636752bcb5177a301d0266270661581de8624828 < 09c9e79f4c10cfb6b9e0e1b4dd355232e4b5a3b3, >= 636752bcb5177a301d0266270661581de8624828 < dfa8929e117b0228a7765f5c3f5988a4a028f3c6, >= 636752bcb5177a301d0266270661581de8624828 < c70e1ba2e7e65255a0ce004f531dd90dada97a8c, >= 636752bcb5177a301d0266270661581de8624828 < 04cc05e3716ae31b17ecdab7bc55c8170def1b8b, >= 636752bcb5177a301d0266270661581de8624828 < b523feb7e8e44652f92f3babb953a976e7ccbbef, >= 636752bcb5177a301d0266270661581de8624828 < 1f583d3813f204449037cd2acbfc09168171362a, >= 636752bcb5177a301d0266270661581de8624828 < e4d8716c3dcec47f1557024add24e1f3c09eb24b, >= 3.6, >= 3.6 < 4.4.271, >= 4.5 < 4.9.271, >= 4.10 < 4.14.235, >= 4.15 < 4.19.193, >= 4.20 < 5.4.124, >= 5.5 < 5.10.42, >= 5.11 < 5.12.9, 5.13)에 포함되는지 확인합니다. OS를 선택하면 해당 OS의 제품·패키지·KB·APAR 확인 명령만 표시됩니다.
조치방안
구조화된 수정 버전 값(4.4.271, 4.9.271, 4.14.235, 4.19.193, 5.4.124, 5.10.42, 5.12.9)은 참고용입니다. 공급사 공식 보안 권고에서 제품·에디션·설치 방식별 수정 기준을 확인한 뒤 적용합니다.
조치 후 확인사항
패치 후 같은 명령으로 전체 버전을 다시 확인해 Linux Linux, linux kernel 4.4.271, 4.9.271, 4.14.235, 4.19.193, 5.4.124, 5.10.42, 5.12.9 기준을 충족하는지 확인합니다. 이어서 메모리 손상 관련 오류·공격 흔적이 새로 발생하지 않는지 확인합니다.