CVE-2026-23274
Last modified
CVE-2026-23274 is a high-severity vulnerability rated 7.8/10 on the CVSS scale. 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.. EPSS estimates a 0.12% chance of exploitation in the next 30 days.
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.
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Linux | Linux Kernel | >= 5.7, < 5.10.253 | — |
| Linux | Linux Kernel | >= 5.11, < 5.15.203 | — |
| Linux | Linux Kernel | >= 5.16, < 6.1.167 | — |
| Linux | Linux Kernel | >= 6.2, < 6.6.130 | — |
| Linux | Linux Kernel | >= 6.7, < 6.12.78 | — |
| Linux | Linux Kernel | >= 6.13, < 6.18.19 | — |
| Linux | Linux Kernel | >= 6.19, < 6.19.9 | — |
| Linux | Linux Kernel | 7.0 | Rc1 |
References
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2026-23274?
How severe is CVE-2026-23274?
How do I fix CVE-2026-23274?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-23269In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2026-2327Versions of the package markdown-it from 13.0.0 and before 1…7.5
- CVE-2026-23270In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-23271In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-23272In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-23273In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-23275In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-23276In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-23277In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-23278In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-23279In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-2328An unauthenticated remote attacker can exploit insufficient …7.5
Are you affected by CVE-2026-23274?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST