Skip to content
Fencer Vulns
medium 5.5

CVE-2024-36003 json

ice: fix LAG and VF lock dependency in ice_reset_vf()

published 2024-05-20 2 y ago modified 2026-06-17 4 mo ago also EUVD-2024-35813

cvss
5.5
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.2%
EPSS 0.2% chance of exploitation in 30 days, percentile 5%
public exploits
0
none known

Summary

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

ice: fix LAG and VF lock dependency in ice_reset_vf()

9f74a3dfcf83 ("ice: Fix VF Reset paths when interface in a failed over aggregate"), the ice driver has acquired the LAG mutex in ice_reset_vf(). The commit placed this lock acquisition just prior to the acquisition of the VF configuration lock.

If ice_reset_vf() acquires the configuration lock via the ICE_VF_RESET_LOCK flag, this could deadlock with ice_vc_cfg_qs_msg() because it always acquires the locks in the order of the VF configuration lock and then the LAG mutex.

Lockdep reports this violation almost immediately on creating and then removing 2 VF:

====================================================== WARNING: possible circular locking dependency detected 6.8.0-rc6 #54 Tainted: G W O ------------------------------------------------------ kworker/60:3/6771 is trying to acquire lock: ff40d43e099380a0 (&vf->cfg_lock){+.+.}-{3:3}, at: ice_reset_vf+0x22f/0x4d0 [ice]

but task is already holding lock: ff40d43ea1961210 (&pf->lag_mutex){+.+.}-{3:3}, at: ice_reset_vf+0xb7/0x4d0 [ice]

which lock already depends on the new lock.

the existing dependency chain (in reverse order) is:

-> #1 (&pf->lag_mutex){+.+.}-{3:3}: __lock_acquire+0x4f8/0xb40 lock_acquire+0xd4/0x2d0 __mutex_lock+0x9b/0xbf0 ice_vc_cfg_qs_msg+0x45/0x690 [ice] ice_vc_process_vf_msg+0x4f5/0x870 [ice] __ice_clean_ctrlq+0x2b5/0x600 [ice] ice_service_task+0x2c9/0x480 [ice] process_one_work+0x1e9/0x4d0 worker_thread+0x1e1/0x3d0 kthread+0x104/0x140 ret_from_fork+0x31/0x50 ret_from_fork_asm+0x1b/0x30

-> #0 (&vf->cfg_lock){+.+.}-{3:3}: check_prev_add+0xe2/0xc50 validate_chain+0x558/0x800 __lock_acquire+0x4f8/0xb40 lock_acquire+0xd4/0x2d0 __mutex_lock+0x9b/0xbf0 ice_reset_vf+0x22f/0x4d0 [ice] ice_process_vflr_event+0x98/0xd0 [ice] ice_service_task+0x1cc/0x480 [ice] process_one_work+0x1e9/0x4d0 worker_thread+0x1e1/0x3d0 kthread+0x104/0x140 ret_from_fork+0x31/0x50 ret_from_fork_asm+0x1b/0x30

other info that might help us debug this: Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(&pf->lag_mutex); lock(&vf->cfg_lock); lock(&pf->lag_mutex); lock(&vf->cfg_lock);

*** DEADLOCK *** 4 locks held by kworker/60:3/6771: #0: ff40d43e05428b38 ((wq_completion)ice){+.+.}-{0:0}, at: process_one_work+0x176/0x4d0 #1: ff50d06e05197e58 ((work_completion)(&pf->serv_task)){+.+.}-{0:0}, at: process_one_work+0x176/0x4d0 #2: ff40d43ea1960e50 (&pf->vfs.table_lock){+.+.}-{3:3}, at: ice_process_vflr_event+0x48/0xd0 [ice] #3: ff40d43ea1961210 (&pf->lag_mutex){+.+.}-{3:3}, at: ice_reset_vf+0xb7/0x4d0 [ice]

