{"timestamp":"2024-09-29T13:58:48.899294Z","id":"CVE-2024-46848","options":[{"exploitation":"none"},{"automatable":"no"},{"technicalImpact":"partial"}],"role":"CISA Coordinator","version":"2.0.3"}

[{"vendor":"Linux","product":"Linux","defaultStatus":"unaffected","programFiles":["arch/x86/events/intel/core.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","versions":[{"version":"3a632cb229bfb18b6d09822cc842451ea46c013e","lessThan":"15210b7c8caff4929f25d049ef8404557f8ae468","versionType":"git","status":"affected"},{"version":"3a632cb229bfb18b6d09822cc842451ea46c013e","lessThan":"0eaf812aa1506704f3b78be87036860e5d0fe81d","versionType":"git","status":"affected"},{"version":"3a632cb229bfb18b6d09822cc842451ea46c013e","lessThan":"8717dc35c0e5896f4110f4b3882f7ff787a5f73d","versionType":"git","status":"affected"},{"version":"3a632cb229bfb18b6d09822cc842451ea46c013e","lessThan":"25dfc9e357af8aed1ca79b318a73f2c59c1f0b2b","versionType":"git","status":"affected"}]},{"vendor":"Linux","product":"Linux","defaultStatus":"affected","programFiles":["arch/x86/events/intel/core.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","versions":[{"version":"3.11","status":"affected"},{"version":"0","lessThan":"3.11","versionType":"semver","status":"unaffected"},{"version":"6.1.110","lessThanOrEqual":"6.1.*","versionType":"semver","status":"unaffected"},{"version":"6.6.51","lessThanOrEqual":"6.6.*","versionType":"semver","status":"unaffected"},{"version":"6.10.10","lessThanOrEqual":"6.10.*","versionType":"semver","status":"unaffected"},{"version":"6.11","lessThanOrEqual":"*","versionType":"original_commit_for_fix","status":"unaffected"}]}]

https://lists.debian.org/debian-lts-announce/2025/01/msg00001.html

NIST AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

NIST NVD-CWE-noinfo

OR
     *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 3.11 up to (excluding) 6.1.110
     *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.2 up to (excluding) 6.6.51
     *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.7 up to (excluding) 6.10.10
     *cpe:2.3:o:linux:linux_kernel:6.11:rc1:*:*:*:*:*:*
     *cpe:2.3:o:linux:linux_kernel:6.11:rc2:*:*:*:*:*:*
     *cpe:2.3:o:linux:linux_kernel:6.11:rc3:*:*:*:*:*:*
     *cpe:2.3:o:linux:linux_kernel:6.11:rc4:*:*:*:*:*:*
     *cpe:2.3:o:linux:linux_kernel:6.11:rc5:*:*:*:*:*:*
     *cpe:2.3:o:linux:linux_kernel:6.11:rc6:*:*:*:*:*:*

https://git.kernel.org/stable/c/0eaf812aa1506704f3b78be87036860e5d0fe81d No Types Assigned

https://git.kernel.org/stable/c/0eaf812aa1506704f3b78be87036860e5d0fe81d Patch

https://git.kernel.org/stable/c/15210b7c8caff4929f25d049ef8404557f8ae468 No Types Assigned

https://git.kernel.org/stable/c/15210b7c8caff4929f25d049ef8404557f8ae468 Patch

https://git.kernel.org/stable/c/25dfc9e357af8aed1ca79b318a73f2c59c1f0b2b No Types Assigned

https://git.kernel.org/stable/c/25dfc9e357af8aed1ca79b318a73f2c59c1f0b2b Patch

https://git.kernel.org/stable/c/8717dc35c0e5896f4110f4b3882f7ff787a5f73d No Types Assigned

https://git.kernel.org/stable/c/8717dc35c0e5896f4110f4b3882f7ff787a5f73d Patch

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.

kernel.org https://git.kernel.org/stable/c/0eaf812aa1506704f3b78be87036860e5d0fe81d [No types assigned]

kernel.org https://git.kernel.org/stable/c/15210b7c8caff4929f25d049ef8404557f8ae468 [No types assigned]

kernel.org https://git.kernel.org/stable/c/25dfc9e357af8aed1ca79b318a73f2c59c1f0b2b [No types assigned]

kernel.org https://git.kernel.org/stable/c/8717dc35c0e5896f4110f4b3882f7ff787a5f73d [No types assigned]