CVE-2026-63955 (GCVE-0-2026-63955)
Vulnerability from cvelistv5
Published
2026-07-19 14:55
Modified
2026-08-05 12:37
Severity ?
7.5 (High) - CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Summary
In the Linux kernel, the following vulnerability has been resolved: mm/vmalloc: do not trigger BUG() on BH disabled context __get_vm_area_node() currently triggers a BUG() if in_interrupt() returns true. However, in_interrupt() also reports true when BH are disabled. The bridge code can call rhashtable_lookup_insert_fast() with bottom halves disabled: __vlan_add() -> br_fdb_add_local() spin_lock_bh(&br->hash_lock); <-- Disable BH -> fdb_add_local() -> fdb_create() -> rhashtable_lookup_insert_fast() -> kvmalloc() -> vmalloc() -> __get_vm_area_node() -> BUG_ON(in_interrupt()) spin_unlock_bh(&br->hash_lock) this triggers the BUG() despite the caller not being in NMI or hard IRQ context. Replace the in_interrupt() check with in_nmi() || in_hardirq().
References
Impacted products
Vendor Product Version
Linux Linux Version: c6307674ed82c0c57d6e1e3408e84ac449ab8e94
Version: c6307674ed82c0c57d6e1e3408e84ac449ab8e94
 Create a notification for this product.
Show details on NVD website

To clipboard 

{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "mm/vmalloc.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "ad7eff07b625f53c3fb513b30d7a8c5a79fbc7ce",
              "status": "affected",
              "version": "c6307674ed82c0c57d6e1e3408e84ac449ab8e94",
              "versionType": "git"
            },
            {
              "lessThan": "04aa71da5f35aacdc9ae9cb5150947daa624f641",
              "status": "affected",
              "version": "c6307674ed82c0c57d6e1e3408e84ac449ab8e94",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "mm/vmalloc.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "6.19"
            },
            {
              "lessThan": "6.19",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "7.0.*",
              "status": "unaffected",
              "version": "7.0.12",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "7.1",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.0.12",
                  "versionStartIncluding": "6.19",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.1",
                  "versionStartIncluding": "6.19",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nmm/vmalloc: do not trigger BUG() on BH disabled context\n\n__get_vm_area_node() currently triggers a BUG() if in_interrupt() returns\ntrue.  However, in_interrupt() also reports true when BH are disabled.\n\nThe bridge code can call rhashtable_lookup_insert_fast() with bottom\nhalves disabled:\n\n__vlan_add()\n -\u003e br_fdb_add_local()\n  spin_lock_bh(\u0026br-\u003ehash_lock); \u003c-- Disable BH\n   -\u003e fdb_add_local()\n    -\u003e fdb_create()\n     -\u003e rhashtable_lookup_insert_fast()\n      -\u003e kvmalloc()\n       -\u003e vmalloc()\n        -\u003e __get_vm_area_node()\n         -\u003e BUG_ON(in_interrupt())\n  spin_unlock_bh(\u0026br-\u003ehash_lock)\n\nthis triggers the BUG() despite the caller not being in NMI or\nhard IRQ context.\n\nReplace the in_interrupt() check with in_nmi() || in_hardirq()."
        }
      ],
      "metrics": [
        {
          "cvssV3_1": {
            "baseScore": 7.5,
            "baseSeverity": "HIGH",
            "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
            "version": "3.1"
          },
          "scenarios": [
            {
              "lang": "en",
              "value": "AV:N - After kvmalloc gained GFP_ATOMIC vmalloc fallback, reachable rhashtable resize paths run from network packet handling (e.g. bridge FDB learning in RX softirq, VXLAN UDP receive/snoop) and can call __get_vm_area_node() while in_interrupt() is true.\nAC:L - An attacker can reliably trigger the BUG by flooding a reachable bridge/VXLAN interface with many unique source MACs (or equivalent netlink admin operations) to force rhashtable growth and a large GFP_ATOMIC kvmalloc vmalloc fallback.\nPR:N - The highest-impact path needs no kernel privileges: sending crafted L2/overlay packets to a learning bridge or VXLAN endpoint is sufficient; netlink-only paths additionally require CAP_NET_ADMIN but are not the ceiling.\nUI:N - Exploitation is fully attacker-driven packet or netlink traffic and does not require any victim user action beyond normal system operation.\nS:U - Impact is a host kernel BUG/panic from the mm/vmalloc path; it does not cross a VM, IOMMU, or sandbox security boundary for privilege escalation.\nC:N - The failure mode is an intentional BUG_ON() kernel panic with no memory corruption, out-of-bounds access, or information disclosure primitive.\nI:N - No attacker-controlled memory is modified; the bug only aborts the kernel via BUG() rather than providing a write or code-execution primitive.\nA:H - Hitting BUG_ON(in_interrupt()) in __get_vm_area_node() causes a kernel BUG/oops/panic, producing total loss of system availability."
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-08-05T12:37:39.551Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/ad7eff07b625f53c3fb513b30d7a8c5a79fbc7ce"
        },
        {
          "url": "https://git.kernel.org/stable/c/04aa71da5f35aacdc9ae9cb5150947daa624f641"
        }
      ],
      "title": "mm/vmalloc: do not trigger BUG() on BH disabled context",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2026-63955",
    "datePublished": "2026-07-19T14:55:46.903Z",
    "dateReserved": "2026-07-19T07:54:57.023Z",
    "dateUpdated": "2026-08-05T12:37:39.551Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2"
}


Log in or create an account to share your comment.




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.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • 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.