CVE-2024-50280: dm cache: fix flushing uninitialized delayed_work on cache_ctr error

Published Nov 19, 2024
·
Updated

In the Linux kernel, the following vulnerability has been resolved:

dm cache: fix flushing uninitialized delayedwork on cachectr error

An unexpected WARNON from flushwork() may occur when cache creation fails, caused by destroying the uninitialized delayedwork waker in the error path of cachecreate(). For example, the warning appears on the superblock checksum error.

Reproduce steps:

dmsetup create cmeta --table "0 8192 linear /dev/sdc 0" dmsetup create cdata --table "0 65536 linear /dev/sdc 8192" dmsetup create corig --table "0 524288 linear /dev/sdc 262144" dd if=/dev/urandom of=/dev/mapper/cmeta bs=4k count=1 oflag=direct dmsetup create cache --table "0 524288 cache /dev/mapper/cmeta \ /dev/mapper/cdata /dev/mapper/corig 128 2 metadata2 writethrough smq 0"

Kernel logs:

(snip) WARNING: CPU: 0 PID: 84 at kernel/workqueue.c:4178 flushwork+0x5d4/0x890

Fix by pulling out the canceldelayedworksync() from the constructor's error path. This patch doesn't affect the use-after-free fix for concurrent dmresume and dmdestroy (commit 6a459d8edbdb ("dm cache: Fix UAF in destroy()")) as cachedtr is not changed.

Other sources

This CVE was automatically created from a reference found in an email or other text. If you are reading this, then this CVE entry is probably erroneous, since this text should be replaced by the official CVE description automatically.

Launchpad

Affected Software

19 affected componentsFixes available
Linux Linux kernel
Linux Linux kernel>=4.9.337<4.10
Linux Linux kernel>=4.14.303<4.15
Linux Linux kernel>=4.19.270<4.20
Linux Linux kernel>=5.4.229<5.5
Linux Linux kernel>=5.10.163<5.11
Linux Linux kernel>=5.15.87<5.16
Linux Linux kernel>=6.0.18<6.1
Linux Linux kernel>=6.1.4<6.1.117
Linux Linux kernel>=6.2<6.6.61
Linux Linux kernel>=6.7<6.11.8
Linux Linux kernel=6.12-rc1
Linux Linux kernel=6.12-rc2
Linux Linux kernel=6.12-rc3
Linux Linux kernel=6.12-rc4
Linux Linux kernel=6.12-rc5
Linux Linux kernel=6.12-rc6
debian/linux<=5.10.223-1, <=5.10.234-1
6.1.129-16.1.135-16.12.22-16.12.25-1
debian/linux-6.1
6.1.129-1~deb11u1

Event History

Nov 19, 2024
CVE Published
via MITRE·01:30 AM
Data Sourced
via MITRE·01:30 AM
Description
Data Sourced
via NVD·02:16 AM
RemedyDescriptionSeverityWeaknessAffected Software
Feb 20, 2025
Data Sourced
via Launchpad·12:50 AM
Description
Apr 29, 2025
Data Sourced
via Ubuntu·01:00 AM
RemedyDescriptionSeverityAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2024-50280?

The severity of CVE-2024-50280 is categorized as moderate due to potential instability in the Linux kernel.

2

How do I fix CVE-2024-50280?

To fix CVE-2024-50280, ensure you update to the latest version of the Linux kernel where the vulnerability has been addressed.

3

What impact does CVE-2024-50280 have on system security?

CVE-2024-50280 could lead to system instability and unexpected warnings during cache creation failures in the Linux kernel.

4

Which versions of the Linux kernel are affected by CVE-2024-50280?

CVE-2024-50280 affects multiple versions of the Linux kernel, particularly those before the patch release that resolves the issue.

5

Is CVE-2024-50280 remotely exploitable?

CVE-2024-50280 does not appear to be remotely exploitable, focusing instead on local kernel operations.

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.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203