CVE-2026-23274

HIGHPre-NVD 7.87.8
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-03-20. NVD baseline CVSS 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
7.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.8Exploit: NoneExposed: 0

A fix is available — apply it.

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.

CVSS v3
7.8
EG Score
7.8(medium)
EPSS
2.9%
KEV
Not listed

Published

March 20, 2026

Last Modified

July 14, 2026

Advisory Details (8)

Auto-updated Jun 10, 2026
No patch confirmed yet.
generic

netfilter: xt_IDLETIMER: reject rev0 reuse of ALARM timer labels - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/f5ef97c13165542480a6ffdbe6f09f40bbb7cbf1
generic

netfilter: xt_IDLETIMER: reject rev0 reuse of ALARM timer labels - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/f228b9ae2a7e84d1153616d8e71c4236cb1f1309
generic

netfilter: xt_IDLETIMER: reject rev0 reuse of ALARM timer labels - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5e7ece24c5cb75a60402aad4d803c7898ea40aa9
generic

netfilter: xt_IDLETIMER: reject rev0 reuse of ALARM timer labels - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/54080355999381fed4a26129579a5765bab87491
generic

netfilter: xt_IDLETIMER: reject rev0 reuse of ALARM timer labels - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/32e937dc6e97f5ed3cdfe3fc0b2b19a05e23fa44
generic

netfilter: xt_IDLETIMER: reject rev0 reuse of ALARM timer labels - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/329f0b9b48ee6ab59d1ab72fef55fe8c6463a6cf
generic

netfilter: xt_IDLETIMER: reject rev0 reuse of ALARM timer labels - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/28c7cfaf0c0ab17cbd7754092116fd1af45271f9
generic

netfilter: xt_IDLETIMER: reject rev0 reuse of ALARM timer labels - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/144f88054ba0180467356f40895bd660b5dceeec

Patch Availability(19)

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Additional Vendor Advisories

(18)

Data Freshness Timeline

