CVE-2026-68124

Source
https://cve.org/CVERecord?id=CVE-2026-68124
Import Source
https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-68124.json
JSON Data
https://api.osv.dev/v1/vulns/CVE-2026-68124
Downstream
Published
2026-08-10T11:58:44.997Z
Modified
2026-08-12T04:19:21.408348759Z
Summary
mctp: serial: handle zero-length frames to prevent rx buffer overflow
Details

In the Linux kernel, the following vulnerability has been resolved:

mctp: serial: handle zero-length frames to prevent rx buffer overflow

The MCTP serial receive state machine reads a frame length byte in mctpserialpush_header() case 2 and validates it upper-bound-only:

if (c > MCTP_SERIAL_FRAME_MTU) {
    dev->rxstate = STATE_ERR;
} else {
    dev->rxlen = c;
    dev->rxpos = 0;
    dev->rxstate = STATE_DATA;
    ...
}

A length of zero passes this check, so rxlen is set to 0 and the state machine advances to STATEDATA. In mctpserialpush() STATEDATA, the incoming byte is stored and rxpos incremented before the terminator is

dev->rxbuf[dev->rxpos] = c;
dev->rxpos++;
dev->rxstate = STATE_DATA;
if (dev->rxpos == dev->rxlen) {
    dev->rxpos = 0;
    dev->rxstate = STATE_TRAILER;
}

With rxlen == 0 the "rxpos == rxlen" terminator can never fire (rxpos is already 1 on the first data byte), so subsequent bytes are written past the end of the fixed 74-byte rxbuf, which is the last member of the netdev private area. Every following data byte is an attacker-controlled 1-byte out-of-bounds heap write, and the overflow continues until a frame (0x7e) or escape byte resets the parser -- effectively unbounded.

Reaching this requires CAPNETADMIN to attach the N_MCTP line discipline and bring the resulting mctpserialN netdev up, after which the bytes arrive via the tty receive path.

Route a zero-length frame straight to STATETRAILER instead of STATEDATA. The trailer/framing bytes are still consumed, and the frame resolves to a zero-length skb that the MCTP core rejects; the parser never enters STATE_DATA with rxlen == 0, so the out-of-bounds write can no longer occur.

KASAN, on a frame of 0x7e 0x01 0x00 followed by data bytes (before this change):

UBSAN: array-index-out-of-bounds in drivers/net/mctp/mctp-serial.c:370 index 74 is out of range for type 'u8 [74]' BUG: KASAN: slab-out-of-bounds in mctpserialttyreceivebuf Write of size 1 at addr ... by task kworker/u16:0 mctpserialttyreceivebuf ttyldiscreceivebuf flushtoldisc Allocated by task 152: allocnetdevmqs mctpserial_open

v2: route zero-length frames to STATETRAILER instead of STATEERR so the trailer/framing bytes are still consumed (Jeremy Kerr).

Found by 0sec automated security-research tooling (https://0sec.ai).

Database specific
{
    "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/68xxx/CVE-2026-68124.json",
    "cna_assigner": "Linux"
}
References

Affected packages

Git / git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git

Affected ranges

Type
GIT
Repo
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Events
Introduced
a0c2ccd9b5ad0a9e838158404e041b5a8ff762dd
Fixed
36dc6d6964a3b90411cc7944cd9b8b6f67b9807b
Fixed
68819427bc07eca7963a9e8be19e5272cc29186c
Fixed
f80ba170d7b3a44e3d244a2c8e06031d61bf3b23
Fixed
06a6b606129c8a25cd457760f5370f3ff01fe05d
Fixed
793b9b729f1e8de57be8c8daf1a9838be96cabed

Database specific

source
"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-68124.json"

Linux / Kernel

Package

Name
Kernel

Affected ranges

Type
ECOSYSTEM
Events
Introduced
5.17.0
Fixed
6.6.148
Type
ECOSYSTEM
Events
Introduced
6.7.0
Fixed
6.12.101
Type
ECOSYSTEM
Events
Introduced
6.13.0
Fixed
6.18.42
Type
ECOSYSTEM
Events
Introduced
6.19.0
Fixed
7.1.6

Database specific

source
"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-68124.json"