CVE-2021-47484

What it actually does

Null pointer dereference in the octeontx2-af driver within rvu_debugfs.c and rvu_nix.c that can trigger a kernel panic or crash when certain debug or NIX paths are exercised.

Why it matters to the business

Unexpected system crashes or reboots on affected Linux hosts using OcteonTX2 network hardware, leading to downtime and potential loss of network connectivity.

How an attack unfolds

An attacker with local access triggers code paths in the octeontx2-af driver that reach an uninitialized or null structure pointer in the debugfs or NIX handling routines, causing an immediate kernel oops.

How to fix it

Apply the upstream fix or upgrade to a kernel version that includes the resolution for the null pointer dereference in rvu_debugfs.c and rvu_nix.c.

How to confirm the fix worked

Confirm the presence of the patch in the running kernel source or verify that the affected driver files no longer contain the vulnerable pointer handling logic.

Typical attack path

1. Obtain local shell or code execution on a vulnerable Linux system with octeontx2-af loaded.
2. Exercise debugfs entries or NIX configuration operations that dereference a null pointer.
3. Trigger kernel panic and potential denial of service.

How to detect it

Review kernel logs for oops or panic messages referencing rvu_debugfs.c or rvu_nix.c; inspect crash dumps for null dereference in octeontx2-af paths.

What your security team should do

• Prioritize kernel updates on systems exposing OcteonTX2 hardware.
• Monitor for kernel oops reports referencing rvu_debugfs or rvu_nix.
• Restrict local access until patches are applied.