# CVE-2026-31574: clockevents: Add missing resets of the next_event_forced flag

> A missing flag reset in the Linux kernel clockevents subsystem can cause timer interrupt starvation, leading to system stalls and denial of service.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 24 Apr 2026
- **Updated:** 14 Jun 2026
- **Also known as:** GHSA-w5vp-hvm6-339g, ROOT-OS-DEBIAN-11-CVE-2026-31574, ROOT-OS-DEBIAN-12-CVE-2026-31574, ROOT-OS-DEBIAN-13-CVE-2026-31574, UBUNTU-CVE-2026-31574

## What is CVE-2026-31574?

CVE-2026-31574 is a medium-severity denial of service vulnerability in Linux kernel, published on 24 Apr 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

## Which versions are affected by CVE-2026-31574?

It affects 1 product.


Products: Linux kernel.

## How do I fix CVE-2026-31574?

Apply the vendor's patch.

## Is CVE-2026-31574 being exploited?

There is no known exploitation of CVE-2026-31574 in the wild and no public exploit code.

## Other vulnerabilities in Linux kernel

- [CVE-2026-53266](https://insights.sbomify.com/CVE-2026-53266/): Linux Kernel Out-of-Bounds Write (high 8.8, exploited in the wild)
- [CVE-2013-6282](https://insights.sbomify.com/CVE-2013-6282/): Linux Kernel Improper Input Validation (high 8.8, exploited in the wild)
- [CVE-2022-0185](https://insights.sbomify.com/CVE-2022-0185/): Linux Kernel Heap-Based Buffer Overflow (high 8.4, exploited in the wild)
- [CVE-2013-2094](https://insights.sbomify.com/CVE-2013-2094/): Linux Kernel Privilege Escalation (high 8.4, exploited in the wild)
- [CVE-2026-53362](https://insights.sbomify.com/CVE-2026-53362/): Linux Kernel Unspecified (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-31574 and fix it if it is affected.

What it is: CVE-2026-31574 is a medium-severity denial of service vulnerability in Linux kernel, published on 24 Apr 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-31574 in the wild and no public exploit code.

Affected product: Linux kernel. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-31574/ (Markdown: https://insights.sbomify.com/CVE-2026-31574/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-31574
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-31574
- OSV: https://osv.dev/vulnerability/CVE-2026-31574

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-31574/
Summaries are generated and may contain mistakes; the official description above is the record.