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

Solution

No solution given by the vendor.


Workaround

No workaround given by the vendor.

History

Wed, 11 Sep 2024 13:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


cve-icon MITRE

Status: PUBLISHED

Assigner: Linux

Published:

Updated: 2025-05-04T12:57:20.201Z

Reserved: 2024-07-12T12:17:45.602Z

Link: CVE-2024-40963

cve-icon Vulnrichment

Updated: 2024-08-02T04:39:55.958Z

cve-icon NVD

Status : Awaiting Analysis

Published: 2024-07-12T13:15:18.243

Modified: 2024-11-21T09:31:57.677

Link: CVE-2024-40963

cve-icon Redhat

Severity : Low

Publid Date: 2024-07-12T00:00:00Z

Links: CVE-2024-40963 - Bugzilla

cve-icon OpenCVE Enrichment

Updated: 2025-07-13T11:22:45Z