CVE-2024-50153: scsi: target: core: Fix null-ptr-deref in target_alloc_device()
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().
Security readout for executives and security teams
Plain-English summary
CVE-2024-50153 is a Linux kernel availability bug in the SCSI target core. Under a memory allocation failure path, the kernel can hit a null pointer dereference and crash. The published scoring requires local access with low privileges, so this is mainly a stability and denial-of-service concern, not a remote compromise issue.
Executive priority
Treat this as a moderate-priority availability issue. Patch through normal kernel maintenance, faster for shared Linux systems, storage infrastructure, and appliances where local users or tenants exist. There is no sourced evidence of active exploitation in the provided bundle.
Technical view
In target_alloc_device(), if device queue allocation fails, cleanup may call dev->transport->free_device() before dev->transport is initialized. That causes a null pointer dereference in target_core_mod. The fix frees the device through hba->backend->ops->free_device() instead. The CVSS vector is AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H.
Likely exposure
Exposure is most relevant to Linux systems running affected kernel versions and using or loading the SCSI target core functionality. The source bundle lists affected Linux kernel ranges and several stable kernel fixes, plus Debian LTS and Siemens advisories. Product-specific exposure beyond those sources is not established here.
Exploitation context
The source bundle does not show CISA KEV listing or confirmed active exploitation. The CVSS vector indicates local, low-privilege conditions with high availability impact. Evidence supports a crash/denial-of-service risk, not confidentiality or integrity impact.
Researcher notes
The vulnerable path is an error cleanup path triggered when dev queue allocation fails during target_alloc_device(). Analysis should focus on affected kernel lineage, whether target_core_mod can be initialized, and whether vendor backports include the stable fix. Do not assume broader product exposure without vendor confirmation.
Mitigation direction
Apply vendor kernel updates that include the referenced stable Linux fixes.
Follow Debian LTS or Siemens guidance where those distributions or products apply.
Prioritize multi-user systems where local low-privilege access is available.
Check vendor guidance before changing SCSI target modules or storage settings.
Validation and detection
Inventory Linux kernel versions across exposed servers and appliances.
Check whether target_core_mod or SCSI target functionality is present or used.
Confirm patched builds include a cited stable commit or vendor advisory fix.
Review crash logs for null pointer dereferences in target_alloc_device.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-476: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.