CVE-2026-64246

HIGHNVD 7.87.8
EchelonGraph scoreMEDIUM confidence

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

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

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 3 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.1%CVSS: 7.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

power: reset: linkstation-poweroff: fix use-after-free in the linkstation_poweroff_init()

Move of_node_put(dn) after the of_match_node() call, which still needs the node pointer. The node reference is correctly released after use.

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 intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity78% × 45%
The EG Score, 7.8 of 10.
Exploitation0.1% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's BOD 26-04 default: no one has published Automatable for this CVE, and CISA treats it as “no” for a CVE not in KEV.
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from 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.1%
EPSS %ILE
1st
KEV
Not listed

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 (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from 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's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” 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

July 24, 2026

Last Modified

August 17, 2026

Advisory Details (7)

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

power: reset: linkstation-poweroff: fix use-after-free in the linkstation_poweroff_init() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/d109e72f3fbccb540473285d17d7519584f7f76e
Web page

power: reset: linkstation-poweroff: fix use-after-free in the linkstation_poweroff_init() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/cdda7d384c05485a232ae9a849f6445accb095bf
Web page

power: reset: linkstation-poweroff: fix use-after-free in the linkstation_poweroff_init() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/c04d606f8b35ee7d3ed243f63893a607e9d6c0bc
Web page

power: reset: linkstation-poweroff: fix use-after-free in the linkstation_poweroff_init() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/93c7ee139721936b6fa717572e74d3994603ae13
Web page

power: reset: linkstation-poweroff: fix use-after-free in the linkstation_poweroff_init() - kernel/git/stable/linux.git - Linux kernel stable tree

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

power: reset: linkstation-poweroff: fix use-after-free in the linkstation_poweroff_init() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3928ae803dee044b01076c478c279c0bd54164cd
Web page

power: reset: linkstation-poweroff: fix use-after-free in the linkstation_poweroff_init() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2205275be9be981e70ff29610b0117d8853fac70

Patch Availability(11)

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

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
linux-6.16.1.106-3~deb11u1 ... 6.1.176-1~deb11u1 (21 versions)
  • every version up to 6.1.177-1~deb11u1: fixed in 6.1.177-1~deb11u1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 6.1.99-1 (54 versions)
  • every version up to 6.1.177-1: fixed in 6.1.177-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.38-1 ... 6.12.95-1~bpo12+1 (29 versions)
  • every version up to 6.12.95-1: fixed in 6.12.95-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.1~rc7-1~exp1 (157 versions)
  • every version up to 7.1.3-1: fixed in 7.1.3-1
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(11)

Data Freshness Timeline

(refreshed 13× in last 7d / 70× 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 214 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 114 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-64246?
CVE-2026-64246 is a high-severity vulnerability; its CVE record was published on July 24, 2026. In the Linux kernel, the following vulnerability has been resolved: power: reset: linkstation-poweroff: fix use-after-free in the linkstationpoweroffinit() Move ofnodeput(dn) after the ofmatchnode() call, which still needs the node pointer. The node reference is correctly released after use.
When was the CVE record for CVE-2026-64246 published?
The CVE record for CVE-2026-64246 was published on July 24, 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 August 17, 2026; the record at its source may have been updated since.
Is CVE-2026-64246 actively exploited?
CVE-2026-64246 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (1st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-64246?
CVE-2026-64246 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-64246?
A fix for CVE-2026-64246 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-64246 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-64246

Explore →

Is Your Infrastructure Affected by CVE-2026-64246?

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