Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2021-46959: spi: Fix use-after-free with devm_spi_alloc_*

HighCVSS 7.8 · v3.1—No exploit Fix available

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.24% (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 001c8e83646ad3b847b18f6ac55a54367d917d74, 28a5529068c51cdf0295ab1e11a99a3a909a03e4, 4.14.233.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 001c8e83646ad3b847b18f6ac55a54367d917d74, 28a5529068c51cdf0295ab1e11a99a3a909a03e4, 4.14.233 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: spi: Fix use-after-free with devm_spi_alloc_* We can't rely on the contents of the devres list during spi_unregister_controller(), as the list is already torn down at the time we perform devres_find() for devm_spi_release_controller. This causes devices registered with devm_spi_alloc_{master,slave}() to be mistakenly identified as legacy, non-devm managed devices and have their reference counters decremented below 0. ------------[ cut here ]------------ WARNING: CPU: 1 PID: 660 at lib/refcount.c:28 refcount_warn_saturate+0x108/0x174 [<b0396f04>] (refcount_warn_saturate) from [<b03c56a4>] (kobject_put+0x90/0x98) [<b03c5614>] (kobject_put) from [<b0447b4c>] (put_device+0x20/0x24) r4:b6700140 [<b0447b2c>] (put_device) from [<b07515e8>] (devm_spi_release_controller+0x3c/0x40) [<b07515ac>] (devm_spi_release_controller) from [<b045343c>] (release_nodes+0x84/0xc4) r5:b6700180 r4:b6700100 [<b04533b8>] (release_nodes) from [<b0454160>] (devres_release_all+0x5c/0x60) r8:b1638c54 r7:b117ad94 r6:b1638c10 r5:b117ad94 r4:b163dc10 [<b0454104>] (devres_release_all) from [<b044e41c>] (__device_release_driver+0x144/0x1ec) r5:b117ad94 r4:b163dc10 [<b044e2d8>] (__device_release_driver) from [<b044f70c>] (device_driver_detach+0x84/0xa0) r9:00000000 r8:00000000 r7:b117ad94 r6:b163dc54 r5:b1638c10 r4:b163dc10 [<b044f688>] (device_driver_detach) from [<b044d274>] (unbind_store+0xe4/0xf8) Instead, determine the devm allocation state as a flag on the controller which is guaranteed to be stable during cleanup.

Published
Feb 29, 2024
Updated
Jun 17, 2026
EPSS
0.2% · 15th percentile

Report tools

JSON

Action score

31

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.

Follow CVE-2021-46959

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools
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.

VendorProduct
linuxlinux 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

    • bd1a5b2307279029faaddbecf2f2ac25eaef8dc6, 5.10affected
    • a4add022c1552b0d51a0b89a4781919d6ebac4f9 and later · before 62bb2c7f2411a0045c24831f11ecacfc35610815affected · git
    • 0870525cf94bc27907e94ce99afb6d7239ffd2f5 and later · before 8bf96425c90f5c1dcf3b7b9df568019a1d4b8a0eaffected · git
    • 8c45a1c6c951bbe7f95db78fcab46f7337364468 and later · before 8e029707f50a82c53172359c686b2536ab54e58caffected · git
    • 234b432c7b6184b2d6c5ba2c55f0dd5023c0edf0 and later · before 28a5529068c51cdf0295ab1e11a99a3a909a03e4affected · git
    • 3e04a4976addbedcad326f47b0dd4efc570a1fac and later · before 001c8e83646ad3b847b18f6ac55a54367d917d74affected · git
    • 5e844cc37a5cbaa460e68f9a989d321d63088a89 and later · before c7fabe372a9031acd00498bc718ce27c253abfd1affected · git
    • 5e844cc37a5cbaa460e68f9a989d321d63088a89 and later · before cee78aa24578edac8cf00513dca618c0acc17cd7affected · git
    • 5e844cc37a5cbaa460e68f9a989d321d63088a89 and later · before 8735248ebb918d25427965f0db07939ed0473ec6affected · git
    • 5e844cc37a5cbaa460e68f9a989d321d63088a89 and later · before 794aaf01444d4e765e2b067cba01cc69c1c68ed9affected · git

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 5.10.38-15.10.38-1

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-2024-26607Feb 29, 2024 · drm/bridge: sii902x: Fix probing race issue
    18Monitor
  • ← EarlierCVE-2023-52485Feb 29, 2024 · drm/amd/display: Wake DMCUB before sending a command
    22Monitor
  • Later →CVE-2021-47016Feb 29, 2024 · m68k: mvme147,mvme16x: Don't wipe PCC timer config bits
    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 / packageFixed versionSource
Linux Linux001c8e83646ad3b847b18f6ac55a54367d917d74Vendor (CNA)
Linux Linux28a5529068c51cdf0295ab1e11a99a3a909a03e4Vendor (CNA)
Linux Linux4.14.233Vendor (CNA)
Linux Linux4.19.191Vendor (CNA)
Linux Linux4.4.271Vendor (CNA)
Linux Linux4.9.271Vendor (CNA)
Linux Linux5.10Vendor (CNA)
Linux Linux5.4.119Vendor (CNA)
Linux Linux62bb2c7f2411a0045c24831f11ecacfc35610815Vendor (CNA)
Linux Linux794aaf01444d4e765e2b067cba01cc69c1c68ed9Vendor (CNA)
Linux Linux8735248ebb918d25427965f0db07939ed0473ec6Vendor (CNA)
Linux Linux8bf96425c90f5c1dcf3b7b9df568019a1d4b8a0eVendor (CNA)
Linux Linux8e029707f50a82c53172359c686b2536ab54e58cVendor (CNA)
Linux Linuxc7fabe372a9031acd00498bc718ce27c253abfd1Vendor (CNA)
Linux Linuxcee78aa24578edac8cf00513dca618c0acc17cd7Vendor (CNA)
debian:linux5.10.38-1 · Debian:12Package 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.

National notice (Türkiye Cybersecurity Directorate / USOM)

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

All national notices →

Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.

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.

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

Vulnerable

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

Fixed

c
lock(&dev->lock);free(dev->buf);dev->buf = NULL;unlock(&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.

References

All records