CVE-2024-56622

What it actually does

Division by zero in Linux kernel UFS sysfs monitoring code path when monitoring is disabled, leading to potential kernel crash.

Why it matters to the business

Unexpected system crashes or denial of service on Linux servers and devices using UFS storage, increasing downtime and requiring emergency kernel updates.

How an attack unfolds

An attacker with local access triggers the vulnerable sysfs attribute read on a UFS device where monitoring remains disabled, causing an immediate division by zero and kernel fault.

How to fix it

Update the Linux kernel to include commit 87bf3ea841a5d77beae6bb85af36b2b3848407ee or later stable releases containing the fix for the UFS sysfs division by zero.

How to confirm the fix worked

Verify kernel source contains the patch preventing the division, confirm UFS sysfs monitoring paths no longer crash when disabled, and test on affected hardware.

Typical attack path

1. Identify Linux system with UFS storage and kernel prior to the fix commit.
2. Access sysfs entries related to UFS monitoring.
3. Read the attribute while monitoring is disabled to trigger division by zero.
4. Cause kernel panic or oops for denial of service.

How to detect it

Search kernel logs for division by zero oops or panic messages referencing UFS or scsi sysfs paths on systems before the fix date.

What your security team should do

• Apply the kernel fix commit immediately on all systems using UFS storage.
• Prioritize patching production servers and embedded devices within the next maintenance window.
• Monitor for kernel oops reports involving UFS sysfs after deployment.