🛡️ CVE-2024-36002 — kernel

🟡 CVSS 5.5 — Medium ✅ No Known Exploit NVD
5.5
CVSS Score
0 Low4 Medium7 High9 Critical10

Description

dpll: fix dpll_pin_on_pin_register() for multiple parent pins

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

dpll: fix dpll_pin_on_pin_register() for multiple parent pins

In scenario where pin is registered with multiple parent pins via

dpll_pin_on_pin_register(..), all belonging to the same dpll device.

A second call to dpll_pin_on_pin_unregister(..) would cause a call trace,

as it tries to use already released registration resources (due to fix

introduced in b446631f355e). In this scenario pin was registered twice,

so resources are not yet expected to be release until each registered

pin/pin pair is unregistered.

Currently, the following crash/call trace is produced when ice driver is

removed on the system with installed E810T NIC which includes dpll device:

WARNING: CPU: 51 PID: 9155 at drivers/dpll/dpll_core.c:809 dpll_pin_ops+0x20/0x30

RIP: 0010:dpll_pin_ops+0x20/0x30

Call Trace:

? __warn+0x7f/0x130

? dpll_pin_ops+0x20/0x30

dpll_msg_add_pin_freq+0x37/0x1d0

dpll_cmd_pin_get_one+0x1c0/0x400

? __nlmsg_put+0x63/0x80

dpll_pin_event_send+0x93/0x140

dpll_pin_on_pin_unregister+0x3f/0x100

ice_dpll_deinit_pins+0xa1/0x230 [ice]

ice_remove+0xf1/0x210 [ice]

Fix by adding a parent pointer as a cookie when creating a registration,

also when searching for it. For the regular pins pass NULL, this allows to

create separated registration for each parent the pin is registered with.

How this vulnerability can be exploited

This issue can be reached with local access to the system, attack complexity is low, an attacker needs low-level privileges on the target. No user interaction is required. The scope is unchanged, so the impact stays within the vulnerable component. Rated impact: confidentiality none, integrity none, availability high.

Affected software

CVE-2024-36002 is recorded against 2 packages.

  • kernel (from 6.8.2 up to 6.8.9)
  • linux-kernel

Timeline and source

Published on 20 May 2024 and last revised on 15 July 2026. No public exploit is currently recorded for this entry. A vendor advisory or fix has been published. Record sourced from NVD.

References

git.kernel.org (Web)
git.kernel.org (Web)
github.com (Advisory)
nvd.nist.gov (Advisory)
git.kernel.org (Package)

CVE-2024-36002 on other distributions

Each distribution ships its own build and its own fixed version. Pick the one you run:

Details

Severity Medium
CVSS Score 5.5
CVSS Vector CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
CWE N/A
Public Exploit ✅ No
Source NVD
Published 2024-05-20
Updated 2026-08-12
Modified 2026-07-15

Affected Packages

Software From version Fixed in
kernel 6.8.2 6.8.9
linux-kernel — —

Similar Threats

Vulnerability Monitoring

Track new vulnerabilities in kernel

CVE-2024-36002 is rated CVSS 5.5 Medium. BotEraser monitors your WordPress installation and notifies you when software you use appears in our vulnerability database.

Set Up Free Alerts →

No credit card required  ·  Results in minutes

ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.