LiveActive security incident?Get immediate response
CVE Record

CVE-2024-40963: mips: bmips: BCM6358: make sure CBR is correctly set

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue can cause a kernel panic on some Broadcom MIPS BCM6358-based systems when an internal CBR address is unexpectedly zero. The business impact is availability: affected embedded or network devices may crash. The sources do not show active exploitation or a remotely reachable attack path.

Executive priority

Handle through normal embedded Linux patch management unless affected devices are business-critical or customer-facing. Urgency rises where BCM6358-based devices provide network access, routing, or managed service availability.

Technical view

The BMIPS BCM6358 path could treat a zero CBR value as valid, so arch_sync_dma_for_cpu_all could trigger a panic during DMA cache handling. The kernel fix adds stronger validation that CBR is a valid address before using RAC flush behavior. Scope appears hardware- and architecture-specific.

Likely exposure

Exposure is likely limited to Linux systems using MIPS BMIPS BCM6358 hardware or derived embedded platforms. General-purpose x86, ARM servers, and cloud workloads are not indicated by the provided sources.

Exploitation context

CISA KEV status is false in the provided bundle, and no cited source reports exploitation in the wild. The evidence describes a crash condition observed during boot or DMA synchronization, not a proven external exploit chain.

Researcher notes

The source bundle lacks CVSS, CWE, and detailed exploitability analysis. Treat this as a kernel availability flaw with narrow hardware scope. Do not assume remote exploitability without additional vendor or distribution evidence.

Mitigation direction

  • Inventory Linux devices using MIPS BMIPS BCM6358 or related Broadcom SoCs.
  • Update affected kernels to vendor or distribution releases containing the referenced stable fixes.
  • Prioritize embedded network devices where downtime affects customers or operations.
  • Check Debian LTS guidance if managing Debian-based affected systems.
  • Monitor vendor advisories for device-specific firmware containing the kernel fix.

Validation and detection

  • Confirm kernel architecture and hardware platform for exposed embedded devices.
  • Compare running kernel versions against vendor advisories and fixed stable commits.
  • Review crash logs for kernel panics around arch_sync_dma_for_cpu_all or BMIPS CBR handling.
  • Verify updated firmware or kernel packages include the referenced Linux stable patches.
Prepared
Confidence
medium
Sources
10

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2024-40963 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
2ADP providers
9Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CVECVE Program Container
CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxd65de5ee8b72868fbbbd39ca73017d0e526fa13a, 47a449ec09b4479b89dcc6b27ec3829fc82ffafb, 65b723644294f1d79770704162c0e8d1f700b6f1, 2cdbcff99f15db86a10672fb220379a1ae46ccae, ab327f8acdf8d06601fbf058859a539a9422afff, ab327f8acdf8d06601fbf058859a539a9422afff, ab327f8acdf8d06601fbf058859a539a9422afff, 288c96aa5b5526cd4a946e84ef85e165857693b5, 5.4.240, 5.10.177, 5.15.106, 6.1.23, 6.2.10unaffected
LinuxLinux6.3, 0, 5.4.279, 5.10.221, 5.15.162, 6.1.96, 6.6.36, 6.9.7, 6.10affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.