Bug 1227817 (CVE-2024-40963)

Summary: VUL-0: CVE-2024-40963: kernel: mips: bmips: BCM6358: make sure CBR is correctly set
Product: [Novell Products] SUSE Security Incidents Reporter: SMASH SMASH <smash_bz>
Component: IncidentsAssignee: Security Team bot <security-team>
Status: NEW --- QA Contact: Security Team bot <security-team>
Severity: Normal    
Priority: P3 - Medium CC: gianluca.gabrielli, miroslav.franc
Version: unspecified   
Target Milestone: ---   
Hardware: Other   
OS: Other   
URL: https://smash.suse.de/issue/413890/
Whiteboard:
Found By: Security Response Team Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description SMASH SMASH 2024-07-15 13:20:12 UTC
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.

References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2024-40963
https://www.cve.org/CVERecord?id=CVE-2024-40963
https://git.kernel.org/stable/c/10afe5f7d30f6fe50c2b1177549d0e04921fc373
https://git.kernel.org/stable/c/2cd4854ef14a487bcfb76c7980675980cad27b52
https://git.kernel.org/stable/c/36d771ce6028b886e18a4a8956a5d23688e4e13d
https://git.kernel.org/stable/c/6c0f6ccd939166f56a904c792d7fcadae43b9085
https://git.kernel.org/stable/c/89167072fd249e5f23ae2f8093f87da5925cef27
https://git.kernel.org/stable/c/ce5cdd3b05216b704a704f466fb4c2dff3778caf
https://git.kernel.org/stable/c/da895fd6da438af8d9326b8f02d715a9c76c3b5b
https://git.kernel.org/pub/scm/linux/security/vulns.git/plain/cve/published/2024/CVE-2024-40963.mbox
Comment 1 Miroslav Franc 2024-07-19 16:14:00 UTC
We don't support MIPS architecture.