CVE-2024-46848

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2024-09-27. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: None knownExposed: 0

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

perf/x86/intel: Limit the period on Haswell

Running the ltp test cve-2015-3290 concurrently reports the following warnings.

perfevents: irq loop stuck! WARNING: CPU: 31 PID: 32438 at arch/x86/events/intel/core.c:3174 intel_pmu_handle_irq+0x285/0x370 Call Trace: ? __warn+0xa4/0x220 ? intel_pmu_handle_irq+0x285/0x370 ? __report_bug+0x123/0x130 ? intel_pmu_handle_irq+0x285/0x370 ? __report_bug+0x123/0x130 ? intel_pmu_handle_irq+0x285/0x370 ? report_bug+0x3e/0xa0 ? handle_bug+0x3c/0x70 ? exc_invalid_op+0x18/0x50 ? asm_exc_invalid_op+0x1a/0x20 ? irq_work_claim+0x1e/0x40 ? intel_pmu_handle_irq+0x285/0x370 perf_event_nmi_handler+0x3d/0x60 nmi_handle+0x104/0x330

Thanks to Thomas Gleixner's analysis, the issue is caused by the low initial period (1) of the frequency estimation algorithm, which triggers the defects of the HW, specifically erratum HSW11 and HSW143. (For the details, please refer https://lore.kernel.org/lkml/87plq9l5d2.ffs@tglx/)

The HSW11 requires a period larger than 100 for the INST_RETIRED.ALL event, but the initial period in the freq mode is 1. The erratum is the same as the BDM11, which has been supported in the kernel. A minimum period of 128 is enforced as well on HSW.

HSW143 is regarding that the fixed counter 1 may overcount 32 with the Hyper-Threading is enabled. However, based on the test, the hardware has more issues than it tells. Besides the fixed counter 1, the message 'interrupt took too long' can be observed on any counter which was armed with a period < 32 and two events expired in the same NMI. A minimum period of 32 is enforced for the rest of the events. The recommended workaround code of the HSW143 is not implemented. Because it only addresses the issue for the fixed counter. It brings extra overhead through extra MSR writing. No related overcounting issue has been reported so far.

CVSS v3
5.5
EG Score
5.5(medium)
EG Risk
25(Track)
EG Risk 25/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity55% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
12%
KEV
Not listed

Published

September 27, 2024

Last Modified

November 3, 2025

References (5)

Vendor Advisories for CVE-2024-46848(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(6)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-virtual-hwe-24.04 (6.8.0-50.51) @ noble2026-05-23ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k (6.8.0-1019.21.1) @ noble2026-05-23ubuntu
ubuntulinux-tools-gkeop-6.8 (6.8.0-1002.4) @ noble2026-05-23ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-50.51~22.04.1) @ jammy2026-05-23ubuntu
ubuntulinux-tools-azure (6.8.0-1020.23) @ noble2026-05-23ubuntu
linuxKernel @ 6.1.110—osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Additional Vendor Advisories

(5)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 6× in last 7d / 40× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 116 total refreshes for this CVE.

  1. 2026-08-07 16:25 UTCEPSS rescore
  2. 2026-08-06 13:45 UTCEPSS rescore
  3. 2026-08-05 19:16 UTCEPSS rescore
  4. 2026-08-04 15:08 UTCEPSS rescore
  5. 2026-08-03 10:34 UTCEPSS rescore
  6. 2026-08-02 02:25 UTCEPSS rescore
  7. 2026-08-01 04:14 UTCEPSS rescore
  8. 2026-07-31 17:42 UTCOSV refresh
  9. 2026-07-30 16:26 UTCEPSS rescore
  10. 2026-07-30 01:29 UTCEPSS rescore
  11. 2026-07-28 15:34 UTCEPSS rescore
  12. 2026-07-27 14:11 UTCEPSS rescore
  13. 2026-07-26 14:53 UTCEPSS rescore
  14. 2026-07-26 14:53 UTCEPSS rescore
  15. 2026-07-25 14:16 UTCEPSS rescore
  16. 2026-07-23 14:17 UTCEPSS rescore
  17. 2026-07-23 02:41 UTCEG score recompute
  18. 2026-07-22 14:07 UTCEPSS rescore
  19. 2026-07-21 15:23 UTCEPSS rescore
  20. 2026-07-21 15:23 UTCEPSS rescore
  21. 2026-07-20 17:06 UTCEPSS rescore
  22. 2026-07-19 14:30 UTCEPSS rescore
  23. 2026-07-19 14:30 UTCEPSS rescore
  24. 2026-07-19 02:28 UTCEPSS rescore
  25. 2026-07-19 02:28 UTCEPSS rescore
