In the Linux kernel, the following vulnerability has been resolved:

mips: bmips: BCM6358: make sure CBR is correctly set

It was discovered that some device have CBR address set to 0 causing
kernel panic when arch_sync_dma_for_cpu_all is called.

This was notice in situation where the system is booted from TP1 and
BMIPS_GET_CBR() returns 0 instead of a valid address and
!!(read_c0_brcm_cmt_local() & (1 << 31)); not failing.

The current check whether RAC flush should be disabled or not are not
enough hence lets check if CBR is a valid address or not.

kernel.org https://git.kernel.org/stable/c/10afe5f7d30f6fe50c2b1177549d0e04921fc373 [No types assigned]

kernel.org https://git.kernel.org/stable/c/2cd4854ef14a487bcfb76c7980675980cad27b52 [No types assigned]

kernel.org https://git.kernel.org/stable/c/36d771ce6028b886e18a4a8956a5d23688e4e13d [No types assigned]

kernel.org https://git.kernel.org/stable/c/6c0f6ccd939166f56a904c792d7fcadae43b9085 [No types assigned]

kernel.org https://git.kernel.org/stable/c/89167072fd249e5f23ae2f8093f87da5925cef27 [No types assigned]

kernel.org https://git.kernel.org/stable/c/ce5cdd3b05216b704a704f466fb4c2dff3778caf [No types assigned]

kernel.org https://git.kernel.org/stable/c/da895fd6da438af8d9326b8f02d715a9c76c3b5b [No types assigned]