ΠΠΎΠ»ΠΈΡΠ΅ΡΡΠ²ΠΎ 16
ΠΠΎΠ»ΠΈΡΠ΅ΡΡΠ²ΠΎ 16
GHSA-772q-fwqp-96rg
In the Linux kernel, the following vulnerability has been resolved: nvme-pci: fix race condition between reset and nvme_dev_disable() nvme_dev_disable() modifies the dev->online_queues field, therefore nvme_pci_update_nr_queues() should avoid racing against it, otherwise we could end up passing invalid values to blk_mq_update_nr_hw_queues(). WARNING: CPU: 39 PID: 61303 at drivers/pci/msi/api.c:347 pci_irq_get_affinity+0x187/0x210 Workqueue: nvme-reset-wq nvme_reset_work [nvme] RIP: 0010:pci_irq_get_affinity+0x187/0x210 Call Trace: <TASK> ? blk_mq_pci_map_queues+0x87/0x3c0 ? pci_irq_get_affinity+0x187/0x210 blk_mq_pci_map_queues+0x87/0x3c0 nvme_pci_map_queues+0x189/0x460 [nvme] blk_mq_update_nr_hw_queues+0x2a/0x40 nvme_reset_work+0x1be/0x2a0 [nvme] Fix the bug by locking the shutdown_lock mutex before using dev->online_queues. Give up if nvme_dev_disable() is running or if it has been executed already.
CVE-2024-50135
In the Linux kernel, the following vulnerability has been resolved: nvme-pci: fix race condition between reset and nvme_dev_disable() nvme_dev_disable() modifies the dev->online_queues field, therefore nvme_pci_update_nr_queues() should avoid racing against it, otherwise we could end up passing invalid values to blk_mq_update_nr_hw_queues(). WARNING: CPU: 39 PID: 61303 at drivers/pci/msi/api.c:347 pci_irq_get_affinity+0x187/0x210 Workqueue: nvme-reset-wq nvme_reset_work [nvme] RIP: 0010:pci_irq_get_affinity+0x187/0x210 Call Trace: <TASK> ? blk_mq_pci_map_queues+0x87/0x3c0 ? pci_irq_get_affinity+0x187/0x210 blk_mq_pci_map_queues+0x87/0x3c0 nvme_pci_map_queues+0x189/0x460 [nvme] blk_mq_update_nr_hw_queues+0x2a/0x40 nvme_reset_work+0x1be/0x2a0 [nvme] Fix the bug by locking the shutdown_lock mutex before using dev->online_queues. Give up if nvme_dev_disable() is running or if it has been executed already.
CVE-2024-50135
In the Linux kernel, the following vulnerability has been resolved: nvme-pci: fix race condition between reset and nvme_dev_disable() nvme_dev_disable() modifies the dev->online_queues field, therefore nvme_pci_update_nr_queues() should avoid racing against it, otherwise we could end up passing invalid values to blk_mq_update_nr_hw_queues(). WARNING: CPU: 39 PID: 61303 at drivers/pci/msi/api.c:347 pci_irq_get_affinity+0x187/0x210 Workqueue: nvme-reset-wq nvme_reset_work [nvme] RIP: 0010:pci_irq_get_affinity+0x187/0x210 Call Trace: <TASK> ? blk_mq_pci_map_queues+0x87/0x3c0 ? pci_irq_get_affinity+0x187/0x210 blk_mq_pci_map_queues+0x87/0x3c0 nvme_pci_map_queues+0x189/0x460 [nvme] blk_mq_update_nr_hw_queues+0x2a/0x40 nvme_reset_work+0x1be/0x2a0 [nvme] Fix the bug by locking the shutdown_lock mutex before using dev->online_queues. Give up if nvme_dev_disable() is running or if it has been executed already.
CVE-2024-50135
In the Linux kernel, the following vulnerability has been resolved: nvme-pci: fix race condition between reset and nvme_dev_disable() nvme_dev_disable() modifies the dev->online_queues field, therefore nvme_pci_update_nr_queues() should avoid racing against it, otherwise we could end up passing invalid values to blk_mq_update_nr_hw_queues(). WARNING: CPU: 39 PID: 61303 at drivers/pci/msi/api.c:347 pci_irq_get_affinity+0x187/0x210 Workqueue: nvme-reset-wq nvme_reset_work [nvme] RIP: 0010:pci_irq_get_affinity+0x187/0x210 Call Trace: <TASK> ? blk_mq_pci_map_queues+0x87/0x3c0 ? pci_irq_get_affinity+0x187/0x210 blk_mq_pci_map_queues+0x87/0x3c0 nvme_pci_map_queues+0x189/0x460 [nvme] blk_mq_update_nr_hw_queues+0x2a/0x40 nvme_reset_work+0x1be/0x2a0 [nvme] Fix the bug by locking the shutdown_lock mutex before using dev->online_queues. Give up if nvme_dev_disable() is running or if it has been executed already.
CVE-2024-50135
nvme-pci: fix race condition between reset and nvme_dev_disable()
CVE-2024-50135
In the Linux kernel, the following vulnerability has been resolved: n ...
BDU:2025-13909
Π£ΡΠ·Π²ΠΈΠΌΠΎΡΡΡ ΡΡΠ½ΠΊΡΠΈΠΈ nvme_pci_nr_maps() ΠΌΠΎΠ΄ΡΠ»Ρ drivers/nvme/host/pci.c Π΄ΡΠ°ΠΉΠ²Π΅ΡΠ° ΠΏΠΎΠ΄Π΄Π΅ΡΠΆΠΊΠΈ NVME ΡΠ΄ΡΠ° ΠΎΠΏΠ΅ΡΠ°ΡΠΈΠΎΠ½Π½ΠΎΠΉ ΡΠΈΡΡΠ΅ΠΌΡ Linux, ΠΏΠΎΠ·Π²ΠΎΠ»ΡΡΡΠ°Ρ Π½Π°ΡΡΡΠΈΡΠ΅Π»Ρ Π²ΡΠ·Π²Π°ΡΡ ΠΎΡΠΊΠ°Π· Π² ΠΎΠ±ΡΠ»ΡΠΆΠΈΠ²Π°Π½ΠΈΠΈ
SUSE-SU-2025:0035-1
Security update for the Linux Kernel
SUSE-SU-2024:4367-1
Security update for the Linux Kernel
SUSE-SU-2024:4316-1
Security update for the Linux Kernel
SUSE-SU-2024:4376-1
Security update for the Linux Kernel
SUSE-SU-2024:4315-1
Security update for the Linux Kernel
SUSE-SU-2024:4314-1
Security update for the Linux Kernel
SUSE-SU-2024:4364-1
Security update for the Linux Kernel
SUSE-SU-2024:4387-1
Security update for the Linux Kernel
SUSE-SU-2024:4318-1
Security update for the Linux Kernel
Π£ΡΠ·Π²ΠΈΠΌΠΎΡΡΠ΅ΠΉ Π½Π° ΡΡΡΠ°Π½ΠΈΡΡ
Π£ΡΠ·Π²ΠΈΠΌΠΎΡΡΡ | CVSS | EPSS | ΠΠΏΡΠ±Π»ΠΈΠΊΠΎΠ²Π°Π½ΠΎ | |
|---|---|---|---|---|
| GHSA-772q-fwqp-96rg In the Linux kernel, the following vulnerability has been resolved: nvme-pci: fix race condition between reset and nvme_dev_disable() nvme_dev_disable() modifies the dev->online_queues field, therefore nvme_pci_update_nr_queues() should avoid racing against it, otherwise we could end up passing invalid values to blk_mq_update_nr_hw_queues(). WARNING: CPU: 39 PID: 61303 at drivers/pci/msi/api.c:347 pci_irq_get_affinity+0x187/0x210 Workqueue: nvme-reset-wq nvme_reset_work [nvme] RIP: 0010:pci_irq_get_affinity+0x187/0x210 Call Trace: <TASK> ? blk_mq_pci_map_queues+0x87/0x3c0 ? pci_irq_get_affinity+0x187/0x210 blk_mq_pci_map_queues+0x87/0x3c0 nvme_pci_map_queues+0x189/0x460 [nvme] blk_mq_update_nr_hw_queues+0x2a/0x40 nvme_reset_work+0x1be/0x2a0 [nvme] Fix the bug by locking the shutdown_lock mutex before using dev->online_queues. Give up if nvme_dev_disable() is running or if it has been executed already. | CVSS3: 4.7 | 0% ΠΠΈΠ·ΠΊΠΈΠΉ | ΠΏΠΎΡΡΠΈ 2 Π³ΠΎΠ΄Π° Π½Π°Π·Π°Π΄ |
 | CVE-2024-50135 In the Linux kernel, the following vulnerability has been resolved: nvme-pci: fix race condition between reset and nvme_dev_disable() nvme_dev_disable() modifies the dev->online_queues field, therefore nvme_pci_update_nr_queues() should avoid racing against it, otherwise we could end up passing invalid values to blk_mq_update_nr_hw_queues(). WARNING: CPU: 39 PID: 61303 at drivers/pci/msi/api.c:347 pci_irq_get_affinity+0x187/0x210 Workqueue: nvme-reset-wq nvme_reset_work [nvme] RIP: 0010:pci_irq_get_affinity+0x187/0x210 Call Trace: <TASK> ? blk_mq_pci_map_queues+0x87/0x3c0 ? pci_irq_get_affinity+0x187/0x210 blk_mq_pci_map_queues+0x87/0x3c0 nvme_pci_map_queues+0x189/0x460 [nvme] blk_mq_update_nr_hw_queues+0x2a/0x40 nvme_reset_work+0x1be/0x2a0 [nvme] Fix the bug by locking the shutdown_lock mutex before using dev->online_queues. Give up if nvme_dev_disable() is running or if it has been executed already. | CVSS3: 4.7 | 0% ΠΠΈΠ·ΠΊΠΈΠΉ | ΠΏΠΎΡΡΠΈ 2 Π³ΠΎΠ΄Π° Π½Π°Π·Π°Π΄ |
 | CVE-2024-50135 In the Linux kernel, the following vulnerability has been resolved: nvme-pci: fix race condition between reset and nvme_dev_disable() nvme_dev_disable() modifies the dev->online_queues field, therefore nvme_pci_update_nr_queues() should avoid racing against it, otherwise we could end up passing invalid values to blk_mq_update_nr_hw_queues(). WARNING: CPU: 39 PID: 61303 at drivers/pci/msi/api.c:347 pci_irq_get_affinity+0x187/0x210 Workqueue: nvme-reset-wq nvme_reset_work [nvme] RIP: 0010:pci_irq_get_affinity+0x187/0x210 Call Trace: <TASK> ? blk_mq_pci_map_queues+0x87/0x3c0 ? pci_irq_get_affinity+0x187/0x210 blk_mq_pci_map_queues+0x87/0x3c0 nvme_pci_map_queues+0x189/0x460 [nvme] blk_mq_update_nr_hw_queues+0x2a/0x40 nvme_reset_work+0x1be/0x2a0 [nvme] Fix the bug by locking the shutdown_lock mutex before using dev->online_queues. Give up if nvme_dev_disable() is running or if it has been executed already. | CVSS3: 4.7 | 0% ΠΠΈΠ·ΠΊΠΈΠΉ | ΠΏΠΎΡΡΠΈ 2 Π³ΠΎΠ΄Π° Π½Π°Π·Π°Π΄ |
 | CVE-2024-50135 In the Linux kernel, the following vulnerability has been resolved: nvme-pci: fix race condition between reset and nvme_dev_disable() nvme_dev_disable() modifies the dev->online_queues field, therefore nvme_pci_update_nr_queues() should avoid racing against it, otherwise we could end up passing invalid values to blk_mq_update_nr_hw_queues(). WARNING: CPU: 39 PID: 61303 at drivers/pci/msi/api.c:347 pci_irq_get_affinity+0x187/0x210 Workqueue: nvme-reset-wq nvme_reset_work [nvme] RIP: 0010:pci_irq_get_affinity+0x187/0x210 Call Trace: <TASK> ? blk_mq_pci_map_queues+0x87/0x3c0 ? pci_irq_get_affinity+0x187/0x210 blk_mq_pci_map_queues+0x87/0x3c0 nvme_pci_map_queues+0x189/0x460 [nvme] blk_mq_update_nr_hw_queues+0x2a/0x40 nvme_reset_work+0x1be/0x2a0 [nvme] Fix the bug by locking the shutdown_lock mutex before using dev->online_queues. Give up if nvme_dev_disable() is running or if it has been executed already. | CVSS3: 4.7 | 0% ΠΠΈΠ·ΠΊΠΈΠΉ | ΠΏΠΎΡΡΠΈ 2 Π³ΠΎΠ΄Π° Π½Π°Π·Π°Π΄ |
 | CVE-2024-50135 nvme-pci: fix race condition between reset and nvme_dev_disable() | 0% ΠΠΈΠ·ΠΊΠΈΠΉ | 6 ΠΌΠ΅ΡΡΡΠ΅Π² Π½Π°Π·Π°Π΄ | |
