# clockevents: Add missing resets of the next_event_forced flag

CVE record · `CVE-2026-31574`

- **Identifiers:** `CVE-2026-31574`
- **State:** Confirmed
- **Severity:** No CVSS score
- **Critical:** No
- **CNA:** Linux
- **Technologies:** [Linux kernel](https://agentprime.io/advisories/technology/linux-kernel.md)
- **Published:** 24 Apr 2026
- **Updated:** 5 Nov 2026
- **Reviewed by a person:** No

Published by the CVE Program (CNA: Linux) at 24 Apr 2026, 14:42 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it.

## Affected products, as the CNA wrote them

- Vendor: Linux. Product: Linux.
  - affected: `d6e152d905bdb1f32f9d99775e2f453350399a6a to before 9401b593fa48218d2667df1610b0ebc518554880` (git)
  - affected: `d6e152d905bdb1f32f9d99775e2f453350399a6a to before 4096fd0e8eaea13ebe5206700b33f49635ae18e5` (git)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `7.0`
  - unaffected: `before 7.0` (semver)
  - unaffected: `7.0.1 to 7.0.*, inclusive` (semver)
  - unaffected: `7.1 to *, inclusive` (original_commit_for_fix)
  - Other versions: affected

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> CVE-2026-31574 affects the Linux kernel clockevents code from commit d6e152d905bd up to the fixes in 9401b593fa48 and 4096fd0e8eae, and the CNA lists Linux 7.0 as affected, with versions before 7.0 and from 7.0.1 onward unaffected. The source describes a stale next_event_forced flag that can cause missed timer interrupts and system stalls, but it does not describe an attacker's ability to trigger this, so the required access is not stated. The fix is to update to a kernel that includes the referenced patches, such as 7.0.1 or later, and no workaround is given.

Written 17 Nov 2026.

## Not analysed yet

We haven’t published our own analysis of this CVE. If a person reviews it, this page will say what’s affected and what has to be true for it to matter.

## Severity and exploitation

No source has published a CVSS score for this record yet.

- **CISA KEV:** Not listed.
- **EPSS:** 0.0011, the 1st percentile, on 18 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 24 Apr 2026, 14:42 UTC: [Confirmed by the CVE List](https://www.cve.org/CVERecord?id=CVE-2026-31574)
- 24 Apr 2026, 15:16 UTC: [Confirmed by NVD](https://nvd.nist.gov/vuln/detail/CVE-2026-31574)

## Sources

- [CVE List: CVE-2026-31574](https://www.cve.org/CVERecord?id=CVE-2026-31574)
- [NVD: CVE-2026-31574](https://nvd.nist.gov/vuln/detail/CVE-2026-31574)

### References from the CNA

- <https://git.kernel.org/stable/c/9401b593fa48218d2667df1610b0ebc518554880>
- <https://git.kernel.org/stable/c/4096fd0e8eaea13ebe5206700b33f49635ae18e5>

Facts on this page come from the CVE List as the CNA published them, with CVSS from the sources named above, CISA KEV and FIRST EPSS. Vendors, products and versions are shown as the CNA wrote them. We don’t reproduce the CVE’s description.

## Check whether this affects you

This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it. Compare the affected versions above with what you run.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), `get_advisory` returns this record and `search_advisories` finds related ones. Setup: <https://agentprime.io/mcp.md>
- As JSON: <https://api.agentprime.io/v1/advisories/CVE-2026-31574>
- Everything that needs attention now: <https://agentprime.io/advisories/critical.md>

---

The web page: <https://agentprime.io/advisories/CVE-2026-31574/>. Everything for agents: <https://agentprime.io/llms.txt>.
