CVE-2023-52809

What it actually does

NULL pointer dereference in fc_lport_ptp_setup() when fc_rport_create() returns NULL, resulting in a kernel crash or denial of service.

Why it matters to the business

Unexpected system crashes or reboots on Linux systems using Fibre Channel storage, leading to downtime and potential data access loss until patched kernels are deployed.

How an attack unfolds

An attacker with local access triggers fc_lport_ptp_setup() under conditions where fc_rport_create() fails and returns NULL; the missing NULL check then causes an immediate dereference and kernel panic.

How to fix it

Upgrade the Linux kernel to a version containing commit 930f0aaba4820d6362de4e6ed569eaf444f1ea4e or later; rebuild and reboot with the fixed kernel.

How to confirm the fix worked

Confirm the running kernel contains commit 930f0aaba4820d6362de4e6ed569eaf444f1ea4e; attempt to exercise fc_lport_ptp_setup() and verify no NULL dereference occurs.

Typical attack path

1. Obtain local user access on an affected Linux system
2. Trigger Fibre Channel port PTP setup path that exercises fc_lport_ptp_setup()
3. Force fc_rport_create() to return NULL
4. Trigger the unchecked dereference to crash the kernel

How to detect it

Review kernel logs for NULL pointer dereference panics or oops messages referencing fc_lport_ptp_setup or fc_rport_create; correlate with Fibre Channel port initialization events.

What your security team should do

• Prioritize kernel updates on systems exposing Fibre Channel interfaces
• Monitor for kernel oops or panic logs containing fc_lport_ptp_setup references
• Apply the fix across all affected stable branches as soon as possible