mips: bmips: BCM6358: make sure CBR is correctly set
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ ab327f8acdf8d06601fbf058859a539a9422afff · < da895fd6da438af8d9326b8f02d715a9c76c3b5b| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
On some BCM6358 devices booted from TP1, the CBR address can be zero. A call to arch_sync_dma_for_cpu_all can then cause a kernel panic. The input does not describe an attacker trigger, authentication requirement, or user interaction.
Engineers running the Linux kernel on BCM6358 devices should check their systems; affected versions are not specified.