CVE-2024-57944

What it actually does

Missing NULL check on devm_kasprintf() return value inside ads1298_init() allows a NULL pointer to be dereferenced during driver initialization when memory allocation fails.

Why it matters to the business

Systems using the ti-ads1298 ADC may experience kernel crashes or instability during device probe, leading to loss of sensor functionality and requiring reboots or driver reloads.

How an attack unfolds

An attacker with local access or the ability to trigger device initialization (for example by loading the driver or hot-plugging the hardware) can induce a memory allocation failure that causes the un-checked NULL pointer to be used, resulting in a crash.

How to fix it

Update the Linux kernel to commit 69b680bbac9bd611aaa308769d6c71e3e70eb3c3 or later; for Red Hat JBoss EAP 5 packages apply the versions 1:2.6.22-2.ep5.el6, 1:2.6.22-2.ep5.el4 or 1:2.6.22-2.ep5.el5 as appropriate.

How to confirm the fix worked

Confirm the patch is present by checking that ads1298_init() contains an explicit NULL test after the devm_kasprintf call; verify driver initialization succeeds under memory pressure.

Typical attack path

1. Gain local access or ability to control hardware attachment
2. Trigger loading or probing of the ti-ads1298 driver
3. Force a memory pressure condition that makes devm_kasprintf return NULL
4. Observe kernel oops or panic from NULL dereference

How to detect it

Search kernel logs and dmesg for ads1298_init and NULL pointer dereference messages; examine crash dumps for calls originating from the ti-ads1298 driver initialization path.

What your security team should do

• Apply the kernel or package update containing commit 69b680bbac9bd611aaa308769d6c71e3e70eb3c3 at the earliest maintenance window
• Monitor kernel logs for ads1298-related NULL pointer dereference oopses
• Prioritize patching on systems that expose the ti-ads1298 hardware