medium
5.5
CWE
476
Advisory Published
CVE Published
Updated

CVE-2024-26802: stmmac: Clear variable when destroying workqueue

First published: Thu Apr 04 2024(Updated: )

In the Linux kernel, the following vulnerability has been resolved: stmmac: Clear variable when destroying workqueue Currently when suspending driver and stopping workqueue it is checked whether workqueue is not NULL and if so, it is destroyed. Function destroy_workqueue() does drain queue and does clear variable, but it does not set workqueue variable to NULL. This can cause kernel/module panic if code attempts to clear workqueue that was not initialized. This scenario is possible when resuming suspended driver in stmmac_resume(), because there is no handling for failed stmmac_hw_setup(), which can fail and return if DMA engine has failed to initialize, and workqueue is initialized after DMA engine. Should DMA engine fail to initialize, resume will proceed normally, but interface won't work and TX queue will eventually timeout, causing 'Reset adapter' error. This then does destroy workqueue during reset process. And since workqueue is initialized after DMA engine and can be skipped, it will cause kernel/module panic. To secure against this possible crash, set workqueue variable to NULL when destroying workqueue. Log/backtrace from crash goes as follows: [88.031977]------------[ cut here ]------------ [88.031985]NETDEV WATCHDOG: eth0 (sxgmac): transmit queue 1 timed out [88.032017]WARNING: CPU: 0 PID: 0 at net/sched/sch_generic.c:477 dev_watchdog+0x390/0x398 <Skipping backtrace for watchdog timeout> [88.032251]---[ end trace e70de432e4d5c2c0 ]--- [88.032282]sxgmac 16d88000.ethernet eth0: Reset adapter. [88.036359]------------[ cut here ]------------ [88.036519]Call trace: [88.036523] flush_workqueue+0x3e4/0x430 [88.036528] drain_workqueue+0xc4/0x160 [88.036533] destroy_workqueue+0x40/0x270 [88.036537] stmmac_fpe_stop_wq+0x4c/0x70 [88.036541] stmmac_release+0x278/0x280 [88.036546] __dev_close_many+0xcc/0x158 [88.036551] dev_close_many+0xbc/0x190 [88.036555] dev_close.part.0+0x70/0xc0 [88.036560] dev_close+0x24/0x30 [88.036564] stmmac_service_task+0x110/0x140 [88.036569] process_one_work+0x1d8/0x4a0 [88.036573] worker_thread+0x54/0x408 [88.036578] kthread+0x164/0x170 [88.036583] ret_from_fork+0x10/0x20 [88.036588]---[ end trace e70de432e4d5c2c1 ]--- [88.036597]Unable to handle kernel NULL pointer dereference at virtual address 0000000000000004

Credit: 416baaa9-dc9f-4396-8d5f-8c081fb06d67 416baaa9-dc9f-4396-8d5f-8c081fb06d67

Affected SoftwareAffected VersionHow to fix
redhat/kernel<5.15.151
5.15.151
redhat/kernel<6.1.81
6.1.81
redhat/kernel<6.6.21
6.6.21
redhat/kernel<6.7.9
6.7.9
redhat/kernel<6.8
6.8
Linux Kernel>=5.13<5.15.151
Linux Kernel>=5.16<6.1.81
Linux Kernel>=6.2<6.6.21
Linux Kernel>=6.7<6.7.9
Linux Kernel=6.8-rc1
Linux Kernel=6.8-rc2
Linux Kernel=6.8-rc3
Linux Kernel=6.8-rc4
Linux Kernel=6.8-rc5
Linux Kernel=6.8-rc6
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

Remedy

https://git.kernel.org/stable/c/17ccd9798fe0beda3db212cfa3ebe373f605cbd6

Remedy

https://git.kernel.org/stable/c/699b103e48ce32d03fc86c35b37ee8ae4288c7e3

Remedy

https://git.kernel.org/stable/c/8af411bbba1f457c33734795f024d0ef26d0963f

Remedy

https://git.kernel.org/stable/c/8e99556301172465c8fe33c7f78c39a3d4ce8462

Remedy

https://git.kernel.org/stable/c/f72cf22dccc94038cbbaa1029cb575bf52e5cbc8

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Read MoreStart Free Trial

Reference Links

Parent vulnerabilities

(Appears in the following advisories)

Frequently Asked Questions

  • What is the severity of CVE-2024-26802?

    CVE-2024-26802 has a medium severity rating due to its potential impact on system performance and stability.

  • How do I fix CVE-2024-26802?

    To fix CVE-2024-26802, update to the appropriate kernel version: Red Hat kernels 5.15.151, 6.1.81, 6.6.21, 6.7.9, 6.8, or Debian Linux versions 5.10.223-1, 5.10.226-1, 6.1.123-1, 6.1.119-1, 6.12.11-1, or 6.12.12-1.

  • Which versions of the Linux kernel are vulnerable to CVE-2024-26802?

    CVE-2024-26802 affects various Red Hat kernel versions up to 5.15.151, 6.1.81, 6.6.21, 6.7.9, 6.8 and specific Debian Linux kernel versions.

  • Is CVE-2024-26802 specific to a certain type of Linux distribution?

    Yes, CVE-2024-26802 primarily affects Red Hat and Debian distributions of the Linux kernel.

  • What impact could CVE-2024-26802 have on my system?

    CVE-2024-26802 could lead to performance issues or instability if the workqueue is improperly handled during driver suspension.

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203