medium
5.5
Advisory Published
CVE Published
Updated

CVE-2024-40904: USB: class: cdc-wdm: Fix CPU lockup caused by excessive log messages

First published: Fri Jul 12 2024(Updated: )

In the Linux kernel, the following vulnerability has been resolved: USB: class: cdc-wdm: Fix CPU lockup caused by excessive log messages The syzbot fuzzer found that the interrupt-URB completion callback in the cdc-wdm driver was taking too long, and the driver's immediate resubmission of interrupt URBs with -EPROTO status combined with the dummy-hcd emulation to cause a CPU lockup: cdc_wdm 1-1:1.0: nonzero urb status received: -71 cdc_wdm 1-1:1.0: wdm_int_callback - 0 bytes watchdog: BUG: soft lockup - CPU#0 stuck for 26s! [syz-executor782:6625] CPU#0 Utilization every 4s during lockup: #1: 98% system, 0% softirq, 3% hardirq, 0% idle #2: 98% system, 0% softirq, 3% hardirq, 0% idle #3: 98% system, 0% softirq, 3% hardirq, 0% idle #4: 98% system, 0% softirq, 3% hardirq, 0% idle #5: 98% system, 1% softirq, 3% hardirq, 0% idle Modules linked in: irq event stamp: 73096 hardirqs last enabled at (73095): [<ffff80008037bc00>] console_emit_next_record kernel/printk/printk.c:2935 [inline] hardirqs last enabled at (73095): [<ffff80008037bc00>] console_flush_all+0x650/0xb74 kernel/printk/printk.c:2994 hardirqs last disabled at (73096): [<ffff80008af10b00>] __el1_irq arch/arm64/kernel/entry-common.c:533 [inline] hardirqs last disabled at (73096): [<ffff80008af10b00>] el1_interrupt+0x24/0x68 arch/arm64/kernel/entry-common.c:551 softirqs last enabled at (73048): [<ffff8000801ea530>] softirq_handle_end kernel/softirq.c:400 [inline] softirqs last enabled at (73048): [<ffff8000801ea530>] handle_softirqs+0xa60/0xc34 kernel/softirq.c:582 softirqs last disabled at (73043): [<ffff800080020de8>] __do_softirq+0x14/0x20 kernel/softirq.c:588 CPU: 0 PID: 6625 Comm: syz-executor782 Tainted: G W 6.10.0-rc2-syzkaller-g8867bbd4a056 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/02/2024 Testing showed that the problem did not occur if the two error messages -- the first two lines above -- were removed; apparently adding material to the kernel log takes a surprisingly large amount of time. In any case, the best approach for preventing these lockups and to avoid spamming the log with thousands of error messages per second is to ratelimit the two dev_err() calls. Therefore we replace them with dev_err_ratelimited().

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

Affected SoftwareAffected VersionHow to fix
redhat/kernel<4.19.317
4.19.317
redhat/kernel<5.4.279
5.4.279
redhat/kernel<5.10.221
5.10.221
redhat/kernel<5.15.162
5.15.162
redhat/kernel<6.1.95
6.1.95
redhat/kernel<6.6.35
6.6.35
redhat/kernel<6.9.6
6.9.6
redhat/kernel<6.10
6.10
Linux Kernel>=2.6.28<4.19.317
Linux Kernel>=4.20<5.4.279
Linux Kernel>=5.5<5.10.221
Linux Kernel>=5.11<5.15.162
Linux Kernel>=5.16<6.1.95
Linux Kernel>=6.2<6.6.35
Linux Kernel>=6.7<6.9.6
Linux Kernel=6.10-rc1
Linux Kernel=6.10-rc2
Linux Kernel=6.10-rc3
debian/linux
5.10.223-1
5.10.234-1
6.1.129-1
6.1.128-1
6.12.20-1
6.12.21-1
debian/linux-6.1
6.1.129-1~deb11u1
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

Remedy

https://git.kernel.org/stable/c/02a4c0499fc3a02e992b4c69a9809912af372d94

Remedy

https://git.kernel.org/stable/c/05b2cd6d33f700597e6f081b53c668a226a96d28

Remedy

https://git.kernel.org/stable/c/217d1f44fff560b3995a685a60aa66e55a7f0f56

Remedy

https://git.kernel.org/stable/c/22f00812862564b314784167a89f27b444f82a46

Remedy

https://git.kernel.org/stable/c/53250b54c92fe087fd4b0c48f85529efe1ebd879

Remedy

https://git.kernel.org/stable/c/72a3fe36cf9f0d030865e571f45a40f9c1e07e8a

Remedy

https://git.kernel.org/stable/c/82075aff7ffccb1e72b0ac8aa349e473624d857c

Remedy

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

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-40904?

    CVE-2024-40904 has been categorized as a moderate severity vulnerability in the Linux kernel relating to CPU lockup caused by excessive log messages.

  • How do I fix CVE-2024-40904?

    To fix CVE-2024-40904, update your Linux kernel to version 4.19.317, 5.4.279, 5.10.221, 5.15.162, 6.1.95, or later versions as specified by your distribution.

  • Which systems are affected by CVE-2024-40904?

    CVE-2024-40904 affects multiple versions of the Linux kernel, particularly those prior to the specified patched versions.

  • What component of the Linux kernel does CVE-2024-40904 affect?

    CVE-2024-40904 specifically affects the cdc-wdm driver component of the Linux kernel.

  • Is there a workaround for CVE-2024-40904?

    There is no documented workaround for CVE-2024-40904, and updating to a patched version is recommended for resolution.

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