CVE-2026-64502

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-07-25. 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

Also known asEUVD-2026-48846 (ENISA EUVD) · GHSA-2vpq-89rm-wm52 (GitHub Security Advisories)Source: ENISA EUVD

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:

iio: adc: ad_sigma_delta: fix clear_pending_event for registerless devices

ad_sigma_delta_clear_pending_event() falls through to the status register read path for devices with has_registers = false and no rdy_gpiod. For such devices, ad_sd_read_reg() skips the address byte entirely and clocks raw MISO bytes with no address phase — making it byte-for-byte identical to reading conversion data. If a pending conversion result is present, this partially consumes it and corrupts the data stream for the subsequent ad_sd_read_reg() call in ad_sigma_delta_single_conversion().

Furthermore, with num_resetclks = 0 on these devices, data_read_len evaluates to 0. If the clocked byte has bit 7 clear, pending_event is set and the code attempts memset(data + 2, 0xff, 0 - 1), overflowing to SIZE_MAX and corrupting the heap.

Fix by returning 0 immediately when neither rdy_gpiod nor has_registers is set. This is safe for all current registerless devices: ad7191 and ad7780 (with powerdown GPIO) are reset between conversions by CS deassertion, so there is no stale result to drain; ad7780 (without powerdown GPIO) and max11205 are continuously-converting and cycle ~DRDY at the output data rate regardless of whether the previous result was read, so the next falling edge fires naturally.

A future registerless device that holds ~DRDY asserted until data is read would be broken by this early return and would require either num_resetclks set or a rdy-gpio.

The same heap corruption is reachable on any device with rdy_gpiod set but num_resetclks = 0: if the GPIO indicates a pending event, the drain path executes memset(data + 2, 0xff, 0 - 1) regardless of has_registers. Add an explicit data_read_len == 0 guard after the pending event check; the stale result is then consumed by the first ad_sd_read_reg() call in ad_sigma_delta_single_conversion().

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 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.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-11-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, and whom BOD 26-04 binds: 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 (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.

The score's inputs: 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 25, 2026

Last Modified

November 18, 2026

Advisory Details (3)

Auto-updated Jul 27, 2026
Patch available.
Web page

iio: adc: ad_sigma_delta: fix clear_pending_event for registerless devices - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/91bc6767a4f55dc470d8a56b55b9f2ea09094efe
Web page

iio: adc: ad_sigma_delta: fix clear_pending_event for registerless devices - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3bceb26dfaf7ba805b459e41c1d0ba916862dade
Web page

iio: adc: ad_sigma_delta: fix clear_pending_event for registerless devices - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3394e0b3328422431cadaf314fa58d3717ed4936

Vendor Advisories for CVE-2026-64502(1)

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

Patch Availability(12)

These rows come from Ubuntu and OSV. Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.1~rc7-1~exp1 (162 versions)
  • every version up to 7.1.4-1: fixed in 7.1.4-1
—

Weakness Classification(1)

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

All Vendor Advisories

(11)

Data Freshness Timeline

(refreshed 11× in last 7d / 38× 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 its CVE.org record (CNA or CISA ADP). 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 332 rows 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 232 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-64502?
CVE-2026-64502 is a high-severity vulnerability; its CVE record was published on July 25, 2026. In the Linux kernel, the following vulnerability has been resolved: iio: adc: ad_sigma_delta: fix clear_pending_event for registerless devices ad_sigma_delta_clear_pending_event() falls through to the status register read path for devices with has_registers = false and no rdy_gpiod. For such…
When was the CVE record for CVE-2026-64502 published?
The CVE record for CVE-2026-64502 was published on July 25, 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 November 18, 2026; the record at its source may have been updated since.
Is CVE-2026-64502 actively exploited?
CVE-2026-64502 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-64502?
CVE-2026-64502 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-64502?
A fix for CVE-2026-64502 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-64502 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-64502

Explore →

Is Your Infrastructure Affected by CVE-2026-64502?

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