CVE-2024-56546

What it actually does

Missing kfree in error path of xlnx_add_cb_for_suspend allows allocated eve_data memory to leak when kmalloc for cb_data fails.

Why it matters to the business

Repeated triggering of the error condition can gradually exhaust kernel memory, degrading performance or causing instability on affected Linux systems.

How an attack unfolds

An attacker with the ability to induce allocation failures in the suspend callback registration path repeatedly triggers the flawed error handling, leaking memory over time without direct code execution.

How to fix it

Update to a fixed kernel containing commit 272168927f38bda46f6c1ed5f40de97689e7a5d2 or equivalent backport; apply vendor kernel updates that include the kfree correction in the error path.

How to confirm the fix worked

Confirm the presence of the kfree call in the error handling branch of xlnx_add_cb_for_suspend in the running kernel source or verify the installed kernel version includes the referenced commit.

Typical attack path

1. Identify or create conditions that cause kmalloc failure during xlnx_add_cb_for_suspend execution
2. Force repeated entry into the function via suspend-related operations
3. Accumulate leaked memory allocations until resource pressure impacts the system

How to detect it

Inspect kernel logs for repeated allocation failures around suspend callbacks and monitor for unexpected memory growth in kernel slab caches; review dmesg or syslog for xlnx_add_cb_for_suspend related entries.

What your security team should do

• Prioritize kernel updates on systems using Xilinx SoC drivers
• Monitor for memory pressure indicators on affected hosts
• Review kernel changelog for backports of the fix in distribution kernels