Home

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.

PUBLISHED Reserved 2026-03-09 | Published 2026-04-24 | Updated 2026-05-11 | Assigner Linux

Product status

Default status
unaffected

d6e152d905bdb1f32f9d99775e2f453350399a6a (git) before 9401b593fa48218d2667df1610b0ebc518554880
affected

d6e152d905bdb1f32f9d99775e2f453350399a6a (git) before 4096fd0e8eaea13ebe5206700b33f49635ae18e5
affected

Default status
affected

7.0
affected

Any version before 7.0
unaffected

7.0.1 (semver)
unaffected

7.1-rc1 (original_commit_for_fix)
unaffected

References

git.kernel.org/...c/9401b593fa48218d2667df1610b0ebc518554880

git.kernel.org/...c/4096fd0e8eaea13ebe5206700b33f49635ae18e5

cve.org (CVE-2026-31574)

nvd.nist.gov (CVE-2026-31574)

Download JSON