First published: Tue Nov 19 2024(Updated: )
In the Linux kernel, the following vulnerability has been resolved: dm: fix a crash if blk_alloc_disk fails If blk_alloc_disk fails, the variable md->disk is set to an error value. cleanup_mapped_device will see that md->disk is non-NULL and it will attempt to access it, causing a crash on this statement "md->disk->private_data = NULL;".
Credit: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Affected Software | Affected Version | How to fix |
---|---|---|
Linux Kernel | <6.11.8 | |
Linux Kernel | =6.12-rc1 | |
Linux Kernel | =6.12-rc2 | |
Linux Kernel | =6.12-rc3 | |
Linux Kernel | =6.12-rc4 | |
Linux Kernel | =6.12-rc5 | |
Linux Kernel | =6.12-rc6 | |
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 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2024-50277 is classified as a moderate severity vulnerability in the Linux kernel.
To fix CVE-2024-50277, update your Linux kernel to a patched version ideally beyond 6.11.8.
CVE-2024-50277 affects Linux kernel versions up to 6.11.8 and the 6.12 release candidates.
CVE-2024-50277 addresses a crash vulnerability when blk_alloc_disk fails and a subsequent access to a non-NULL disk occurs.
There are no recommended workarounds for CVE-2024-50277, thus applying the kernel update is necessary.