stack backtrace: CPU: 60 PID: 6771 Comm: kworker/60:3 Tainted: G W O 6.8.0-rc6 #54 Hardware name: Workqueue: ice ice_service_task [ice] Call Trace: <TASK> dump_stack_lvl+0x4a/0x80 check_noncircular+0x12d/0x150 check_prev_add+0xe2/0xc50 ? save_trace+0x59/0x230 ? add_chain_cache+0x109/0x450 validate_chain+0x558/0x800 __lock_acquire+0x4f8/0xb40 ? lockdep_hardirqs_on+0x7d/0x100 lock_acquire+0xd4/0x2d0 ? ice_reset_vf+0x22f/0x4d0 [ice] ? lock_is_held_type+0xc7/0x120 __mutex_lock+0x9b/0xbf0 ? ice_reset_vf+0x22f/0x4d0 [ice] ? ice_reset_vf+0x22f/0x4d0 [ice] ? rcu_is_watching+0x11/0x50 ? ice_reset_vf+0x22f/0x4d0 [ice] ice_reset_vf+0x22f/0x4d0 [ice] ? process_one_work+0x176/0x4d0 ice_process_vflr_event+0x98/0xd0 [ice] ice_service_task+0x1cc/0x480 [ice] process_one_work+0x1e9/0x4d0 worker_thread+0x1e1/0x3d0 ? __pfx_worker_thread+0x10/0x10 kthread+0x104/0x140 ? __pfx_kthread+0x10/0x10 ret_from_fork+0x31/0x50 ? __pfx_kthread+0x10/0x10 ret_from_fork_asm+0x1b/0x30 </TASK>

To avoid deadlock, we must acquire the LAG ---truncated---

Patch / fix

  • Linux Linux 6.6.30, 6.8.9, 6.9
  • linux Debian 14, Debian 13 6.8.9-1

debian advisories DEBIAN-CVE-2024-36003

  • linux Ubuntu 24.04 LTS 6.8.0-40.40
  • linux-aws Ubuntu 24.04 LTS 6.8.0-1013.14
  • linux-gcp Ubuntu 24.04 LTS 6.8.0-1012.13
  • linux-gke Ubuntu 24.04 LTS 6.8.0-1008.11
  • linux-ibm Ubuntu 24.04 LTS 6.8.0-1010.10
  • linux-azure Ubuntu 24.04 LTS 6.8.0-1012.14
  • linux-raspi Ubuntu 24.04 LTS 6.8.0-1009.10
  • linux-riscv Ubuntu 24.04 LTS 6.8.0-40.40.1

ubuntu advisories UBUNTU-CVE-2024-36003

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

  • kernel RHEL 9 5.14.0-427.33.1.el9_4
  • rv RHEL 9 5.14.0-427.33.1.el9_4
  • perf RHEL 9 5.14.0-427.33.1.el9_4
  • rtla RHEL 9 5.14.0-427.33.1.el9_4
  • bpftool RHEL 9 7.3.0-427.33.1.el9_4
  • libperf RHEL 9 5.14.0-427.33.1.el9_4
  • kernel-rt RHEL 9 5.14.0-427.33.1.el9_4
  • kernel-64k RHEL 9 5.14.0-427.33.1.el9_4

red hat advisories RHSA-2024:5928

  • kernel-rt Linux Micro 6.0 6.4.0-9.1
  • kernel-source-rt Linux Micro 6.0 6.4.0-9.1
  • kernel-source Linux Micro 6.0 6.4.0-18.1
  • kernel-default Linux Micro 6.0 6.4.0-18.1
  • kernel-kvmsmall Linux Micro 6.0 6.4.0-18.1
  • kernel-default-base Linux Micro 6.0 6.4.0-17.1.1.51
  • kernel-rt Real Time Module 15 SP6, openSUSE Leap 15.6 6.4.0-150600.10.5.1
  • kernel-syms-rt Real Time Module 15 SP6, openSUSE Leap 15.6 6.4.0-150600.10.5.1

