CVE-2024-42071 [Medium] | Security Vulnerability in Linux Kernel

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+0x16/0x80 [ 4371.404199] ionic_tx_clean+0x18a/0x240 [ionic] [ 4371.404354] ionic_tx_cq_service+0xc4/0x200 [ionic] [ 4371.404505] ionic_tx_flush+0x15/0x70 [ionic] [ 4371.404653] ? ionic_lif_qcq_deinit.isra.23+0x5b/0x70 [ionic] [ 4371.404805] ionic_txrx_deinit+0x71/0x190 [ionic] [ 4371.404956] ionic_reconfigure_queues+0x5f5/0xff0 [ionic] [ 4371.405111] ionic_set_ringparam+0x2e8/0x3e0 [ionic] [ 4371.405265] ethnl_set_rings+0x1f1/0x300 [ 4371.405418] ethnl_default_set_doit+0xbb/0x160 [ 4371.405571] genl_family_rcv_msg_doit+0xff/0x130 [...] I found that ionic_tx_clean() calls napi_consume_skb() which calls napi_skb_cache_put(), but before that last call is the note /* Zero budget indicate non-NAPI context called us, like netpoll */ and DEBUG_NET_WARN_ON_ONCE(!in_softirq()); Those are pretty big hints that we're doing it wrong. We can pass a context hint down through the calls to let ionic_tx_clean() know what we're doing so it can call napi_consume_skb() correctly.

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2025-11-21	0.05%	0.01%	-0.05%
2	2025-11-18	0.04%	0.05%	+0.01%
3	2025-03-30	—	0.04%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2025-11-21

0.05%

0.01%

-0.05%

2025-11-18

0.04%

0.05%

+0.01%

2025-03-30

—

0.04%

—

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
5.5	3.1	MEDIUM	`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H` Click to expand Attack vector (AV:L) They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by. Attack complexity (AC:L) Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup. Privileges required (PR:L) A normal user session is enough; they don’t have to be admin. User interaction (UI:N) Nobody has to click “OK” or open a trap file; it can work without a victim helping. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:N) Doesn’t really leak secrets in a meaningful way. Integrity (I:N) Data isn’t meaningfully altered or forged. Availability (A:H) Could take the service down hard or make it unusable for people who depend on it.	1.8	3.6	[email protected]

Base score

Version

Severity

Vector

Exploitability

Impact

Score source

5.5

3.1

MEDIUM

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H Click to expand

Attack vector (AV:L): They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L): Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L): A normal user session is enough; they don’t have to be admin.
User interaction (UI:N): Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N): Doesn’t really leak secrets in a meaningful way.
Integrity (I:N): Data isn’t meaningfully altered or forged.
Availability (A:H): Could take the service down hard or make it unusable for people who depend on it.

1.8

3.6

[email protected]

OS Trackers for CVE-2024-42071

vendor	priority	summary	link
`debian`	unimportant	CVE-2024-42071 unimportant priority: Debian including 1 source packages (linux), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5.	https://security-tracker.debian.org/tracker/CVE-2024-42071
`redhat`	low	—	https://access.redhat.com/security/cve/CVE-2024-42071
`suse`	medium	CVE-2024-42071 severity moderate: SUSE including 36 source package names (cluster-md-kmp-default, dlm-kmp-default, …), 233 product×package rows across 46 product lines (SUSE Enterprise Storage 7.1, SUSE Linux Enterprise High Performance Computing 12 SP5, … (46 product lines)): Known Not Affected 221, Fixed 12.	https://www.suse.com/security/cve/CVE-2024-42071/
`ubuntu`	medium	CVE-2024-42071 medium priority: Ubuntu including 121 source packages (linux, linux-allwinner-5.19, …), 557 status rows across 7 suites (bionic, focal, jammy, noble, trusty, upstream, xenial): DNE 262, ignored 137, not-affected 101, released 57.	https://ubuntu.com/security/CVE-2024-42071

Affected software / configurations for CVE-2024-42071

Vendor	Product	Version	Raw CPE
linux	linux_kernel	< 6.9	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 6.9.1, < 6.9.8	cpe:2.3:o:linux:linux_kernel::::::::

References for CVE-2024-42071

URL	Tags
https://git.kernel.org/stable/c/84b767f9e34fdb143c09e66a2a20722fc2921821	Patch
https://git.kernel.org/stable/c/ef7646ed49fff962e97b276f4ab91327a67eeb5a	Patch

URL

CVE-2024-42071 | ionic: use dev_consume_skb_any outside of napi

Exploit prediction scoring system (EPSS) score for CVE-2024-42071

Common vulnerability scoring system (CVSS) metrics for CVE-2024-42071

Weakness enumeration for CVE-2024-42071

OS Trackers for CVE-2024-42071

Affected software / configurations for CVE-2024-42071

References for CVE-2024-42071