Skip to main content

Boteraser | Website and Server Security Solutions

🛡️ CVE-2024-53089 — kernel

🟡 CVSS 5.5 — Medium ✅ No Known Exploit NVD
5.5
CVSS Score
0 Low4 Medium7 High9 Critical10

Description

LoongArch: KVM: Mark hrtimer to expire in hard interrupt context

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

LoongArch: KVM: Mark hrtimer to expire in hard interrupt context

Like commit 2c0d278f3293f ("KVM: LAPIC: Mark hrtimer to expire in hard

interrupt context") and commit 9090825fa9974 ("KVM: arm/arm64: Let the

timer expire in hardirq context on RT"), On PREEMPT_RT enabled kernels

unmarked hrtimers are moved into soft interrupt expiry mode by default.

Then the timers are canceled from an preempt-notifier which is invoked

with disabled preemption which is not allowed on PREEMPT_RT.

The timer callback is short so in could be invoked in hard-IRQ context.

So let the timer expire on hard-IRQ context even on -RT.

This fix a "scheduling while atomic" bug for PREEMPT_RT enabled kernels:

BUG: scheduling while atomic: qemu-system-loo/1011/0x00000002

Modules linked in: amdgpu rfkill nft_fib_inet nft_fib_ipv4 nft_fib_ipv6 nft_fib nft_reject_inet nf_reject_ipv4 nf_reject_ipv6 nft_reject nft_ct nft_chain_nat ns

CPU: 1 UID: 0 PID: 1011 Comm: qemu-system-loo Tainted: G W 6.12.0-rc2+ #1774

Tainted: [W]=WARN

Hardware name: Loongson Loongson-3A5000-7A1000-1w-CRB/Loongson-LS3A5000-7A1000-1w-CRB, BIOS vUDK2018-LoongArch-V2.0.0-prebeta9 10/21/2022

Stack : ffffffffffffffff 0000000000000000 9000000004e3ea38 9000000116744000

90000001167475a0 0000000000000000 90000001167475a8 9000000005644830

90000000058dc000 90000000058dbff8 9000000116747420 0000000000000001

0000000000000001 6a613fc938313980 000000000790c000 90000001001c1140

00000000000003fe 0000000000000001 000000000000000d 0000000000000003

0000000000000030 00000000000003f3 000000000790c000 9000000116747830

90000000057ef000 0000000000000000 9000000005644830 0000000000000004

0000000000000000 90000000057f4b58 0000000000000001 9000000116747868

900000000451b600 9000000005644830 9000000003a13998 0000000010000020

00000000000000b0 0000000000000004 0000000000000000 0000000000071c1d

...

Call Trace:

[<9000000003a13998>] show_stack+0x38/0x180

[<9000000004e3ea34>] dump_stack_lvl+0x84/0xc0

[<9000000003a71708>] __schedule_bug+0x48/0x60

[<9000000004e45734>] __schedule+0x1114/0x1660

[<9000000004e46040>] schedule_rtlock+0x20/0x60

[<9000000004e4e330>] rtlock_slowlock_locked+0x3f0/0x10a0

[<9000000004e4f038>] rt_spin_lock+0x58/0x80

[<9000000003b02d68>] hrtimer_cancel_wait_running+0x68/0xc0

[<9000000003b02e30>] hrtimer_cancel+0x70/0x80

[<ffff80000235eb70>] kvm_restore_timer+0x50/0x1a0 [kvm]

[<ffff8000023616c8>] kvm_arch_vcpu_load+0x68/0x2a0 [kvm]

[<ffff80000234c2d4>] kvm_sched_in+0x34/0x60 [kvm]

[<9000000003a749a0>] finish_task_switch.isra.0+0x140/0x2e0

[<9000000004e44a70>] __schedule+0x450/0x1660

[<9000000004e45cb0>] schedule+0x30/0x180

[<ffff800002354c70>] kvm_vcpu_block+0x70/0x120 [kvm]

[<ffff800002354d80>] kvm_vcpu_halt+0x60/0x3e0 [kvm]

[<ffff80000235b194>] kvm_handle_gspr+0x3f4/0x4e0 [kvm]

[<ffff80000235f548>] kvm_handle_exit+0x1c8/0x260 [kvm]

How this vulnerability can be exploited

This issue can be reached with local access to the system, attack complexity is low, an attacker needs low-level privileges on the target. No user interaction is required. The scope is unchanged, so the impact stays within the vulnerable component. Rated impact: confidentiality none, integrity none, availability high.

CVSS metrics in full

The score comes from this vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

  • Attack vector: Local — a local account, shell or session on the host is needed.
  • Attack complexity: Low — the attack works reliably, with no preparation.
  • Privileges required: Low — an ordinary user account is enough.
  • User interaction: None — nobody has to be tricked into anything.
  • Scope: Unchanged — the damage stays inside the vulnerable component.
  • Confidentiality impact: None.
  • Integrity impact: None.
  • Availability impact: High — total loss, or loss the attacker controls.

Affected software

CVE-2024-53089 is recorded against 2 packages.

  • kernel (from 5.19.0 up to 6.11.9)
  • linux-kernel

Timeline and source

Published on 21 November 2024 and last revised on 12 August 2026. No public exploit is currently recorded for this entry. A vendor advisory or fix has been published. Record sourced from NVD.

References

git.kernel.org (Web)
git.kernel.org (Web)
github.com (Advisory)
nvd.nist.gov (Advisory)
git.kernel.org (Package)

Other advisories for this package

kernel has other advisories on record. If you are patching this one, these are worth checking on the same host:

CVE-2024-53089 on other distributions

Each distribution ships its own build and its own fixed version. Pick the one you run:

Details

Severity Medium
CVSS Score 5.5
CVSS Vector CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
CWE N/A
Public Exploit ✅ No
Source NVD
Published 2024-11-21
Updated 2026-08-20
Modified 2026-08-12

Affected Packages

Software From version Fixed in
kernel 5.19.0 6.11.9
linux-kernel — —

Similar Threats

Vulnerability Monitoring

Track new vulnerabilities in kernel

CVE-2024-53089 is rated CVSS 5.5 Medium. BotEraser monitors your WordPress installation and notifies you when software you use appears in our vulnerability database.

Set Up Free Alerts →

No credit card required  ·  Results in minutes

ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.

Browse related advisories

All advisoriesCVECVE 2024
✓