CVE-2026-74264

HIGHPre-NVD 7.87.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-08-15. A secondary CVSS source baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 4 sources updated this week
7.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 7.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

net: watchdog: fix refcount tracking races

Blamed commit converted the untracked dev_hold()/dev_put() calls in the watchdog code to use the tracked dev_hold_track()/dev_put_track() (which were later renamed/interfaced to netdev_hold() and netdev_put()).

By introducing dev->watchdog_dev_tracker to store the reference tracking information without adding synchronization between netdev_watchdog_up() and dev_watchdog(), it enabled the race condition where this pointer could be overwritten or freed concurrently, leading to the list corruption crash syzbot reported:

list_del corruption, ffff888114a18c00->next is NULL kernel BUG at lib/list_debug.c:52 ! Oops: invalid opcode: 0000 [#1] SMP KASAN PTI CPU: 1 UID: 0 PID: 91 Comm: kworker/u8:5 Not tainted syzkaller #0 PREEMPT(lazy) Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/09/2026 Workqueue: events_unbound linkwatch_event RIP: 0010:__list_del_entry_valid_or_report.cold+0x22/0x2a lib/list_debug.c:52 Call Trace: __list_del_entry_valid include/linux/list.h:132 [inline] __list_del_entry include/linux/list.h:246 [inline] list_move_tail include/linux/list.h:341 [inline] ref_tracker_free+0x1a7/0x6c0 lib/ref_tracker.c:329 netdev_tracker_free include/linux/netdevice.h:4491 [inline] netdev_put include/linux/netdevice.h:4508 [inline] netdev_put include/linux/netdevice.h:4504 [inline] netdev_watchdog_down net/sched/sch_generic.c:600 [inline] dev_deactivate_many+0x28c/0xfe0 net/sched/sch_generic.c:1363 dev_deactivate+0x109/0x1d0 net/sched/sch_generic.c:1397 linkwatch_do_dev net/core/link_watch.c:184 [inline] linkwatch_do_dev+0xd3/0x120 net/core/link_watch.c:166 __linkwatch_run_queue+0x3a5/0x810 net/core/link_watch.c:240 linkwatch_event+0x8f/0xc0 net/core/link_watch.c:314 process_one_work+0xa0e/0x1980 kernel/workqueue.c:3314 process_scheduled_works kernel/workqueue.c:3397 [inline] worker_thread+0x5ef/0xe50 kernel/workqueue.c:3478 kthread+0x370/0x450 kernel/kthread.c:436 ret_from_fork+0x69a/0xc80 arch/x86/kernel/process.c:158 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245

This patch has three coordinated parts:

1) Add dev->watchdog_lock and dev->watchdog_ref_held to serialize watchdog operations.

2) Remove netdev_watchdog_up() call from netif_carrier_on(): This ensures netdev_watchdog_up() is only called from process/BH context (via linkwatch workqueue dev_activate()), allowing us to use spin_lock_bh() for synchronization.

3) Synchronize watchdog up and watchdog timer: Protect netdev_watchdog_up() with tx_global_lock and watchdog_lock. Only allocate a new tracker in netdev_watchdog_up() if one is not already present. In dev_watchdog(), ensure we don't release the tracker if the timer was rescheduled either by dev_watchdog() itself or concurrently by netdev_watchdog_up().

CVSS v3
7.8
EG Score
7.8HIGHmedium confidence
EG Risk
35
EG Risk 35/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity78% × 45%
Impact severity (EG Severity): CVSS 7.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.2% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.2%
EPSS %ILE
6th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.8): severity, escalated by confirmed exploitation. This CVE's 7.8 is its impact severity (EG Severity), not escalated.

EG Severity
7.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-17). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

August 15, 2026

Last Modified

October 16, 2026

Advisory Details (3)

Auto-updated Aug 17, 2026
Patch available.
Web page

net: watchdog: fix refcount tracking races - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8eed5519e496b7a07f441a0f579cb228a33189f7
Web page

net: watchdog: fix refcount tracking races - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7ce2b00ff058ec4cafc9b447e1f0a6d6f49275d9
Web page

net: watchdog: fix refcount tracking races - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/446fe8ce699ce0a4d702f7b0fcdb50de340b9260

Vendor Advisories for CVE-2026-74264(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(7)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-tools-aws-edge (7.0.0-1014.14~24.04.1) @ noble2026-10-16ubuntu
ubuntulinux-tools-azure-lts-26.04 (7.0.0-1017.17) @ resolute2026-10-16ubuntu
ubuntulinux-tools-oem-7.0 (7.0.0-1015.15) @ resolute2026-10-16ubuntu
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-38.38) @ resolute2026-10-16ubuntu
ubuntulinux-tools-azure-fde-edge (7.0.0-1016.16~24.04.1) @ noble2026-10-16ubuntu
ubuntulinux-virtual-hwe-24.04-edge (7.0.0-38.38~24.04.4) @ noble2026-10-16ubuntu
ubuntulinux-tools-nvidia-tegra-rt-6.8 (6.8.0-1035.38) @ noble2026-10-16ubuntu

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.

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 7.2~rc7-1~exp1 (358 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (181 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.1~rc7-1~exp1 (160 versions)
  • every version up to 7.1.5-1: fixed in 7.1.5-1
—

Additional Vendor Advisories

(7)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 13× in last 7d / 101× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 246 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 146 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same vendor)

Frequently asked(5)

What is CVE-2026-74264?
CVE-2026-74264 is a high-severity vulnerability; its CVE record was published on August 15, 2026. In the Linux kernel, the following vulnerability has been resolved: net: watchdog: fix refcount tracking races Blamed commit converted the untracked devhold()/devput() calls in the watchdog code to use the tracked devholdtrack()/devputtrack() (which were later renamed/interfaced to netdevhold() and…
When was the CVE record for CVE-2026-74264 published?
The CVE record for CVE-2026-74264 was published on August 15, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 16, 2026; the record at its source may have been updated since.
Is CVE-2026-74264 actively exploited?
CVE-2026-74264 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (6th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-74264?
CVE-2026-74264 has a CVSS base score of 7.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-74264?
A fix for CVE-2026-74264 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-74264 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-74264

Explore →

Is Your Infrastructure Affected by CVE-2026-74264?

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

Book a Demo →Browse All CVEs