CVE-2024-46848— perf/x86/intel: Limit the period on Haswell
Get alerts for future matching vulnerabilitiesLog in to subscribe
I. Basic Information for CVE-2024-46848
Vulnerability Information
Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗ Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.
Vulnerability Title
perf/x86/intel: Limit the period on Haswell
Source: NVD (National Vulnerability Database)
Vulnerability Description
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: <NMI> ? __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.
Source: NVD (National Vulnerability Database)
CVSS Information
N/A
Source: NVD (National Vulnerability Database)
Vulnerability Type
N/A
Source: NVD (National Vulnerability Database)
Vulnerability Title
Linux kernel 安全漏洞
Source: CNNVD (China National Vulnerability Database)
Vulnerability Description
Linux kernel是美国Linux基金会的开源操作系统Linux所使用的内核。 Linux kernel存在安全漏洞，该漏洞源于在Haswell处理器上设置的周期过短，触发了硬件缺陷。
Source: CNNVD (China National Vulnerability Database)
CVSS Information
N/A
Source: CNNVD (China National Vulnerability Database)
Vulnerability Type
N/A
Source: CNNVD (China National Vulnerability Database)
Affected Products
II. Public POCs for CVE-2024-46848
| # | POC Description | Source Link | Shenlong Link |
|---|
AI-Generated POCPremium
No public POC found.
Login to generate AI POCIII. Intelligence Information for CVE-2024-46848
请登录查看更多情报信息。
Same Patch Batch · Linux · 2024-09-27 · 66 CVEs total
| CVE-2024-46844 | um: line: always fill *error_out in setup_one_line() | |
| CVE-2024-46865 | fou: fix initialization of grc | |
| CVE-2024-46864 | x86/hyperv: fix kexec crash due to VP assist page corruption | |
| CVE-2024-46863 | ASoC: Intel: soc-acpi-intel-lnl-match: add missing empty item | |
| CVE-2024-46851 | drm/amd/display: Avoid race between dcn10_set_drr() and dc_state_destruct() | |
| CVE-2024-46852 | dma-buf: heaps: Fix off-by-one in CMA heap fault handler | |
| CVE-2024-46850 | drm/amd/display: Avoid race between dcn35_set_drr() and dc_state_destruct() | |
| CVE-2024-46849 | ASoC: meson: axg-card: fix 'use-after-free' | |
| CVE-2024-46847 | mm: vmalloc: ensure vmap_block is initialised before adding to queue | |
| CVE-2024-46846 | spi: rockchip: Resolve unbalanced runtime PM / system PM handling | |
| CVE-2024-46853 | spi: nxp-fspi: fix the KASAN report out-of-bounds bug | |
| CVE-2024-46845 | tracing/timerlat: Only clear timer if a kthread exists | |
| CVE-2024-46843 | scsi: ufs: core: Remove SCSI host only if added | |
| CVE-2024-46841 | btrfs: don't BUG_ON on ENOMEM from btrfs_lookup_extent_info() in walk_down_proc() | |
| CVE-2024-46842 | scsi: lpfc: Handle mailbox timeouts in lpfc_get_sfp_info | |
| CVE-2024-46840 | btrfs: clean up our handling of refs == 0 in snapshot delete | |
| CVE-2024-46838 | userfaultfd: don't BUG_ON() if khugepaged yanks our page table | |
| CVE-2024-46837 | drm/panthor: Restrict high priorities on group_create | |
| CVE-2024-46835 | drm/amdgpu: Fix smatch static checker warning | |
| CVE-2024-46836 | usb: gadget: aspeed_udc: validate endpoint index for ast udc |
Showing top 20 of 66 CVEs. View all on vendor page → →
IV. Related Vulnerabilities
Same product: Linux
- CVE-2026-43500
rxrpc: Also unshare DATA/RESPONSE packets when paged frags a - CVE-2026-43475
scsi: storvsc: Fix scheduling while atomic on PREEMPT_RT - CVE-2026-43474
fs: init flags_valid before calling vfs_fileattr_get - CVE-2026-43473
scsi: mpi3mr: Add NULL checks when resetting request and rep - CVE-2026-43472
unshare: fix unshare_fs() handling
Same vendor: Linux
- CVE-2026-43500
rxrpc: Also unshare DATA/RESPONSE packets when paged frags a - CVE-2026-43475
scsi: storvsc: Fix scheduling while atomic on PREEMPT_RT - CVE-2026-43474
fs: init flags_valid before calling vfs_fileattr_get - CVE-2026-43473
scsi: mpi3mr: Add NULL checks when resetting request and rep - CVE-2026-43472
unshare: fix unshare_fs() handling
V. Comments for CVE-2024-46848
No comments yet