CVE-2023-4133

What it actually does

Use-after-free in the cxgb4 Linux kernel driver triggered by rearming flower_stats_timer from the work queue during device detach, allowing a local user to crash the kernel.

Why it matters to the business

Local denial-of-service crashes can interrupt services and require reboots; low public exploit activity and no ransomware use reduce immediate urgency despite the long time since disclosure.

How an attack unfolds

An attacker with local access triggers the cxgb4 device detach condition that races with the work-queue timer, freeing memory that is later accessed to cause a kernel panic.

How to fix it

Update the affected package to a fixed version such as aio-libs/aiohttp (GIT): fixed in f016f0680e4ace6742b03a70cb0382ce86abe371; apply vendor kernel patches addressing the cxgb4 driver timer race.

How to confirm the fix worked

Confirm the installed kernel or package version is at or above the listed fixed commit; review dmesg or kernel logs for absence of cxgb4 timer-related crashes after upgrade.

Typical attack path

1. Obtain local shell on affected Linux system
2. Load or interact with cxgb4 device to initiate detach
3. Trigger concurrent flower_stats_timer rearm from work queue
4. Cause use-after-free leading to kernel crash

How to detect it

Review kernel logs and dmesg for cxgb4 detach or flower_stats_timer warnings; look for repeated system crashes coinciding with device removal events.

What your security team should do

• Prioritize patching systems exposing the cxgb4 driver
• Restrict local user access where possible until updated
• Monitor EPSS and KEV status for any future rise in activity