CVE-2026-80624

A flaw was found in the Linux kernel's mfd: cs42l43 component. This vulnerability occurs because the system does not properly verify that the received firmware's size is larger than its header. An attacker could exploit this by providing a malformed firmware, leading to an out-of-bounds memory...

Linux Distros Unpatched Vulnerability : CVE-2026-80624

The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available. - In the Linux kernel, the following vulnerability has been resolved: mfd: cs42l43: Sanity check firmware size Currently the code checks if a firmware was receive...

SUSE CVE-2026-80624

In the Linux kernel, the following vulnerability has been resolved: mfd: cs42l43: Sanity check firmware size Currently the code checks if a firmware was received, however it does not verify that the firmware size is larger than the firmware header. As the firmware pointer is dereferenced as a...

CVE-2026-80624

In the Linux kernel, the following vulnerability has been resolved: mfd: cs42l43: Sanity check firmware size Currently the code checks if a firmware was received, however it does not verify that the firmware size is larger than the firmware header. As the firmware pointer is dereferenced as a...

UBUNTU-CVE-2026-80624

In the Linux kernel, the following vulnerability has been resolved: mfd: cs42l43: Sanity check firmware size Currently the code checks if a firmware was received, however it does not verify that the firmware size is larger than the firmware header. As the firmware pointer is dereferenced as a...

CVE-2026-80624

In the Linux kernel, the following vulnerability has been resolved: mfd: cs42l43: Sanity check firmware size Currently the code checks if a firmware was received, however it does not verify that the firmware size is larger than the firmware header. As the firmware pointer is dereferenced as a...

CVE-2026-80624 mfd: cs42l43: Sanity check firmware size

In the Linux kernel, the following vulnerability has been resolved: mfd: cs42l43: Sanity check firmware size Currently the code checks if a firmware was received, however it does not verify that the firmware size is larger than the firmware header. As the firmware pointer is dereferenced as a...

CVE-2026-80624 mfd: cs42l43: Sanity check firmware size

In the Linux kernel, the following vulnerability has been resolved: mfd: cs42l43: Sanity check firmware size Currently the code checks if a firmware was received, however it does not verify that the firmware size is larger than the firmware header. As the firmware pointer is dereferenced as a...

CVE-2026-80624

In the Linux kernel, the following vulnerability has been resolved: mfd: cs42l43: Sanity check firmware size Currently the code checks if a firmware was received, however it does not verify that the firmware size is larger than the firmware header. As the firmware pointer is dereferenced as a...

EUVD-2026-67500

In the Linux kernel, the following vulnerability has been resolved: mfd: cs42l43: Sanity check firmware size Currently the code checks if a firmware was received, however it does not verify that the firmware size is larger than the firmware header. As the firmware pointer is dereferenced as a...

CVE-2026-80624

CVE-2026-80624 affects the Linux kernel 's mfd: cs42l43 driver. The root cause is a missing sanity check: the code verifies that a firmware was received but does not confirm that the firmware size exceeds the firmware header size. Because the firmware pointer is dereferenced as a pointer to the h...

CVE-2026-80624: Undefined Security Weakness

In the Linux kernel, the following vulnerability has been resolved: mfd: cs42l43: Sanity check firmware size Currently the code checks if a firmware was received, however it does not verify that the firmware size is larger than the firmware header. As the firmware pointer is dereferenced as a...

PT-2026-82924

Name of the Vulnerable Software and Affected Versions Linux kernel affected versions not specified Description An issue exists in the cs42l43 multi-function device mfd driver where the system fails to verify if the received firmware size is larger than the firmware header. Because the firmware...

cs42l43pinprobe Heap Buffer Overflow DoS

The vulnerability of the cs42l43pinprobe function in the drivers/pinctrl/cirrus/pinctrl-cs42l43.c driver for Linux kernel’s PINCTRL output interface is related to the multiple release of the same resource or descriptor. Exploiting this vulnerability could allow an attacker to compromise the...

Astra Linux – Vulnerability in Linux 6.12

In the Linux kernel, the following vulnerability has been resolved: pinctrl: cirrus: cs42l43: Fixed double-put in cs42l43pinprobe devmaddactionorreset already invokes the action in case of failure; therefore, the explicit put causes a double-put...

SUSE CVE-2026-23387

In the Linux kernel, the following vulnerability has been resolved: pinctrl: cirrus: cs42l43: Fix double-put in cs42l43pinprobe devmaddactionorreset already invokes the action on failure, so the explicit put causes a double-put...

CVE-2026-23387

A flaw was found in the Linux kernel, specifically within the pinctrl subsystem's cirrus cs42l43 driver. This flaw involves a 'double-put' error in the cs42l43pinprobe function, where a resource is incorrectly released twice. This issue arises because the devmaddactionorreset function already...

EUVD-2026-15387

In the Linux kernel, the following vulnerability has been resolved: pinctrl: cirrus: cs42l43: Fix double-put in cs42l43pinprobe devmaddactionorreset already invokes the action on failure, so the explicit put causes a double-put...

CVE-2026-23387

In the Linux kernel, the following vulnerability has been resolved: pinctrl: cirrus: cs42l43: Fix double-put in cs42l43pinprobe devmaddactionorreset already invokes the action on failure, so the explicit put causes a double-put...

CVE-2026-23387

In the Linux kernel, the following vulnerability has been resolved: pinctrl: cirrus: cs42l43: Fix double-put in cs42l43pinprobe devmaddactionorreset already invokes the action on failure, so the explicit put causes a double-put...