CVE-2024-42071

/// Technical description

In the Linux kernel, the following vulnerability has been resolved:

ionic: use dev_consume_skb_any outside of napi

If we're not in a NAPI softirq context, we need to be careful

about how we call napi_consume_skb(), specifically we need to

call it with budget==0 to signal to it that we're not in a

safe context.

This was found while running some configuration stress testing

of traffic and a change queue config loop running, and this

curious note popped out:

[ 4371.402645] BUG: using smp_processor_id() in preemptible [00000000] code: ethtool/20545

[ 4371.402897] caller is napi_skb_cache_put+0x16/0x80

[ 4371.403120] CPU: 25 PID: 20545 Comm: ethtool Kdump: loaded Tainted: G OE 6.10.0-rc3-netnext+ #8

[ 4371.403302] Hardware name: HPE ProLiant DL360 Gen10/ProLiant DL360 Gen10, BIOS U32 01/23/2021

[ 4371.403460] Call Trace:

[ 4371.403613] <TASK>

[ 4371.403758] dump_stack_lvl+0x4f/0x70

[ 4371.403904] check_preemption_disabled+0xc1/0xe0

[ 4371.404051] napi_skb_cache_put+0x

/// Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

/// References