CVE-2021-46925: net/smc: fix kernel panic caused by race of smc_sock
Noroxi assessment
Priority: Monitor (action score 18/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.18% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. Special conditions such as timing or configuration are required.
- Fixed version: Linux Linux 349d43127dac00c15231e8ffbcaabd70f7b0e544, b85f751d71ae8e2a15e9bda98852ea9af35282eb, e8a5988a85c719ce7205cb00dcf0716dcf611332.
- Severity is disputed: the assigning authority (CNA) scores it 7.8, NVD 4.7.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 349d43127dac00c15231e8ffbcaabd70f7b0e544, b85f751d71ae8e2a15e9bda98852ea9af35282eb, e8a5988a85c719ce7205cb00dcf0716dcf611332 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: net/smc: fix kernel panic caused by race of smc_sock A crash occurs when smc_cdc_tx_handler() tries to access smc_sock but smc_release() has already freed it. [ 4570.695099] BUG: unable to handle page fault for address: 000000002eae9e88 [ 4570.696048] #PF: supervisor write access in kernel mode [ 4570.696728] #PF: error_code(0x0002) - not-present page [ 4570.697401] PGD 0 P4D 0 [ 4570.697716] Oops: 0002 [#1] PREEMPT SMP NOPTI [ 4570.698228] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 5.16.0-rc4+ #111 [ 4570.699013] Hardware name: Alibaba Cloud Alibaba Cloud ECS, BIOS 8c24b4c 04/0 [ 4570.699933] RIP: 0010:_raw_spin_lock+0x1a/0x30 <...> [ 4570.711446] Call Trace: [ 4570.711746] <IRQ> [ 4570.711992] smc_cdc_tx_handler+0x41/0xc0 [ 4570.712470] smc_wr_tx_tasklet_fn+0x213/0x560 [ 4570.712981] ? smc_cdc_tx_dismisser+0x10/0x10 [ 4570.713489] tasklet_action_common.isra.17+0x66/0x140 [ 4570.714083] __do_softirq+0x123/0x2f4 [ 4570.714521] irq_exit_rcu+0xc4/0xf0 [ 4570.714934] common_interrupt+0xba/0xe0 Though smc_cdc_tx_handler() checked the existence of smc connection, smc_release() may have already dismissed and released the smc socket before smc_cdc_tx_handler() further visits it. smc_cdc_tx_handler() |smc_release() if (!conn) | | |smc_cdc_tx_dismiss_slots() | smc_cdc_tx_dismisser() | |sock_put(&smc->sk) <- last sock_put, | smc_sock freed bh_lock_sock(&smc->sk) (panic) | To make sure we won't receive any CDC messages after we free the smc_sock, add a refcount on the smc_connection for inflight CDC message(posted to the QP but haven't received related CQE), and don't release the smc_connection until all the inflight CDC messages haven been done, for both success or failed ones. Using refcount on CDC messages brings another problem: when the link is going to be destroyed, smcr_link_clear() will reset the QP, which then remove all the pending CQEs related to the QP in the CQ. To make sure all the CQEs will always come back so the refcount on the smc_connection can always reach 0, smc_ib_modify_qp_reset() was replaced by smc_ib_modify_qp_error(). And remove the timeout in smc_wr_tx_wait_no_pending_sends() since we need to wait for all pending WQEs done, or we may encounter use-after- free when handling CQEs. For IB device removal routine, we need to wait for all the QPs on that device been destroyed before we can destroy CQs on the device, or the refcount on smc_connection won't reach 0 and smc_sock cannot be released.
- Published
- Feb 27, 2024
- Updated
- Aug 5, 2026
- EPSS
- 0.1% · 7th percentile
- CWE
- CWE-362
Report tools
Action score
18
Low priority for now.
- CVSS
- 18 / 40 · 4.7 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 4.7
- CNA · Linux
- 7.8
- 3.1 point gap
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
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
- 4.11affected
- 5f08318f617b05b6ee389d8bd174c7af921ebf19 and later · before e8a5988a85c719ce7205cb00dcf0716dcf611332affected · git
- 5f08318f617b05b6ee389d8bd174c7af921ebf19 and later · before b85f751d71ae8e2a15e9bda98852ea9af35282ebaffected · git
- 5f08318f617b05b6ee389d8bd174c7af921ebf19 and later · before 349d43127dac00c15231e8ffbcaabd70f7b0e544affected · git
- before 4.11not affected · semver
- 5.10.90 and later · up to and including 5.10.*not affected · semver
- 5.15.13 and later · up to and including 5.15.*not affected · semver
- 5.16 and laternot affected · original_commit_for_fix
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel4.11.0 and later · before 5.10.90
- linux linux kernel5.11.0 and later · before 5.15.13
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 |
| openSUSE:Leap 15.5 | dtb-aarch64 | before 5.14.21-150500.55.59.1 | 5.14.21-150500.55.59.1 |
| openSUSE:Leap 15.5 | kernel-64kb | before 5.14.21-150500.55.59.1 | 5.14.21-150500.55.59.1 |
| openSUSE:Leap 15.5 | kernel-azure | before 5.14.21-150500.33.48.1 | 5.14.21-150500.33.48.1 |
| openSUSE:Leap 15.5 | kernel-debug | before 5.14.21-150500.55.59.1 | 5.14.21-150500.55.59.1 |
| openSUSE:Leap 15.5 | kernel-default | before 5.14.21-150500.55.59.1 | 5.14.21-150500.55.59.1 |
| openSUSE:Leap 15.5 | kernel-default-base | before 5.14.21-150500.55.59.1.150500.6.25.7 | 5.14.21-150500.55.59.1.150500.6.25.7 |
| openSUSE:Leap 15.5 | kernel-docs | before 5.14.21-150500.55.59.1 | 5.14.21-150500.55.59.1 |
| openSUSE:Leap 15.5 | kernel-kvmsmall | before 5.14.21-150500.55.59.1 | 5.14.21-150500.55.59.1 |
| openSUSE:Leap 15.5 | kernel-obs-build | before 5.14.21-150500.55.59.1 | 5.14.21-150500.55.59.1 |
| openSUSE:Leap 15.5 | kernel-obs-qa | before 5.14.21-150500.55.59.1 | 5.14.21-150500.55.59.1 |
| openSUSE:Leap 15.5 | kernel-rt | before 5.14.21-150500.13.47.1 | 5.14.21-150500.13.47.1 |
| openSUSE:Leap 15.5 | kernel-rt_debug | before 5.14.21-150500.13.47.1 | 5.14.21-150500.13.47.1 |
| openSUSE:Leap 15.5 | kernel-source | before 5.14.21-150500.55.59.1 | 5.14.21-150500.55.59.1 |
| openSUSE:Leap 15.5 | kernel-source-azure | before 5.14.21-150500.33.48.1 | 5.14.21-150500.33.48.1 |
| openSUSE:Leap 15.5 | kernel-source-rt | before 5.14.21-150500.13.47.1 | 5.14.21-150500.13.47.1 |
| openSUSE:Leap 15.5 | kernel-syms | before 5.14.21-150500.55.59.1 | 5.14.21-150500.55.59.1 |
| openSUSE:Leap 15.5 | kernel-syms-azure | before 5.14.21-150500.33.48.1 | 5.14.21-150500.33.48.1 |
| openSUSE:Leap 15.5 | kernel-syms-rt | before 5.14.21-150500.13.47.1 | 5.14.21-150500.13.47.1 |
| openSUSE:Leap 15.5 | kernel-zfcpdump | before 5.14.21-150500.55.59.1 | 5.14.21-150500.55.59.1 |
| openSUSE:Leap Micro 5.3 | kernel-default | before 5.14.21-150400.24.116.1 | 5.14.21-150400.24.116.1 |
| openSUSE:Leap Micro 5.3 | kernel-default-base | before 5.14.21-150400.24.116.1.150400.24.54.5 | 5.14.21-150400.24.116.1.150400.24.54.5 |
| openSUSE:Leap Micro 5.3 | kernel-rt | before 5.14.21-150400.15.76.1 | 5.14.21-150400.15.76.1 |
| SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS | kernel-64kb | before 5.14.21-150400.24.116.1 | 5.14.21-150400.24.116.1 |
+31
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-46923Feb 27, 2024 · fs/mount_setattr: always cleanup mount_kattr22Monitor
- ← EarlierCVE-2021-46924Feb 27, 2024 · NFC: st21nfca: Fix memory leak in device probe and remove22Monitor
- Later →CVE-2021-46926Feb 27, 2024 · ALSA: hda: intel-sdw-acpi: harden detection of controller22Monitor
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 | 349d43127dac00c15231e8ffbcaabd70f7b0e544 | Vendor (CNA) |
| Linux Linux | b85f751d71ae8e2a15e9bda98852ea9af35282eb | Vendor (CNA) |
| Linux Linux | e8a5988a85c719ce7205cb00dcf0716dcf611332 | Vendor (CNA) |
| debian:linux | 5.15.15-1 · Debian:12 | Package registry (OSV) |
| opensuse:dtb-aarch64 | 5.14.21-150500.55.59.1 · openSUSE:Leap 15.5 | Package registry (OSV) |
| opensuse:kernel-64kb | 5.14.21-150500.55.59.1 · openSUSE:Leap 15.5 | Package registry (OSV) |
| opensuse:kernel-debug | 5.14.21-150500.55.59.1 · openSUSE:Leap 15.5 | Package registry (OSV) |
| opensuse:kernel-default | 5.14.21-150400.24.116.1 · openSUSE:Leap Micro 5.3 | Package registry (OSV) |
| opensuse:kernel-default-base | 5.14.21-150400.24.116.1.150400.24.54.5 · openSUSE:Leap Micro 5.3 | Package registry (OSV) |
| opensuse:kernel-docs | 5.14.21-150500.55.59.1 · openSUSE:Leap 15.5 | Package registry (OSV) |
| opensuse:kernel-kvmsmall | 5.14.21-150500.55.59.1 · openSUSE:Leap 15.5 | Package registry (OSV) |
| opensuse:kernel-obs-build | 5.14.21-150500.55.59.1 · openSUSE:Leap 15.5 | Package registry (OSV) |
| opensuse:kernel-rt | 5.14.21-150400.15.76.1 · openSUSE:Leap Micro 5.3 | Package registry (OSV) |
| opensuse:kernel-rt_debug | 5.14.21-150500.13.47.1 · openSUSE:Leap 15.5 | Package registry (OSV) |
| opensuse:kernel-source-rt | 5.14.21-150500.13.47.1 · openSUSE:Leap 15.5 | Package registry (OSV) |
| opensuse:kernel-syms-rt | 5.14.21-150500.13.47.1 · openSUSE:Leap 15.5 | Package registry (OSV) |
| suse:kernel-64kb | 5.14.21-150400.24.116.1 · SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS | Package registry (OSV) |
| suse:kernel-default | 5.14.21-150400.24.116.1 · SUSE:Linux Enterprise Micro 5.3 | Package registry (OSV) |
| suse:kernel-default-base | 5.14.21-150400.24.116.1.150400.24.54.5 · SUSE:Linux Enterprise Micro 5.3 | Package registry (OSV) |
| suse:kernel-docs | 5.14.21-150400.24.116.1 · SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS | Package registry (OSV) |
| suse:kernel-livepatch-SLE15-SP4_Update_25 | 1-150400.9.5.1 · SUSE:Linux Enterprise Live Patching 15 SP4 | Package registry (OSV) |
| suse:kernel-livepatch-SLE15-SP5-RT_Update_13 | 1-150500.11.3.1 · SUSE:Linux Enterprise Live Patching 15 SP5 | Package registry (OSV) |
| suse:kernel-obs-build | 5.14.21-150400.24.116.1 · SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS | Package registry (OSV) |
| suse:kernel-rt | 5.14.21-150400.15.76.1 · SUSE:Linux Enterprise Micro 5.3 | Package registry (OSV) |
| suse:kernel-source | 5.14.21-150400.24.116.1 · SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS | Package registry (OSV) |
| suse:kernel-source-rt | 5.14.21-150400.15.76.1 · SUSE:Linux Enterprise Micro 5.3 | Package registry (OSV) |
| suse:kernel-syms | 5.14.21-150400.24.116.1 · SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS | Package registry (OSV) |
| suse:kernel-zfcpdump | 5.14.21-150400.24.116.1 · SUSE:Linux Enterprise Server 15 SP4-LTSS | 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.
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-24-0138 · Feb 28, 2024(Linux Kernel Güncellemesi)
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.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- High
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-362 · Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')CVSS vector
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.