CVE-2023-53654: octeontx2-af: Add validation before accessing cgx and lmac
In the Linux kernel, the following vulnerability has been resolved:
octeontx2-af: Add validation before accessing cgx and lmac
with the addition of new MAC blocks like CN10K RPM and CN10KB
RPM_USX, LMACs are noncontiguous and CGX blocks are also
noncontiguous. But during RVU driver initialization, the driver
is assuming they are contiguous and trying to access
cgx or lmac with their id which is resulting in kernel panic.
This patch fixes the issue by adding proper checks.
[ 23.219150] pc : cgx_lmac_read+0x38/0x70
[ 23.219154] lr : rvu_program_channels+0x3f0/0x498
[ 23.223852] sp : ffff000100d6fc80
[ 23.227158] x29: ffff000100d6fc80 x28: ffff00010009f880 x27:
000000000000005a
[ 23.234288] x26: ffff000102586768 x25: 0000000000002500 x24:
fffffffffff0f000
Security readout for executives and security teams
Plain-English summary
This is a Linux kernel driver bug that can crash the kernel during initialization on systems using octeontx2-af networking hardware paths. The issue comes from assuming CGX and LMAC identifiers are contiguous when newer MAC blocks can be noncontiguous. The available sources do not provide CVSS, public exploitation evidence, or downstream distro status.
Executive priority
Prioritize for platforms that depend on affected Linux networking hardware, because the documented failure mode is kernel panic. For general fleets without this driver path, urgency is lower until vendor advisories show broader exposure.
Technical view
In octeontx2-af, RVU driver initialization can access CGX or LMAC entries by ID without validating that the target exists. With CN10K RPM and CN10KB RPM_USX layouts, blocks may be noncontiguous, causing invalid access and kernel panic. Stable kernel commits add validation before CGX and LMAC access.
Likely exposure
Exposure appears limited to Linux systems using the affected octeontx2-af RVU driver path with newer noncontiguous MAC block layouts. The bundle lists Linux kernel versions and stable commits, but does not identify affected distributions, cloud images, or appliance products.
Exploitation context
The provided sources describe a kernel panic during driver initialization, not a remote attack path. KEV is false, and no cited source states active exploitation or public exploit availability. Treat this as an availability risk for matching hardware and kernel combinations.
Researcher notes
Evidence is narrow and kernel-specific. The root issue is missing validation around noncontiguous CGX and LMAC identifiers during RVU initialization. No CVSS, CWE, exploit status, or distro mapping is included in the supplied bundle.
Mitigation direction
Check vendor or distribution advisories for fixed kernel packages.
Prioritize kernel updates on systems using octeontx2-af hardware paths.
Review the listed stable kernel commits for patch inclusion.
Avoid assuming generic Linux exposure without matching driver and hardware evidence.
Validation and detection
Inventory systems loading the octeontx2-af driver.
Confirm kernel versions against vendor fixed-package guidance.
Check boot logs for RVU initialization panics or CGX/LMAC access failures.
Verify whether relevant stable commits are present in deployed kernels.
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-2023-53654 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
5Source 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.
Oct 7, 2025, 15:19 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.