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-2026-43079perf/x86/intel/uncore: Skip discovery table for offline dies

Description

In the Linux kernel, the following vulnerability has been resolved: perf/x86/intel/uncore: Skip discovery table for offline dies This warning can be triggered if NUMA is disabled and the system boots with fewer CPUs than the number of CPUs in die 0. WARNING: CPU: 9 PID: 7257 at uncore.c:1157 uncore_pci_pmu_register+0x136/0x160 [intel_uncore] Currently, the discovery table continues to be parsed even if all CPUs in the associated die are offline. This can lead to an array overflow at "pmu->boxes[die] = box" in uncore_pci_pmu_register(), which may trigger the warning above or cause other issues.

Timeline

  1. ID reserved

    By Linux

  2. · 5 days later

    Published

  3. · 6 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-2026-43079, 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.12% · top 98% of all CVEs (18 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 edae1f06c2cda41edffc93de6aedc8ba8dc883c3 – < d18da11a5e21eac7651c8897e5e0908f6c2bc9de
    • affected edae1f06c2cda41edffc93de6aedc8ba8dc883c3 – < dfcba8c8674cead6c88a2f269b71aa4efd3d384a
    • affected edae1f06c2cda41edffc93de6aedc8ba8dc883c3 – < cfab2c817d2e7e0bee98d66850246ce842ed5f18
    • affected edae1f06c2cda41edffc93de6aedc8ba8dc883c3 – < 6cfc187d85f18f976d0fe527d4c6f6171542cc19
    • affected edae1f06c2cda41edffc93de6aedc8ba8dc883c3 – < f34feda8e0c9535fee3f8870ce8bab53c2798f71
    • affected edae1f06c2cda41edffc93de6aedc8ba8dc883c3 – < 7a2cb02437d92ed14fe494d8994056d5bd2c72b4
    • affected edae1f06c2cda41edffc93de6aedc8ba8dc883c3 – < 7b568e9eba2fad89a696f22f0413d44cf4a1f892
  • Linux · Linux

    • affected 5.13
    • unaffected < 5.13
    • unaffected 5.15.209 – ≤ 5.15.*
    • unaffected 6.1.175 – ≤ 6.1.*
    • unaffected 6.6.136 – ≤ 6.6.*
    • unaffected 6.12.83 – ≤ 6.12.*
    • unaffected 6.18.24 – ≤ 6.18.*
    • unaffected 6.19.14 – ≤ 6.19.*
    • unaffected 7.0 – ≤ *

References

References7

Sources

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

Badge for a README or a ticket

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

Record last updated .