Answer in brief
CVE-2026-64084 records a Unknown severity vulnerability in hwmon: (pmbus/adm1266) cap PDIO scan in get_multiple at ADM1266_PDIO_NR. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
Answer in brief
CVE-2026-64084 records a Unknown severity vulnerability in hwmon: (pmbus/adm1266) cap PDIO scan in get_multiple at ADM1266_PDIO_NR. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=d98dfad35c38c037b37c4adc99df01da571031a5 <d0593e15fdeb56048a72c5c6e720f702759d0ccd || >=d98dfad35c38c037b37c4adc99df01da571031a5 <17cee2f59029039416e8f6303050038eb59ba149 || >=d98dfad35c38c037b37c4adc99df01da571031a5 <299efd14c2eda7e5fd40025e54addd4151a01081 || >=d98dfad35c38c037b37c4adc99df01da571031a5 <4d1da9a6be5a8156c532d571c2ed237169f99244 || >=d98dfad35c38c037b37c4adc99df01da571031a5 <b96c7f0bc0713dc6403912f6527d4ff9168d6fe6 || >=d98dfad35c38c037b37c4adc99df01da571031a5 <fa7ca363069a70b0d1aa51e8892e3095fe2ac1ec || >=d98dfad35c38c037b37c4adc99df01da571031a5 <2aef8f08c479f4cbc83e1e6b19d1c94d4dd24f17 || >=d98dfad35c38c037b37c4adc99df01da571031a5 <d7834d92251baade796812876e95555e2066fa9f | d0593e15fdeb56048a72c5c6e720f702759d0ccd, 17cee2f59029039416e8f6303050038eb59ba149, 299efd14c2eda7e5fd40025e54addd4151a01081, 4d1da9a6be5a8156c532d571c2ed237169f99244, b96c7f0bc0713dc6403912f6527d4ff9168d6fe6, fa7ca363069a70b0d1aa51e8892e3095fe2ac1ec, 2aef8f08c479f4cbc83e1e6b19d1c94d4dd24f17, d7834d92251baade796812876e95555e2066fa9f |
| Linux/Linuxgeneric | 5.10 | Not reported |
Published upstream
Jul 19, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
In the Linux kernel, the following vulnerability has been resolved: hwmon: (pmbus/adm1266) cap PDIO scan in get_multiple at ADM1266_PDIO_NR adm1266_gpio_get_multiple() iterates the PDIO portion of the caller-supplied mask using for_each_set_bit_from(gpio_nr, mask, ADM1266_GPIO_NR + ADM1266_PDIO_STATUS) { ... } where ADM1266_PDIO_STATUS is the PMBus command code (0xE9, i.e. 233), not the number of PDIO pins. The intended upper bound is ADM1266_GPIO_NR + ADM1266_PDIO_NR = 25. gpiolib hands in a mask sized for gc.ngpio (= 25 bits on this chip), so the iteration walks find_next_bit() up to 242, reading up to 217 extra bits (a handful of unsigned-long words: four on 64-bit, seven on 32-bit) of whatever lives past the end of the mask in the caller's stack. Any incidental set bit in that range then drives a set_bit(gpio_nr, bits) call that writes past the end of the caller-supplied bits array too -- both out-of-bounds. Substitute ADM1266_PDIO_NR for the constant so the scan stops at the last real PDIO bit.
Quoted source text, attributed separately from HOL analysis.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=d98dfad35c38c037b37c4adc99df01da571031a5 <d0593e15fdeb56048a72c5c6e720f702759d0ccd || >=d98dfad35c38c037b37c4adc99df01da571031a5 <17cee2f59029039416e8f6303050038eb59ba149 || >=d98dfad35c38c037b37c4adc99df01da571031a5 <299efd14c2eda7e5fd40025e54addd4151a01081 || >=d98dfad35c38c037b37c4adc99df01da571031a5 <4d1da9a6be5a8156c532d571c2ed237169f99244 || >=d98dfad35c38c037b37c4adc99df01da571031a5 <b96c7f0bc0713dc6403912f6527d4ff9168d6fe6 || >=d98dfad35c38c037b37c4adc99df01da571031a5 <fa7ca363069a70b0d1aa51e8892e3095fe2ac1ec || >=d98dfad35c38c037b37c4adc99df01da571031a5 <2aef8f08c479f4cbc83e1e6b19d1c94d4dd24f17 || >=d98dfad35c38c037b37c4adc99df01da571031a5 <d7834d92251baade796812876e95555e2066fa9f | d0593e15fdeb56048a72c5c6e720f702759d0ccd, 17cee2f59029039416e8f6303050038eb59ba149, 299efd14c2eda7e5fd40025e54addd4151a01081, 4d1da9a6be5a8156c532d571c2ed237169f99244, b96c7f0bc0713dc6403912f6527d4ff9168d6fe6, fa7ca363069a70b0d1aa51e8892e3095fe2ac1ec, 2aef8f08c479f4cbc83e1e6b19d1c94d4dd24f17, d7834d92251baade796812876e95555e2066fa9f |
| Linux/Linuxgeneric | 5.10 | Not reported |
Published upstream
Jul 19, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
In the Linux kernel, the following vulnerability has been resolved: hwmon: (pmbus/adm1266) cap PDIO scan in get_multiple at ADM1266_PDIO_NR adm1266_gpio_get_multiple() iterates the PDIO portion of the caller-supplied mask using for_each_set_bit_from(gpio_nr, mask, ADM1266_GPIO_NR + ADM1266_PDIO_STATUS) { ... } where ADM1266_PDIO_STATUS is the PMBus command code (0xE9, i.e. 233), not the number of PDIO pins. The intended upper bound is ADM1266_GPIO_NR + ADM1266_PDIO_NR = 25. gpiolib hands in a mask sized for gc.ngpio (= 25 bits on this chip), so the iteration walks find_next_bit() up to 242, reading up to 217 extra bits (a handful of unsigned-long words: four on 64-bit, seven on 32-bit) of whatever lives past the end of the mask in the caller's stack. Any incidental set bit in that range then drives a set_bit(gpio_nr, bits) call that writes past the end of the caller-supplied bits array too -- both out-of-bounds. Substitute ADM1266_PDIO_NR for the constant so the scan stops at the last real PDIO bit.
Quoted source text, attributed separately from HOL analysis.