scsi: smartpqi: Fix memory leak in pqi_report_phys_luns()
Summary
| CVE | CVE-2026-45872 |
|---|---|
| State | PUBLISHED |
| Assigner | Linux |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-05-27 14:17:00 UTC |
| Updated | 2026-06-25 21:06:15 UTC |
| Description | In the Linux kernel, the following vulnerability has been resolved: scsi: smartpqi: Fix memory leak in pqi_report_phys_luns() pqi_report_phys_luns() fails to release the rpl_list buffer when encountering an unsupported data format or when the allocation for rpl_16byte_wwid_list fails. These early returns bypass the cleanup logic, leading to memory leaks. Consolidate the error handling by adding an out_free_rpl_list label and use goto statements to ensure rpl_list is consistently freed on failure. Compile tested only. Issue found using a prototype static analysis tool and code review. |
Risk And Classification
Primary CVSS: v3.1 5.5 MEDIUM from [email protected]
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS: 0.000240000 probability, percentile 0.073320000 (date 2026-06-01)
Problem Types: CWE-401
CVSS v3.1 Breakdown
Attack Vector
LocalAttack Complexity
LowPrivileges Required
LowUser Interaction
NoneScope
UnchangedConfidentiality
NoneIntegrity
NoneAvailability
HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
NVD Known Affected Configurations (CPE 2.3)
| Type | Vendor | Product | Version | Update | Edition | Language |
|---|---|---|---|---|---|---|
| Operating System | Linux | Linux Kernel | All | All | All | All |
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|---|---|---|---|
| CNA | Linux | Linux | affected 28ca6d876c5a375094847606046e0bf5d044d9b4 f471ecfec093e39ef8fd08978413793087daa14d git | Not specified |
| CNA | Linux | Linux | affected 28ca6d876c5a375094847606046e0bf5d044d9b4 fdf1188cfa80f88c9f18d58cb33d57ff40e70e26 git | Not specified |
| CNA | Linux | Linux | affected 28ca6d876c5a375094847606046e0bf5d044d9b4 d52e13122d3771f753dd73ae6512fa01f58015cb git | Not specified |
| CNA | Linux | Linux | affected 28ca6d876c5a375094847606046e0bf5d044d9b4 e5579ebaadc7b699868dad0f591a7bf83cd647e1 git | Not specified |
| CNA | Linux | Linux | affected 28ca6d876c5a375094847606046e0bf5d044d9b4 454570434114e4862767f506a442a0f110b639b2 git | Not specified |
| CNA | Linux | Linux | affected 28ca6d876c5a375094847606046e0bf5d044d9b4 41b37312bd9722af77ec7817ccf22d7a4880c289 git | Not specified |
| CNA | Linux | Linux | affected 5.16 | Not specified |
| CNA | Linux | Linux | unaffected 5.16 semver | Not specified |
| CNA | Linux | Linux | unaffected 6.1.165 6.1.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.6.128 6.6.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.12.75 6.12.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.18.14 6.18.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.19.4 6.19.* semver | Not specified |
| CNA | Linux | Linux | unaffected 7.0 * original_commit_for_fix | Not specified |
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| git.kernel.org/stable/c/41b37312bd9722af77ec7817ccf22d7a4880c289 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | Patch |
| git.kernel.org/stable/c/fdf1188cfa80f88c9f18d58cb33d57ff40e70e26 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | Patch |
| git.kernel.org/stable/c/f471ecfec093e39ef8fd08978413793087daa14d | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | Patch |
| git.kernel.org/stable/c/e5579ebaadc7b699868dad0f591a7bf83cd647e1 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | Patch |
| git.kernel.org/stable/c/454570434114e4862767f506a442a0f110b639b2 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | Patch |
| git.kernel.org/stable/c/d52e13122d3771f753dd73ae6512fa01f58015cb | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | Patch |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.