Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2023-52775: net/smc: avoid data corruption caused by decline

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.67% (FIRST EPSS); higher than 52.4% of all records.
  • 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 5ada292b5c504720a0acef8cae9acc62a694d19c, 7234d2b5dffa5af77fd4e0deaebab509e130c6b1, 90072af9efe8c7bd7d086709014ddd44cebd5e7c.

Low priority for now. Upgrade to Linux Linux 5ada292b5c504720a0acef8cae9acc62a694d19c, 7234d2b5dffa5af77fd4e0deaebab509e130c6b1, 90072af9efe8c7bd7d086709014ddd44cebd5e7c 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: avoid data corruption caused by decline We found a data corruption issue during testing of SMC-R on Redis applications. The benchmark has a low probability of reporting a strange error as shown below. "Error: Protocol error, got "\xe2" as reply type byte" Finally, we found that the retrieved error data was as follows: 0xE2 0xD4 0xC3 0xD9 0x04 0x00 0x2C 0x20 0xA6 0x56 0x00 0x16 0x3E 0x0C 0xCB 0x04 0x02 0x01 0x00 0x00 0x20 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0xE2 It is quite obvious that this is a SMC DECLINE message, which means that the applications received SMC protocol message. We found that this was caused by the following situations: client server ¦ clc proposal -------------> ¦ clc accept <------------- ¦ clc confirm -------------> wait llc confirm send llc confirm ¦failed llc confirm ¦ x------ (after 2s)timeout wait llc confirm rsp wait decline (after 1s) timeout (after 2s) timeout ¦ decline --------------> ¦ decline <-------------- As a result, a decline message was sent in the implementation, and this message was read from TCP by the already-fallback connection. This patch double the client timeout as 2x of the server value, With this simple change, the Decline messages should never cross or collide (during Confirm link timeout). This issue requires an immediate solution, since the protocol updates involve a more long-term solution.

Published
May 21, 2024
Updated
Aug 5, 2026
EPSS
0.6% · 52th 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.6%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
7.8
CNA · Linux
8.2
0.4 point gap

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

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-2023-52775

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

  • Stack 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

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records
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

    • 5.8affected
    • 0fb0b02bd6fd26cba38002be4a6bbcae2228fd44 and later · before 5ada292b5c504720a0acef8cae9acc62a694d19caffected · git
    • 0fb0b02bd6fd26cba38002be4a6bbcae2228fd44 and later · before 90072af9efe8c7bd7d086709014ddd44cebd5e7caffected · git
    • 0fb0b02bd6fd26cba38002be4a6bbcae2228fd44 and later · before 94a0ae698b4d5d5bb598e23228002a1491c50addaffected · git
    • 0fb0b02bd6fd26cba38002be4a6bbcae2228fd44 and later · before 7234d2b5dffa5af77fd4e0deaebab509e130c6b1affected · git
    • 0fb0b02bd6fd26cba38002be4a6bbcae2228fd44 and later · before e6d71b437abc2f249e3b6a1ae1a7228e09c6e563affected · git
    • before 5.8not affected · semver
    • 5.10.203 and later · up to and including 5.10.*not affected · semver
    • 5.15.141 and later · up to and including 5.15.*not affected · semver
    • 6.1.65 and later · up to and including 6.1.*not affected · semver
Affected versions · NVD (5)

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

  • linux linux kernel5.8 and later · before 5.10.203
  • linux linux kernel5.11 and later · before 5.15.141
  • linux linux kernel5.16 and later · before 6.1.65
  • linux linux kernel6.2 and later · before 6.6.4
  • linux linux kernel6.7

Package-level exposure

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

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.66-16.1.66-1
Debian:13linuxbefore 6.6.8-16.6.8-1
openSUSE:Leap 15.6dtb-aarch64before 6.4.0-150600.23.17.16.4.0-150600.23.17.1
openSUSE:Leap 15.6kernel-64kbbefore 6.4.0-150600.23.17.16.4.0-150600.23.17.1
openSUSE:Leap 15.6kernel-debugbefore 6.4.0-150600.23.17.16.4.0-150600.23.17.1
openSUSE:Leap 15.6kernel-defaultbefore 6.4.0-150600.23.17.16.4.0-150600.23.17.1
openSUSE:Leap 15.6kernel-default-basebefore 6.4.0-150600.23.17.1.150600.12.6.26.4.0-150600.23.17.1.150600.12.6.2
openSUSE:Leap 15.6kernel-docsbefore 6.4.0-150600.23.17.36.4.0-150600.23.17.3
openSUSE:Leap 15.6kernel-kvmsmallbefore 6.4.0-150600.23.17.16.4.0-150600.23.17.1
openSUSE:Leap 15.6kernel-obs-buildbefore 6.4.0-150600.23.17.16.4.0-150600.23.17.1
openSUSE:Leap 15.6kernel-obs-qabefore 6.4.0-150600.23.17.16.4.0-150600.23.17.1
openSUSE:Leap 15.6kernel-sourcebefore 6.4.0-150600.23.17.16.4.0-150600.23.17.1
openSUSE:Leap 15.6kernel-symsbefore 6.4.0-150600.23.17.16.4.0-150600.23.17.1
openSUSE:Leap 15.6kernel-zfcpdumpbefore 6.4.0-150600.23.17.16.4.0-150600.23.17.1
Red Hat:rhel_eus:9.4::appstreambpftool-debuginfobefore 0:7.3.0-427.47.1.el9_40:7.3.0-427.47.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-64k-debug-debuginfobefore 0:5.14.0-427.47.1.el9_40:5.14.0-427.47.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-64k-debug-develbefore 0:5.14.0-427.47.1.el9_40:5.14.0-427.47.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-64k-debug-devel-matchedbefore 0:5.14.0-427.47.1.el9_40:5.14.0-427.47.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-64k-debuginfobefore 0:5.14.0-427.47.1.el9_40:5.14.0-427.47.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-64k-develbefore 0:5.14.0-427.47.1.el9_40:5.14.0-427.47.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-64k-devel-matchedbefore 0:5.14.0-427.47.1.el9_40:5.14.0-427.47.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-debug-debuginfobefore 0:5.14.0-427.47.1.el9_40:5.14.0-427.47.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-debug-develbefore 0:5.14.0-427.47.1.el9_40:5.14.0-427.47.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-debug-devel-matchedbefore 0:5.14.0-427.47.1.el9_40:5.14.0-427.47.1.el9_4

