CVE-2024-42284

What it actually does

tipc_udp_addr2str() returning zero on invalid UDP media address allows tipc_media_addr_printf() to perform out-of-bounds write due to missing error check.

Why it matters to the business

Local attackers on affected Linux systems can crash the kernel or escalate privileges; 35 downstream dependents increase exposure across distributions and embedded devices.

How an attack unfolds

An attacker with local access supplies an invalid UDP media address to TIPC, causing tipc_udp_addr2str() to return success; subsequent printf operation writes beyond buffer bounds, enabling code execution or denial of service. Threat actors including espionage and financially motivated groups have targeted similar Linux kernel issues in 2024 campaigns.

How to fix it

Upgrade Linux kernel to commit 7ec3335dd89c8d169e9650e4bac64fde71fdf15b or later stable releases containing the fix; apply vendor backports for supported distributions.

How to confirm the fix worked

Verify kernel source contains the return-1 change in tipc_udp_addr2str(); confirm no zero return on invalid address and test with crafted UDP media addresses.

Typical attack path

1. Obtain local user access on target Linux system
2. Invoke TIPC UDP address handling with malformed input
3. Trigger buffer overflow in media address formatting
4. Achieve kernel memory corruption for privilege escalation or crash

How to detect it

Review kernel logs for TIPC media address formatting errors or oops messages; inspect audit logs for unusual local process activity involving TIPC sockets.

What your security team should do

• Prioritize kernel updates on all systems using TIPC over UDP within 30 days given local exploit potential
• Audit configurations disabling TIPC UDP media where not required
• Monitor for local privilege escalation attempts on production hosts