CVE-2024-40963: Linux kernel · mips: bmips: BCM6358: make sure CBR is correctly set
Affects Linux kernelSource GCVE Database
Not known to be exploited · CVSS 5.5 Medium · fixed in 5.4.0-1132.142~18.04.1 : update Linux kernel when convenient.
Data as of 12 Nov 2026, 19:04 UTC
- Patch
- Available – fixed in 5.4.0-1132.142~18.04.1, 5.4.0-1137.144~18.04.1, 5.4.0-1136.145~18.04.1 +71
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 12 Jul 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 12 Nov 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Patches and advisories
- ubuntu.com/security/notices/USN-6999-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7003-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7003-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-7004-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7005-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7006-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7003-3 (opens in a new tab)
- ubuntu.com/security/notices/USN-7007-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7008-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7005-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-7009-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7019-1 (opens in a new tab)
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Ubuntu 24.04 LTSlinuxpkg:deb/ubuntu/linux?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-awspkg:deb/ubuntu/linux-aws?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-azurepkg:deb/ubuntu/linux-azure?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-gcppkg:deb/ubuntu/linux-gcp?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-gkepkg:deb/ubuntu/linux-gke?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-ibmpkg:deb/ubuntu/linux-ibm?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
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.
References
- ubuntu.com/security/CVE-2024-40963 (opens in a new tab)
- cve.org/CVERecord?id=CVE-2024-40963 (opens in a new tab)
- git.kernel.org/linus/ce5cdd3b05216b704a704f466fb4c2dff3778caf (opens in a new tab)
- git.kernel.org/stable/c/10afe5f7d30f6fe50c2b1177549d0e04921fc373 (opens in a new tab)
- git.kernel.org/stable/c/36d771ce6028b886e18a4a8956a5d23688e4e13d (opens in a new tab)
- git.kernel.org/stable/c/89167072fd249e5f23ae2f8093f87da5925cef27 (opens in a new tab)
- git.kernel.org/stable/c/6c0f6ccd939166f56a904c792d7fcadae43b9085 (opens in a new tab)
- git.kernel.org/stable/c/2cd4854ef14a487bcfb76c7980675980cad27b52 (opens in a new tab)
- git.kernel.org/stable/c/da895fd6da438af8d9326b8f02d715a9c76c3b5b (opens in a new tab)
- git.kernel.org/stable/c/ce5cdd3b05216b704a704f466fb4c2dff3778caf (opens in a new tab)
- ubuntu.com/security/notices/USN-6999-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7003-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7003-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-7004-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7005-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7006-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7003-3 (opens in a new tab)
- ubuntu.com/security/notices/USN-7007-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7008-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7005-2 (opens in a new tab)