Skip to content
CVE Tracker
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API documentationPage
  • MCP serverPage
  • Data sourcesPage
  • ChangelogPage
  • AboutPage
  • How it's builtPage
Back

CVE-2023-52860

drivers/perf: hisi: use cpuhp_state_remove_instance_nocalls() for hisi_hns3_pmu uninit process

Medium5.5EPSS 0.24%
Published
Updated
Reserved
Assigned by
Linux

Description

In the Linux kernel, the following vulnerability has been resolved: drivers/perf: hisi: use cpuhp_state_remove_instance_nocalls() for hisi_hns3_pmu uninit process When tearing down a 'hisi_hns3' PMU, we mistakenly run the CPU hotplug callbacks after the device has been unregistered, leading to fireworks when we try to execute empty function callbacks within the driver: | Unable to handle kernel NULL pointer dereference at virtual address 0000000000000000 | CPU: 0 PID: 15 Comm: cpuhp/0 Tainted: G W O 5.12.0-rc4+ #1 | Hardware name: , BIOS KpxxxFPGA 1P B600 V143 04/22/2021 | pstate: 80400009 (Nzcv daif +PAN -UAO -TCO BTYPE=--) | pc : perf_pmu_migrate_context+0x98/0x38c | lr : perf_pmu_migrate_context+0x94/0x38c | | Call trace: | perf_pmu_migrate_context+0x98/0x38c | hisi_hns3_pmu_offline_cpu+0x104/0x12c [hisi_hns3_pmu] Use cpuhp_state_remove_instance_nocalls() instead of cpuhp_state_remove_instance() so that the notifiers don't execute after the PMU device has been unregistered. [will: Rewrote commit message]

Scores

CVSS scores of CVE-2023-52860, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.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.24% · top 85% of all CVEs (6 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.

Weakness

Affected products

  • Linux · Linux

    • affected 66637ab137b44914356a9dc7a9b3f8ebcf0b0695 – < 4589403a343bb0c72a6faf5898386ff964d4e01a
    • affected 66637ab137b44914356a9dc7a9b3f8ebcf0b0695 – < 3f5827371763f2d9c70719c270055a81d030f3d0
    • affected 66637ab137b44914356a9dc7a9b3f8ebcf0b0695 – < d04ff5437a45f275db5530efb49b68d0ec851f6f
    • affected 66637ab137b44914356a9dc7a9b3f8ebcf0b0695 – < 50b560783f7f71790bcf70e9e9855155fb0af8c1
  • Linux · Linux

    • affected 6.0
    • unaffected < 6.0
    • unaffected 6.1.63 – ≤ 6.1.*
    • unaffected 6.5.12 – ≤ 6.5.*
    • unaffected 6.6.2 – ≤ 6.6.*
    • unaffected 6.7 – ≤ *

References (4)

Sources

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

Badge for a README or a ticket

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

Record last updated .