ΠΠΎΠ»ΠΈΡΠ΅ΡΡΠ²ΠΎ 17
ΠΠΎΠ»ΠΈΡΠ΅ΡΡΠ²ΠΎ 17
CVE-2024-37021
In the Linux kernel, the following vulnerability has been resolved: fpga: manager: add owner module and take its refcount The current implementation of the fpga manager assumes that the low-level module registers a driver for the parent device and uses its owner pointer to take the module's refcount. This approach is problematic since it can lead to a null pointer dereference while attempting to get the manager if the parent device does not have a driver. To address this problem, add a module owner pointer to the fpga_manager struct and use it to take the module's refcount. Modify the functions for registering the manager to take an additional owner module parameter and rename them to avoid conflicts. Use the old function names for helper macros that automatically set the module that registers the manager as the owner. This ensures compatibility with existing low-level control modules and reduces the chances of registering a manager without setting the owner. Also, update the docume...
CVE-2024-37021
In the Linux kernel, the following vulnerability has been resolved: fpga: manager: add owner module and take its refcount The current implementation of the fpga manager assumes that the low-level module registers a driver for the parent device and uses its owner pointer to take the module's refcount. This approach is problematic since it can lead to a null pointer dereference while attempting to get the manager if the parent device does not have a driver. To address this problem, add a module owner pointer to the fpga_manager struct and use it to take the module's refcount. Modify the functions for registering the manager to take an additional owner module parameter and rename them to avoid conflicts. Use the old function names for helper macros that automatically set the module that registers the manager as the owner. This ensures compatibility with existing low-level control modules and reduces the chances of registering a manager without setting the owner. Also, update the docume...
CVE-2024-37021
In the Linux kernel, the following vulnerability has been resolved: fpga: manager: add owner module and take its refcount The current implementation of the fpga manager assumes that the low-level module registers a driver for the parent device and uses its owner pointer to take the module's refcount. This approach is problematic since it can lead to a null pointer dereference while attempting to get the manager if the parent device does not have a driver. To address this problem, add a module owner pointer to the fpga_manager struct and use it to take the module's refcount. Modify the functions for registering the manager to take an additional owner module parameter and rename them to avoid conflicts. Use the old function names for helper macros that automatically set the module that registers the manager as the owner. This ensures compatibility with existing low-level control modules and reduces the chances of registering a manager without setting the owner. Also, update the docum
CVE-2024-37021
fpga: manager: add owner module and take its refcount
CVE-2024-37021
In the Linux kernel, the following vulnerability has been resolved: f ...
GHSA-9g63-jv3j-6766
In the Linux kernel, the following vulnerability has been resolved: fpga: manager: add owner module and take its refcount The current implementation of the fpga manager assumes that the low-level module registers a driver for the parent device and uses its owner pointer to take the module's refcount. This approach is problematic since it can lead to a null pointer dereference while attempting to get the manager if the parent device does not have a driver. To address this problem, add a module owner pointer to the fpga_manager struct and use it to take the module's refcount. Modify the functions for registering the manager to take an additional owner module parameter and rename them to avoid conflicts. Use the old function names for helper macros that automatically set the module that registers the manager as the owner. This ensures compatibility with existing low-level control modules and reduces the chances of registering a manager without setting the owner. Also, update the do...
BDU:2025-03051
Π£ΡΠ·Π²ΠΈΠΌΠΎΡΡΡ ΡΡΠ½ΠΊΡΠΈΠΈ fpga_mgr_register() ΠΌΠΎΠ΄ΡΠ»Ρ Documentation/driver-api/fpga/fpga-mgr.rst ΡΠ΄ΡΠ° ΠΎΠΏΠ΅ΡΠ°ΡΠΈΠΎΠ½Π½ΠΎΠΉ ΡΠΈΡΡΠ΅ΠΌΡ Linux, ΠΏΠΎΠ·Π²ΠΎΠ»ΡΡΡΠ°Ρ Π½Π°ΡΡΡΠΈΡΠ΅Π»Ρ Π²ΡΠ·Π²Π°ΡΡ ΠΎΡΠΊΠ°Π· Π² ΠΎΠ±ΡΠ»ΡΠΆΠΈΠ²Π°Π½ΠΈΠΈ
ROS-20260112-7324
Π£ΡΠ·Π²ΠΈΠΌΠΎΡΡΡ kernel-lt
SUSE-SU-2024:2381-1
Security update for the Linux Kernel
SUSE-SU-2024:2360-1
Security update for the Linux Kernel
SUSE-SU-2024:2561-1
Security update for the Linux Kernel
SUSE-SU-2024:2394-1
Security update for the Linux Kernel
SUSE-SU-2024:2372-1
Security update for the Linux Kernel
SUSE-SU-2024:2571-1
Security update for the Linux Kernel
SUSE-SU-2024:2896-1
Security update for the Linux Kernel
SUSE-SU-2024:2939-1
Security update for the Linux Kernel
SUSE-SU-2024:2973-1
Security update for the Linux Kernel
Π£ΡΠ·Π²ΠΈΠΌΠΎΡΡΠ΅ΠΉ Π½Π° ΡΡΡΠ°Π½ΠΈΡΡ
Π£ΡΠ·Π²ΠΈΠΌΠΎΡΡΡ | CVSS | EPSS | ΠΠΏΡΠ±Π»ΠΈΠΊΠΎΠ²Π°Π½ΠΎ | |
|---|---|---|---|---|
CVE-2024-37021 In the Linux kernel, the following vulnerability has been resolved: fpga: manager: add owner module and take its refcount The current implementation of the fpga manager assumes that the low-level module registers a driver for the parent device and uses its owner pointer to take the module's refcount. This approach is problematic since it can lead to a null pointer dereference while attempting to get the manager if the parent device does not have a driver. To address this problem, add a module owner pointer to the fpga_manager struct and use it to take the module's refcount. Modify the functions for registering the manager to take an additional owner module parameter and rename them to avoid conflicts. Use the old function names for helper macros that automatically set the module that registers the manager as the owner. This ensures compatibility with existing low-level control modules and reduces the chances of registering a manager without setting the owner. Also, update the docume... | CVSS3: 5.5 | 0% ΠΠΈΠ·ΠΊΠΈΠΉ | ΠΎΠΊΠΎΠ»ΠΎ 2 Π»Π΅Ρ Π½Π°Π·Π°Π΄ | |
CVE-2024-37021 In the Linux kernel, the following vulnerability has been resolved: fpga: manager: add owner module and take its refcount The current implementation of the fpga manager assumes that the low-level module registers a driver for the parent device and uses its owner pointer to take the module's refcount. This approach is problematic since it can lead to a null pointer dereference while attempting to get the manager if the parent device does not have a driver. To address this problem, add a module owner pointer to the fpga_manager struct and use it to take the module's refcount. Modify the functions for registering the manager to take an additional owner module parameter and rename them to avoid conflicts. Use the old function names for helper macros that automatically set the module that registers the manager as the owner. This ensures compatibility with existing low-level control modules and reduces the chances of registering a manager without setting the owner. Also, update the docume... | CVSS3: 4.4 | 0% ΠΠΈΠ·ΠΊΠΈΠΉ | ΠΎΠΊΠΎΠ»ΠΎ 2 Π»Π΅Ρ Π½Π°Π·Π°Π΄ | |
CVE-2024-37021 In the Linux kernel, the following vulnerability has been resolved: fpga: manager: add owner module and take its refcount The current implementation of the fpga manager assumes that the low-level module registers a driver for the parent device and uses its owner pointer to take the module's refcount. This approach is problematic since it can lead to a null pointer dereference while attempting to get the manager if the parent device does not have a driver. To address this problem, add a module owner pointer to the fpga_manager struct and use it to take the module's refcount. Modify the functions for registering the manager to take an additional owner module parameter and rename them to avoid conflicts. Use the old function names for helper macros that automatically set the module that registers the manager as the owner. This ensures compatibility with existing low-level control modules and reduces the chances of registering a manager without setting the owner. Also, update the docum | CVSS3: 5.5 | 0% ΠΠΈΠ·ΠΊΠΈΠΉ | ΠΎΠΊΠΎΠ»ΠΎ 2 Π»Π΅Ρ Π½Π°Π·Π°Π΄ | |
CVE-2024-37021 fpga: manager: add owner module and take its refcount | 0% ΠΠΈΠ·ΠΊΠΈΠΉ | 5 ΠΌΠ΅ΡΡΡΠ΅Π² Π½Π°Π·Π°Π΄ | ||
CVE-2024-37021 In the Linux kernel, the following vulnerability has been resolved: f ... | CVSS3: 5.5 | 0% ΠΠΈΠ·ΠΊΠΈΠΉ | ΠΎΠΊΠΎΠ»ΠΎ 2 Π»Π΅Ρ Π½Π°Π·Π°Π΄ | |
GHSA-9g63-jv3j-6766 In the Linux kernel, the following vulnerability has been resolved: fpga: manager: add owner module and take its refcount The current implementation of the fpga manager assumes that the low-level module registers a driver for the parent device and uses its owner pointer to take the module's refcount. This approach is problematic since it can lead to a null pointer dereference while attempting to get the manager if the parent device does not have a driver. To address this problem, add a module owner pointer to the fpga_manager struct and use it to take the module's refcount. Modify the functions for registering the manager to take an additional owner module parameter and rename them to avoid conflicts. Use the old function names for helper macros that automatically set the module that registers the manager as the owner. This ensures compatibility with existing low-level control modules and reduces the chances of registering a manager without setting the owner. Also, update the do... | CVSS3: 5.5 | 0% ΠΠΈΠ·ΠΊΠΈΠΉ | ΠΎΠΊΠΎΠ»ΠΎ 2 Π»Π΅Ρ Π½Π°Π·Π°Π΄ | |
BDU:2025-03051 Π£ΡΠ·Π²ΠΈΠΌΠΎΡΡΡ ΡΡΠ½ΠΊΡΠΈΠΈ fpga_mgr_register() ΠΌΠΎΠ΄ΡΠ»Ρ Documentation/driver-api/fpga/fpga-mgr.rst ΡΠ΄ΡΠ° ΠΎΠΏΠ΅ΡΠ°ΡΠΈΠΎΠ½Π½ΠΎΠΉ ΡΠΈΡΡΠ΅ΠΌΡ Linux, ΠΏΠΎΠ·Π²ΠΎΠ»ΡΡΡΠ°Ρ Π½Π°ΡΡΡΠΈΡΠ΅Π»Ρ Π²ΡΠ·Π²Π°ΡΡ ΠΎΡΠΊΠ°Π· Π² ΠΎΠ±ΡΠ»ΡΠΆΠΈΠ²Π°Π½ΠΈΠΈ | CVSS3: 5.5 | 0% ΠΠΈΠ·ΠΊΠΈΠΉ | Π±ΠΎΠ»ΡΡΠ΅ 2 Π»Π΅Ρ Π½Π°Π·Π°Π΄ | |
ROS-20260112-7324 Π£ΡΠ·Π²ΠΈΠΌΠΎΡΡΡ kernel-lt | CVSS3: 5.5 | 0% ΠΠΈΠ·ΠΊΠΈΠΉ | 7 ΠΌΠ΅ΡΡΡΠ΅Π² Π½Π°Π·Π°Π΄ | |
SUSE-SU-2024:2381-1 Security update for the Linux Kernel | ΠΎΠΊΠΎΠ»ΠΎ 2 Π»Π΅Ρ Π½Π°Π·Π°Π΄ | |||
SUSE-SU-2024:2360-1 Security update for the Linux Kernel | ΠΎΠΊΠΎΠ»ΠΎ 2 Π»Π΅Ρ Π½Π°Π·Π°Π΄ | |||
SUSE-SU-2024:2561-1 Security update for the Linux Kernel | ΠΎΠΊΠΎΠ»ΠΎ 2 Π»Π΅Ρ Π½Π°Π·Π°Π΄ | |||
SUSE-SU-2024:2394-1 Security update for the Linux Kernel | ΠΎΠΊΠΎΠ»ΠΎ 2 Π»Π΅Ρ Π½Π°Π·Π°Π΄ | |||
SUSE-SU-2024:2372-1 Security update for the Linux Kernel | ΠΎΠΊΠΎΠ»ΠΎ 2 Π»Π΅Ρ Π½Π°Π·Π°Π΄ | |||
SUSE-SU-2024:2571-1 Security update for the Linux Kernel | ΠΎΠΊΠΎΠ»ΠΎ 2 Π»Π΅Ρ Π½Π°Π·Π°Π΄ | |||
SUSE-SU-2024:2896-1 Security update for the Linux Kernel | ΠΏΠΎΡΡΠΈ 2 Π³ΠΎΠ΄Π° Π½Π°Π·Π°Π΄ | |||
SUSE-SU-2024:2939-1 Security update for the Linux Kernel | ΠΏΠΎΡΡΠΈ 2 Π³ΠΎΠ΄Π° Π½Π°Π·Π°Π΄ | |||
SUSE-SU-2024:2973-1 Security update for the Linux Kernel | ΠΏΠΎΡΡΠΈ 2 Π³ΠΎΠ΄Π° Π½Π°Π·Π°Π΄ |
Π£ΡΠ·Π²ΠΈΠΌΠΎΡΡΠ΅ΠΉ Π½Π° ΡΡΡΠ°Π½ΠΈΡΡ