mips: bmips: BCM6358: make sure CBR is correctly set
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 5.4.279, 5.10.221, 5.15.162, 6.1.96, 6.3
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- Linux 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 Linux
6.3
References 7
git.kernel.org
- stable/c/10afe5f7d30f6fe50c2b1177549d0e04921fc373
- stable/c/36d771ce6028b886e18a4a8956a5d23688e4e13d
- stable/c/89167072fd249e5f23ae2f8093f87da5925cef27
- stable/c/6c0f6ccd939166f56a904c792d7fcadae43b9085
- stable/c/2cd4854ef14a487bcfb76c7980675980cad27b52
- stable/c/da895fd6da438af8d9326b8f02d715a9c76c3b5b
- stable/c/ce5cdd3b05216b704a704f466fb4c2dff3778caf