136 matches found
CVE-2024-57889
In the Linux kernel, the following vulnerability has been resolved: pinctrl: mcp23s08: Fix sleeping in atomic context due to regmap locking If a device uses MCP23xxx IO expander to receive IRQs, the following bug can happen: BUG: sleeping function called from invalid context at...
DEBIAN-CVE-2024-57889
In the Linux kernel, the following vulnerability has been resolved: pinctrl: mcp23s08: Fix sleeping in atomic context due to regmap locking If a device uses MCP23xxx IO expander to receive IRQs, the following bug can happen: BUG: sleeping function called from invalid context at...
UBUNTU-CVE-2024-57889
In the Linux kernel, the following vulnerability has been resolved: pinctrl: mcp23s08: Fix sleeping in atomic context due to regmap locking If a device uses MCP23xxx IO expander to receive IRQs, the following bug can happen: BUG: sleeping function called from invalid context at...
CVE-2024-57889 pinctrl: mcp23s08: Fix sleeping in atomic context due to regmap locking
In the Linux kernel, the following vulnerability has been resolved: pinctrl: mcp23s08: Fix sleeping in atomic context due to regmap locking If a device uses MCP23xxx IO expander to receive IRQs, the following bug can happen: BUG: sleeping function called from invalid context at...
CVE-2024-57889
CVE-2024-57889 is resolved in the Linux kernel via a patch to the pinctrl-mcp23s08 driver. The issue occurred when using MCP23xxx IO expanders to receive IRQs, where regmap locking (mutex) around regmap_update_bits_base was invoked from a context that held a spinlock in __setup_irq(), leading to ...
SUSE CVE-2024-57804
In the Linux kernel, the following vulnerability has been resolved: scsi: mpi3mr: Fix corrupt config pages PHY state is switched in sysfs The driver, through the SAS transport, exposes a sysfs interface to enable/disable PHYs in a controller/expander setup. When multiple PHYs are disabled and...
UBUNTU-CVE-2024-56589
In the Linux kernel, the following vulnerability has been resolved: scsi: hisisas: Add condresched for no forced preemption model For no forced preemption model kernel, in the scenario where the expander is connected to 12 high performance SAS SSDs, the following call trace may occur: 214.409199...
CVE-2024-56625 can: dev: can_set_termination(): allow sleeping GPIOs
In the Linux kernel, the following vulnerability has been resolved: can: dev: cansettermination: allow sleeping GPIOs In commit 6e86a1543c37 "can: dev: provide optional GPIO based termination support" GPIO based termination support was added. For no particular reason that patch uses gpiodsetvalue...
PT-2025-3582
Name of the Vulnerable Software and Affected Versions Linux kernel affected versions not specified Description A vulnerability in the Linux kernel has been resolved, related to the scsi: mpi3mr driver. The driver exposes a sysfs interface to enable or disable PHYs in a controller/expander setup...
CVE-2024-49961
In the Linux kernel, the following vulnerability has been resolved: media: i2c: ar0521: Use cansleep version of gpiodsetvalue If we use GPIO reset from I2C port expander, we must use cansleep variant of GPIO functions. This was not done in ar0521poweron/ar0521poweroff functions. Let's fix that...
CVE-2024-49961
In the Linux kernel, the following vulnerability has been resolved: media: i2c: ar0521: Use cansleep version of gpiodsetvalue If we use GPIO reset from I2C port expander, we must use cansleep variant of GPIO functions. This was not done in ar0521poweron/ar0521poweroff functions. Let's fix that...
CVE-2024-49961
CVE-2024-49961 is a Linux kernel issue affecting GPIO handling via an I2C port expander (ar0521). The fix updates ar0521_power_on/power_off to use the cansleep variant of gpiod_set_value(), correcting a mismatch where GPIO resets using I2C expander were not cansleep-enabled. The CVE context in th...
CVE-2024-49961 media: i2c: ar0521: Use cansleep version of gpiod_set_value()
In the Linux kernel, the following vulnerability has been resolved: media: i2c: ar0521: Use cansleep version of gpiodsetvalue If we use GPIO reset from I2C port expander, we must use cansleep variant of GPIO functions. This was not done in ar0521poweron/ar0521poweroff functions. Let's fix that...
PT-2024-33802
Name of the Vulnerable Software and Affected Versions: Linux kernel versions prior to 6.6.58 Description: A vulnerability in the Linux kernel has been resolved. The issue is related to the use of GPIO reset from I2C port expander, where the cansleep variant of GPIO functions was not used in the...
SUSE CVE-2018-20836
An issue was discovered in the Linux kernel before 4.20. There is a race condition in smptasktimedout and smptaskdone in drivers/scsi/libsas/sasexpander.c, leading to a use-after-free...
SUSE CVE-2019-15807
In the Linux kernel before 5.1.13, there is a memory leak in drivers/scsi/libsas/sasexpander.c when SAS expander discovery fails. This will cause a BUG and denial of service...
SOUND4 IMPACT/FIRST/PULSE/Eco 2.x Radio Steam Disclosure
SOUND4 IMPACT/FIRST/PULSE/Eco =2.x Unauthenticated Radio Stream Disclosure Vendor: SOUND4 Ltd. Product web page: https://www.sound4.com | https://www.sound4.biz Affected version: FM/HD Radio Processing: Impact/Pulse/First Version 2: 1.1/2.15 Impact/Pulse/First Version 1: 2.1/1.69 Impact/Pulse Eco...
SOUND4 IMPACT/FIRST/PULSE/Eco 2.x Cross Site Request Forgery
SOUND4 IMPACT/FIRST/PULSE/Eco =2.x Cross-Site Request Forgery Vendor: SOUND4 Ltd. Product web page: https://www.sound4.com | https://www.sound4.biz Affected version: FM/HD Radio Processing: Impact/Pulse/First Version 2: 1.1/2.15 Impact/Pulse/First Version 1: 2.1/1.69 Impact/Pulse Eco 1.16 Voice...
SOUND4 IMPACT/FIRST/PULSE/Eco <=2.x Cross-Site Request Forgery
Summary The SOUND4 IMPACT introduces an innovative process - mono and stereo parts of the signal are processed separately to obtain perfect consistency in terms of both sound and level. Therefore, in moving reception, when the FM receiver switches from stereo to mono and back to stereo, the sound...
GHSA-RMFF-F8W9-C9RM Data races in max7301
The ImmediateIO and TransactionalIO types implement Sync for all contained Expander types regardless of if the Expander itself is safe to use across threads. As the IO types allow retrieving the Expander, this can lead to non-thread safe types being sent across threads as part of the Expander...