CVE-2024-36900

What it actually does

Race condition allows devlink reload to access uninitialized hardware registers in the hns3 driver, resulting in a kernel crash.

Why it matters to the business

Systems using affected Linux kernel versions with hns3 network devices may experience unexpected crashes and downtime during device reload operations, increasing operational risk until patched.

How an attack unfolds

An attacker or automated process issues a devlink reload command while the hns3 hardware initialization is still in progress, triggering the uninitialized register access and kernel panic.

How to fix it

Update the Linux kernel to a version containing commit 72ede790f5a03c3957487400a1b72ebce293a2e7 or later; rebuild and deploy the updated kernel on all affected systems.

How to confirm the fix worked

Verify the running kernel contains commit 72ede790f5a03c3957487400a1b72ebce293a2e7 or a backported equivalent; confirm devlink reload no longer crashes the system during initialization.

Typical attack path

1. Identify a system running an unpatched Linux kernel with the hns3 driver
2. Time or force a devlink reload operation during the driver's early initialization window
3. Trigger kernel crash via the resulting invalid hardware register access

How to detect it

Review kernel logs for hns3-related crashes or register access faults occurring around devlink reload events; correlate with system boot or device initialization timelines.

What your security team should do

• Prioritize kernel updates on all systems using the hns3 driver
• Test the fixed kernel in a staging environment before broad deployment
• Monitor for kernel panics referencing hns3 during device reload windows