Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 23 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2024-40963, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.29% · top 78% of all CVEs (13 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected d65de5ee8b72868fbbbd39ca73017d0e526fa13a – < 10afe5f7d30f6fe50c2b1177549d0e04921fc373
    • affected 47a449ec09b4479b89dcc6b27ec3829fc82ffafb – < 36d771ce6028b886e18a4a8956a5d23688e4e13d
    • affected 65b723644294f1d79770704162c0e8d1f700b6f1 – < 89167072fd249e5f23ae2f8093f87da5925cef27
    • affected 2cdbcff99f15db86a10672fb220379a1ae46ccae – < 6c0f6ccd939166f56a904c792d7fcadae43b9085
    • affected ab327f8acdf8d06601fbf058859a539a9422afff – < 2cd4854ef14a487bcfb76c7980675980cad27b52
    • affected ab327f8acdf8d06601fbf058859a539a9422afff – < da895fd6da438af8d9326b8f02d715a9c76c3b5b
    • affected ab327f8acdf8d06601fbf058859a539a9422afff – < ce5cdd3b05216b704a704f466fb4c2dff3778caf
    • affected 288c96aa5b5526cd4a946e84ef85e165857693b5
    • affected 5.4.240 – < 5.4.279
    • affected 5.10.177 – < 5.10.221
    • affected 5.15.106 – < 5.15.162
    • affected 6.1.23 – < 6.1.96
    • affected 6.2.10 – < 6.3
  • Linux · Linux

    • affected 6.3
    • unaffected < 6.3
    • unaffected 5.4.279 – ≤ 5.4.*
    • unaffected 5.10.221 – ≤ 5.10.*
    • unaffected 5.15.162 – ≤ 5.15.*
    • unaffected 6.1.96 – ≤ 6.1.*
    • unaffected 6.6.36 – ≤ 6.6.*
    • unaffected 6.9.7 – ≤ 6.9.*
    • unaffected 6.10 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2024-40963 badge
[![CVE-2024-40963](https://cveledger.app/badge/CVE-2024-40963.svg)](https://cveledger.app/cve/CVE-2024-40963)

Record last updated .