ghsa-cwj5-fc98-66qg
Vulnerability from github
Published
2024-07-12 15:31
Modified
2024-07-12 15:31
Details

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.

Show details on source website

To clipboard 

{
   affected: [],
   aliases: [
      "CVE-2024-40963",
   ],
   database_specific: {
      cwe_ids: [],
      github_reviewed: false,
      github_reviewed_at: null,
      nvd_published_at: "2024-07-12T13:15:18Z",
      severity: null,
   },
   details: "In the Linux kernel, the following vulnerability has been resolved:\n\nmips: bmips: BCM6358: make sure CBR is correctly set\n\nIt was discovered that some device have CBR address set to 0 causing\nkernel panic when arch_sync_dma_for_cpu_all is called.\n\nThis was notice in situation where the system is booted from TP1 and\nBMIPS_GET_CBR() returns 0 instead of a valid address and\n!!(read_c0_brcm_cmt_local() & (1 << 31)); not failing.\n\nThe current check whether RAC flush should be disabled or not are not\nenough hence lets check if CBR is a valid address or not.",
   id: "GHSA-cwj5-fc98-66qg",
   modified: "2024-07-12T15:31:28Z",
   published: "2024-07-12T15:31:28Z",
   references: [
      {
         type: "ADVISORY",
         url: "https://nvd.nist.gov/vuln/detail/CVE-2024-40963",
      },
      {
         type: "WEB",
         url: "https://git.kernel.org/stable/c/10afe5f7d30f6fe50c2b1177549d0e04921fc373",
      },
      {
         type: "WEB",
         url: "https://git.kernel.org/stable/c/2cd4854ef14a487bcfb76c7980675980cad27b52",
      },
      {
         type: "WEB",
         url: "https://git.kernel.org/stable/c/36d771ce6028b886e18a4a8956a5d23688e4e13d",
      },
      {
         type: "WEB",
         url: "https://git.kernel.org/stable/c/6c0f6ccd939166f56a904c792d7fcadae43b9085",
      },
      {
         type: "WEB",
         url: "https://git.kernel.org/stable/c/89167072fd249e5f23ae2f8093f87da5925cef27",
      },
      {
         type: "WEB",
         url: "https://git.kernel.org/stable/c/ce5cdd3b05216b704a704f466fb4c2dff3778caf",
      },
      {
         type: "WEB",
         url: "https://git.kernel.org/stable/c/da895fd6da438af8d9326b8f02d715a9c76c3b5b",
      },
   ],
   schema_version: "1.4.0",
   severity: [],
}


Log in or create an account to share your comment.

Security Advisory comment format.

This schema specifies the format of a comment related to a security advisory.

UUIDv4 of the comment
UUIDv4 of the Vulnerability-Lookup instance
When the comment was created originally
When the comment was last updated
Title of the comment
Description of the comment
The identifier of the vulnerability (CVE ID, GHSA-ID, PYSEC ID, etc.).



Tags
Taxonomy of the tags.




Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
  • Confirmed: The vulnerability is confirmed from an analyst perspective.
  • Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
  • Patched: This vulnerability was successfully patched by the user reporting the sighting.
  • Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
  • Not confirmed: The user expresses doubt about the veracity of the vulnerability.
  • Not patched: This vulnerability was not successfully patched by the user reporting the sighting.