CVE-2026-68467

In the Linux kernel, the following vulnerability has been resolved: mtd: mchp23k256: use SPI match data for chip caps The driver stores chip capacity information in both the OF match table and the SPI id table. Probe currently uses ofdevicegetmatchdata, so a non-OF SPI modalias match falls back t...

CVE-2026-68466

In the Linux kernel, the following vulnerability has been resolved: mtd: rawnand: lpc32xxslc: fail DMA transfer on completion timeout lpc32xxxmitdma waits for the DMA completion callback but ignores waitforcompletiontimeout. A timed out DMA transfer is therefore unmapped and reported as successfu...

CVE-2026-68466

The CVE concerns the Linux kernel driver path mtd: rawnand: lpc32xx_slc. lpc32xx_xmit_dma() waits for a DMA completion callback but uses wait_for_completion_timeout() and can time out, causing a DMA transfer to be unmapped and reported as successful to the NAND read/write path. The fix is to retu...

CVE-2026-68467 mtd: mchp23k256: use SPI match data for chip caps

In the Linux kernel, the following vulnerability has been resolved: mtd: mchp23k256: use SPI match data for chip caps The driver stores chip capacity information in both the OF match table and the SPI id table. Probe currently uses ofdevicegetmatchdata, so a non-OF SPI modalias match falls back t...

CVE-2026-68467

The CVE-2026-68467 issue affects the Linux kernel mtd: mchp23k256 driver. The driver stored chip capacity in both the OF match table and the SPI id table, and probe used of_device_get_match_data(), which caused an id-table-only match to fallback to mchp23k256_caps. The fix switches to spi_get_dev...

EUVD-2026-59089

In the Linux kernel, the following vulnerability has been resolved: mtd: mchp23k256: use SPI match data for chip caps The driver stores chip capacity information in both the OF match table and the SPI id table. Probe currently uses ofdevicegetmatchdata, so a non-OF SPI modalias match falls back t...

CVE-2026-68465

The CVE concerns the Linux kernel MMC subsystem (sdhci-esdhc-imx). The root cause was esdhc_change_pinstate() evaluating pins_100mhz/pins_200mhz at the top and returning -EINVAL if either is undefined, which could prevent the default pin configuration from being restored for devices with a sleep ...

EUVD-2026-59087

In the Linux kernel, the following vulnerability has been resolved: mmc: sdhci-esdhc-imx: fix esdhcchangepinstate to allow default state restore esdhcchangepinstate checks for pins100mhz and pins200mhz at the top of the function and returns -EINVAL if either is not defined. This prevents the...

CVE-2026-68465

In the Linux kernel, the following vulnerability has been resolved: mmc: sdhci-esdhc-imx: fix esdhcchangepinstate to allow default state restore esdhcchangepinstate checks for pins100mhz and pins200mhz at the top of the function and returns -EINVAL if either is not defined. This prevents the...

CVE-2026-68464 mmc: sdhci-esdhc-imx: disable irq during suspend to fix unhandled interrupt

In the Linux kernel, the following vulnerability has been resolved: mmc: sdhci-esdhc-imx: disable irq during suspend to fix unhandled interrupt When using WIFI out-of-band wakeup, an "irq xxx: nobody cared" warning occurs. This happens because the usdhc interrupt is not disabled during system...

CVE-2026-68464

In the Linux kernel, the following vulnerability has been resolved: mmc: sdhci-esdhc-imx: disable irq during suspend to fix unhandled interrupt When using WIFI out-of-band wakeup, an "irq xxx: nobody cared" warning occurs. This happens because the usdhc interrupt is not disabled during system...

CVE-2026-68464

The CVE concerns the Linux kernel driver for mmc: sdhci-esdhc-imx. The root cause was that the usdhc interrupt was not disabled during system suspend when device_may_wakeup() returned false, allowing an out-of-band WiFi wakeup to trigger a resume followed by a card interrupt while the controller ...

EUVD-2026-59086

In the Linux kernel, the following vulnerability has been resolved: mmc: sdhci-esdhc-imx: disable irq during suspend to fix unhandled interrupt When using WIFI out-of-band wakeup, an "irq xxx: nobody cared" warning occurs. This happens because the usdhc interrupt is not disabled during system...

CVE-2026-68463 mmc: sdhci-esdhc-imx: use pm_runtime_resume_and_get() in suspend

In the Linux kernel, the following vulnerability has been resolved: mmc: sdhci-esdhc-imx: use pmruntimeresumeandget in suspend Replace pmruntimegetsync with pmruntimeresumeandget to simplify error handling. pmruntimeresumeandget automatically drops the usage counter on failure, avoiding the need...

EUVD-2026-59085

In the Linux kernel, the following vulnerability has been resolved: mmc: sdhci-esdhc-imx: use pmruntimeresumeandget in suspend Replace pmruntimegetsync with pmruntimeresumeandget to simplify error handling. pmruntimeresumeandget automatically drops the usage counter on failure, avoiding the need...

CVE-2026-68463

In the Linux kernel, the following vulnerability has been resolved: mmc: sdhci-esdhc-imx: use pmruntimeresumeandget in suspend Replace pmruntimegetsync with pmruntimeresumeandget to simplify error handling. pmruntimeresumeandget automatically drops the usage counter on failure, avoiding the need...

CVE-2026-68463

CVE-2026-68463 affects the Linux kernel component mmc: sdhci-esdhc-imx . The vulnerability arises from suspend handling where code was changed to use pm_runtime_resume_and_get() instead of pm_runtime_get_sync() to simplify error handling. The new function automatically drops the usage counter on ...

CVE-2026-68461 device property: initialize the remaining fields of fwnode_handle in fwnode_init()

In the Linux kernel, the following vulnerability has been resolved: device property: initialize the remaining fields of fwnodehandle in fwnodeinit If a firmware node is allocated on the stack for instance: temporary software node whose life-time we control or on the heap - but using a non-zeroing...

CVE-2026-68461

In the Linux kernel, CVE-2026-68461 is resolved by fixing fwnode_init() so that fwnode_handle and its secondary pointer are initialized (setting fwnode->secondary to NULL and initializing remaining fields). This prevents a firmware node allocated on stack/heap with non-zeroing allocation from ...

EUVD-2026-59083

In the Linux kernel, the following vulnerability has been resolved: device property: initialize the remaining fields of fwnodehandle in fwnodeinit If a firmware node is allocated on the stack for instance: temporary software node whose life-time we control or on the heap - but using a non-zeroing...