Skip to main content
Vulnerability Database/CVE-2026-98525

CVE-2026-98525: Linux Kernel MCTP Privilege Escalation

CVE-2026-98525 is a privilege escalation flaw in the Linux kernel MCTP routing layer that allows unauthorized tag consumption across sockets. This article covers the technical details, security impact, and remediation.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2026-98525 Overview

CVE-2026-98525 is a Linux kernel vulnerability in the Management Component Transport Protocol (MCTP) routing subsystem. The function mctp_lookup_prealloc_tag() iterates the per-network-namespace &mns->keys list and matches on netid, req_tag, peer_addr, and manual_alloc without verifying that the matched key belongs to the calling socket. Any MCTP socket within the same network namespace can therefore consume another socket's preallocated tag when transmitting a packet with MCTP_TAG_PREALLOC set. The flaw was validated in QEMU against Linux 7.3.0-rc3, where a second socket successfully transmitted using another socket's manually allocated tag.

Critical Impact

Any MCTP socket in the same network namespace can hijack another socket's preallocated tag, enabling cross-socket packet transmission under a tag the attacker never allocated.

Affected Products

  • Linux kernel MCTP subsystem (net/mctp/route.c)
  • Linux kernel versions prior to the fix commits referenced below
  • Linux 7.3.0-rc3 confirmed vulnerable in QEMU testing

Discovery Timeline

  • 2026-10-18 - CVE-2026-98525 published to NVD
  • 2026-10-19 - Last updated in NVD database

Technical Details for CVE-2026-98525

Vulnerability Analysis

The Management Component Transport Protocol (MCTP) permits userspace sockets to preallocate transmission tags via SIOCMCTPALLOCTAG. These tags are tracked in two scopes: a per-network-namespace list &mns->keys and a per-socket list &msk->keys reachable through sklist. When a socket calls sendto() with MCTP_TAG_PREALLOC, mctp_lookup_prealloc_tag() must locate the previously allocated tag.

The vulnerable implementation searches the namespace-wide &mns->keys list and matches on tuple fields netid, req_tag, peer_addr, and manual_alloc. It never checks that tmp->sk == &msk->sk. Any socket in the namespace that supplies the same tuple will match another socket's key.

Reproduction in QEMU demonstrated the flaw: socket A allocated manual tag 0x18 for peer EID 9, after which socket B successfully transmitted a 4-byte message using that tag (sendto() returned 4). After the patch, the same call from socket B returns -ENOENT while the owning socket A continues to transmit successfully.

Root Cause

The root cause is a missing ownership check in a lookup routine, a form of broken access control at the kernel object level. The lookup trusts namespace-scoped state to enforce per-socket boundaries, violating the isolation that MCTP tag preallocation is meant to provide.

Attack Vector

Exploitation requires a local attacker with the ability to open MCTP sockets in the same network namespace as the victim socket. The attacker calls sendto() with MCTP_TAG_PREALLOC and the victim's tuple, consuming or interfering with the victim's reserved tag. This can disrupt MCTP-based device management traffic or inject packets under tags associated with another socket. No synthetic exploit code is published; refer to the upstream commits for the authoritative reproduction.

// No verified exploit code published. See upstream fix commits for the
// authoritative patch and reproduction notes.

Detection Methods for CVE-2026-98525

Indicators of Compromise

  • Unexpected MCTP packets transmitted with tags allocated by a different process or socket.
  • sendto() success on sockets that did not call SIOCMCTPALLOCTAG for the tag in use.
  • Anomalous MCTP peer communication from processes that do not legitimately manage baseboard or device endpoints.

Detection Strategies

  • Audit kernel versions across Linux hosts and compare against the fix commits 09299add, 26cc0e69, e35cb500, and f178300e.
  • Monitor SIOCMCTPALLOCTAG ioctl usage and correlate allocating PIDs with sockets that later transmit under the allocated tags.
  • Review MCTP traffic captures on management interfaces for tag reuse across unrelated userspace processes.

Monitoring Recommendations

  • Enable auditd rules for MCTP socket creation and ioctl operations on hosts that use MCTP for BMC or peripheral management.
  • Alert on new processes opening AF_MCTP sockets outside of expected management daemons.
  • Track kernel package versions through configuration management to detect unpatched hosts.

How to Mitigate CVE-2026-98525

Immediate Actions Required

  • Apply the upstream kernel patches that iterate &msk->keys via sklist instead of the namespace-wide &mns->keys in mctp_lookup_prealloc_tag().
  • Restrict AF_MCTP socket creation to trusted system services where possible using Linux capabilities or seccomp policies.
  • Isolate MCTP-using workloads into dedicated network namespaces to shrink the pool of sockets that can collide on the vulnerable lookup.

Patch Information

The fix changes mctp_lookup_prealloc_tag() to iterate the socket's own tag list, ensuring only tags allocated by the calling socket match. Patches are available in upstream commits: Kernel Git Commit 09299add, Kernel Git Commit 26cc0e69, Kernel Git Commit e35cb500, and Kernel Git Commit f178300e.

Workarounds

  • Disable the MCTP kernel module (CONFIG_MCTP) on systems that do not require MCTP transport.
  • Use network namespace isolation to prevent untrusted processes from sharing a namespace with MCTP management daemons.
  • Enforce mandatory access control (SELinux, AppArmor) policies that restrict AF_MCTP socket creation to known-good binaries.
bash
# Blacklist the MCTP module if not required
echo 'blacklist mctp' | sudo tee /etc/modprobe.d/disable-mctp.conf
sudo rmmod mctp 2>/dev/null || true

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.