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-2023-53273Drivers: vmbus: Check for channel allocation before looking up relids

Description

In the Linux kernel, the following vulnerability has been resolved: Drivers: vmbus: Check for channel allocation before looking up relids relid2channel() assumes vmbus channel array to be allocated when called. However, in cases such as kdump/kexec, not all relids will be reset by the host. When the second kernel boots and if the guest receives a vmbus interrupt during vmbus driver initialization before vmbus_connect() is called, before it finishes, or if it fails, the vmbus interrupt service routine is called which in turn calls relid2channel() and can cause a null pointer dereference. Print a warning and error out in relid2channel() for a channel id that's invalid in the second kernel.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 8 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-2023-53273, by who scored it
Scored byCVSSScoreVector
CISA-ADPADP (enrichment)3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
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.16% · top 95% of all CVEs (15 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 8b6a877c060ed6b86878fe66c7c6493a6054cf23 – < 176c6b4889195fbe7016d9401175b48c5c9edf68
    • affected 8b6a877c060ed6b86878fe66c7c6493a6054cf23 – < c373e49fbb87aa177819866ed9194ebc5414dfd6
    • affected 8b6a877c060ed6b86878fe66c7c6493a6054cf23 – < 8c3f0ae5435fd20bb1e3a8308488aa6ac33151ee
    • affected 8b6a877c060ed6b86878fe66c7c6493a6054cf23 – < a5c44f3446a0565139b7d8abc78f58b86c398123
    • affected 8b6a877c060ed6b86878fe66c7c6493a6054cf23 – < 1eb65c8687316c65140b48fad27133d583178e15
  • Linux · Linux

    • affected 5.8
    • unaffected < 5.8
    • unaffected 5.10.178 – ≤ 5.10.*
    • unaffected 5.15.107 – ≤ 5.15.*
    • unaffected 6.1.24 – ≤ 6.1.*
    • unaffected 6.2.11 – ≤ 6.2.*
    • unaffected 6.3 – ≤ *

References

References5

Sources

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

Badge for a README or a ticket

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

Record last updated .