CVE-2024-43821

What it actually does

Null pointer dereference in lpfc_xcvr_data_show when kmalloc for rdp_context fails, followed by subsequent dereference of the null pointer.

Why it matters to the business

Kernel instability or crash on systems using the lpfc driver can disrupt storage I/O; 286 downstream dependents increase exposure across affected Linux environments.

How an attack unfolds

An attacker with sufficient privileges triggers lpfc_xcvr_data_show under memory pressure so kmalloc fails, leaving rdp_context null and causing an immediate dereference that panics the kernel.

How to fix it

Apply the upstream fix that adds the null-pointer check before use; update affected nltk (PyPI) packages to version 3.6.6 where applicable.

How to confirm the fix worked

Confirm the null check exists in lpfc_xcvr_data_show, rebuild the module, and test under artificial memory pressure to ensure no dereference occurs.

Typical attack path

1. Obtain local access or execute code on a system with the lpfc driver loaded
2. Induce memory allocation failure while invoking the xcvr data show path
3. Trigger the missing null check and dereference
4. Cause kernel panic or denial of service

How to detect it

Inspect kernel logs and oops reports for entries referencing lpfc_xcvr_data_show or rdp_context null dereference.

• lpfc_xcvr_data_show
• rdp_context
• Unable to allocate memory for rdp_context

What your security team should do

• Prioritize patching systems that expose the lpfc driver
• Add kernel oops monitoring for lpfc-related null dereferences
• Review memory-pressure test coverage for similar kmalloc paths