CVE-2024-57980

What it actually does

Double-free in uvc_status_init error path where dev->status is freed but not nulled, allowing kfree in uvc_status_cleanup to free the same memory again.

Why it matters to the business

Kernel instability or crashes on systems with USB video devices; low urgency given false KEV status and minimal EPSS but still requires kernel update to avoid memory corruption risks.

How an attack unfolds

An attacker with access to trigger UVC device initialization errors causes the pointer-not-nulled condition; subsequent cleanup path performs the second free, enabling use-after-free style memory corruption. Related Linux kernel privilege escalation campaigns noted in threat actors.

How to fix it

Apply the upstream fix that nulls dev->status after the error-path free; rebuild and deploy updated Linux kernel. No salt (PyPI) remediation applies despite listed fixed versions in 2016.3.6.

How to confirm the fix worked

Confirm kernel source contains the pointer-null assignment after kfree in uvc_status_init error handling; test with UVC device attach under allocation-failure injection.

Typical attack path

1. Attach or initialize a UVC-compliant USB video device
2. Force uvc_status_init to fail allocation of int_urb
3. Trigger uvc_status_cleanup to execute the second kfree
4. Exploit resulting memory state for corruption or crash

How to detect it

Review kernel logs for UVC status allocation failures followed by double-free warnings or oops; inspect USB device attach events around crash timestamps. Correlate with known Linux kernel privilege-escalation actor TTPs.

What your security team should do

• Prioritize kernel upgrade on any system exposing UVC video drivers
• Monitor EPSS trend stability and re-evaluate if new exploit code appears
• Restrict untrusted USB device access until patched