CVE-2024-35247

What it actually does

Null pointer dereference in FPGA region programming path when parent device lacks a driver, allowing module refcount mishandling that can crash the kernel or enable memory corruption.

Why it matters to the business

Linux systems performing FPGA operations risk kernel crashes or privilege escalation during hardware programming, disrupting availability of accelerated workloads and increasing exposure on servers or embedded devices.

How an attack unfolds

An attacker triggers FPGA region registration or programming on a kernel without the owner module fix; when the parent device has no driver the code dereferences a null owner pointer, leading to panic or potential further corruption in kernel context.

How to fix it

Upgrade the Linux kernel to commit 26e6e25d742e29885cf44274fcf6b744366c4702 or later equivalent stable releases that include the fpga_region owner module pointer and refcount changes.

How to confirm the fix worked

Verify kernel source contains the updated fpga_region struct with owner pointer and modified registration functions; confirm no null dereference occurs in region programming tests on affected hardware.

Typical attack path

1. Identify systems running vulnerable Linux kernel versions with FPGA region support
2. Gain local access or trigger device programming paths involving fpga_region
3. Cause registration of a region whose parent device lacks a driver
4. Trigger programming operation to dereference null module owner pointer
5. Exploit resulting memory corruption for denial of service or code execution

How to detect it

Search kernel logs for oops or null pointer dereference messages referencing fpga_region, fpga_region_get or module refcount operations during device programming.

What your security team should do

• Prioritize kernel upgrades on all systems exposing FPGA region interfaces
• Apply the fix commit across stable trees before the next scheduled maintenance window
• Audit custom low-level FPGA control modules for correct owner parameter usage after update
• Monitor for related kernel oops reports until patches are deployed