CVE-2026-74694

net/ncsi: fix heap OOB read in NCSI_CMD_SEND_CMD payload length

N/A
Published: August 22, 2026 at 03:32 PM UTC
Updated: October 14, 2026 at 01:10 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: net/ncsi: fix heap OOB read in NCSI_CMD_SEND_CMD payload length ncsi_send_cmd_nl() takes the number of bytes to copy from the attacker-controlled ncsi_pkt_hdr.length field of the in-band packet header, while the source buffer is the NCSI_ATTR_DATA netlink attribute whose readable size is nla_len() - sizeof(ncsi_pkt_hdr). The two length sources are never cross-checked: only nla_len() >= sizeof(struct ncsi_pkt_hdr) is enforced. With hdr->length set larger than the attribute payload (up to 65535 against at most 2032 readable bytes), ncsi_cmd_handler_oem() copies past the end of the netlink attribute buffer with unsafe_memcpy(), leaking up to ~64KB of kernel heap memory into the transmitted NCSI command packet. The destination skb is sized by the declared payload, so the write side does not overflow - this is a pure OOB read / information leak, reachable with CAP_NET_ADMIN on systems with a registered NCSI device (e.g. OpenBMC on Aspeed BMC SoCs, where NET_NCSI=y is standard). Reject commands whose declared payload extends past the end of the data attribute. The issue was found by the autokbug dynamic kernel fuzzer at Tencent Yunding Lab.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

4.209771b8ccdfa6dcb1ac5128ca7fe8649f3092d392
Vendor states this is fixed in 02226af69362758046822840fc6a497f5de33f00 (fixed)
Vendor states this is fixed in 3a60b5af75abe8e3494ccd074fb4ae6e601a3e55 (fixed)
Vendor states this is fixed in 43c7d0a6917751ea898ae584d00f24f5deac46d4 (fixed)
Vendor states this is fixed in 4489b4a17892750131e4bef4bc1d3d703c8fb5ba (fixed)
Vendor states this is fixed in 67c72b8ef63d9d9a610546fda30b116638f39745 (fixed)
Vendor states this is fixed in afa58b7384913c8773d837acdb07b035690ec5d2 (fixed)
Vendor states this is fixed in b5231ad0b376b801ab8cf2962b182cc29deaedb3 (fixed)
Vendor states this is fixed in e60afa01d35f8b2671b27ca93309921427144cce (fixed)
Vendor states this is fixed in 4.20 (unaffected)
Vendor states this is fixed in 5.10.265 (unaffected)
Vendor states this is fixed in 5.15.216 (unaffected)
Vendor states this is fixed in 6.1.183 (unaffected)
Vendor states this is fixed in 6.12.104 (unaffected)
Vendor states this is fixed in 6.18.45 (unaffected)
Vendor states this is fixed in 6.6.152 (unaffected)
Vendor states this is fixed in 7.1.9 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card