| CVE-2024-50135 In the Linux kernel, the following vulnerability has been resolved: n ... | CVSS3: 4.7 | 0% ΠΠΈΠ·ΠΊΠΈΠΉ | ΠΏΠΎΡΡΠΈ 2 Π³ΠΎΠ΄Π° Π½Π°Π·Π°Π΄ |
 | BDU:2025-13909 Π£ΡΠ·Π²ΠΈΠΌΠΎΡΡΡ ΡΡΠ½ΠΊΡΠΈΠΈ nvme_pci_nr_maps() ΠΌΠΎΠ΄ΡΠ»Ρ drivers/nvme/host/pci.c Π΄ΡΠ°ΠΉΠ²Π΅ΡΠ° ΠΏΠΎΠ΄Π΄Π΅ΡΠΆΠΊΠΈ NVME ΡΠ΄ΡΠ° ΠΎΠΏΠ΅ΡΠ°ΡΠΈΠΎΠ½Π½ΠΎΠΉ ΡΠΈΡΡΠ΅ΠΌΡ Linux, ΠΏΠΎΠ·Π²ΠΎΠ»ΡΡΡΠ°Ρ Π½Π°ΡΡΡΠΈΡΠ΅Π»Ρ Π²ΡΠ·Π²Π°ΡΡ ΠΎΡΠΊΠ°Π· Π² ΠΎΠ±ΡΠ»ΡΠΆΠΈΠ²Π°Π½ΠΈΠΈ | CVSS3: 4.7 | 0% ΠΠΈΠ·ΠΊΠΈΠΉ | ΠΏΠΎΡΡΠΈ 2 Π³ΠΎΠ΄Π° Π½Π°Π·Π°Π΄ |
 | SUSE-SU-2025:0035-1 Security update for the Linux Kernel | Π±ΠΎΠ»ΡΡΠ΅ 1 Π³ΠΎΠ΄Π° Π½Π°Π·Π°Π΄ | ||
