CVE-2024-40963: Vulnerability in Linux Linux
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.
AI Analysis
Technical Summary
CVE-2024-40963 is a vulnerability identified in the Linux kernel specifically affecting the MIPS architecture variant bmips, and more precisely the BCM6358 chipset. The issue arises due to improper handling of the CBR (Cache Block Register) address, which in some devices is set to zero. This incorrect setting leads to a kernel panic when the function arch_sync_dma_for_cpu_all is invoked. The root cause is that the system, when booted from TP1, causes the BMIPS_GET_CBR() macro to return zero instead of a valid memory address. Additionally, the existing check involving read_c0_brcm_cmt_local() does not fail as expected, allowing the kernel to proceed with an invalid CBR address. The vulnerability stems from insufficient validation of the CBR address before deciding whether to disable RAC (Read-Ahead Cache) flush operations. This flaw can cause system instability and crashes due to kernel panics triggered by invalid memory operations during DMA synchronization. The vulnerability is specific to certain MIPS-based devices using the BCM6358 chipset and Linux kernel versions identified by the provided commit hashes. No known exploits are currently reported in the wild, and no CVSS score has been assigned yet.
Potential Impact
For European organizations, the impact of CVE-2024-40963 is primarily related to system availability and stability. Organizations using embedded systems, network devices, or specialized hardware running Linux on MIPS bmips architecture with BCM6358 chipsets could experience unexpected kernel panics leading to system crashes and downtime. This could disrupt critical infrastructure, industrial control systems, or telecommunications equipment that rely on these devices. While the vulnerability does not directly expose confidentiality or integrity risks, the denial of service caused by kernel panics can affect operational continuity. Given that MIPS-based devices are less common in mainstream enterprise servers but prevalent in embedded and network hardware, the impact is more pronounced in sectors relying on such specialized equipment. European organizations in telecommunications, manufacturing, and critical infrastructure sectors could be particularly affected if their hardware platforms include the vulnerable chipset and kernel versions.
Mitigation Recommendations
To mitigate CVE-2024-40963, organizations should: 1) Identify and inventory all devices running Linux on MIPS bmips architecture, especially those with BCM6358 chipsets. 2) Apply the latest Linux kernel patches that address this vulnerability as soon as they become available from trusted sources or Linux distributions. 3) If patching is not immediately possible, consider isolating affected devices from critical networks to reduce the risk of disruption. 4) Monitor system logs for kernel panic events related to DMA synchronization or CBR address issues to detect potential triggers of this vulnerability. 5) Engage with hardware vendors to confirm if firmware or hardware updates are necessary to complement kernel patches. 6) Implement robust backup and recovery procedures to minimize downtime in case of system crashes. 7) For embedded systems, consider firmware updates or configuration changes that ensure the CBR address is correctly initialized during boot.
Affected Countries
Germany, France, United Kingdom, Netherlands, Italy, Spain, Poland
CVE-2024-40963: Vulnerability in Linux Linux
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.
AI-Powered Analysis
Technical Analysis
CVE-2024-40963 is a vulnerability identified in the Linux kernel specifically affecting the MIPS architecture variant bmips, and more precisely the BCM6358 chipset. The issue arises due to improper handling of the CBR (Cache Block Register) address, which in some devices is set to zero. This incorrect setting leads to a kernel panic when the function arch_sync_dma_for_cpu_all is invoked. The root cause is that the system, when booted from TP1, causes the BMIPS_GET_CBR() macro to return zero instead of a valid memory address. Additionally, the existing check involving read_c0_brcm_cmt_local() does not fail as expected, allowing the kernel to proceed with an invalid CBR address. The vulnerability stems from insufficient validation of the CBR address before deciding whether to disable RAC (Read-Ahead Cache) flush operations. This flaw can cause system instability and crashes due to kernel panics triggered by invalid memory operations during DMA synchronization. The vulnerability is specific to certain MIPS-based devices using the BCM6358 chipset and Linux kernel versions identified by the provided commit hashes. No known exploits are currently reported in the wild, and no CVSS score has been assigned yet.
Potential Impact
For European organizations, the impact of CVE-2024-40963 is primarily related to system availability and stability. Organizations using embedded systems, network devices, or specialized hardware running Linux on MIPS bmips architecture with BCM6358 chipsets could experience unexpected kernel panics leading to system crashes and downtime. This could disrupt critical infrastructure, industrial control systems, or telecommunications equipment that rely on these devices. While the vulnerability does not directly expose confidentiality or integrity risks, the denial of service caused by kernel panics can affect operational continuity. Given that MIPS-based devices are less common in mainstream enterprise servers but prevalent in embedded and network hardware, the impact is more pronounced in sectors relying on such specialized equipment. European organizations in telecommunications, manufacturing, and critical infrastructure sectors could be particularly affected if their hardware platforms include the vulnerable chipset and kernel versions.
Mitigation Recommendations
To mitigate CVE-2024-40963, organizations should: 1) Identify and inventory all devices running Linux on MIPS bmips architecture, especially those with BCM6358 chipsets. 2) Apply the latest Linux kernel patches that address this vulnerability as soon as they become available from trusted sources or Linux distributions. 3) If patching is not immediately possible, consider isolating affected devices from critical networks to reduce the risk of disruption. 4) Monitor system logs for kernel panic events related to DMA synchronization or CBR address issues to detect potential triggers of this vulnerability. 5) Engage with hardware vendors to confirm if firmware or hardware updates are necessary to complement kernel patches. 6) Implement robust backup and recovery procedures to minimize downtime in case of system crashes. 7) For embedded systems, consider firmware updates or configuration changes that ensure the CBR address is correctly initialized during boot.
Affected Countries
For access to advanced analysis and higher rate limits, contact root@offseq.com
Technical Details
- Data Version
- 5.1
- Assigner Short Name
- Linux
- Date Reserved
- 2024-07-12T12:17:45.602Z
- Cisa Enriched
- true
- Cvss Version
- null
- State
- PUBLISHED
Threat ID: 682d9821c4522896dcbddeef
Added to database: 5/21/2025, 9:08:49 AM
Last enriched: 6/28/2025, 4:24:46 AM
Last updated: 8/12/2025, 10:14:04 AM
Views: 13
Related Threats
CVE-2025-53948: CWE-415 Double Free in Santesoft Sante PACS Server
HighCVE-2025-52584: CWE-122 Heap-based Buffer Overflow in Ashlar-Vellum Cobalt
HighCVE-2025-46269: CWE-122 Heap-based Buffer Overflow in Ashlar-Vellum Cobalt
HighCVE-2025-54862: CWE-79 Improper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') in Santesoft Sante PACS Server
MediumCVE-2025-54759: CWE-79 Improper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') in Santesoft Sante PACS Server
MediumActions
Updates to AI analysis are available only with a Pro account. Contact root@offseq.com for access.
External Links
Need enhanced features?
Contact root@offseq.com for Pro access with improved analysis and higher rate limits.