cve.bz

CVE-2023-53517 linux linux kernel

5.5 mediumEPSS 0.3%Fix available

Medium (5.5) in linux linux kernel. EPSS 0.3% estimated probability of exploitation activity in the next 30 days.

On this page
In the Linux kernel, the following vulnerability has been resolved: tipc: do not update mtu if msg_max is too small in mtu negotiation When doing link mtu negotiation, a malicious peer may send Activate msg with a very small mtu, e.g. 4 in Shuang's testing, without checking for the minimum mtu, l->mtu will be set to 4 in tipc_link_proto_rcv(), then n->links[bearer_id].mtu is set to 4294967228, which is a overflow of '4 - INT_H_SIZE - EMSG_OVERHEAD' in tipc_link_mss(). With tipc_link.mtu = 4, tipc_link_xmit() kept printing the warning: tipc: Too large msg, purging xmit list 1 5 0 40 4! tipc: Too large msg, purging xmit list 1 15 0 60 4! And with tipc_link_entry.mtu 4294967228, a huge skb was allocated in named_distribute(), and when purging it in tipc_link_xmit(), a crash was even caused: general protection fault, probably for non-canonical address 0x2100001011000dd: 0000 [#1] PREEMPT SMP PTI CPU: 0 PID: 0 Comm: swapper/0 Kdump: loaded Not tainted 6.3.0.neta #19 RIP: 0010:kfree_skb_list_reason+0x7e/0x1f0 Call Trace: <IRQ> skb_release_data+0xf9/0x1d0 kfree_skb_reason+0x40/0x100 tipc_link_xmit+0x57a/0x740 [tipc] tipc_node_xmit+0x16c/0x5c0 [tipc] tipc_named_node_up+0x27f/0x2c0 [tipc] tipc_node_write_unlock+0x149/0x170 [tipc] tipc_rcv+0x608/0x740 [tipc] tipc_udp_recv+0xdc/0x1f0 [tipc] udp_queue_rcv_one_skb+0x33e/0x620 udp_unicast_rcv_skb.isra.72+0x75/0x90 __udp4_lib_rcv+0x56d/0xc20 ip_protocol_deliver_rcu+0x100/0x2d0 This patch fixes it by checking the new mtu against tipc_bearer_min_mtu(), and not updating mtu if it is too small.

Severity

CVSS 3.1

5.5 medium
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS
0.3% (unchanged from 0.3% a week ago; 0.3% 30 days ago) estimated probability of exploitation activity in the next 30 days; 24th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: total, assessed 2026-10-15. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2023-53517 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2023-53517?via=ask-ai-copy and https://cve.bz/cve/CVE-2023-53517?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2023-53517 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Linux4.1 and later

Fixed in

ProductRelease lineFixed in
Linux5.105.10.181
Linux5.155.15.113
Linux6.16.1.30
Linux6.36.3.4
Linuxlater releases6.4

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12linux6.1.37-1DEBIAN-CVE-2023-53517
Debian13, 14linux6.3.7-1DEBIAN-CVE-2023-53517
Ubuntu16.04:LTSlinux-hwe-edgeno fix listedUBUNTU-CVE-2023-53517
Ubuntu18.04:LTSlinux-gcp, linux-hwe, linux-oem and 12 moreno fix listedUBUNTU-CVE-2023-53517
Ubuntu20.04:LTSlinux-aws-5.155.15.0-1044.49~20.04.1UBUNTU-CVE-2023-53517
Ubuntu20.04:LTSlinux-azure-5.155.15.0-1046.53~20.04.1UBUNTU-CVE-2023-53517
Ubuntu20.04:LTSlinux-gcp-5.155.15.0-1041.49~20.04.1UBUNTU-CVE-2023-53517
Ubuntu20.04:LTSlinux-gke, linux-gkeop, linux-riscv and 26 moreno fix listedUBUNTU-CVE-2023-53517
Ubuntu20.04:LTSlinux-hwe-5.15, linux-lowlatency-hwe-5.155.15.0-83.92~20.04.1UBUNTU-CVE-2023-53517
Ubuntu20.04:LTSlinux-ibm-5.155.15.0-1037.40~20.04.1UBUNTU-CVE-2023-53517
Ubuntu20.04:LTSlinux-intel-iotg-5.155.15.0-1040.46~20.04.1UBUNTU-CVE-2023-53517
Ubuntu20.04:LTSlinux-nvidia-tegra-5.155.15.0-1017.17~20.04.1UBUNTU-CVE-2023-53517
Ubuntu20.04:LTSlinux-oracle-5.155.15.0-1042.48~20.04.1UBUNTU-CVE-2023-53517
Ubuntu20.04:LTSlinux-riscv-5.155.15.0-1040.44~20.04.3UBUNTU-CVE-2023-53517
25 more for Ubuntu in the JSON and on Ubuntu's page.
Red Hatenterprise_linux:8::baseosperf, kernel, bpftool and 30 more0:4.18.0-513.5.1.el8_9RHSA-2023:7077
Red Hatenterprise_linux:8::crbperf-debuginfo, kernel-debuginfo, bpftool-debuginfo and 7 more0:4.18.0-513.5.1.el8_9RHSA-2023:7077
Red Hatenterprise_linux:9::appstreamrv, perf, rtla and 24 more0:5.14.0-362.8.1.el9_3RHSA-2023:6583
Red Hatenterprise_linux:9::appstream, enterprise_linux:9::crb, enterprise_linux:9::nfv and 1 morebpftool-debuginfo0:7.2.0-362.8.1.el9_3RHSA-2023:6583
Red Hatenterprise_linux:9::baseosbpftool, bpftool-debuginfo0:7.2.0-362.8.1.el9_3RHSA-2023:6583
Red Hatenterprise_linux:9::baseoskernel, kernel-64k, kernel-core and 41 more0:5.14.0-362.8.1.el9_3RHSA-2023:6583
Red Hatenterprise_linux:9::crblibperf, perf-debuginfo, kernel-debuginfo and 12 more0:5.14.0-362.8.1.el9_3RHSA-2023:6583
Red Hatenterprise_linux:9::nfvkernel-rt, kernel-rt-kvm, kernel-rt-core and 20 more0:5.14.0-362.8.1.el9_3RHSA-2023:6583
Red Hatenterprise_linux:9::realtimekernel-rt, kernel-rt-core, perf-debuginfo and 18 more0:5.14.0-362.8.1.el9_3RHSA-2023:6583
SUSELinux Enterprise Live Patching 12 SP5kernel-default4.12.14-122.280.1SUSE-SU-2025:4189-1
SUSELinux Enterprise Live Patching 12 SP5kgraft-patch-SLE12-SP5_Update_741-8.5.1SUSE-SU-2025:4189-1
SUSELinux Enterprise Server 12 SP5-LTSS, Linux Enterprise Server LTSS Extended Security 12 SP5kernel-syms, kernel-source, kernel-default4.12.14-122.280.1SUSE-SU-2025:4189-1
Alpaquitastreamlinux-lts6.6.58-r0BELL-CVE-2023-53517

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; Red Hat Security Data © Red Hat, Inc., CC BY 4.0; SUSE security data, CC BY 4.0; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · Red Hat · SUSE · Alpaquita.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

A moderate-severity denial of service flaw was found in the Linux kernel's Transparent Inter-Process Communication (TIPC) implementation shipped in Red Hat Enterprise Linux 8 and 9. During TIPC link MTU negotiation, a malicious peer can send a specially crafted Activate message advertising a very small MTU value (as small as 4 bytes). Because the negotiated MTU was not validated against the bearer minimum MTU, the MSS computation underflows and produces a huge link MTU value. This causes repeated transmission failures and, through the allocation and subsequent purge of a very large socket buffer, can crash the kernel, resulting in a denial of service. There is no impact on confidentiality or integrity.

The kernel and kernel-rt packages in Red Hat Enterprise Linux 8 and 9 are affected, and the fix for these streams is currently deferred given the moderate, availability-only impact of the flaw. The residual risk on affected releases is a system crash (denial of service) on systems where TIPC is configured and in use and where an attacker is able to act as a peer in link MTU negotiation. Red Hat Enterprise Linux 6, 7, and 10, and Red Hat In-Vehicle OS, are not affected because the vulnerable code is not present in those releases.

Red Hat and NIST both rate this flaw as Moderate (CVSS 3.1 base score 5.5, CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H), which differs significantly from the Critical score (9.8) in the upstream CVEORG record. Red Hat's scoring reflects the availability-only impact and the requirement that TIPC be configured and the attacker able to participate as a peer in link MTU negotiation.

Red Hat's mitigation

To mitigate this issue, prevent the `tipc` kernel module from loading by creating a blacklist file. This may impact functionality that relies on TIPC.

Create a file named `/etc/modprobe.d/blacklist-tipc.conf` with the following content:

```

blacklist tipc

```

After creating the file, regenerate the initramfs and reboot the system for the changes to take effect.

```bash

druncate -s 0 /etc/modprobe.d/blacklist-tipc.conf

echo "blacklist tipc" >> /etc/modprobe.d/blacklist-tipc.conf

druncate -s 0 /etc/modules-load.d/tipc.conf

mkinitrd -f /boot/initramfs-$(uname -r).img $(uname -r)

reboot

```

Warning: A system reboot is required for the mitigation to be fully applied and to ensure the module is not loaded.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 8kernel-0:4.18.0-513.5.1.el8_9Fixed 2023-11-14RHSA-2023:7077
Red Hat Enterprise Linux 10kernelNot affected
Red Hat Enterprise Linux 6kernelNot affected
Red Hat Enterprise Linux 7kernelNot affected
Red Hat Enterprise Linux 7kernel-rtNot affected
Red Hat Enterprise Linux 8kernel-rtFix deferred
Red Hat Enterprise Linux 9kernelFix deferred
Red Hat Enterprise Linux 9kernel-rtFix deferred

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2023-53517.

References

Check your stackJSON