CVE-2026-23070: Octeontx2-af: Add proper checks for fwdata
In the Linux kernel, the following vulnerability has been resolved:
Octeontx2-af: Add proper checks for fwdata
firmware populates MAC address, link modes (supported, advertised)
and EEPROM data in shared firmware structure which kernel access
via MAC block(CGX/RPM).
Accessing fwdata, on boards booted with out MAC block leading to
kernel panics.
Internal error: Oops: 0000000096000005 [#1] SMP
[ 10.460721] Modules linked in:
[ 10.463779] CPU: 0 UID: 0 PID: 174 Comm: kworker/0:3 Not tainted 6.19.0-rc5-00154-g76ec646abdf7-dirty #3 PREEMPT
[ 10.474045] Hardware name: Marvell OcteonTX CN98XX board (DT)
[ 10.479793] Workqueue: events work_for_cpu_fn
[ 10.484159] pstate: 80400009 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
[ 10.491124] pc : rvu_sdp_init+0x18/0x114
[ 10.495051] lr : rvu_probe+0xe58/0x1d18
Security readout for executives and security teams
Plain-English summary
This Linux kernel issue can make certain Marvell OcteonTX2 systems crash during boot or driver initialization. The crash occurs when firmware data is accessed on boards that lack the expected MAC block. The business risk is mainly service availability on specialized hardware, not broadly exposed internet attack surface.
Executive priority
Treat this as a targeted availability risk. It is not presented as mass-exploitable, but affected appliances or servers could fail during boot or initialization until patched.
Technical view
The Octeontx2-af driver reads firmware-populated MAC, link mode, and EEPROM fields through CGX/RPM. On systems booted without the MAC block, insufficient fwdata checks can trigger a kernel Oops in rvu_sdp_init during rvu_probe. Stable kernel commits add validation before accessing that firmware data.
Likely exposure
Exposure appears limited to Linux systems using the Octeontx2-af networking driver on affected Marvell OcteonTX/CN98XX-class hardware or similar boards with missing MAC block conditions.
Exploitation context
The bundle does not report active exploitation, KEV listing, exploit availability, or a remote attack path. Evidence supports a kernel panic condition under specific hardware and firmware layout assumptions.
Researcher notes
Key gaps are missing CVSS, CWE, and precise distro package ranges. Analysis should stay tied to the kernel commits and hardware preconditions. Do not infer network-triggered exploitation from the available description.
Mitigation direction
Apply a kernel update containing the referenced stable fixes.
Check distribution advisories for backported fixes for your deployed kernel branch.
Prioritize affected OcteonTX2 systems with production availability requirements.
If patching is delayed, follow vendor guidance for hardware-specific workarounds.
Validation and detection
Inventory Linux hosts using Marvell OcteonTX2 or CN98XX hardware.
Check whether the octeontx2-af driver is present or loaded.
Compare running kernel builds against vendor fixed packages or referenced commits.
Review boot logs for rvu_probe, rvu_sdp_init, or kernel Oops messages.
Confirm patched systems boot cleanly on affected board variants.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2026-23070 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
0CVSS vectors
3Timeline events
0ADP providers
4Source links
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
CVE publishedCVE Program
The CVE record was published.
Feb 4, 2026, 16:07 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.