In the Linux kernel, the following vulnerability has been resolved: octeontx2-af: validate body pcifunc in rvu_mbox_handler_rep_event_notify… (CVE-2026-63923)
A vulnerability in the Linux kernel's octeontx2-af driver allowed an attacker-controlled field (pcifunc) in a REP_EVENT_NOTIFY request to bypass bounds checks, leading to out-of-bounds memory writes. This occurs because the body pcifunc field was not validated before being used as an index into internal arrays, causing a slab-out-of-bounds write. The issue affects the handling of mailbox messages from virtual functions (VFs) attached to physical functions (PFs) in switchdev representor mode. The vulnerability has been resolved by adding proper validation of the pcifunc field using the existing is_pf_func_valid() check.
AI Analysis
Technical Summary
The Linux kernel vulnerability CVE-2026-63923 involves the octeontx2-af driver's rvu_mbox_handler_rep_event_notify() function, which queues a sender-controlled REP_EVENT_NOTIFY request body without validating the nested pcifunc field. This attacker-controlled pcifunc is then used without bounds checking in functions rvu_get_pfvf(), rvu_get_pf(), and for mailbox device indexing, leading to out-of-bounds memory access. Specifically, an out-of-range pcifunc can cause an out-of-bounds write via ether_addr_copy() in the queued worker, as detected by KASAN. The vulnerability arises because the VF mailbox handler forwards all message IDs including REP_EVENT_NOTIFY without an allowlist, and the AF dispatcher only rewrites the header pcifunc, leaving the body pcifunc attacker-controlled. The fix involves rejecting malformed requests early by gating on the canonical is_pf_func_valid() function to ensure pcifunc is within valid range.
Potential Impact
This vulnerability allows a local attacker with access to a VF attached to a PF in switchdev representor mode to cause out-of-bounds memory writes in kernel space. The CVSS score of 8.8 indicates high severity with potential for complete confidentiality, integrity, and availability compromise (C:H/I:H/A:H). The out-of-bounds write could lead to kernel memory corruption, potentially resulting in privilege escalation, denial of service, or arbitrary code execution within the kernel context.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. The vulnerability has been resolved by adding validation of the pcifunc field using is_pf_func_valid() to reject malformed requests early. Until an official patch is applied, restrict access to VFs in switchdev representor mode and monitor for unusual mailbox message activity. Follow vendor advisories for updates and apply official fixes when available.
In the Linux kernel, the following vulnerability has been resolved: octeontx2-af: validate body pcifunc in rvu_mbox_handler_rep_event_notify… (CVE-2026-63923)
Description
A vulnerability in the Linux kernel's octeontx2-af driver allowed an attacker-controlled field (pcifunc) in a REP_EVENT_NOTIFY request to bypass bounds checks, leading to out-of-bounds memory writes. This occurs because the body pcifunc field was not validated before being used as an index into internal arrays, causing a slab-out-of-bounds write. The issue affects the handling of mailbox messages from virtual functions (VFs) attached to physical functions (PFs) in switchdev representor mode. The vulnerability has been resolved by adding proper validation of the pcifunc field using the existing is_pf_func_valid() check.
CVSS v3.1
Score 8.8high
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The Linux kernel vulnerability CVE-2026-63923 involves the octeontx2-af driver's rvu_mbox_handler_rep_event_notify() function, which queues a sender-controlled REP_EVENT_NOTIFY request body without validating the nested pcifunc field. This attacker-controlled pcifunc is then used without bounds checking in functions rvu_get_pfvf(), rvu_get_pf(), and for mailbox device indexing, leading to out-of-bounds memory access. Specifically, an out-of-range pcifunc can cause an out-of-bounds write via ether_addr_copy() in the queued worker, as detected by KASAN. The vulnerability arises because the VF mailbox handler forwards all message IDs including REP_EVENT_NOTIFY without an allowlist, and the AF dispatcher only rewrites the header pcifunc, leaving the body pcifunc attacker-controlled. The fix involves rejecting malformed requests early by gating on the canonical is_pf_func_valid() function to ensure pcifunc is within valid range.
Potential Impact
This vulnerability allows a local attacker with access to a VF attached to a PF in switchdev representor mode to cause out-of-bounds memory writes in kernel space. The CVSS score of 8.8 indicates high severity with potential for complete confidentiality, integrity, and availability compromise (C:H/I:H/A:H). The out-of-bounds write could lead to kernel memory corruption, potentially resulting in privilege escalation, denial of service, or arbitrary code execution within the kernel context.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. The vulnerability has been resolved by adding validation of the pcifunc field using is_pf_func_valid() to reject malformed requests early. Until an official patch is applied, restrict access to VFs in switchdev representor mode and monitor for unusual mailbox message activity. Follow vendor advisories for updates and apply official fixes when available.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-95j3-7q26-w637
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-63923"]
- Ecosystems
- []
- Database Specific Severity
- null
- Cvss Version
- 3.1
Threat ID: 6a5d27ab2a4a8d598912f258
Added to database: 07/19/2026, 19:38:19 UTC
Last enriched: 08/03/2026, 22:46:25 UTC
Last updated: 08/30/2026, 10:52:10 UTC
Views: 63
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.