Vulnary
← back to the feed
Critical· 9.8official fix available

CVE-2023-53517

A flaw in the Linux kernel’s TIPC module allows a malicious peer to send a very small MTU value during link negotiation, causing an integer overflow that can crash the kernel. The bug is triggered by an attacker who sends an Activate message with an MTU of 4, leading to a huge memory allocation and a kernel panic. The issue has been fixed in a kernel patch that validates the MTU before updating it.

publishedOct 1, 2025
last modifiedAug 4, 2026
sourcesNVD
severity · cvss
9.8
critical · how bad it is
exploitation · epss
<1%
20th percentile · chance of exploitation in 30 days
(ai-assisted) A model wrote this summary from the official data, so double-check it against the source before you act on it. Read the official advisory →
auto-deletes from the system
counting…on Sep 3, 2026

An official fix is available, so this entry is kept for 30 days and then removed automatically.

01

Who is affected

Linux kernel users running versions that include the TIPC module before the patch, notably kernel 6.4 and earlier. Any system that accepts TIPC connections is potentially affected.

02

Real-world impact

An attacker can cause the kernel to crash, resulting in a denial‑of‑service that brings the entire system down. The crash can be triggered remotely without authentication, making it a critical threat to uptime and availability.

03

Why this severity

The CVSS score of 9.8 reflects that the vulnerability is exploitable over the network (AV:N), requires no privileges (PR:N), has no user interaction (UI:N), and can lead to complete compromise of confidentiality, integrity, and availability (C:H/I:H/A:H).

04

What to do about it

official fix available
recommended steps
  1. 011. Verify your current kernel version with `uname -r`.
  2. 022. If your kernel is older than 6.4, upgrade to Linux kernel 6.4 or a later release that includes the TIPC MTU validation patch.
  3. 033. Reboot the system to load the updated kernel.

NVD-referenced vendor advisory

05

Timeline

  1. Oct 1, 2025 · Oct 1, 2025
    Published
    Disclosed and added to the National Vulnerability Database.
  2. Aug 4, 2026 · 1d ago
    Advisory updated
    The NVD record was last revised.
  3. Aug 4, 2026 · 1d ago
    Official fix available
    A vendor patch or mitigation now exists — see the remediation steps above.
06

How it’s attacked

Attack vectorNetwork (remote)
Attack complexityLow
Privileges requiredNone
User interactionNone needed
ScopeUnchanged
Confidentiality impactHigh
Integrity impactHigh
Availability impactHigh
07

References & advisories

(ai-assisted) A model wrote this summary from the official data, so double-check it against the source before you act on it. Read the official advisory →