FlawAtlas
Search the atlas
CVE-2026-23274 Not scored

netfilter: xt_IDLETIMER: reject rev0 reuse of ALARM timer labels

In the Linux kernel, the following vulnerability has been resolved: netfilter: xt_IDLETIMER: reject rev0 reuse of ALARM timer labels IDLETIMER revision 0 rules reuse existing timers by label and always call mod_timer() on timer->timer. If the label was created first by revision 1 with XT_IDLETIMER_ALARM, the object uses alarm timer semantics and timer->timer is never initialized. Reusing that object from revision 0 causes mod_timer() on an uninitialized timer_list, triggering debugobjects warnings and possible panic when panic_on_warn=1. Fix this by rejecting revision 0 rule insertion when an existing timer with the same label is of ALARM type.

Exploit probability 0.1%
Published March 20, 2026
Required by Not available
Last source change July 16, 2026

02 / AFFECTED SOFTWARE

Affected packages

Linux Kernel
Unknown Unknown

03 / CONNECTIONS

Connected vulnerabilities

related OPENSUSE-SU-2026:20572-1
related SUSE-SU-2026:1342-1
related SUSE-SU-2026:1557-1
related SUSE-SU-2026:1563-1
related SUSE-SU-2026:1573-1
related SUSE-SU-2026:1574-1
related SUSE-SU-2026:1575-1
related SUSE-SU-2026:1606-1
related SUSE-SU-2026:1643-1
related SUSE-SU-2026:1661-1
related SUSE-SU-2026:21114-1
related SUSE-SU-2026:21123-1
related SUSE-SU-2026:21237-1
related SUSE-SU-2026:21255-1
related SUSE-SU-2026:2131-1
related SUSE-SU-2026:2134-1
related SUSE-SU-2026:21352-1
related SUSE-SU-2026:21361-1
related SUSE-SU-2026:2141-1
related SUSE-SU-2026:2149-1
related SUSE-SU-2026:2158-1
related SUSE-SU-2026:2159-1
related SUSE-SU-2026:2172-1
related SUSE-SU-2026:2176-1
related SUSE-SU-2026:2181-1
related SUSE-SU-2026:2189-1
related SUSE-SU-2026:2199-1

04 / EVIDENCE

Source records

Open Source Vulnerabilities CVE-2026-23274

In the Linux kernel, the following vulnerability has been resolved: netfilter: xt_IDLETIMER: reject rev0 reuse of ALARM timer labels IDLETIMER revision 0 rules reuse existing timers by label and always call mod_timer() on timer->timer. If the label was created first by revision 1 with XT_IDLETIMER_ALARM, the object uses alarm timer semantics and timer->timer is never initialized. Reusing that object from revision 0 causes mod_timer() on an uninitialized timer_list, triggering debugobjects warnings and possible panic when panic_on_warn=1. Fix this by rejecting revision 0 rule insertion when an existing timer with the same label is of ALARM type.

View original source

05 / REFERENCES

Further evidence