CVE-2026-74694 — net/ncsi: fix heap OOB read in NCSI_CMD_SEND_CMD payload length
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.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.2% (30-day exploitation probability)+2
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Linux Linux).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Linux | Linux |
≥ 9771b8ccdfa6dcb1ac5128ca7fe8649f3092d392 and < e60afa01d35f8b2671b27ca93309921427144cce≥ 9771b8ccdfa6dcb1ac5128ca7fe8649f3092d392 and < 67c72b8ef63d9d9a610546fda30b116638f39745≥ 9771b8ccdfa6dcb1ac5128ca7fe8649f3092d392 and < 4489b4a17892750131e4bef4bc1d3d703c8fb5ba≥ 9771b8ccdfa6dcb1ac5128ca7fe8649f3092d392 and < 43c7d0a6917751ea898ae584d00f24f5deac46d4≥ 9771b8ccdfa6dcb1ac5128ca7fe8649f3092d392 and < b5231ad0b376b801ab8cf2962b182cc29deaedb3≥ 9771b8ccdfa6dcb1ac5128ca7fe8649f3092d392 and < 02226af69362758046822840fc6a497f5de33f00≥ 9771b8ccdfa6dcb1ac5128ca7fe8649f3092d392 and < 3a60b5af75abe8e3494ccd074fb4ae6e601a3e55≥ 9771b8ccdfa6dcb1ac5128ca7fe8649f3092d392 and < afa58b7384913c8773d837acdb07b035690ec5d2 and 1 moreversion 4.20 |
Vulnerable | CVE Program (cve.org) e CISA ADP |
EPSS over time FIRST
Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 0.22%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Not enough vector or weakness data: use the affected application’s logs as a starting point.
Timeline
What happened to this CVE, newest first.
- 2026
- Record published
- Affected products added · linux/linux
- Source status changed · → Received
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× References added · Oct 14, 2026 – Oct 14, 2026
- 1× Official description updated · Oct 14, 2026 – Oct 14, 2026
References
10 on the record
- git.kernel.org/stable/c/3a60b5af75abe8e3494ccd074fb4ae6e601a3e55
- git.kernel.org/stable/c/43c7d0a6917751ea898ae584d00f24f5deac46d4
- git.kernel.org/stable/c/afa58b7384913c8773d837acdb07b035690ec5d2
- github.com/advisories/GHSA-9677-c9p4-rgm3
- git.kernel.org/stable/c/67c72b8ef63d9d9a610546fda30b116638f39745
- git.kernel.org/stable/c/02226af69362758046822840fc6a497f5de33f00
- git.kernel.org/stable/c/4489b4a17892750131e4bef4bc1d3d703c8fb5ba
- git.kernel.org/stable/c/b5231ad0b376b801ab8cf2962b182cc29deaedb3
- git.kernel.org/stable/c/e60afa01d35f8b2671b27ca93309921427144cce
- nvd.nist.gov/vuln/detail/CVE-2026-74694
Elsewhere on this site
Related CVEs (same products)
- Critical CVE-2026-99999 ipv4: validate checksum_start before completing checksum 10h
- Unknown CVE-2026-98432 ipv4: free inet_opt and ireq_opt after an RCU grace period 10h
- Unknown CVE-2026-98430 RDMA/efa: Keep admin queues alive while IRQ is registered 1d
- Unknown CVE-2026-98431 RDMA/uverbs: Fix mmap_lock/disassociation_lock circular dependency 1d
- Unknown CVE-2026-98429 RDMA/efa: Keep EQ resources alive while IRQ is registered 1d
- Unknown CVE-2026-98428 ALSA: usb: 6fire: Avoid embedded URBs 1d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No CVSS score published by NVD, the CNA, CISA or GitHub so far.
- No fixed version, patch or mitigation documented.
- No CISA SSVC assessment.
- No CWE classification.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-74694 is "net/ncsi: fix heap OOB read in NCSI_CMD_SEND_CMD payload length", rated Unknown. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. EPSS 0.22% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.