VulnerabilityPublished 4 Feb 2026Updated 5 Nov 2026

CVE-2026-23104: Linux kernel · ice: fix devlink reload call trace

Affects Linux kernelSource CVE Database V5

Compare

Not known to be exploited · fixed in d3f867e7a04678640ebcbfb81893c59f4af48586 : update Linux kernel when convenient.

Data as of 5 Nov 2026, 21:49 UTC

Severity

Unrated

Rated by Threat Radar · No CVSS score from NVD or the CNA

Thin evidence

One scorer or none

Exploitation: No evidence of active exploitation and no public proof of concept
Automatable: Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact: Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-11-05.

Patch

Available – fixed in d3f867e7a04678640ebcbfb81893c59f4af48586, 87c1dacca197cc64e06fedeb269e3dd6699bae60, 8ac7dd0f813fb65ff2fd9543900c3009f8e84110

Exploitation evidence

Disclosed: evidence found.
CVE published 4 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 5 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade Linux kernel to d3f867e7a04678640ebcbfb81893c59f4af48586, 87c1dacca197cc64e06fedeb269e3dd6699bae60 or 8ac7dd0f813fb65ff2fd9543900c3009f8e84110.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected ≥ 4da71a77fc3be1fcb680c8d78e1a1fb8017905ad, < d3f867e7a04678640ebcbfb81893c59f4af48586	Fixed in d3f867e7a04678640ebcbfb81893c59f4af48586
LinuxLinux	Affected ≥ 4da71a77fc3be1fcb680c8d78e1a1fb8017905ad, < 87c1dacca197cc64e06fedeb269e3dd6699bae60	Fixed in 87c1dacca197cc64e06fedeb269e3dd6699bae60
LinuxLinux	Affected ≥ 4da71a77fc3be1fcb680c8d78e1a1fb8017905ad, < 8ac7dd0f813fb65ff2fd9543900c3009f8e84110	Fixed in 8ac7dd0f813fb65ff2fd9543900c3009f8e84110
LinuxLinux	Affected =6.8	Fixed in–

Description

In the Linux kernel, the following vulnerability has been resolved: ice: fix devlink reload call trace Commit 4da71a77fc3b ("ice: read internal temperature sensor") introduced internal temperature sensor reading via HWMON. ice_hwmon_init() was added to ice_init_feature() and ice_hwmon_exit() was added to ice_remove(). As a result if devlink reload is used to reinit the device and then the driver is removed, a call trace can occur. BUG: unable to handle page fault for address: ffffffffc0fd4b5d Call Trace: string+0x48/0xe0 vsnprintf+0x1f9/0x650 sprintf+0x62/0x80 name_show+0x1f/0x30 dev_attr_show+0x19/0x60 The call trace repeats approximately every 10 minutes when system monitoring tools (e.g., sadc) attempt to read the orphaned hwmon sysfs attributes that reference freed module memory. The sequence is: 1. Driver load, ice_hwmon_init() gets called from ice_init_feature() 2. Devlink reload down, flow does not call ice_remove() 3. Devlink reload up, ice_hwmon_init() gets called from ice_init_feature() resulting in a second instance 4. Driver unload, ice_hwmon_exit() called from ice_remove() leaving the first hwmon instance orphaned with dangling pointer Fix this by moving ice_hwmon_exit() from ice_remove() to ice_deinit_features() to ensure proper cleanup symmetry with ice_hwmon_init().

References

Community reviews

Loading reviews…