CVE-2021-47329: scsi: megaraid_sas: Fix resource leak in case of probe failure
Noroxi assessment
Priority: Monitor (action score 24/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.26% (FIRST EPSS).
- Someone with local access to the system can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 04b6b9ea80906e3b41ff120b45db31768947cf72, 0680db6f41920b2c91c7df3cc9cd5968701a6f74, 0c6226601c3e191a44a57d8f9f814b7e5c308959.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 04b6b9ea80906e3b41ff120b45db31768947cf72, 0680db6f41920b2c91c7df3cc9cd5968701a6f74, 0c6226601c3e191a44a57d8f9f814b7e5c308959 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
In the Linux kernel, the following vulnerability has been resolved: scsi: megaraid_sas: Fix resource leak in case of probe failure The driver doesn't clean up all the allocated resources properly when scsi_add_host(), megasas_start_aen() function fails during the PCI device probe. Clean up all those resources.
- Published
- May 21, 2024
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 17th percentile
- CWE
- CWE-400
Report tools
Action score
24
Low priority for now.
- CVSS
- 24 / 40 · 6.2 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 3.0affected
- 541f90b7c6dffe4cf4a3e8142ac8bd047da94733 and later · before 0c6226601c3e191a44a57d8f9f814b7e5c308959affected · git
- 541f90b7c6dffe4cf4a3e8142ac8bd047da94733 and later · before 0680db6f41920b2c91c7df3cc9cd5968701a6f74affected · git
- 541f90b7c6dffe4cf4a3e8142ac8bd047da94733 and later · before 04b6b9ea80906e3b41ff120b45db31768947cf72affected · git
- 541f90b7c6dffe4cf4a3e8142ac8bd047da94733 and later · before e623f79691c5104317669ab36ec316a90c05062faffected · git
- 541f90b7c6dffe4cf4a3e8142ac8bd047da94733 and later · before b5438f48fdd8e1c3f130d32637511efd32038152affected · git
- before 3.0not affected · semver
- 5.4.134 and later · up to and including 5.4.*not affected · semver
- 5.10.52 and later · up to and including 5.10.*not affected · semver
- 5.12.19 and later · up to and including 5.12.*not affected · semver
Affected versions · NVD (4)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernelbefore 5.4.134
- linux linux kernel5.5 and later · before 5.10.52
- linux linux kernel5.11 and later · before 5.12.19
- linux linux kernel5.13 and later · before 5.13.4
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 5.14.6-1 | 5.14.6-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2021-47327May 21, 2024 · iommu/arm-smmu: Fix arm_smmu_device refcount leak when arm_smmu_rpm_get fails28Monitor
- ← EarlierCVE-2021-47328May 21, 2024 · scsi: iscsi: Fix conn use after free during resets31Monitor
- Later →CVE-2021-47330May 21, 2024 · tty: serial: 8250: serial_cs: Fix a memory leak in error handling path22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 04b6b9ea80906e3b41ff120b45db31768947cf72 | Vendor (CNA) |
| Linux Linux | 0680db6f41920b2c91c7df3cc9cd5968701a6f74 | Vendor (CNA) |
| Linux Linux | 0c6226601c3e191a44a57d8f9f814b7e5c308959 | Vendor (CNA) |
| Linux Linux | b5438f48fdd8e1c3f130d32637511efd32038152 | Vendor (CNA) |
| Linux Linux | e623f79691c5104317669ab36ec316a90c05062f | Vendor (CNA) |
| debian:linux | 5.14.6-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2024-3946235 days apartclk: bcm: dvp: Assign ->num before accessing ->hws39Monitor
- CVE-2021-444035 days apartx86/xen: Drop USERGS_SYSRET64 paravirt call35Monitor
- CVE-2021-473130 days apartcpufreq: CPPC: Fix potential memleak in cppc_cpufreq_cpu_init33Monitor
- CVE-2024-3861629 days apartwifi: carl9170: re-fix fortified-memset warning32Monitor
- CVE-2021-4702383 days apartnet: marvell: prestera: fix port event handling on init32Monitor
- CVE-2024-359481 days apartbcachefs: Check for journal entries overruning end of sb clean section31Monitor
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-24-0519 · May 22, 2024(Linux Kernel Güncellemesi)
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-400 · Uncontrolled Resource ConsumptionCVSS vector
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
nvd-secondary
Root cause
Code that parses nested structures sets no depth or size limit. A small input can turn into a disproportionate processing load.
The bug in code
The whole CWE-400 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
function expand(node) {
return node.children.map(expand);
}Fixed
const MAX_DEPTH = 32;
function expand(node, depth = 0) {
if (depth > MAX_DEPTH) throw new Error("too deep");
return node.children.map((c) => expand(c, depth + 1));
}Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (4 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.