Поиск уязвимостей
Количество 21
Количество 21
CVE-2022-48975
In the Linux kernel, the following vulnerability has been resolved: gpiolib: fix memory leak in gpiochip_setup_dev() Here is a backtrace report about memory leak detected in gpiochip_setup_dev(): unreferenced object 0xffff88810b406400 (size 512): comm "python3", pid 1682, jiffies 4295346908 (age 24.090s) backtrace: kmalloc_trace device_add device_private_init at drivers/base/core.c:3361 (inlined by) device_add at drivers/base/core.c:3411 cdev_device_add gpiolib_cdev_register gpiochip_setup_dev gpiochip_add_data_with_key gcdev_register() & gcdev_unregister() would call device_add() & device_del() (no matter CONFIG_GPIO_CDEV is enabled or not) to register/unregister device. However, if device_add() succeeds, some resource (like struct device_private allocated by device_private_init()) is not released by device_del(). Therefore, after device_add() succeeds by gcdev_register(), it needs to call put_device() to release resource in the error handle path. Here we move forward the register...
CVE-2022-48975
In the Linux kernel, the following vulnerability has been resolved: gpiolib: fix memory leak in gpiochip_setup_dev() Here is a backtrace report about memory leak detected in gpiochip_setup_dev(): unreferenced object 0xffff88810b406400 (size 512): comm "python3", pid 1682, jiffies 4295346908 (age 24.090s) backtrace: kmalloc_trace device_adddevice_private_init at drivers/base/core.c:3361 (inlined by) device_add at drivers/base/core.c:3411 cdev_device_add gpiolib_cdev_register gpiochip_setup_dev gpiochip_add_data_with_key gcdev_register() & gcdev_unregister() would call device_add() & device_del() (no matter CONFIG_GPIO_CDEV is enabled or not) to register/unregister device. However, if device_add() succeeds, some resource (like struct device_private allocated by device_private_init()) is not released by device_del(). Therefore, after device_add() succeeds by gcdev_register(), it needs to call put_device() to release resource in the error handle path. Here we move forward the register o...
CVE-2022-48975
In the Linux kernel, the following vulnerability has been resolved: gpiolib: fix memory leak in gpiochip_setup_dev() Here is a backtrace report about memory leak detected in gpiochip_setup_dev(): unreferenced object 0xffff88810b406400 (size 512): comm "python3", pid 1682, jiffies 4295346908 (age 24.090s) backtrace: kmalloc_trace device_add device_private_init at drivers/base/core.c:3361 (inlined by) device_add at drivers/base/core.c:3411 cdev_device_add gpiolib_cdev_register gpiochip_setup_dev gpiochip_add_data_with_key gcdev_register() & gcdev_unregister() would call device_add() & device_del() (no matter CONFIG_GPIO_CDEV is enabled or not) to register/unregister device. However, if device_add() succeeds, some resource (like struct device_private allocated by device_private_init()) is not released by device_del(). Therefore, after device_add() succeeds by gcdev_register(), it needs to call put_device() to release resource in the error handle path.
CVE-2022-48975
In the Linux kernel, the following vulnerability has been resolved: g ...
GHSA-5rmx-h57x-xq29
In the Linux kernel, the following vulnerability has been resolved: gpiolib: fix memory leak in gpiochip_setup_dev() Here is a backtrace report about memory leak detected in gpiochip_setup_dev(): unreferenced object 0xffff88810b406400 (size 512): comm "python3", pid 1682, jiffies 4295346908 (age 24.090s) backtrace: kmalloc_trace device_add device_private_init at drivers/base/core.c:3361 (inlined by) device_add at drivers/base/core.c:3411 cdev_device_add gpiolib_cdev_register gpiochip_setup_dev gpiochip_add_data_with_key gcdev_register() & gcdev_unregister() would call device_add() & device_del() (no matter CONFIG_GPIO_CDEV is enabled or not) to register/unregister device. However, if device_add() succeeds, some resource (like struct device_private allocated by device_private_init()) is not released by device_del(). Therefore, after device_add() succeeds by gcdev_register(), it needs to call put_device() to release resource in the error handle pa...
BDU:2025-01684
Уязвимость компонента gpiolib ядра операционной системы Linux, позволяющая нарушителю получить несанкционированный доступ к защищаемой информации
ALT-PU-2022-7818
ALT-PU-2022-7818: package `kernel-image-std-def` update to version 5.15.83-alt1
SUSE-SU-2025:0834-1
Security update for the Linux Kernel
ROS-20250211-01
Множественные уязвимости kernel-lt
ALT-PU-2022-7839
ALT-PU-2022-7839: package `kernel-image-un-def` update to version 6.0.13-alt1
SUSE-SU-2024:4131-1
Security update for the Linux Kernel
SUSE-SU-2024:3983-1
Security update for the Linux Kernel
SUSE-SU-2024:3985-1
Security update for the Linux Kernel
ALT-PU-2023-1011
ALT-PU-2023-1011: package `kernel-image-mp` update to version 6.0.16-alt1
SUSE-SU-2024:4364-1
Security update for the Linux Kernel
ALT-PU-2023-1044
ALT-PU-2023-1044: package `kernel-image-un-def` update to version 5.15.87-alt1
ALT-PU-2022-3371
ALT-PU-2022-3371: package `kernel-image-rpi-un` update to version 6.1.0-alt1
ALT-PU-2022-3364
ALT-PU-2022-3364: package `kernel-image-rpi-un` update to version 6.1.0-alt1
ALT-PU-2023-7682
ALT-PU-2023-7682: package `kernel-image-rpi-def` update to version 5.15.92-alt2
ALT-PU-2023-7007
ALT-PU-2023-7007: package `kernel-image-rpi-def` update to version 5.15.92-alt1
Уязвимостей на страницу
Уязвимость | CVSS | EPSS | Опубликовано | |
|---|---|---|---|---|
CVE-2022-48975 In the Linux kernel, the following vulnerability has been resolved: gpiolib: fix memory leak in gpiochip_setup_dev() Here is a backtrace report about memory leak detected in gpiochip_setup_dev(): unreferenced object 0xffff88810b406400 (size 512): comm "python3", pid 1682, jiffies 4295346908 (age 24.090s) backtrace: kmalloc_trace device_add device_private_init at drivers/base/core.c:3361 (inlined by) device_add at drivers/base/core.c:3411 cdev_device_add gpiolib_cdev_register gpiochip_setup_dev gpiochip_add_data_with_key gcdev_register() & gcdev_unregister() would call device_add() & device_del() (no matter CONFIG_GPIO_CDEV is enabled or not) to register/unregister device. However, if device_add() succeeds, some resource (like struct device_private allocated by device_private_init()) is not released by device_del(). Therefore, after device_add() succeeds by gcdev_register(), it needs to call put_device() to release resource in the error handle path. Here we move forward the register... | CVSS3: 5.5 | 0% Низкий | около 2 лет назад | |
CVE-2022-48975 In the Linux kernel, the following vulnerability has been resolved: gpiolib: fix memory leak in gpiochip_setup_dev() Here is a backtrace report about memory leak detected in gpiochip_setup_dev(): unreferenced object 0xffff88810b406400 (size 512): comm "python3", pid 1682, jiffies 4295346908 (age 24.090s) backtrace: kmalloc_trace device_adddevice_private_init at drivers/base/core.c:3361 (inlined by) device_add at drivers/base/core.c:3411 cdev_device_add gpiolib_cdev_register gpiochip_setup_dev gpiochip_add_data_with_key gcdev_register() & gcdev_unregister() would call device_add() & device_del() (no matter CONFIG_GPIO_CDEV is enabled or not) to register/unregister device. However, if device_add() succeeds, some resource (like struct device_private allocated by device_private_init()) is not released by device_del(). Therefore, after device_add() succeeds by gcdev_register(), it needs to call put_device() to release resource in the error handle path. Here we move forward the register o... | CVSS3: 7.1 | 0% Низкий | около 2 лет назад | |
CVE-2022-48975 In the Linux kernel, the following vulnerability has been resolved: gpiolib: fix memory leak in gpiochip_setup_dev() Here is a backtrace report about memory leak detected in gpiochip_setup_dev(): unreferenced object 0xffff88810b406400 (size 512): comm "python3", pid 1682, jiffies 4295346908 (age 24.090s) backtrace: kmalloc_trace device_add device_private_init at drivers/base/core.c:3361 (inlined by) device_add at drivers/base/core.c:3411 cdev_device_add gpiolib_cdev_register gpiochip_setup_dev gpiochip_add_data_with_key gcdev_register() & gcdev_unregister() would call device_add() & device_del() (no matter CONFIG_GPIO_CDEV is enabled or not) to register/unregister device. However, if device_add() succeeds, some resource (like struct device_private allocated by device_private_init()) is not released by device_del(). Therefore, after device_add() succeeds by gcdev_register(), it needs to call put_device() to release resource in the error handle path. | CVSS3: 5.5 | 0% Низкий | около 2 лет назад | |
CVE-2022-48975 In the Linux kernel, the following vulnerability has been resolved: g ... | CVSS3: 5.5 | 0% Низкий | около 2 лет назад | |
GHSA-5rmx-h57x-xq29 In the Linux kernel, the following vulnerability has been resolved: gpiolib: fix memory leak in gpiochip_setup_dev() Here is a backtrace report about memory leak detected in gpiochip_setup_dev(): unreferenced object 0xffff88810b406400 (size 512): comm "python3", pid 1682, jiffies 4295346908 (age 24.090s) backtrace: kmalloc_trace device_add device_private_init at drivers/base/core.c:3361 (inlined by) device_add at drivers/base/core.c:3411 cdev_device_add gpiolib_cdev_register gpiochip_setup_dev gpiochip_add_data_with_key gcdev_register() & gcdev_unregister() would call device_add() & device_del() (no matter CONFIG_GPIO_CDEV is enabled or not) to register/unregister device. However, if device_add() succeeds, some resource (like struct device_private allocated by device_private_init()) is not released by device_del(). Therefore, after device_add() succeeds by gcdev_register(), it needs to call put_device() to release resource in the error handle pa... | CVSS3: 5.5 | 0% Низкий | около 2 лет назад | |
BDU:2025-01684 Уязвимость компонента gpiolib ядра операционной системы Linux, позволяющая нарушителю получить несанкционированный доступ к защищаемой информации | CVSS3: 5.5 | 0% Низкий | почти 4 года назад | |
ALT-PU-2022-7818 ALT-PU-2022-7818: package `kernel-image-std-def` update to version 5.15.83-alt1 | CVSS3: 7.8 | почти 4 года назад | ||
SUSE-SU-2025:0834-1 Security update for the Linux Kernel | больше 1 года назад | |||
ROS-20250211-01 Множественные уязвимости kernel-lt | CVSS3: 7.8 | больше 1 года назад | ||
ALT-PU-2022-7839 ALT-PU-2022-7839: package `kernel-image-un-def` update to version 6.0.13-alt1 | CVSS3: 7.8 | почти 4 года назад | ||
SUSE-SU-2024:4131-1 Security update for the Linux Kernel | почти 2 года назад | |||
SUSE-SU-2024:3983-1 Security update for the Linux Kernel | почти 2 года назад | |||
SUSE-SU-2024:3985-1 Security update for the Linux Kernel | почти 2 года назад | |||
ALT-PU-2023-1011 ALT-PU-2023-1011: package `kernel-image-mp` update to version 6.0.16-alt1 | CVSS3: 8 | почти 4 года назад | ||
SUSE-SU-2024:4364-1 Security update for the Linux Kernel | почти 2 года назад | |||
ALT-PU-2023-1044 ALT-PU-2023-1044: package `kernel-image-un-def` update to version 5.15.87-alt1 | CVSS3: 8.8 | почти 4 года назад | ||
ALT-PU-2022-3371 ALT-PU-2022-3371: package `kernel-image-rpi-un` update to version 6.1.0-alt1 | CVSS3: 9.3 | почти 4 года назад | ||
ALT-PU-2022-3364 ALT-PU-2022-3364: package `kernel-image-rpi-un` update to version 6.1.0-alt1 | CVSS3: 9.3 | почти 4 года назад | ||
ALT-PU-2023-7682 ALT-PU-2023-7682: package `kernel-image-rpi-def` update to version 5.15.92-alt2 | CVSS3: 9.3 | почти 3 года назад | ||
ALT-PU-2023-7007 ALT-PU-2023-7007: package `kernel-image-rpi-def` update to version 5.15.92-alt1 | CVSS3: 9.3 | около 3 лет назад |
Уязвимостей на страницу