CVE-2023-53330

What it actually does

Memory leak in cfctrl_linkup_request() where pkt is not released on unknown linktype or kzalloc failure paths.

Why it matters to the business

Gradual kernel memory exhaustion over time can degrade performance or trigger out-of-memory conditions on systems running the affected Linux kernel code.

How an attack unfolds

An attacker triggers repeated calls to cfctrl_linkup_request under error conditions (invalid linktype or allocation failure) to leak packet memory without release, potentially leading to resource depletion.

How to fix it

Apply the fix from commit badea57569db04b010e922e29a7aaf40a979a70b; update to kernel versions containing this commit or later fixed releases such as those listed for Debian packages.

How to confirm the fix worked

Confirm kernel source contains the release of pkt in the error paths of cfctrl_linkup_request or verify running kernel includes the referenced commit.

Typical attack path

1. Identify systems running vulnerable kernel versions with caif enabled
2. Send crafted CAIF control messages that hit the error paths in cfctrl_linkup_request
3. Repeat the triggering conditions to accumulate leaked memory
4. Monitor for system-wide memory pressure or OOM events

How to detect it

Inspect kernel logs and memory statistics for repeated caif allocation failures without corresponding frees; correlate with processes using the caif subsystem.

What your security team should do

• Prioritize kernel updates on all affected systems
• Disable caif module if not required
• Monitor kernel memory usage and OOM killer activity
• Review EPSS trend and threat actor mentions for any escalation in exploit activity