Show 75 more
  1. 2026-07-18 10:03 UTCEPSS rescore
  2. 2026-07-18 10:03 UTCEPSS rescore
  3. 2026-07-16 17:02 UTCEPSS rescore
  4. 2026-07-15 16:56 UTCEPSS rescore
  5. 2026-07-15 16:56 UTCEPSS rescore
  6. 2026-07-15 01:59 UTCEPSS rescore
  7. 2026-07-15 01:59 UTCEPSS rescore
  8. 2026-07-14 00:38 UTCOSV refresh
  9. 2026-07-13 22:29 UTCEPSS rescore
  10. 2026-07-13 06:12 UTCEPSS rescore
  11. 2026-07-12 05:45 UTCEPSS rescore
  12. 2026-07-12 05:45 UTCEPSS rescore
  13. 2026-07-11 08:26 UTCEPSS rescore
  14. 2026-07-09 19:09 UTCEPSS rescore
  15. 2026-07-09 19:09 UTCEPSS rescore
  16. 2026-07-08 15:14 UTCEPSS rescore
  17. 2026-07-07 13:45 UTCEPSS rescore
  18. 2026-07-06 16:26 UTCEPSS rescore
  19. 2026-07-06 02:22 UTCEPSS rescore
  20. 2026-07-06 02:22 UTCEPSS rescore
  21. 2026-07-04 06:30 UTCEPSS rescore
  22. 2026-07-01 15:05 UTCEPSS rescore
  23. 2026-06-30 23:21 UTCEPSS rescore
  24. 2026-06-30 23:21 UTCEPSS rescore
  25. 2026-06-29 14:05 UTCEPSS rescore
  26. 2026-06-28 14:07 UTCEPSS rescore
  27. 2026-06-28 14:06 UTCEPSS rescore
  28. 2026-06-28 04:55 UTCEPSS rescore
  29. 2026-06-28 04:55 UTCEPSS rescore
  30. 2026-06-27 03:07 UTCEPSS rescore
  31. 2026-06-27 03:07 UTCEPSS rescore
  32. 2026-06-25 22:16 UTCOSV refresh
  33. 2026-06-25 13:49 UTCEPSS rescore
  34. 2026-06-24 14:04 UTCEPSS rescore
  35. 2026-06-24 14:04 UTCEPSS rescore
  36. 2026-06-23 21:32 UTCEPSS rescore
  37. 2026-06-23 21:32 UTCEPSS rescore
  38. 2026-06-22 14:25 UTCEPSS rescore
  39. 2026-06-22 14:25 UTCEPSS rescore
  40. 2026-06-21 14:55 UTCEPSS rescore
  41. 2026-06-21 01:58 UTCEPSS rescore
  42. 2026-06-21 01:58 UTCEPSS rescore
  43. 2026-06-19 19:25 UTCEPSS rescore
  44. 2026-06-19 19:25 UTCEPSS rescore
  45. 2026-06-18 17:52 UTCEPSS rescore
  46. 2026-06-18 17:52 UTCEPSS rescore
  47. 2026-06-17 17:52 UTCEPSS rescore
  48. 2026-06-16 17:52 UTCEPSS rescore
  49. 2026-06-16 17:52 UTCEPSS rescore
  50. 2026-06-15 17:47 UTCEPSS rescore
  51. 2026-06-14 23:17 UTCEPSS rescore
  52. 2026-06-13 22:59 UTCEPSS rescore
  53. 2026-06-13 22:59 UTCEPSS rescore
  54. 2026-06-13 22:59 UTCEPSS rescore
  55. 2026-06-12 23:11 UTCEPSS rescore
  56. 2026-06-12 23:11 UTCEPSS rescore
  57. 2026-06-11 13:59 UTCEPSS rescore
  58. 2026-06-10 22:18 UTCEPSS rescore
  59. 2026-06-10 13:21 UTCEPSS rescore
  60. 2026-06-08 14:16 UTCEPSS rescore
  61. 2026-06-08 14:16 UTCEPSS rescore
  62. 2026-06-08 11:44 UTCOSV refresh
  63. 2026-06-07 15:24 UTCEPSS rescore
  64. 2026-06-07 15:24 UTCEPSS rescore
  65. 2026-06-06 13:46 UTCEPSS rescore
  66. 2026-06-06 13:46 UTCEPSS rescore
  67. 2026-06-05 22:46 UTCEPSS rescore
  68. 2026-06-05 22:46 UTCEPSS rescore
  69. 2026-06-04 13:11 UTCEPSS rescore
  70. 2026-06-04 13:11 UTCEPSS rescore
  71. 2026-06-02 20:12 UTCEPSS rescore
  72. 2026-06-02 20:12 UTCEPSS rescore
  73. 2026-06-01 13:51 UTCEPSS rescore
  74. 2026-06-01 13:51 UTCEPSS rescore
  75. 2026-05-31 22:30 UTCEPSS rescore

Frequently asked(5)

What is CVE-2024-46848?
CVE-2024-46848 is a medium vulnerability published on September 27, 2024. In the Linux kernel, the following vulnerability has been resolved: perf/x86/intel: Limit the period on Haswell Running the ltp test cve-2015-3290 concurrently reports the following warnings. perfevents: irq loop stuck! WARNING: CPU: 31 PID: 32438 at arch/x86/events/intel/core.c:3174…
When was CVE-2024-46848 disclosed?
CVE-2024-46848 was first published in the National Vulnerability Database on September 27, 2024, with the most recent update on November 3, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2024-46848 actively exploited?
CVE-2024-46848 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 87.6% of all scored CVEs.
What is the CVSS score of CVE-2024-46848?
CVE-2024-46848 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2024-46848?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2024-46848, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2024-46848

Explore →

Is Your Infrastructure Affected by CVE-2024-46848?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs