UBUNTU-CVE-2026-26399

A stack-use-after-return issue exists in the ArduinoCoreSTM32 library prior to version 1.7.0. The pwmstart function allocates a TIMHandleTypeDef structure on the stack and passes its address to HAL initialization routines, where it is stored in a global timer handle registry. After the function...

CVE-2026-26399

A stack-use-after-return issue exists in the ArduinoCoreSTM32 library prior to version 1.7.0. The pwmstart function allocates a TIMHandleTypeDef structure on the stack and passes its address to HAL initialization routines, where it is stored in a global timer handle registry. After the function...

CVE-2026-26399

Summary of CVE-2026-26399 (Arduino_Core_STM32) : A stack-use-after-return vulnerability exists in the Arduino Core STM32 library for versions prior to 1.7.0. The function pwm_start() allocates a TIM_HandleTypeDef on the stack and passes its address to HAL initialization routines, which store a re...

CVE-2026-26399

A stack-use-after-return issue exists in the ArduinoCoreSTM32 library prior to version 1.7.0. The pwmstart function allocates a TIMHandleTypeDef structure on the stack and passes its address to HAL initialization routines, where it is stored in a global timer handle registry. After the function...

CVE-2026-26399

A stack-use-after-return issue exists in the ArduinoCoreSTM32 library prior to version 1.7.0. The pwmstart function allocates a TIMHandleTypeDef structure on the stack and passes its address to HAL initialization routines, where it is stored in a global timer handle registry. After the function...

CVE-2026-26399

A stack-use-after-return issue exists in the ArduinoCoreSTM32 library prior to version 1.7.0. The pwmstart function allocates a TIMHandleTypeDef structure on the stack and passes its address to HAL initialization routines, where it is stored in a global timer handle registry. After the function...

CVE-2026-4179

Issues in stm32 USB device driver drivers/usb/device/usbdcstm32.c can lead to an infinite while loop...

CVE-2026-4179

Issues in stm32 USB device driver drivers/usb/device/usbdcstm32.c can lead to an infinite while loop...

CVE-2026-4179

CVE-2026-4179 affects the STM32 USB device driver, specifically the USB interrupt handling path in drivers/usb/device/usb_dc_stm32.c. The issue is an infinite loop (infinite while loop) in the USB interrupt handler, as described across multiple sources (Red Hat, NVD, CVE listing, CVE enrichment)....

CVE-2026-4179 stm32: usb: Infinite while loop in Interrupt Handler

Issues in stm32 USB device driver drivers/usb/device/usbdcstm32.c can lead to an infinite while loop...

EUVD-2026-12190

Issues in stm32 USB device driver drivers/usb/device/usbdcstm32.c can lead to an infinite while loop...

CVE-2026-4179 stm32: usb: Infinite while loop in Interrupt Handler

Issues in stm32 USB device driver drivers/usb/device/usbdcstm32.c can lead to an infinite while loop...

CVE-2026-4179 stm32: usb: Infinite while loop in Interrupt Handler

Issues in stm32 USB device driver drivers/usb/device/usbdcstm32.c can lead to an infinite while loop...

PT-2026-25510

CVE-2026-4179 Issues in stm32 USB device driver drivers/usb/device/usb dc stm32.c can lead to an infinite while loop. https://t.co/WkHKaV9kyz...

SUSE CVE-2025-71196

In the Linux kernel, the following vulnerability has been resolved: phy: stm32-usphyc: Fix off by one in probe The "index" variable is used as an index into the usbphyc-phys array which has usbphyc-nphys elements. So if it is equal to usbphyc-nphys then it is one element out of bounds. The "index...

CVE-2025-71196

In the Linux kernel, the following vulnerability has been resolved: phy: stm32-usphyc: Fix off by one in probe The "index" variable is used as an index into the usbphyc-phys array which has usbphyc-nphys elements. So if it is equal to usbphyc-nphys then it is one element out of bounds. The "index...

CVE-2025-71196

In the Linux kernel, the following vulnerability has been resolved: phy: stm32-usphyc: Fix off by one in probe The "index" variable is used as an index into the usbphyc-phys array which has usbphyc-nphys elements. So if it is equal to usbphyc-nphys then it is one element out of bounds. The "index...

UBUNTU-CVE-2025-71196

In the Linux kernel, the following vulnerability has been resolved: phy: stm32-usphyc: Fix off by one in probe The "index" variable is used as an index into the usbphyc-phys array which has usbphyc-nphys elements. So if it is equal to usbphyc-nphys then it is one element out of bounds. The "index...

CVE-2025-71196 phy: stm32-usphyc: Fix off by one in probe()

In the Linux kernel, the following vulnerability has been resolved: phy: stm32-usphyc: Fix off by one in probe The "index" variable is used as an index into the usbphyc-phys array which has usbphyc-nphys elements. So if it is equal to usbphyc-nphys then it is one element out of bounds. The "index...

CVE-2025-71196

Consolidated details from multiple sources confirm a Linux kernel vulnerability in phy: stm32-usphyc where the “index” used to access usbphyc->phys[] can exceed bounds when it equals usbphyc->nphys. The root cause is an off-by-one condition in probe(); the patch fixes this by changing the c...