Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2022-48751: net/smc: Transitional solution for clcsock race issue

MediumCVSS 4.7 · v3.1—No exploit Fix available

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.22% (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 38f0bdd548fd2ef5d481b88d8a2bfef968452e34, 4.20, 4284225cd8001e134f5cf533a7cd244bbb654d0f.
  • Severity is disputed: the assigning authority (CNA) scores it 7.8, NVD 4.7.

Low priority for now. Upgrade to Linux Linux 38f0bdd548fd2ef5d481b88d8a2bfef968452e34, 4.20, 4284225cd8001e134f5cf533a7cd244bbb654d0f 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: Transitional solution for clcsock race issue We encountered a crash in smc_setsockopt() and it is caused by accessing smc->clcsock after clcsock was released. BUG: kernel NULL pointer dereference, address: 0000000000000020 #PF: supervisor read access in kernel mode #PF: error_code(0x0000) - not-present page PGD 0 P4D 0 Oops: 0000 [#1] PREEMPT SMP PTI CPU: 1 PID: 50309 Comm: nginx Kdump: loaded Tainted: G E 5.16.0-rc4+ #53 RIP: 0010:smc_setsockopt+0x59/0x280 [smc] Call Trace: <TASK> __sys_setsockopt+0xfc/0x190 __x64_sys_setsockopt+0x20/0x30 do_syscall_64+0x34/0x90 entry_SYSCALL_64_after_hwframe+0x44/0xae RIP: 0033:0x7f16ba83918e </TASK> This patch tries to fix it by holding clcsock_release_lock and checking whether clcsock has already been released before access. In case that a crash of the same reason happens in smc_getsockopt() or smc_switch_to_fallback(), this patch also checkes smc->clcsock in them too. And the caller of smc_switch_to_fallback() will identify whether fallback succeeds according to the return value.

Published
Jun 20, 2024
Updated
Aug 5, 2026
EPSS
0.2% · 12th percentile

Report tools

JSON

Action score

18

Monitor

Low priority for now.

CVSS
18 / 40 · 4.7 / 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.

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.

Follow CVE-2022-48751

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

    • d1d004585b40c212b338fc8a40cbaaf230ea4703, 5.1affected
    • fd57770dd198f5b2ddd5b9e6bf282cf98d63adb9 and later · before 38f0bdd548fd2ef5d481b88d8a2bfef968452e34affected · git
    • fd57770dd198f5b2ddd5b9e6bf282cf98d63adb9 and later · before 4284225cd8001e134f5cf533a7cd244bbb654d0faffected · git
    • fd57770dd198f5b2ddd5b9e6bf282cf98d63adb9 and later · before c0bf3d8a943b6f2e912b7c1de03e2ef28e76f760affected · git
    • 4.19.299 and later · before 4.20affected · semver
    • before 5.1not affected · semver
    • 5.15.19 and later · up to and including 5.15.*not affected · semver
    • 5.16.5 and later · up to and including 5.16.*not affected · semver
    • 5.17 and laternot affected · original_commit_for_fix

Package-level exposure

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

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 5.16.7-15.16.7-1
SUSE:Linux Enterprise High Availability Extension 12 SP5kernel-defaultbefore 4.12.14-122.228.14.12.14-122.228.1
SUSE:Linux Enterprise Live Patching 12 SP5kgraft-patch-SLE12-SP5_Update_60before 1-8.3.11-8.3.1
SUSE:Linux Enterprise Real Time 12 SP5kernel-rtbefore 4.12.14-10.200.14.12.14-10.200.1
SUSE:Linux Enterprise Real Time 12 SP5kernel-rt_debugbefore 4.12.14-10.200.14.12.14-10.200.1
SUSE:Linux Enterprise Real Time 12 SP5kernel-source-rtbefore 4.12.14-10.200.14.12.14-10.200.1
SUSE:Linux Enterprise Real Time 12 SP5kernel-syms-rtbefore 4.12.14-10.200.14.12.14-10.200.1
SUSE:Linux Enterprise Server 12 SP5kernel-azurebefore 4.12.14-16.197.14.12.14-16.197.1
SUSE:Linux Enterprise Server 12 SP5kernel-sourcebefore 4.12.14-122.228.14.12.14-122.228.1
SUSE:Linux Enterprise Server 12 SP5kernel-source-azurebefore 4.12.14-16.197.14.12.14-16.197.1
SUSE:Linux Enterprise Server 12 SP5kernel-symsbefore 4.12.14-122.228.14.12.14-122.228.1
SUSE:Linux Enterprise Server 12 SP5kernel-syms-azurebefore 4.12.14-16.197.14.12.14-16.197.1
SUSE:Linux Enterprise Software Development Kit 12 SP5kernel-docsbefore 4.12.14-122.228.24.12.14-122.228.2
SUSE:Linux Enterprise Software Development Kit 12 SP5kernel-obs-buildbefore 4.12.14-122.228.24.12.14-122.228.2

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-2022-48749Jun 20, 2024 · drm/msm/dpu: invalid parameter check in dpu_setup_dspp_pcc
    22Monitor
  • ← EarlierCVE-2022-48750Jun 20, 2024 · hwmon: (nct6775) Fix crash in clear_caseopen
    22Monitor
  • Later →CVE-2022-48752Jun 20, 2024 · powerpc/perf: Fix power_pmu_disable to call clear_pmi_irq_pending only if PMI is pending
    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 Linux38f0bdd548fd2ef5d481b88d8a2bfef968452e34Vendor (CNA)
Linux Linux4.20Vendor (CNA)
Linux Linux4284225cd8001e134f5cf533a7cd244bbb654d0fVendor (CNA)
Linux Linuxc0bf3d8a943b6f2e912b7c1de03e2ef28e76f760Vendor (CNA)
debian:linux5.16.7-1 · Debian:12Package registry (OSV)
suse:kernel-azure4.12.14-16.197.1 · SUSE:Linux Enterprise Server 12 SP5Package registry (OSV)
suse:kernel-default4.12.14-122.228.1 · SUSE:Linux Enterprise High Availability Extension 12 SP5Package registry (OSV)
suse:kernel-docs4.12.14-122.228.2 · SUSE:Linux Enterprise Software Development Kit 12 SP5Package registry (OSV)
suse:kernel-obs-build4.12.14-122.228.2 · SUSE:Linux Enterprise Software Development Kit 12 SP5Package registry (OSV)
suse:kernel-rt4.12.14-10.200.1 · SUSE:Linux Enterprise Real Time 12 SP5Package registry (OSV)
suse:kernel-rt_debug4.12.14-10.200.1 · SUSE:Linux Enterprise Real Time 12 SP5Package registry (OSV)
suse:kernel-source4.12.14-122.228.1 · SUSE:Linux Enterprise Server 12 SP5Package registry (OSV)
suse:kernel-source-azure4.12.14-16.197.1 · SUSE:Linux Enterprise Server 12 SP5Package registry (OSV)
suse:kernel-source-rt4.12.14-10.200.1 · SUSE:Linux Enterprise Real Time 12 SP5Package registry (OSV)
suse:kernel-syms4.12.14-122.228.1 · SUSE:Linux Enterprise Server 12 SP5Package registry (OSV)
suse:kernel-syms-rt4.12.14-10.200.1 · SUSE:Linux Enterprise Real Time 12 SP5Package registry (OSV)
suse:kgraft-patch-SLE12-SP5_Update_601-8.3.1 · SUSE:Linux Enterprise Live Patching 12 SP5Package 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.

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

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.

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

References

All records