Access of Uninitialized Pointer Affecting kernel-zfcpdump package, versions *
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-CENTOS10-KERNELZFCPDUMP-18047293
- published21 Jul 2026
- disclosed19 Jul 2026
Introduced: 19 Jul 2026
NewCVE-2026-64083 (opens in a new tab)How to fix?
There is no fixed version for Centos:10 kernel-zfcpdump.
NVD Description
Note: Versions mentioned in the description apply only to the upstream kernel-zfcpdump package and not the kernel-zfcpdump package as distributed by Centos.
See How to fix? for Centos:10 relevant fixed versions and status.
In the Linux kernel, the following vulnerability has been resolved:
hwmon: (pmbus/adm1266) reject short block-read responses in the GPIO accessors
adm1266_gpio_get() and adm1266_gpio_get_multiple() both compose the pin-status word as
pins_status = read_buf[0] + (read_buf[1] << 8);
right after i2c_smbus_read_block_data(), guarding only against an error return. A well-behaved device returns 2 bytes for GPIO_STATUS/PDIO_STATUS, but the helper happily reports a 0- or 1-byte response too. If the device returns 0 bytes, both read_buf slots are uninitialized stack memory; if it returns 1 byte, read_buf[1] is.
The composed value then flows through set_bit() into the caller's *bits in adm1266_gpio_get_multiple(), or into the return value of adm1266_gpio_get(), and ends up in userspace via gpiolib (sysfs and the char-dev ioctls). That leaks a few bits of kernel stack per request on any device whose firmware glitch, bus error, or hostile slave produces a short block-read response.
Add the missing length check to both call sites and surface a short response as -EIO.
References
- https://bugzilla.redhat.com/show_bug.cgi?id=2502528
- https://access.redhat.com/security/cve/CVE-2026-64083
- https://git.kernel.org/stable/c/64fa9328948ddcc0f7f3c23ea1756c126d9dffac
- https://git.kernel.org/stable/c/a2d1c819348b36fccbbfcf37c5fa7a50a9b4528f
- https://git.kernel.org/stable/c/a7232f68c43ca62f545049b7f5fbfc75137b843b
- https://git.kernel.org/stable/c/ae25cf2ea9ebd06d7ad416647dbdc7b5d0172946
- https://git.kernel.org/stable/c/c603b6c6840ac0c6285f5eefea0de6242710af21
- https://git.kernel.org/stable/c/eb3cd9bb590460c6127145cb245be925d23f5232
- https://git.kernel.org/stable/c/ee4799becf7d2af3778007e22c2e55c4009a49c7
- https://git.kernel.org/stable/c/fd9196aad9e5a3845cea17de3405ebc700382142