suse advisories SUSE-SU-2025:20028-1SUSE-SU-2025:20008-1SUSE-SU-2024:2973-1SUSE-SU-2024:2896-1SUSE-SU-2024:2802-1

  • kernel AlmaLinux 9 5.14.0-427.33.1.el9_4
  • rv AlmaLinux 9 5.14.0-427.33.1.el9_4
  • perf AlmaLinux 9 5.14.0-427.33.1.el9_4
  • rtla AlmaLinux 9 5.14.0-427.33.1.el9_4
  • bpftool AlmaLinux 9 7.3.0-427.33.1.el9_4
  • libperf AlmaLinux 9 5.14.0-427.33.1.el9_4
  • kernel-rt AlmaLinux 9 5.14.0-427.33.1.el9_4
  • kernel-64k AlmaLinux 9 5.14.0-427.33.1.el9_4

almalinux advisories ALSA-2024:5928

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2024-36003 updated cvss 5.5

kernel: ice: fix LAG and VF lock dependency in ice_reset_vf()

  • Red Hat Enterprise Linux 9 kernel-rt, kernel-rt-kvm, kernel-rt-core, kernel-rt-modules, kernel-rt-debug-kvm, kernel-rt-debug-core, +12 more
    affected: no fix available
  • Red Hat Enterprise Linux AppStream (v. 9) rv 5.14.0-427.33.1.el9_4, perf 5.14.0-427.33.1.el9_4, rtla 5.14.0-427.33.1.el9_4, kernel-devel-matched 5.14.0-427.33.1.el9_4, kernel-64k-devel-matched 5.14.0-427.33.1.el9_4, kernel-debug-devel-matched 5.14.0-427.33.1.el9_4, +6 more Red Hat Enterprise Linux BaseOS (v. 9) bpftool 7.3.0-427.33.1.el9_4, kernel 5.14.0-427.33.1.el9_4, kernel-64k 5.14.0-427.33.1.el9_4, kernel-core 5.14.0-427.33.1.el9_4, kernel-tools 5.14.0-427.33.1.el9_4, python3-perf 5.14.0-427.33.1.el9_4, +28 more Red Hat Enterprise Linux CRB (v. 9) libperf 5.14.0-427.33.1.el9_4, kernel-debuginfo-common-s390x 5.14.0-427.33.1.el9_4, kernel-debuginfo-common-x86_64 5.14.0-427.33.1.el9_4, kernel-debuginfo-common-aarch64 5.14.0-427.33.1.el9_4, kernel-debuginfo-common-ppc64le 5.14.0-427.33.1.el9_4 Red Hat Enterprise Linux NFV (v. 9) kernel-rt 5.14.0-427.33.1.el9_4, kernel-rt-kvm 5.14.0-427.33.1.el9_4, kernel-rt-core 5.14.0-427.33.1.el9_4, kernel-rt-modules 5.14.0-427.33.1.el9_4, kernel-rt-debug-kvm 5.14.0-427.33.1.el9_4, kernel-rt-debug-core 5.14.0-427.33.1.el9_4, +6 more Red Hat Enterprise Linux RT (v. 9) kernel-rt 5.14.0-427.33.1.el9_4, kernel-rt-core 5.14.0-427.33.1.el9_4, kernel-rt-modules 5.14.0-427.33.1.el9_4, kernel-rt-debug-core 5.14.0-427.33.1.el9_4, kernel-rt-modules-core 5.14.0-427.33.1.el9_4, kernel-rt-debug-modules 5.14.0-427.33.1.el9_4, +4 more
    fixed: vendor fix RHSA-2024:5928
  • Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
2 y ago

Exploit prediction

0.17% chance of exploitation in the next 30 days, higher than 5% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
NVD 3.1 5.5 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Affected products

  • Linux Linux

Classification

Weakness
Technology feeds

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.