CVE-2024-50153: Vulnerability in Linux Linux
In the Linux kernel, the following vulnerability has been resolved: scsi: target: core: Fix null-ptr-deref in target_alloc_device() There is a null-ptr-deref issue reported by KASAN: BUG: KASAN: null-ptr-deref in target_alloc_device+0xbc4/0xbe0 [target_core_mod] ... kasan_report+0xb9/0xf0 target_alloc_device+0xbc4/0xbe0 [target_core_mod] core_dev_setup_virtual_lun0+0xef/0x1f0 [target_core_mod] target_core_init_configfs+0x205/0x420 [target_core_mod] do_one_initcall+0xdd/0x4e0 ... entry_SYSCALL_64_after_hwframe+0x76/0x7e In target_alloc_device(), if allocing memory for dev queues fails, then dev will be freed by dev->transport->free_device(), but dev->transport is not initialized at that time, which will lead to a null pointer reference problem. Fixing this bug by freeing dev with hba->backend->ops->free_device().
AI Analysis
Technical Summary
CVE-2024-50153 is a vulnerability identified in the Linux kernel's SCSI target core module (target_core_mod). The issue arises in the function target_alloc_device(), which is responsible for allocating and initializing device structures for SCSI targets. Specifically, when memory allocation for device queues fails, the code attempts to free the partially allocated device structure by calling dev->transport->free_device(). However, at this point in execution, the dev->transport pointer has not yet been initialized, leading to a null pointer dereference (null-ptr-deref). This results in a kernel crash or panic, as detected by Kernel Address Sanitizer (KASAN). The root cause is improper handling of error conditions during device allocation, where the cleanup code references an uninitialized pointer. The fix involves changing the cleanup routine to use hba->backend->ops->free_device() instead, which is a valid and initialized pointer at the time of failure, thus preventing the null pointer dereference. This vulnerability affects certain versions of the Linux kernel as identified by specific commit hashes. No known exploits are reported in the wild as of the publication date (November 7, 2024). The vulnerability is a denial-of-service (DoS) type, as it causes a kernel crash, impacting system availability. It does not appear to allow privilege escalation or code execution directly. The flaw is triggered by failure in memory allocation during device queue setup, which could be induced by resource exhaustion or crafted inputs in environments where SCSI target functionality is used.
Potential Impact
For European organizations, the impact of CVE-2024-50153 primarily concerns systems running Linux kernels with SCSI target support enabled, such as storage servers, SAN gateways, or virtualization hosts that expose SCSI targets. A successful trigger of this vulnerability results in a kernel panic and system crash, causing denial of service. This can disrupt critical storage infrastructure, leading to downtime, data unavailability, and potential operational losses. Organizations relying on Linux-based storage solutions or virtualization platforms with target_core_mod enabled are at risk. While the vulnerability does not directly compromise confidentiality or integrity, the availability impact can be significant, especially in data centers or cloud environments supporting business-critical applications. European enterprises in finance, healthcare, telecommunications, and public sectors that operate Linux storage or virtualization infrastructure could face service interruptions. Additionally, the lack of known exploits suggests limited immediate threat, but the vulnerability could be leveraged in targeted attacks or combined with other exploits to amplify impact. The risk is heightened in environments where memory pressure or resource exhaustion can be induced by attackers or faulty workloads.
Mitigation Recommendations
1. Apply the official Linux kernel patches that fix CVE-2024-50153 as soon as they become available from trusted sources or Linux distribution vendors. 2. For organizations unable to immediately patch, consider disabling SCSI target functionality (target_core_mod) if it is not required, to eliminate the attack surface. 3. Monitor kernel logs and system stability for signs of null pointer dereference crashes related to target_alloc_device(). 4. Implement resource management controls to prevent memory exhaustion scenarios that could trigger the vulnerability, such as cgroup limits or memory quotas on relevant hosts. 5. Use kernel hardening features and runtime protections like KASAN in testing environments to detect similar issues proactively. 6. Maintain strict access controls and network segmentation around storage and virtualization hosts to limit exposure to untrusted users who might attempt to exploit this flaw. 7. Regularly update Linux kernel versions and subscribe to security advisories from Linux vendors and communities to stay informed about patches and related vulnerabilities.
Affected Countries
Germany, France, United Kingdom, Netherlands, Sweden, Finland, Italy, Spain
CVE-2024-50153: Vulnerability in Linux Linux
Description
In the Linux kernel, the following vulnerability has been resolved: scsi: target: core: Fix null-ptr-deref in target_alloc_device() There is a null-ptr-deref issue reported by KASAN: BUG: KASAN: null-ptr-deref in target_alloc_device+0xbc4/0xbe0 [target_core_mod] ... kasan_report+0xb9/0xf0 target_alloc_device+0xbc4/0xbe0 [target_core_mod] core_dev_setup_virtual_lun0+0xef/0x1f0 [target_core_mod] target_core_init_configfs+0x205/0x420 [target_core_mod] do_one_initcall+0xdd/0x4e0 ... entry_SYSCALL_64_after_hwframe+0x76/0x7e In target_alloc_device(), if allocing memory for dev queues fails, then dev will be freed by dev->transport->free_device(), but dev->transport is not initialized at that time, which will lead to a null pointer reference problem. Fixing this bug by freeing dev with hba->backend->ops->free_device().
AI-Powered Analysis
Technical Analysis
CVE-2024-50153 is a vulnerability identified in the Linux kernel's SCSI target core module (target_core_mod). The issue arises in the function target_alloc_device(), which is responsible for allocating and initializing device structures for SCSI targets. Specifically, when memory allocation for device queues fails, the code attempts to free the partially allocated device structure by calling dev->transport->free_device(). However, at this point in execution, the dev->transport pointer has not yet been initialized, leading to a null pointer dereference (null-ptr-deref). This results in a kernel crash or panic, as detected by Kernel Address Sanitizer (KASAN). The root cause is improper handling of error conditions during device allocation, where the cleanup code references an uninitialized pointer. The fix involves changing the cleanup routine to use hba->backend->ops->free_device() instead, which is a valid and initialized pointer at the time of failure, thus preventing the null pointer dereference. This vulnerability affects certain versions of the Linux kernel as identified by specific commit hashes. No known exploits are reported in the wild as of the publication date (November 7, 2024). The vulnerability is a denial-of-service (DoS) type, as it causes a kernel crash, impacting system availability. It does not appear to allow privilege escalation or code execution directly. The flaw is triggered by failure in memory allocation during device queue setup, which could be induced by resource exhaustion or crafted inputs in environments where SCSI target functionality is used.
Potential Impact
For European organizations, the impact of CVE-2024-50153 primarily concerns systems running Linux kernels with SCSI target support enabled, such as storage servers, SAN gateways, or virtualization hosts that expose SCSI targets. A successful trigger of this vulnerability results in a kernel panic and system crash, causing denial of service. This can disrupt critical storage infrastructure, leading to downtime, data unavailability, and potential operational losses. Organizations relying on Linux-based storage solutions or virtualization platforms with target_core_mod enabled are at risk. While the vulnerability does not directly compromise confidentiality or integrity, the availability impact can be significant, especially in data centers or cloud environments supporting business-critical applications. European enterprises in finance, healthcare, telecommunications, and public sectors that operate Linux storage or virtualization infrastructure could face service interruptions. Additionally, the lack of known exploits suggests limited immediate threat, but the vulnerability could be leveraged in targeted attacks or combined with other exploits to amplify impact. The risk is heightened in environments where memory pressure or resource exhaustion can be induced by attackers or faulty workloads.
Mitigation Recommendations
1. Apply the official Linux kernel patches that fix CVE-2024-50153 as soon as they become available from trusted sources or Linux distribution vendors. 2. For organizations unable to immediately patch, consider disabling SCSI target functionality (target_core_mod) if it is not required, to eliminate the attack surface. 3. Monitor kernel logs and system stability for signs of null pointer dereference crashes related to target_alloc_device(). 4. Implement resource management controls to prevent memory exhaustion scenarios that could trigger the vulnerability, such as cgroup limits or memory quotas on relevant hosts. 5. Use kernel hardening features and runtime protections like KASAN in testing environments to detect similar issues proactively. 6. Maintain strict access controls and network segmentation around storage and virtualization hosts to limit exposure to untrusted users who might attempt to exploit this flaw. 7. Regularly update Linux kernel versions and subscribe to security advisories from Linux vendors and communities to stay informed about patches and related vulnerabilities.
Affected Countries
For access to advanced analysis and higher rate limits, contact root@offseq.com
Technical Details
- Data Version
- 5.1
- Assigner Short Name
- Linux
- Date Reserved
- 2024-10-21T19:36:19.960Z
- Cisa Enriched
- false
- Cvss Version
- null
- State
- PUBLISHED
Threat ID: 682d9825c4522896dcbe0111
Added to database: 5/21/2025, 9:08:53 AM
Last enriched: 6/28/2025, 5:55:44 PM
Last updated: 7/27/2025, 4:46:16 AM
Views: 11
Related Threats
CVE-2025-43735: CWE-79 Improper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') in Liferay Portal
MediumCVE-2025-40770: CWE-300: Channel Accessible by Non-Endpoint in Siemens SINEC Traffic Analyzer
HighCVE-2025-40769: CWE-1164: Irrelevant Code in Siemens SINEC Traffic Analyzer
HighCVE-2025-40768: CWE-200: Exposure of Sensitive Information to an Unauthorized Actor in Siemens SINEC Traffic Analyzer
HighCVE-2025-40767: CWE-250: Execution with Unnecessary Privileges in Siemens SINEC Traffic Analyzer
HighActions
Updates to AI analysis are available only with a Pro account. Contact root@offseq.com for access.
External Links
Need enhanced features?
Contact root@offseq.com for Pro access with improved analysis and higher rate limits.