CVE-2023-53078

scsi: scsi_dh_alua: Fix memleak for 'qdata' in alua_activate()

MEDIUM

5.5

CVSS Score

Published: May 2, 2025 at 03:55 PM UTC

Updated: June 17, 2026 at 06:44 AM UTC

1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available

Start Free Sign In

Severity

MEDIUM5.5

Exploit prediction

EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: scsi: scsi_dh_alua: Fix memleak for 'qdata' in alua_activate() If alua_rtpg_queue() failed from alua_activate(), then 'qdata' is not freed, which will cause following memleak: unreferenced object 0xffff88810b2c6980 (size 32): comm "kworker/u16:2", pid 635322, jiffies 4355801099 (age 1216426.076s) hex dump (first 32 bytes): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 40 39 24 c1 ff ff ff ff 00 f8 ea 0a 81 88 ff ff @9$............. backtrace: [<0000000098f3a26d>] alua_activate+0xb0/0x320 [<000000003b529641>] scsi_dh_activate+0xb2/0x140 [<000000007b296db3>] activate_path_work+0xc6/0xe0 [dm_multipath] [<000000007adc9ace>] process_one_work+0x3c5/0x730 [<00000000c457a985>] worker_thread+0x93/0x650 [<00000000cb80e628>] kthread+0x1ba/0x210 [<00000000a1e61077>] ret_from_fork+0x22/0x30 Fix the problem by freeing 'qdata' in error path.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Linux Kernel · Linux

95%

v ≥ 4.10.9v ≥ 4.9.214.10.9 ≤ v < 4.114.11 ≤ v < 4.14.3124.11 ≤ v < 4.19.2804.11 ≤ v < 5.10.1774.11 ≤ v < 5.15.1054.11 ≤ v < 5.4.2404.11 ≤ v < 6.1.224.11 ≤ v < 6.2.94.11 ≤ v < 6.34.11.1 ≤ v < 4.14.3124.15 ≤ v < 4.19.2804.20 ≤ v < 5.4.2404.9.21 ≤ v < 4.105.11 ≤ v < 5.15.1055.16 ≤ v < 6.1.225.5 ≤ v < 5.10.1776.2 ≤ v < 6.2.92b1725d1df362499f6bbd5a7e245a4090b29c2bb4.10.9 4.11 4.11 rc5 4.11 rc6 4.11 rc7 4.11 rc8 4.9.21 6.3 rc1 6.3 rc2 6.3 rc3625fe857e4fac6518716f3c0ff5e5deb8ec6d23868b275b7cbf065a8ea9b964cbb7d78d2b63c635f

Vendor states this is fixed in 0d89254a4320eb7de0970c478172f764125c6355 (fixed)

Vendor states this is fixed in 123483df146492ca22b503ae6dacc2ce7c3a3974 (fixed)

Vendor states this is fixed in 1c55982beb80c7d3c30278fc6cfda8496a31dbe6 (fixed)

Vendor states this is fixed in 5c4d71424df34fc23dc5336d09394ce68c849542 (fixed)

Vendor states this is fixed in 9311e7a554dffd3823499e309a8b86a5cd1540e5 (fixed)

Vendor states this is fixed in a13faca032acbf2699293587085293bdfaafc8ae (fixed)

Vendor states this is fixed in c09cdf6eb815ee35e55d6c50ac7f63db58bd20b8 (fixed)

Vendor states this is fixed in c110051d335ef7f62ad33474b0c23997fee5bfb5 (fixed)

Affected range stops below 4.10, so it looks safe — our inference, not a vendor statement

Vendor states this is fixed in 4.11 (unaffected)

Vendor states this is fixed in 4.14.312 (unaffected)

Vendor states this is fixed in 4.19.280 (unaffected)