+77

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-2023-52773May 21, 2024 · drm/amd/display: fix a NULL pointer dereference in amdgpu_dm_i2c_xfer()
    22Monitor
  • ← EarlierCVE-2023-52774May 21, 2024 · s390/dasd: protect device queue against concurrent access
    22Monitor
  • Later →CVE-2023-52776May 21, 2024 · wifi: ath12k: fix dfs-radar and temperature event locking
    35Monitor

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 Linux5ada292b5c504720a0acef8cae9acc62a694d19cVendor (CNA)
Linux Linux7234d2b5dffa5af77fd4e0deaebab509e130c6b1Vendor (CNA)
Linux Linux90072af9efe8c7bd7d086709014ddd44cebd5e7cVendor (CNA)
Linux Linux94a0ae698b4d5d5bb598e23228002a1491c50addVendor (CNA)
Linux Linuxe6d71b437abc2f249e3b6a1ae1a7228e09c6e563Vendor (CNA)
debian:linux6.1.66-1 · Debian:12Package registry (OSV)
opensuse:dtb-aarch646.4.0-150600.23.17.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-64kb6.4.0-150600.23.17.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-debug6.4.0-150600.23.17.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-default6.4.0-150600.23.17.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-default-base6.4.0-150600.23.17.1.150600.12.6.2 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-docs6.4.0-150600.23.17.3 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-kvmsmall6.4.0-150600.23.17.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-obs-build6.4.0-150600.23.17.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-obs-qa6.4.0-150600.23.17.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-source6.4.0-150600.23.17.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-syms6.4.0-150600.23.17.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-zfcpdump6.4.0-150600.23.17.1 · openSUSE:Leap 15.6Package registry (OSV)
red hat:bpftool-debuginfo0:7.3.0-427.47.1.el9_4 · Red Hat:rhel_eus:9.4::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-debuginfo0:5.14.0-427.47.1.el9_4 · Red Hat:rhel_eus:9.4::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel0:5.14.0-427.47.1.el9_4 · Red Hat:rhel_eus:9.4::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel-matched0:5.14.0-427.47.1.el9_4 · Red Hat:rhel_eus:9.4::appstreamPackage registry (OSV)
red hat:kernel-64k-debuginfo0:5.14.0-427.47.1.el9_4 · Red Hat:rhel_eus:9.4::appstreamPackage registry (OSV)
red hat:kernel-64k-devel0:5.14.0-427.47.1.el9_4 · Red Hat:rhel_eus:9.4::appstreamPackage registry (OSV)
red hat:kernel-64k-devel-matched0:5.14.0-427.47.1.el9_4 · Red Hat:rhel_eus:9.4::appstreamPackage registry (OSV)
red hat:kernel-debug-debuginfo0:5.14.0-427.47.1.el9_4 · Red Hat:rhel_eus:9.4::appstreamPackage registry (OSV)
red hat:kernel-debug-devel0:5.14.0-427.47.1.el9_4 · Red Hat:rhel_eus:9.4::appstreamPackage registry (OSV)
red hat:kernel-debug-devel-matched0:5.14.0-427.47.1.el9_4 · Red Hat:rhel_eus:9.4::appstreamPackage registry (OSV)
red hat:kernel-debuginfo0:5.14.0-427.47.1.el9_4 · Red Hat:rhel_eus:9.4::appstreamPackage registry (OSV)
red hat:kernel-debuginfo-common-aarch640:5.14.0-427.47.1.el9_4 · Red Hat:rhel_eus:9.4::appstreamPackage registry (OSV)

+9

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.
  • 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-787 · Out-of-bounds Write

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/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

Show all references (4 more)

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

All records