Skip to main content

Linux Kernel EUVDEUVD-2026-25467

| CVE-2026-31574 MEDIUM
2026-04-24 Linux GHSA-w5vp-hvm6-339g
Information Disclosure Linux
5.5
CVSS 3.1 · NVD
Share

Severity by source

NVD PRIMARY
5.5 MEDIUM
AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
vuln.today AI
5.5 MEDIUM

Local-only trigger via kernel timer subsystem events; low-privilege sufficient; no confidentiality or integrity impact - purely availability degradation through stall.

3.1 AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
4.0 AV:L/AC:L/AT:P/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
SUSE
MEDIUM
qualitative
Red Hat
5.5 MEDIUM
qualitative

Primary rating from NVD.

CVSS VectorNVD

Attack Vector
Local
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

Lifecycle Timeline

6
Analysis Generated
Jul 24, 2026 - 03:06 vuln.today
CVSS changed
Apr 27, 2026 - 20:37 NVD
5.5 (MEDIUM)
Patch released
Apr 27, 2026 - 20:34 nvd
Patch available
Patch available
Apr 24, 2026 - 16:16 EUVD
EUVD ID Assigned
Apr 24, 2026 - 15:00 euvd
EUVD-2026-25467
CVE Published
Apr 24, 2026 - 14:42 nvd
MEDIUM 5.5

DescriptionCVE.org

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

clockevents: Add missing resets of the next_event_forced flag

The prevention mechanism against timer interrupt starvation missed to reset the next_event_forced flag in a couple of places:

  • When the clock event state changes. That can cause the flag to be

stale over a shutdown/startup sequence

  • When a non-forced event is armed, which then prevents rearming before

that event. If that event is far out in the future this will cause missed timer interrupts.

  • In the suspend wakeup handler.

That led to stalls which have been reported by several people.

Add the missing resets, which fixes the problems for the reporters.

AnalysisAI

Timer interrupt starvation in the Linux kernel clockevents subsystem results from the next_event_forced flag not being reset across three distinct code paths: clock event state transitions (shutdown/startup), non-forced event arming when a far-future event follows, and the suspend wakeup handler. This stale flag prevents timer rearming and causes system stalls, confirmed by multiple user reports. The vulnerability carries a CVSS 5.5 (Medium) score, is not listed in CISA KEV, and EPSS rates it at 0.02% (5th percentile), placing it firmly in the reliability-defect category rather than active exploitation risk. Patch commit 9401b593fa48218d2667df1610b0ebc518554880 is available in Linux 7.0.1.

Technical ContextAI

The Linux kernel clockevents framework abstracts hardware timer devices and manages the scheduling of timer interrupts across CPUs. The next_event_forced flag is a starvation-prevention sentinel that signals whether the next timer event was force-armed to avoid missed interrupts. The defect is a state-management error: the flag is set in certain paths but never cleared during clock event device state transitions (e.g., shutdown followed by startup), when a non-forced event is successfully programmed after a forced one, or upon resume from suspend. A stale true value then suppresses rearming logic that would otherwise fire, leading to missed timer interrupts and subsequent CPU stalls. While no formal CWE is assigned, the root cause class is improper lifecycle management of a boolean state flag - conceptually aligned with CWE-664 (Improper Control of a Resource Through its Lifetime). The CPE cpe:2.3:a:linux:linux:* identifies the upstream Linux kernel as the affected artifact, with the bug present from the initial codebase commit (1da177e4c3f41524e886b7f1b8a0c1fc7321cac2) through the fix commit (9401b593fa48218d2667df1610b0ebc518554880).

RemediationAI

The primary remediation is to upgrade to Linux kernel 7.0.1 or apply fix commit 9401b593fa48218d2667df1610b0ebc518554880 directly from the upstream stable tree at https://git.kernel.org/stable/c/9401b593fa48218d2667df1610b0ebc518554880. A second stable fix is available at https://git.kernel.org/stable/c/4096fd0e8eeba13ebe5206700b33f49635ae18e5. Ubuntu users should apply the patches referenced in USN-8488-1 via their standard package manager. Where immediate patching is not feasible, reducing suspend/resume cycles and avoiding dynamic clock event device reconfiguration (e.g., CPU hotplug scenarios that trigger shutdown/startup of timer devices) may reduce the frequency of stall occurrences - these are operational mitigations only and do not eliminate the defect. No network-layer controls are applicable given the entirely local nature of the vulnerability.

Same technique Information Disclosure

View all
CVE-2019-2725 CRITICAL POC
9.8
CVE-2021-34523 CRITICAL POC
9.0
CVE-2013-2251 CRITICAL POC
9.8
CVE-2017-5638 CRITICAL POC
9.8
CVE-2025-24813 CRITICAL POC
9.8
CVE-2015-1701 HIGH POC
7.8
CVE-2017-0147 HIGH POC
7.5
CVE-2014-6324 HIGH POC
8.8

Vendor StatusVendor

SUSE

Severity: Medium
Product Status
SUSE Linux Enterprise Desktop 15 SP7 Fixed
SUSE Linux Enterprise Desktop 15 SP7 Fixed
SUSE Linux Enterprise High Availability Extension 15 SP7 Fixed
SUSE Linux Enterprise High Availability Extension 15 SP7 Fixed
SUSE Linux Enterprise High Performance Computing 15 SP7 Fixed

Share

EUVD-2026-25467 vulnerability details – vuln.today
Back

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy