Vulnerability · Published Oct 1, 2025 · Assigned by Linux

CVE-2023-53517tipc: do not update mtu if msg_max is too small in mtu negotiation

Critical 9.8

In plain English

A critical-severity security flaw in Linux from Linux. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.3% (higher than 23% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS 3.1)9.8Critical
Exploit odds (30 days)0.3%top 76.6% of all CVEs
Exploited in the wildNo reportsCISA SSVC: none
Attack toolingNoneno public tooling known

Official description

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.

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
Debian:12linux6.1.37-1DEBIAN-CVE-2023-53517
Debian:13linux6.3.7-1DEBIAN-CVE-2023-53517
Debian:14linux6.3.7-1DEBIAN-CVE-2023-53517
Ubuntu:22.04:LTSlinux5.15.0-83.92UBUNTU-CVE-2023-53517
Ubuntu:22.04:LTSlinux-allwinner-5.19no fix listedUBUNTU-CVE-2023-53517
Ubuntu:22.04:LTSlinux-aws5.15.0-1044.49UBUNTU-CVE-2023-53517
Ubuntu:22.04:LTSlinux-aws-5.19no fix listedUBUNTU-CVE-2023-53517
Ubuntu:22.04:LTSlinux-aws-6.2no fix listedUBUNTU-CVE-2023-53517
Ubuntu:22.04:LTSlinux-aws-6.5no fix listedUBUNTU-CVE-2023-53517
Ubuntu:22.04:LTSlinux-azure5.15.0-1046.53UBUNTU-CVE-2023-53517
Ubuntu:22.04:LTSlinux-azure-5.19no fix listedUBUNTU-CVE-2023-53517
Ubuntu:24.04:LTSlinux-azure-6.11no fix listedUBUNTU-CVE-2023-53517
Ubuntu:22.04:LTSlinux-azure-6.2no fix listedUBUNTU-CVE-2023-53517
Ubuntu:22.04:LTSlinux-azure-6.5no fix listedUBUNTU-CVE-2023-53517
Ubuntu:22.04:LTSlinux-azure-fde5.15.0-1046.53.1UBUNTU-CVE-2023-53517
Ubuntu:22.04:LTSlinux-azure-fde-5.19no fix listedUBUNTU-CVE-2023-53517
Ubuntu:22.04:LTSlinux-azure-fde-6.2no fix listedUBUNTU-CVE-2023-53517
Ubuntu:22.04:LTSlinux-gcp5.15.0-1041.49UBUNTU-CVE-2023-53517
Ubuntu:22.04:LTSlinux-gcp-5.19no fix listedUBUNTU-CVE-2023-53517
Ubuntu:24.04:LTSlinux-gcp-6.11no fix listedUBUNTU-CVE-2023-53517
Ubuntu:22.04:LTSlinux-gcp-6.2no fix listedUBUNTU-CVE-2023-53517
Ubuntu:22.04:LTSlinux-gcp-6.5no fix listedUBUNTU-CVE-2023-53517
Ubuntu:22.04:LTSlinux-gke5.15.0-1041.46UBUNTU-CVE-2023-53517
Ubuntu:22.04:LTSlinux-gkeop5.15.0-1027.32UBUNTU-CVE-2023-53517
Ubuntu:22.04:LTSlinux-hwe-5.19no fix listedUBUNTU-CVE-2023-53517
Ubuntu:24.04:LTSlinux-hwe-6.11no fix listedUBUNTU-CVE-2023-53517
Ubuntu:22.04:LTSlinux-hwe-6.2no fix listedUBUNTU-CVE-2023-53517
Ubuntu:22.04:LTSlinux-hwe-6.5no fix listedUBUNTU-CVE-2023-53517
Ubuntu:22.04:LTSlinux-ibm5.15.0-1037.40UBUNTU-CVE-2023-53517
Ubuntu:24.04:LTSlinux-intelno fix listedUBUNTU-CVE-2023-53517
Ubuntu:22.04:LTSlinux-intel-iot-realtimeno fix listedUBUNTU-CVE-2023-53517
Ubuntu:22.04:LTSlinux-intel-iotg5.15.0-1039.45UBUNTU-CVE-2023-53517
Ubuntu:22.04:LTSlinux-kvm5.15.0-1041.46UBUNTU-CVE-2023-53517
Ubuntu:22.04:LTSlinux-lowlatency5.15.0-83.92UBUNTU-CVE-2023-53517
Ubuntu:22.04:LTSlinux-lowlatency-hwe-5.19no fix listedUBUNTU-CVE-2023-53517
Ubuntu:24.04:LTSlinux-lowlatency-hwe-6.11no fix listedUBUNTU-CVE-2023-53517
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.2no fix listedUBUNTU-CVE-2023-53517
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.5no fix listedUBUNTU-CVE-2023-53517
Ubuntu:22.04:LTSlinux-nvidia5.15.0-1032.32UBUNTU-CVE-2023-53517
Ubuntu:22.04:LTSlinux-nvidia-6.2no fix listedUBUNTU-CVE-2023-53517
Ubuntu:22.04:LTSlinux-nvidia-6.5no fix listedUBUNTU-CVE-2023-53517
Ubuntu:22.04:LTSlinux-nvidia-tegra5.15.0-1017.17UBUNTU-CVE-2023-53517
Ubuntu:22.04:LTSlinux-nvidia-tegra-igx5.15.0-1004.4UBUNTU-CVE-2023-53517
Ubuntu:22.04:LTSlinux-oem-5.17no fix listedUBUNTU-CVE-2023-53517
Ubuntu:22.04:LTSlinux-oem-6.0no fix listedUBUNTU-CVE-2023-53517
Ubuntu:22.04:LTSlinux-oem-6.1no fix listedUBUNTU-CVE-2023-53517
Ubuntu:24.04:LTSlinux-oem-6.11no fix listedUBUNTU-CVE-2023-53517
Ubuntu:22.04:LTSlinux-oem-6.5no fix listedUBUNTU-CVE-2023-53517
Ubuntu:24.04:LTSlinux-oem-6.8no fix listedUBUNTU-CVE-2023-53517
Ubuntu:22.04:LTSlinux-oracle5.15.0-1042.48UBUNTU-CVE-2023-53517
Ubuntu:22.04:LTSlinux-oracle-6.5no fix listedUBUNTU-CVE-2023-53517
Ubuntu:22.04:LTSlinux-raspi5.15.0-1037.40UBUNTU-CVE-2023-53517
Ubuntu:24.04:LTSlinux-raspi-realtimeno fix listedUBUNTU-CVE-2023-53517
Ubuntu:22.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2023-53517
Ubuntu:24.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2023-53517
Ubuntu:22.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2023-53517
Ubuntu:24.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2023-53517
Ubuntu:22.04:LTSlinux-riscv-5.19no fix listedUBUNTU-CVE-2023-53517
Ubuntu:22.04:LTSlinux-riscv-6.5no fix listedUBUNTU-CVE-2023-53517
Ubuntu:22.04:LTSlinux-starfive-5.19no fix listedUBUNTU-CVE-2023-53517
Ubuntu:22.04:LTSlinux-starfive-6.2no fix listedUBUNTU-CVE-2023-53517
Ubuntu:22.04:LTSlinux-starfive-6.5no fix listedUBUNTU-CVE-2023-53517
Ubuntu:22.04:LTSlinux-xilinx-zynqmp5.15.0-1025.29UBUNTU-CVE-2023-53517

Affected products (as reported)

VendorProductVersions
Linux Linux ed193ece2649c194a87a9d8470195760d367c075 – before 2bd4ff4ffb92113f8acd04dbaed83269172c24b4ed193ece2649c194a87a9d8470195760d367c075 – before 575e84d90a74c0b091b3417ba763ebb237aa0a8ced193ece2649c194a87a9d8470195760d367c075 – before 259683001d7e879fea4b42084fb6560dd9408a7eed193ece2649c194a87a9d8470195760d367c075 – before 1dd7ae5e0cf5a56e513f7ab7ab9570b7496281d2ed193ece2649c194a87a9d8470195760d367c075 – before 56077b56cd3fb78e1c8619e29581ba25a5c55e86
Linux Linux 4.1

References