(refreshed 11× in last 7d / 46× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 121 total refreshes for this CVE.

  1. 2026-07-15 16:57 UTCEPSS rescore
  2. 2026-07-15 16:57 UTCEPSS rescore
  3. 2026-07-15 02:00 UTCEPSS rescore
  4. 2026-07-15 02:00 UTCEPSS rescore
  5. 2026-07-13 22:30 UTCEPSS rescore
  6. 2026-07-13 06:13 UTCEPSS rescore
  7. 2026-07-13 06:13 UTCEPSS rescore
  8. 2026-07-12 05:46 UTCEPSS rescore
  9. 2026-07-12 05:46 UTCEPSS rescore
  10. 2026-07-11 08:27 UTCEPSS rescore
  11. 2026-07-09 19:10 UTCEPSS rescore
  12. 2026-07-08 15:15 UTCEPSS rescore
  13. 2026-07-08 15:15 UTCEPSS rescore
  14. 2026-07-07 13:46 UTCEPSS rescore
  15. 2026-07-06 16:27 UTCEPSS rescore
  16. 2026-07-06 16:27 UTCEPSS rescore
  17. 2026-07-05 02:30 UTCEPSS rescore
  18. 2026-07-01 15:06 UTCEPSS rescore
  19. 2026-07-01 15:06 UTCEPSS rescore
  20. 2026-06-30 23:22 UTCEPSS rescore
  21. 2026-06-30 23:22 UTCEPSS rescore
  22. 2026-06-29 14:06 UTCEPSS rescore
  23. 2026-06-29 06:02 UTCOSV refresh
  24. 2026-06-28 14:07 UTCEPSS rescore
  25. 2026-06-28 14:07 UTCEPSS rescore
Show 75 more
  1. 2026-06-28 04:56 UTCEPSS rescore
  2. 2026-06-28 04:56 UTCEPSS rescore
  3. 2026-06-27 03:08 UTCEPSS rescore
  4. 2026-06-25 13:49 UTCEPSS rescore
  5. 2026-06-25 13:49 UTCEPSS rescore
  6. 2026-06-24 14:05 UTCEPSS rescore
  7. 2026-06-24 14:05 UTCEPSS rescore
  8. 2026-06-23 21:33 UTCEPSS rescore
  9. 2026-06-23 21:32 UTCEPSS rescore
  10. 2026-06-22 14:25 UTCEPSS rescore
  11. 2026-06-22 14:25 UTCEPSS rescore
  12. 2026-06-21 14:56 UTCEPSS rescore
  13. 2026-06-21 14:56 UTCEPSS rescore
  14. 2026-06-21 01:59 UTCEPSS rescore
  15. 2026-06-21 01:59 UTCEPSS rescore
  16. 2026-06-19 19:25 UTCEPSS rescore
  17. 2026-06-19 19:25 UTCEPSS rescore
  18. 2026-06-18 17:52 UTCEPSS rescore
  19. 2026-06-17 17:53 UTCEPSS rescore
  20. 2026-06-17 17:53 UTCEPSS rescore
  21. 2026-06-16 17:52 UTCEPSS rescore
  22. 2026-06-15 17:48 UTCEPSS rescore
  23. 2026-06-14 23:18 UTCEPSS rescore
  24. 2026-06-13 23:00 UTCEPSS rescore
  25. 2026-06-13 23:00 UTCEPSS rescore
  26. 2026-06-12 23:12 UTCEPSS rescore
  27. 2026-06-11 23:42 UTCEG score recompute
  28. 2026-06-11 23:42 UTCVendor advisory
  29. 2026-06-11 23:42 UTCGHSA enrichment
  30. 2026-06-11 14:00 UTCEPSS rescore
  31. 2026-06-10 22:18 UTCEPSS rescore
  32. 2026-06-10 18:15 UTCEG score recompute
  33. 2026-06-10 18:15 UTCVendor advisory
  34. 2026-06-10 18:15 UTCGHSA enrichment
  35. 2026-06-10 13:22 UTCEPSS rescore
  36. 2026-06-10 05:42 UTCEG score recompute
  37. 2026-06-10 05:42 UTCVendor advisory
  38. 2026-06-10 05:41 UTCGHSA enrichment
  39. 2026-06-09 16:28 UTCEG score recompute
  40. 2026-06-09 16:28 UTCVendor advisory
  41. 2026-06-09 16:28 UTCGHSA enrichment
  42. 2026-06-08 14:17 UTCEPSS rescore
  43. 2026-06-08 14:17 UTCEPSS rescore
  44. 2026-06-08 02:48 UTCEG score recompute
  45. 2026-06-08 02:48 UTCVendor advisory
  46. 2026-06-08 02:48 UTCGHSA enrichment
  47. 2026-06-07 15:25 UTCEPSS rescore
  48. 2026-06-07 15:24 UTCEPSS rescore
  49. 2026-06-07 14:18 UTCEG score recompute
  50. 2026-06-07 14:18 UTCVendor advisory
  51. 2026-06-07 14:18 UTCGHSA enrichment
  52. 2026-06-06 13:47 UTCEPSS rescore
  53. 2026-06-06 13:47 UTCEPSS rescore
  54. 2026-06-06 13:47 UTCEPSS rescore
  55. 2026-06-05 22:47 UTCEPSS rescore
  56. 2026-06-05 06:10 UTCEPSS rescore
  57. 2026-06-05 06:10 UTCEPSS rescore
  58. 2026-06-04 13:12 UTCEPSS rescore
  59. 2026-06-04 13:12 UTCEPSS rescore
  60. 2026-06-04 13:12 UTCEPSS rescore
  61. 2026-06-02 20:13 UTCEPSS rescore
  62. 2026-06-02 20:13 UTCEPSS rescore
  63. 2026-06-01 13:51 UTCEPSS rescore
  64. 2026-06-01 13:51 UTCEPSS rescore
  65. 2026-06-01 13:51 UTCEPSS rescore
  66. 2026-06-01 08:43 UTCOSV refresh
  67. 2026-05-31 22:30 UTCEPSS rescore
  68. 2026-05-31 22:30 UTCEPSS rescore
  69. 2026-05-31 00:16 UTCEPSS rescore
  70. 2026-05-31 00:16 UTCEPSS rescore
  71. 2026-05-31 00:16 UTCEPSS rescore
  72. 2026-05-29 13:44 UTCEPSS rescore
  73. 2026-05-29 13:44 UTCEPSS rescore
  74. 2026-05-28 13:44 UTCEPSS rescore
  75. 2026-05-28 13:44 UTCEPSS rescore

Frequently asked(5)

What is CVE-2026-23274?
CVE-2026-23274 is a high vulnerability published on March 20, 2026. 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…
When was CVE-2026-23274 disclosed?
CVE-2026-23274 was first published in the National Vulnerability Database on March 20, 2026, with the most recent update on July 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-23274 actively exploited?
CVE-2026-23274 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-23274?
CVE-2026-23274 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-23274?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-23274, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-23274

Explore →

Is Your Infrastructure Affected by CVE-2026-23274?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.