NVD / CVE Program· CNA Linux

CVE-2021-47565: scsi: mpt3sas: Fix kernel panic during drive powercycle test

Noroxi assessment

Priority: Monitor (action score 31/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.22% (FIRST EPSS).
Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
Fixed version: Linux Linux 0d4b29eaadc1f59cec0c7e85eae77d08fcca9824, 0ee4ba13e09c9d9c1cb6abb59da8295d9952328b, 2bf9c5a5039c8f4b037236aed505e6a25c1d5f7b.

Low priority for now. Upgrade to Linux Linux 0d4b29eaadc1f59cec0c7e85eae77d08fcca9824, 0ee4ba13e09c9d9c1cb6abb59da8295d9952328b, 2bf9c5a5039c8f4b037236aed505e6a25c1d5f7b 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: mpt3sas: Fix kernel panic during drive powercycle test While looping over shost's sdev list it is possible that one of the drives is getting removed and its sas_target object is freed but its sdev object remains intact. Consequently, a kernel panic can occur while the driver is trying to access the sas_address field of sas_target object without also checking the sas_target object for NULL.

HighCVSS 7.8 · v3.1—No exploit Fix available

Memory safety

BDU:2024-10665

Published: May 24, 2024
Updated: Jun 17, 2026
EPSS: 0.2% · 13th percentile
CWE: CWE-416

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 31 / 40 · 7.8 / 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.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi 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 help

Affected 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

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

linux linux kernel3.8 and later · before 4.4.294
linux linux kernel4.5 and later · before 4.9.292
linux linux kernel4.10 and later · before 4.14.257
linux linux kernel4.15 and later · before 4.19.219
linux linux kernel4.20 and later · before 5.4.163
linux linux kernel5.5 and later · before 5.10.83
linux linux kernel5.11 and later · before 5.15.6
linux linux kernel5.16

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.8affected
- f92363d12359498f9a9960511de1a550f0ec41c2 and later · before 5d4d50b1f159a5ebab7617f47121b4370aa58afeaffected · git
- f92363d12359498f9a9960511de1a550f0ec41c2 and later · before 58ef2c7a6de13721865d84b80eecf56d6cba0937affected · git
- f92363d12359498f9a9960511de1a550f0ec41c2 and later · before dd035ca0e7a142870a970d46b1d19276cfe2bc8caffected · git
- f92363d12359498f9a9960511de1a550f0ec41c2 and later · before 0d4b29eaadc1f59cec0c7e85eae77d08fcca9824affected · git
- f92363d12359498f9a9960511de1a550f0ec41c2 and later · before 7e324f734a914957b8cc3ff4b4c9f0409558adb5affected · git
- f92363d12359498f9a9960511de1a550f0ec41c2 and later · before 2bf9c5a5039c8f4b037236aed505e6a25c1d5f7baffected · git
- f92363d12359498f9a9960511de1a550f0ec41c2 and later · before 8485649a7655e791a6e4e9f15b4d30fdae937184affected · git
- f92363d12359498f9a9960511de1a550f0ec41c2 and later · before 0ee4ba13e09c9d9c1cb6abb59da8295d9952328baffected · git
- before 3.8not affected · semver

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.15.15-1	5.15.15-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
90Now
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 KEV
89Now
CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
85Now

Published before and after this one in the same product

← EarlierCVE-2021-47563May 24, 2024 · ice: avoid bpf_prog refcount underflow
22Monitor
← EarlierCVE-2021-47564May 24, 2024 · net: marvell: prestera: fix double free issue on err path
31Monitor
Later →CVE-2021-47566May 24, 2024 · proc/vmcore: fix clearing user buffer by properly using clear_user()
31Monitor

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	0d4b29eaadc1f59cec0c7e85eae77d08fcca9824	Vendor (CNA)
Linux Linux	0ee4ba13e09c9d9c1cb6abb59da8295d9952328b	Vendor (CNA)
Linux Linux	2bf9c5a5039c8f4b037236aed505e6a25c1d5f7b	Vendor (CNA)
Linux Linux	58ef2c7a6de13721865d84b80eecf56d6cba0937	Vendor (CNA)
Linux Linux	5d4d50b1f159a5ebab7617f47121b4370aa58afe	Vendor (CNA)
Linux Linux	7e324f734a914957b8cc3ff4b4c9f0409558adb5	Vendor (CNA)
Linux Linux	8485649a7655e791a6e4e9f15b4d30fdae937184	Vendor (CNA)
Linux Linux	dd035ca0e7a142870a970d46b1d19276cfe2bc8c	Vendor (CNA)
debian:linux	5.15.15-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.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

Someone with local access to the system can trigger it.
A low-privileged account is enough.
No user action is required.
No special conditions are required; it is repeatable.

If successful

Confidentiality: high · data can be read
Integrity: high · data or configuration can be modified
Availability: high · the service can be disrupted

Attack vector: Local
Attack complexity: Low
Privileges required: Low
User interaction: None
Scope: Unchanged
Confidentiality impact: High
Integrity impact: High
Availability impact: High

Weakness class (CWE)

CWE-416 · Use After Free

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

nvd-primary

Root cause

After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.

The bug in code

The whole CWE-416 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1free(dev->buf);
2/* ... another thread is still running ... */
3process(dev->buf);

Fixed

1lock(&dev->lock);
2free(dev->buf);
3dev->buf = NULL;
4unlock(&dev->lock);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

Fix✗ → ✓Sep 28, 2026, 10:08 PM UTC

For records you follow, these changes also arrive as notifications. →

References

git.kernel.org/stable/c/0d4b29eaadc1f59cec0c7e85eae77d08fcca9824

Show all references (7 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records