NVD / CVE Program· CNA Linux

CVE-2021-47549: sata_fsl: fix UAF in sata_fsl_port_stop when rmmod sata_fsl

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.23% (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 0769449b0a5eabc3545337217ae690e46673e73a, 325ea49fc43cbc03a5e1e37de8f0ca6357ced4b1, 4a46b2f5dce02539e88a300800812bd24a45e097.
Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 0769449b0a5eabc3545337217ae690e46673e73a, 325ea49fc43cbc03a5e1e37de8f0ca6357ced4b1, 4a46b2f5dce02539e88a300800812bd24a45e097 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: sata_fsl: fix UAF in sata_fsl_port_stop when rmmod sata_fsl When the `rmmod sata_fsl.ko` command is executed in the PPC64 GNU/Linux, a bug is reported: ================================================================== BUG: Unable to handle kernel data access on read at 0x80000800805b502c Oops: Kernel access of bad area, sig: 11 [#1] NIP [c0000000000388a4] .ioread32+0x4/0x20 LR [80000000000c6034] .sata_fsl_port_stop+0x44/0xe0 [sata_fsl] Call Trace: .free_irq+0x1c/0x4e0 (unreliable) .ata_host_stop+0x74/0xd0 [libata] .release_nodes+0x330/0x3f0 .device_release_driver_internal+0x178/0x2c0 .driver_detach+0x64/0xd0 .bus_remove_driver+0x70/0xf0 .driver_unregister+0x38/0x80 .platform_driver_unregister+0x14/0x30 .fsl_sata_driver_exit+0x18/0xa20 [sata_fsl] .__se_sys_delete_module+0x1ec/0x2d0 .system_call_exception+0xfc/0x1f0 system_call_common+0xf8/0x200 ================================================================== The triggering of the BUG is shown in the following stack: driver_detach device_release_driver_internal __device_release_driver drv->remove(dev) --> platform_drv_remove/platform_remove drv->remove(dev) --> sata_fsl_remove iounmap(host_priv->hcr_base); <---- unmap kfree(host_priv); <---- free devres_release_all release_nodes dr->node.release(dev, dr->data) --> ata_host_stop ap->ops->port_stop(ap) --> sata_fsl_port_stop ioread32(hcr_base + HCONTROL) <---- UAF host->ops->host_stop(host) The iounmap(host_priv->hcr_base) and kfree(host_priv) functions should not be executed in drv->remove. These functions should be executed in host_stop after port_stop. Therefore, we move these functions to the new function sata_fsl_host_stop and bind the new function to host_stop.

HighCVSS 7.8 · v3.1—No exploit Fix available

Memory safety

Published: May 24, 2024
Updated: Jun 17, 2026
EPSS: 0.2% · 14th 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 kernel2.6.24 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.220
linux linux kernel4.20 and later · before 5.4.164
linux linux kernel5.5 and later · before 5.10.84
linux linux kernel5.11 and later · before 5.15.7
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
- 2.6.24affected
- faf0b2e5afe7dae072d2715763c7f992b612b628 and later · before cdcd80292106df5cda325426e96495503e41f947affected · git
- faf0b2e5afe7dae072d2715763c7f992b612b628 and later · before 91ba94d3f7afca195b224f77a72044fbde1389ceaffected · git
- faf0b2e5afe7dae072d2715763c7f992b612b628 and later · before 325ea49fc43cbc03a5e1e37de8f0ca6357ced4b1affected · git
- faf0b2e5afe7dae072d2715763c7f992b612b628 and later · before 0769449b0a5eabc3545337217ae690e46673e73aaffected · git
- faf0b2e5afe7dae072d2715763c7f992b612b628 and later · before 77393806c76b6b44f1c44bd957788c8bd9152c45affected · git
- faf0b2e5afe7dae072d2715763c7f992b612b628 and later · before 4a46b2f5dce02539e88a300800812bd24a45e097affected · git
- faf0b2e5afe7dae072d2715763c7f992b612b628 and later · before adf098e2a8a1e1fc075d6a5ba2edd13cf7189082affected · git
- faf0b2e5afe7dae072d2715763c7f992b612b628 and later · before 6c8ad7e8cf29eb55836e7a0215f967746ab2b504affected · git
- before 2.6.24not 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
SUSE:Linux Enterprise High Availability Extension 12 SP5	kernel-default	before 4.12.14-122.228.1	4.12.14-122.228.1
SUSE:Linux Enterprise Live Patching 12 SP5	kgraft-patch-SLE12-SP5_Update_60	before 1-8.3.1	1-8.3.1
SUSE:Linux Enterprise Real Time 12 SP5	kernel-rt	before 4.12.14-10.200.1	4.12.14-10.200.1
SUSE:Linux Enterprise Real Time 12 SP5	kernel-rt_debug	before 4.12.14-10.200.1	4.12.14-10.200.1
SUSE:Linux Enterprise Real Time 12 SP5	kernel-source-rt	before 4.12.14-10.200.1	4.12.14-10.200.1
SUSE:Linux Enterprise Real Time 12 SP5	kernel-syms-rt	before 4.12.14-10.200.1	4.12.14-10.200.1
SUSE:Linux Enterprise Server 12 SP5	kernel-azure	before 4.12.14-16.197.1	4.12.14-16.197.1
SUSE:Linux Enterprise Server 12 SP5	kernel-source	before 4.12.14-122.228.1	4.12.14-122.228.1
SUSE:Linux Enterprise Server 12 SP5	kernel-source-azure	before 4.12.14-16.197.1	4.12.14-16.197.1
SUSE:Linux Enterprise Server 12 SP5	kernel-syms	before 4.12.14-122.228.1	4.12.14-122.228.1
SUSE:Linux Enterprise Server 12 SP5	kernel-syms-azure	before 4.12.14-16.197.1	4.12.14-16.197.1
SUSE:Linux Enterprise Software Development Kit 12 SP5	kernel-docs	before 4.12.14-122.228.2	4.12.14-122.228.2
SUSE:Linux Enterprise Software Development Kit 12 SP5	kernel-obs-build	before 4.12.14-122.228.2	4.12.14-122.228.2

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-47547May 24, 2024 · net: tulip: de4x5: fix the problem that the array 'lp->phy[8]' may be out of bound
17Monitor
← EarlierCVE-2021-47548May 24, 2024 · ethernet: hisilicon: hns: hns_dsaf_misc: fix a possible array overflow in hns_dsaf_ge_srst_by_port()
39Monitor
Later →CVE-2021-47550May 24, 2024 · drm/amd/amdgpu: fix potential memleak
22Monitor

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	0769449b0a5eabc3545337217ae690e46673e73a	Vendor (CNA)
Linux Linux	325ea49fc43cbc03a5e1e37de8f0ca6357ced4b1	Vendor (CNA)
Linux Linux	4a46b2f5dce02539e88a300800812bd24a45e097	Vendor (CNA)
Linux Linux	6c8ad7e8cf29eb55836e7a0215f967746ab2b504	Vendor (CNA)
Linux Linux	77393806c76b6b44f1c44bd957788c8bd9152c45	Vendor (CNA)
Linux Linux	91ba94d3f7afca195b224f77a72044fbde1389ce	Vendor (CNA)
Linux Linux	adf098e2a8a1e1fc075d6a5ba2edd13cf7189082	Vendor (CNA)
Linux Linux	cdcd80292106df5cda325426e96495503e41f947	Vendor (CNA)
debian:linux	5.15.15-1 · Debian:12	Package registry (OSV)
suse:kernel-azure	4.12.14-16.197.1 · SUSE:Linux Enterprise Server 12 SP5	Package registry (OSV)
suse:kernel-default	4.12.14-122.228.1 · SUSE:Linux Enterprise High Availability Extension 12 SP5	Package registry (OSV)
suse:kernel-docs	4.12.14-122.228.2 · SUSE:Linux Enterprise Software Development Kit 12 SP5	Package registry (OSV)
suse:kernel-obs-build	4.12.14-122.228.2 · SUSE:Linux Enterprise Software Development Kit 12 SP5	Package registry (OSV)
suse:kernel-rt	4.12.14-10.200.1 · SUSE:Linux Enterprise Real Time 12 SP5	Package registry (OSV)
suse:kernel-rt_debug	4.12.14-10.200.1 · SUSE:Linux Enterprise Real Time 12 SP5	Package registry (OSV)
suse:kernel-source	4.12.14-122.228.1 · SUSE:Linux Enterprise Server 12 SP5	Package registry (OSV)
suse:kernel-source-azure	4.12.14-16.197.1 · SUSE:Linux Enterprise Server 12 SP5	Package registry (OSV)
suse:kernel-source-rt	4.12.14-10.200.1 · SUSE:Linux Enterprise Real Time 12 SP5	Package registry (OSV)
suse:kernel-syms	4.12.14-122.228.1 · SUSE:Linux Enterprise Server 12 SP5	Package registry (OSV)
suse:kernel-syms-rt	4.12.14-10.200.1 · SUSE:Linux Enterprise Real Time 12 SP5	Package registry (OSV)
suse:kgraft-patch-SLE12-SP5_Update_60	1-8.3.1 · SUSE:Linux Enterprise Live Patching 12 SP5	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).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

TR-24-0551 · May 27, 2024(Linux Kernel Güncellemesi)

All national notices →

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:11 PM UTC

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

References

git.kernel.org/stable/c/0769449b0a5eabc3545337217ae690e46673e73a

Show all references (7 more)

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

All records