Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2023-52700: tipc: fix kernel warning when sending SYN message

MediumCVSS 5.5 · v3.1—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 22/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.21% (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 11a4d6f67cf55883dc78e31c247d1903ed7feccc, 54b6082aec178f16ad6d193b4ecdc9c4823d9a32.

Low priority for now. Upgrade to Linux Linux 11a4d6f67cf55883dc78e31c247d1903ed7feccc, 54b6082aec178f16ad6d193b4ecdc9c4823d9a32 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: tipc: fix kernel warning when sending SYN message When sending a SYN message, this kernel stack trace is observed: ... [ 13.396352] RIP: 0010:_copy_from_iter+0xb4/0x550 ... [ 13.398494] Call Trace: [ 13.398630] <TASK> [ 13.398630] ? __alloc_skb+0xed/0x1a0 [ 13.398630] tipc_msg_build+0x12c/0x670 [tipc] [ 13.398630] ? shmem_add_to_page_cache.isra.71+0x151/0x290 [ 13.398630] __tipc_sendmsg+0x2d1/0x710 [tipc] [ 13.398630] ? tipc_connect+0x1d9/0x230 [tipc] [ 13.398630] ? __local_bh_enable_ip+0x37/0x80 [ 13.398630] tipc_connect+0x1d9/0x230 [tipc] [ 13.398630] ? __sys_connect+0x9f/0xd0 [ 13.398630] __sys_connect+0x9f/0xd0 [ 13.398630] ? preempt_count_add+0x4d/0xa0 [ 13.398630] ? fpregs_assert_state_consistent+0x22/0x50 [ 13.398630] __x64_sys_connect+0x16/0x20 [ 13.398630] do_syscall_64+0x42/0x90 [ 13.398630] entry_SYSCALL_64_after_hwframe+0x63/0xcd It is because commit a41dad905e5a ("iov_iter: saner checks for attempt to copy to/from iterator") has introduced sanity check for copying from/to iov iterator. Lacking of copy direction from the iterator viewpoint would lead to kernel stack trace like above. This commit fixes this issue by initializing the iov iterator with the correct copy direction when sending SYN or ACK without data.

Published
May 21, 2024
Updated
Jun 17, 2026
EPSS
0.2% · 12th percentile

Report tools

JSON

Action score

22

Monitor

Low priority for now.

CVSS
22 / 40 · 5.5 / 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-2023-52700

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

    • 4.0affected
    • f25dcc7687d42a72de18aa41b04990a24c9e77c7 and later · before 54b6082aec178f16ad6d193b4ecdc9c4823d9a32affected · git
    • f25dcc7687d42a72de18aa41b04990a24c9e77c7 and later · before 11a4d6f67cf55883dc78e31c247d1903ed7fecccaffected · git
    • before 4.0not affected · semver
    • 6.1.13 and later · up to and including 6.1.*not affected · semver
    • 6.2 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.0 and later · before 6.1.13
  • linux linux kernel6.2

Package-level exposure

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

EcosystemPackageAffected rangeFix
AlmaLinux:8kernel-rtbefore 4.18.0-553.8.1.rt7.349.el8_104.18.0-553.8.1.rt7.349.el8_10
AlmaLinux:8kernel-rt-corebefore 4.18.0-553.8.1.rt7.349.el8_104.18.0-553.8.1.rt7.349.el8_10
AlmaLinux:8kernel-rt-debugbefore 4.18.0-553.8.1.rt7.349.el8_104.18.0-553.8.1.rt7.349.el8_10
AlmaLinux:8kernel-rt-debug-corebefore 4.18.0-553.8.1.rt7.349.el8_104.18.0-553.8.1.rt7.349.el8_10
AlmaLinux:8kernel-rt-debug-develbefore 4.18.0-553.8.1.rt7.349.el8_104.18.0-553.8.1.rt7.349.el8_10
AlmaLinux:8kernel-rt-debug-kvmbefore 4.18.0-553.8.1.rt7.349.el8_104.18.0-553.8.1.rt7.349.el8_10
AlmaLinux:8kernel-rt-debug-modulesbefore 4.18.0-553.8.1.rt7.349.el8_104.18.0-553.8.1.rt7.349.el8_10
AlmaLinux:8kernel-rt-debug-modules-extrabefore 4.18.0-553.8.1.rt7.349.el8_104.18.0-553.8.1.rt7.349.el8_10
AlmaLinux:8kernel-rt-develbefore 4.18.0-553.8.1.rt7.349.el8_104.18.0-553.8.1.rt7.349.el8_10
AlmaLinux:8kernel-rt-kvmbefore 4.18.0-553.8.1.rt7.349.el8_104.18.0-553.8.1.rt7.349.el8_10
AlmaLinux:8kernel-rt-modulesbefore 4.18.0-553.8.1.rt7.349.el8_104.18.0-553.8.1.rt7.349.el8_10
AlmaLinux:8kernel-rt-modules-extrabefore 4.18.0-553.8.1.rt7.349.el8_104.18.0-553.8.1.rt7.349.el8_10
Debian:12linuxbefore 6.1.15-16.1.15-1
Red Hat:enterprise_linux:8::nfvkernel-rtbefore 0:4.18.0-553.8.1.rt7.349.el8_100:4.18.0-553.8.1.rt7.349.el8_10
Red Hat:enterprise_linux:8::nfvkernel-rt-corebefore 0:4.18.0-553.8.1.rt7.349.el8_100:4.18.0-553.8.1.rt7.349.el8_10
Red Hat:enterprise_linux:8::nfvkernel-rt-debugbefore 0:4.18.0-553.8.1.rt7.349.el8_100:4.18.0-553.8.1.rt7.349.el8_10
Red Hat:enterprise_linux:8::nfvkernel-rt-debug-corebefore 0:4.18.0-553.8.1.rt7.349.el8_100:4.18.0-553.8.1.rt7.349.el8_10
Red Hat:enterprise_linux:8::nfvkernel-rt-debug-debuginfobefore 0:4.18.0-553.8.1.rt7.349.el8_100:4.18.0-553.8.1.rt7.349.el8_10
Red Hat:enterprise_linux:8::nfvkernel-rt-debug-develbefore 0:4.18.0-553.8.1.rt7.349.el8_100:4.18.0-553.8.1.rt7.349.el8_10
Red Hat:enterprise_linux:8::nfvkernel-rt-debug-kvmbefore 0:4.18.0-553.8.1.rt7.349.el8_100:4.18.0-553.8.1.rt7.349.el8_10
Red Hat:enterprise_linux:8::nfvkernel-rt-debug-modulesbefore 0:4.18.0-553.8.1.rt7.349.el8_100:4.18.0-553.8.1.rt7.349.el8_10
Red Hat:enterprise_linux:8::nfvkernel-rt-debug-modules-extrabefore 0:4.18.0-553.8.1.rt7.349.el8_100:4.18.0-553.8.1.rt7.349.el8_10
Red Hat:enterprise_linux:8::nfvkernel-rt-debuginfobefore 0:4.18.0-553.8.1.rt7.349.el8_100:4.18.0-553.8.1.rt7.349.el8_10
Red Hat:enterprise_linux:8::nfvkernel-rt-debuginfo-common-x86_64before 0:4.18.0-553.8.1.rt7.349.el8_100:4.18.0-553.8.1.rt7.349.el8_10

+5

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-48709May 21, 2024 · ice: switch: fix potential memleak in ice_add_adv_recipe()
    22Monitor
  • ← EarlierCVE-2022-48710May 21, 2024 · drm/radeon: fix a possible null pointer dereference
    22Monitor
  • Later →CVE-2023-52701May 21, 2024 · net: use a bounce buffer for copying skb->mark
    28Monitor

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 Linux11a4d6f67cf55883dc78e31c247d1903ed7fecccVendor (CNA)
Linux Linux54b6082aec178f16ad6d193b4ecdc9c4823d9a32Vendor (CNA)
almalinux:kernel-rt4.18.0-553.8.1.rt7.349.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-core4.18.0-553.8.1.rt7.349.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-debug4.18.0-553.8.1.rt7.349.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-debug-core4.18.0-553.8.1.rt7.349.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-debug-devel4.18.0-553.8.1.rt7.349.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-debug-kvm4.18.0-553.8.1.rt7.349.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-debug-modules4.18.0-553.8.1.rt7.349.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-debug-modules-extra4.18.0-553.8.1.rt7.349.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-devel4.18.0-553.8.1.rt7.349.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-kvm4.18.0-553.8.1.rt7.349.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-modules4.18.0-553.8.1.rt7.349.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-modules-extra4.18.0-553.8.1.rt7.349.el8_10 · AlmaLinux:8Package registry (OSV)
debian:linux6.1.15-1 · Debian:12Package registry (OSV)
red hat:kernel-rt0:4.18.0-553.8.1.rt7.349.el8_10 · Red Hat:enterprise_linux:8::nfvPackage registry (OSV)
red hat:kernel-rt-core0:4.18.0-553.8.1.rt7.349.el8_10 · Red Hat:enterprise_linux:8::nfvPackage registry (OSV)
red hat:kernel-rt-debug0:4.18.0-553.8.1.rt7.349.el8_10 · Red Hat:enterprise_linux:8::nfvPackage registry (OSV)
red hat:kernel-rt-debug-core0:4.18.0-553.8.1.rt7.349.el8_10 · Red Hat:enterprise_linux:8::nfvPackage registry (OSV)
red hat:kernel-rt-debug-debuginfo0:4.18.0-553.8.1.rt7.349.el8_10 · Red Hat:enterprise_linux:8::nfvPackage registry (OSV)
red hat:kernel-rt-debug-devel0:4.18.0-553.8.1.rt7.349.el8_10 · Red Hat:enterprise_linux:8::nfvPackage registry (OSV)
red hat:kernel-rt-debug-kvm0:4.18.0-553.8.1.rt7.349.el8_10 · Red Hat:enterprise_linux:8::nfvPackage registry (OSV)
red hat:kernel-rt-debug-modules0:4.18.0-553.8.1.rt7.349.el8_10 · Red Hat:enterprise_linux:8::nfvPackage registry (OSV)
red hat:kernel-rt-debug-modules-extra0:4.18.0-553.8.1.rt7.349.el8_10 · Red Hat:enterprise_linux:8::nfvPackage registry (OSV)
red hat:kernel-rt-debuginfo0:4.18.0-553.8.1.rt7.349.el8_10 · Red Hat:enterprise_linux:8::nfvPackage registry (OSV)
red hat:kernel-rt-debuginfo-common-x86_640:4.18.0-553.8.1.rt7.349.el8_10 · Red Hat:enterprise_linux:8::nfvPackage registry (OSV)
red hat:kernel-rt-devel0:4.18.0-553.8.1.rt7.349.el8_10 · Red Hat:enterprise_linux:8::nfvPackage registry (OSV)
rocky linux:kernel-rt0:4.18.0-553.8.1.rt7.349.el8_10 · Rocky Linux:8Package 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.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2025-22069330 days apartriscv: fgraph: Fix stack layout to match __arch_ftrace_regs argument of ftrace_return_to_handler
    31Monitor
  • CVE-2024-360329 days apartBluetooth: qca: fix info leak when fetching fw build id
    28Monitor
  • CVE-2024-360339 days apartBluetooth: qca: fix info leak when fetching board id
    28Monitor
  • CVE-2022-4875730 days apartnet: fix information leakage in /proc/net/ptype
    28Monitor
  • CVE-2024-3949952 days apartvmci: prevent speculation leaks by sanitizing event in event_deliver()
    28Monitor
  • CVE-2024-4388191 days apartwifi: ath12k: change DMA direction while mapping reinjected packets
    28Monitor

Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · 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
none
Availability
none
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
None
Availability impact
None

CVSS vector

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

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 (1 more)

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

All records