| SUSE-SU-2024:4367-1 Security update for the Linux Kernel | Π±ΠΎΠ»ΡΡΠ΅ 1 Π³ΠΎΠ΄Π° Π½Π°Π·Π°Π΄ | ||
| SUSE-SU-2024:4316-1 Security update for the Linux Kernel | Π±ΠΎΠ»ΡΡΠ΅ 1 Π³ΠΎΠ΄Π° Π½Π°Π·Π°Π΄ | ||
| SUSE-SU-2024:4376-1 Security update for the Linux Kernel | Π±ΠΎΠ»ΡΡΠ΅ 1 Π³ΠΎΠ΄Π° Π½Π°Π·Π°Π΄ | ||
| SUSE-SU-2024:4315-1 Security update for the Linux Kernel | Π±ΠΎΠ»ΡΡΠ΅ 1 Π³ΠΎΠ΄Π° Π½Π°Π·Π°Π΄ | ||
| SUSE-SU-2024:4314-1 Security update for the Linux Kernel | Π±ΠΎΠ»ΡΡΠ΅ 1 Π³ΠΎΠ΄Π° Π½Π°Π·Π°Π΄ | ||
| SUSE-SU-2024:4364-1 Security update for the Linux Kernel | Π±ΠΎΠ»ΡΡΠ΅ 1 Π³ΠΎΠ΄Π° Π½Π°Π·Π°Π΄ | ||
| SUSE-SU-2024:4387-1 Security update for the Linux Kernel | Π±ΠΎΠ»ΡΡΠ΅ 1 Π³ΠΎΠ΄Π° Π½Π°Π·Π°Π΄ | ||
| SUSE-SU-2024:4318-1 Security update for the Linux Kernel | Π±ΠΎΠ»ΡΡΠ΅ 1 Π³ΠΎΠ΄Π° Π½Π°Π·Π°Π΄ |
Π£ΡΠ·Π²ΠΈΠΌΠΎΡΡΠ΅ΠΉ Π½Π° ΡΡΡΠ°Π½ΠΈΡΡ