Description
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.
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:HWeakness enumeration
Affected software
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= d65de5ee8b72868fbbbd39ca73017d0e526fa13a, < 10afe5f7d30f6fe50c2b1177549d0e04921fc373; >= 47a449ec09b4479b89dcc6b27ec3829fc82ffafb, < 36d771ce6028b886e18a4a8956a5d23688e4e13d; >= 65b723644294f1d79770704162c0e8d1f700b6f1, < 89167072fd249e5f23ae2f8093f87da5925cef27; >= 2cdbcff99f15db86a10672fb220379a1ae46ccae, < 6c0f6ccd939166f56a904c792d7fcadae43b9085; >= ab327f8acdf8d06601fbf058859a539a9422afff, < 2cd4854ef14a487bcfb76c7980675980cad27b52; >= ab327f8acdf8d06601fbf058859a539a9422afff, < da895fd6da438af8d9326b8f02d715a9c76c3b5b; >= ab327f8acdf8d06601fbf058859a539a9422afff, < ce5cdd3b05216b704a704f466fb4c2dff3778caf; 288c96aa5b5526cd4a946e84ef85e165857693b5; >= 5.4.240, < 5.4.279; >= 5.10.177, < 5.10.221; >= 5.15.106, < 5.15.162; >= 6.1.23, < 6.1.96; >= 6.2.10, < 6.3 |
| Linux | Linux | 6.3 |
References
- https://git.kernel.org/stable/c/10afe5f7d30f6fe50c2b1177549d0e04921fc373Patch
- https://git.kernel.org/stable/c/2cd4854ef14a487bcfb76c7980675980cad27b52Patch
- https://git.kernel.org/stable/c/36d771ce6028b886e18a4a8956a5d23688e4e13dPatch
- https://git.kernel.org/stable/c/6c0f6ccd939166f56a904c792d7fcadae43b9085Patch
- https://git.kernel.org/stable/c/89167072fd249e5f23ae2f8093f87da5925cef27Patch
- https://git.kernel.org/stable/c/ce5cdd3b05216b704a704f466fb4c2dff3778cafPatch
- https://git.kernel.org/stable/c/da895fd6da438af8d9326b8f02d715a9c76c3b5bPatch
- https://git.kernel.org/stable/c/10afe5f7d30f6fe50c2b1177549d0e04921fc373Patch
- https://git.kernel.org/stable/c/2cd4854ef14a487bcfb76c7980675980cad27b52Patch
- https://git.kernel.org/stable/c/36d771ce6028b886e18a4a8956a5d23688e4e13dPatch
- https://git.kernel.org/stable/c/6c0f6ccd939166f56a904c792d7fcadae43b9085Patch
- https://git.kernel.org/stable/c/89167072fd249e5f23ae2f8093f87da5925cef27Patch
- https://git.kernel.org/stable/c/ce5cdd3b05216b704a704f466fb4c2dff3778cafPatch
- https://git.kernel.org/stable/c/da895fd6da438af8d9326b8f02d715a9c76c3b5bPatch
- https://lists.debian.org/debian-lts-announce/2025/01/msg00001.html
Timeline
- Published
- Jul 12, 2024
- Last modified
- Jun 17, 2026
- NVD status
- Modified