CVE-2024-58090

Aliases:UBUNTU-CVE-2024-58090DEBIAN-CVE-2024-58090
Advisory lineage Upstream: 0 Downstream: 66
Modified
Published: 27 Mar 2025, 14:57
Last modified:11 May 2026, 21:03

Vulnerability Summary

Overall Risk (default)
low
22/100
CVSS Score
5.5 MEDIUM
v3.1 (nvd)
EPSS Score
0.21% LOW
0% probability +0.13%
KEV
Not listed
Ransomware
No reports
Public exploits
None found
Dark Web
Not detected

Timeline

27 Mar 2025, 14:57
Published
Vulnerability first disclosed
11 May 2026, 21:03
Last Modified
Vulnerability information updated

Description

In the Linux kernel, the following vulnerability has been resolved: sched/core: Prevent rescheduling when interrupts are disabled David reported a warning observed while loop testing kexec jump: Interrupts enabled after irqrouter_resume+0x0/0x50 WARNING: CPU: 0 PID: 560 at drivers/base/syscore.c:103 syscore_resume+0x18a/0x220 kernel_kexec+0xf6/0x180 __do_sys_reboot+0x206/0x250 do_syscall_64+0x95/0x180 The corresponding interrupt flag trace: hardirqs last enabled at (15573): [<ffffffffa8281b8e>] __up_console_sem+0x7e/0x90 hardirqs last disabled at (15580): [<ffffffffa8281b73>] __up_console_sem+0x63/0x90 That means __up_console_sem() was invoked with interrupts enabled. Further instrumentation revealed that in the interrupt disabled section of kexec jump one of the syscore_suspend() callbacks woke up a task, which set the NEED_RESCHED flag. A later callback in the resume path invoked cond_resched() which in turn led to the invocation of the scheduler: __cond_resched+0x21/0x60 down_timeout+0x18/0x60 acpi_os_wait_semaphore+0x4c/0x80 acpi_ut_acquire_mutex+0x3d/0x100 acpi_ns_get_node+0x27/0x60 acpi_ns_evaluate+0x1cb/0x2d0 acpi_rs_set_srs_method_data+0x156/0x190 acpi_pci_link_set+0x11c/0x290 irqrouter_resume+0x54/0x60 syscore_resume+0x6a/0x200 kernel_kexec+0x145/0x1c0 __do_sys_reboot+0xeb/0x240 do_syscall_64+0x95/0x180 This is a long standing problem, which probably got more visible with the recent printk changes. Something does a task wakeup and the scheduler sets the NEED_RESCHED flag. cond_resched() sees it set and invokes schedule() from a completely bogus context. The scheduler enables interrupts after context switching, which causes the above warning at the end. Quite some of the code paths in syscore_suspend()/resume() can result in triggering a wakeup with the exactly same consequences. They might not have done so yet, but as they share a lot of code with normal operations it's just a question of time. The problem only affects the PREEMPT_NONE and PREEMPT_VOLUNTARY scheduling models. Full preemption is not affected as cond_resched() is disabled and the preemption check preemptible() takes the interrupt disabled flag into account. Cure the problem by adding a corresponding check into cond_resched().

CVSS Metrics

  • v3.1•MEDIUM•Score: 5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

EPSS Trends

Current EPSS score: 0.21%• Percentile: 12%

Affected Systems

  • debian•linux

    < 5.10.237-1 | < 6.1.133-1 | < 6.12.19-1 | < 6.12.19-1

  • debian•linux-6.1

    < 6.1.137-1~deb11u1

  • ubuntu•linux

    all | < 5.4.0-216.236 | < 5.15.0-140.150 | < 6.8.0-84.84

  • ubuntu•linux-allwinner-5.19

    all

  • ubuntu•linux-aws

    all | < 5.4.0-1146.156 | < 5.15.0-1084.91 | < 6.8.0-1039.41

  • ubuntu•linux-aws-5.0

    all

  • ubuntu•linux-aws-5.11

    all

  • ubuntu•linux-aws-5.13

    all

  • ubuntu•linux-aws-5.15

    < 5.15.0-1084.91~20.04.1

  • ubuntu•linux-aws-5.19

    all

  • ubuntu•linux-aws-5.3

    all

  • ubuntu•linux-aws-5.4

    < 5.4.0-1146.156~18.04.1

  • ubuntu•linux-aws-5.8

    all

  • ubuntu•linux-aws-6.2

    all

  • ubuntu•linux-aws-6.5

    all

  • ubuntu•linux-aws-6.8

    < 6.8.0-1039.41~22.04.1

  • ubuntu•linux-aws-fips

    all | < 5.4.0-1146.156+fips1 | < 5.15.0-1084.91+fips1 | < 6.8.0-1039.41+fips1

  • ubuntu•linux-aws-hwe

    all

  • ubuntu•linux-azure

    all | all | < 5.4.0-1151.158 | < 5.15.0-1089.98 | < 6.8.0-1038.44

  • ubuntu•linux-azure-4.15

    all

  • ubuntu•linux-azure-5.11

    all

  • ubuntu•linux-azure-5.13

    all

  • ubuntu•linux-azure-5.15

    < 5.15.0-1089.98~20.04.1

  • ubuntu•linux-azure-5.19

    all

  • ubuntu•linux-azure-5.3

    all

  • ubuntu•linux-azure-5.4

    < 5.4.0-1151.158~18.04.1

  • ubuntu•linux-azure-5.8

    all

  • ubuntu•linux-azure-6.11

    < 6.11.0-1015.15~24.04.1

  • ubuntu•linux-azure-6.2

    all

  • ubuntu•linux-azure-6.5

    all

  • ubuntu•linux-azure-6.8

    < 6.8.0-1036.42~22.04.1

  • ubuntu•linux-azure-edge

    all

  • ubuntu•linux-azure-fde

    all | all

  • ubuntu•linux-azure-fde-5.15

    < 5.15.0-1114.123~20.04.1

  • ubuntu•linux-azure-fde-5.19

    all

  • ubuntu•linux-azure-fde-6.2

    all

  • ubuntu•linux-azure-fips

    all | < 5.4.0-1151.158+fips1 | < 5.15.0-1089.98+fips1 | < 6.8.0-1040.46+fips1

  • ubuntu•linux-azure-nvidia

    < 6.8.0-1025.27

  • ubuntu•linux-bluefield

    all | < 5.4.0-1105.112 | < 5.15.0-1066.68

  • ubuntu•linux-fips

    all | < 5.4.0-1120.130 | < 5.15.0-140.150+fips1 | < 6.8.0-84.84+fips1

  • ubuntu•linux-gcp

    all | all | < 5.4.0-1149.158 | < 5.15.0-1083.92 | < 6.8.0-1040.42

  • ubuntu•linux-gcp-4.15

    all

  • ubuntu•linux-gcp-5.11

    all

  • ubuntu•linux-gcp-5.13

    all

  • ubuntu•linux-gcp-5.15

    < 5.15.0-1083.92~20.04.1

  • ubuntu•linux-gcp-5.19

    all

  • ubuntu•linux-gcp-5.3

    all

  • ubuntu•linux-gcp-5.4

    < 5.4.0-1149.158~18.04.1

  • ubuntu•linux-gcp-5.8

    all

  • ubuntu•linux-gcp-6.11

    < 6.11.0-1015.15~24.04.1

Showing first 50 affected entries in server-rendered view.

References (61)