CVE-2024-50280: dm cache: fix flushing uninitialized delayed_work on cache_ctr error
First published: Tue Nov 19 2024(Updated: )
In the Linux kernel, the following vulnerability has been resolved: dm cache: fix flushing uninitialized delayed_work on cache_ctr error An unexpected WARN_ON from flush_work() may occur when cache creation fails, caused by destroying the uninitialized delayed_work waker in the error path of cache_create(). 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 __flush_work+0x5d4/0x890 Fix by pulling out the cancel_delayed_work_sync() from the constructor's error path. This patch doesn't affect the use-after-free fix for concurrent dm_resume and dm_destroy (commit 6a459d8edbdb ("dm cache: Fix UAF in destroy()")) as cache_dtr is not changed.
Credit: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Linux Kernel | ||
| debian/linux | <=5.10.223-1<=5.10.226-1 | 6.1.123-1 6.1.128-1 6.12.12-1 6.12.15-1 |
| debian/linux-6.1 | 6.1.119-1~deb11u1 |
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.
Reference Links
- https://git.kernel.org/stable/c/135496c208ba26fd68cdef10b64ed7a91ac9a7ff
- https://git.kernel.org/stable/c/5a754d3c771280f2d06bf8ab716d6a0d36ca256e
- https://git.kernel.org/stable/c/8cc12dab635333c4ea28e72d7b947be7d0543c2c
- https://git.kernel.org/stable/c/aee3ecda73ce13af7c3e556383342b57e6bd0718
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-50280
- https://nvd.nist.gov/vuln/detail/CVE-2024-50280
- https://launchpad.net/bugs/cve/CVE-2024-50280
- https://security-tracker.debian.org/tracker/CVE-2024-50280
- https://ubuntu.com/security/CVE-2024-50280
- https://git.kernel.org/linus/135496c208ba26fd68cdef10b64ed7a91ac9a7ff
Frequently Asked Questions
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.
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.
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.
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.
Is CVE-2024-50280 remotely exploitable?
CVE-2024-50280 does not appear to be remotely exploitable, focusing instead on local kernel operations.
- agent/title
- agent/type
- agent/first-publish-date
- agent/author
- collector/nvd-api
- source/NVD
- agent/severity
- agent/weakness
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/guess-ai
- agent/software-canonical-lookup
- agent/software-canonical-lookup-request
- collector/usn-cve
- source/Ubuntu
- collector/launchpad-cve
- source/Launchpad
- collector/security-tracker-debian
- source/Debian
- agent/references
- agent/source
- agent/softwarecombine
- agent/tags
- agent/description
- agent/event
- vendor/linux
- canonical/linux kernel
- package-manager/debian