[Xen HVM] kernel-4.18.0-553.50.1.el8_10 panic at 'xen_time_init()' during boot.

Solution Verified - Updated -

Issue

  • The kernel-4.18.0-553.50.1.el8_10 fails to boot and panic at xen_time_init() function during boot, specifically on standalone Xen + intel CPU, and legacy AWS instances.
  • The issue started reproducing after updating the system from 4.18.0-553.47.1.el8_10 to 4.18.0-553.50.1.el8_10 as part of CVE-2024-53241.
[    0.262012] invalid opcode: 0000 [#1] SMP PTI
[    0.263000] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.18.0-553.50.1.el8_10.x86_64 #1
[    0.263000] Hardware name: Xen HVM domU, BIOS 4.13 12/03/2021
[    0.263000] RIP: 0010:xen_time_init+0x66/0x1f2
..
[    0.263000] Call Trace:
[    0.263000]  native_smp_prepare_cpus+0xc4/0x166
[    0.263000]  xen_hvm_smp_prepare_cpus+0xc/0x65
[    0.263000]  kernel_init_freeable+0xd3/0x23a
[    0.263000]  kernel_init+0xa/0x10a
[    0.263000]  ret_from_fork+0x1f/0x40
[    0.263000] Modules linked in:
[    0.487004] ---[ end trace 2762b0c1555c06ae ]---
[    0.490001] RIP: 0010:xen_time_init+0x66/0x1f2

Environment

  • Standalone Xen + Intel CPU
  • AWS legacy instances
  • kernel-4.18.0-553.50.1.el8_10

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content