First published: Fri Jul 12 2024(Updated: )
In the Linux kernel, the following vulnerability has been resolved: wifi: mt76: mt7921s: fix potential hung tasks during chip recovery During chip recovery (e.g. chip reset), there is a possible situation that kernel worker reset_work is holding the lock and waiting for kernel thread stat_worker to be parked, while stat_worker is waiting for the release of the same lock. It causes a deadlock resulting in the dumping of hung tasks messages and possible rebooting of the device. This patch prevents the execution of stat_worker during the chip recovery.
Credit: 416baaa9-dc9f-4396-8d5f-8c081fb06d67 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Affected Software | Affected Version | How to fix |
---|---|---|
redhat/kernel | <6.1.96 | 6.1.96 |
redhat/kernel | <6.6.36 | 6.6.36 |
redhat/kernel | <6.9.7 | 6.9.7 |
redhat/kernel | <6.10 | 6.10 |
Linux kernel | <6.1.96 | |
Linux kernel | >=6.2<6.6.36 | |
Linux kernel | >=6.7<6.9.7 | |
Linux Kernel | <6.1.96 | |
Linux Kernel | >=6.2<6.6.36 | |
Linux Kernel | >=6.7<6.9.7 | |
IBM Security Verify Governance - Identity Manager | <=ISVG 10.0.2 | |
IBM Security Verify Governance, Identity Manager Software Stack | <=ISVG 10.0.2 | |
IBM Security Verify Governance, Identity Manager Virtual Appliance | <=ISVG 10.0.2 | |
IBM Security Verify Governance Identity Manager Container | <=ISVG 10.0.2 | |
debian/linux | <=5.10.223-1<=5.10.234-1 | 6.1.129-1 6.1.128-1 6.12.21-1 6.12.22-1 |
debian/linux-6.1 | 6.1.129-1~deb11u1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2024-40977 has been classified with a moderate severity level due to potential risks during chip recovery in the Linux kernel.
To fix CVE-2024-40977, update your kernel to versions 6.1.96, 6.6.36, 6.9.7, or a later fixed version.
CVE-2024-40977 affects several versions of the Linux kernel across various distributions, including Red Hat and Debian.
Symptoms of CVE-2024-40977 may include hung tasks during chip recovery operations in systems using affected kernel versions.
Currently, the most reliable approach to mitigateg CVE-2024-40977 is to apply the recommended kernel updates as soon as possible.