LiveActive security incident?Get immediate response
CVE Record

CVE-2026-23104: ice: fix devlink reload call trace

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().

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysislow

Security readout for executives and security teams

Plain-English summary

CVE-2026-23104 is a Linux kernel ice driver cleanup bug. After a devlink reload and later driver removal, stale HWMON sysfs entries can point at freed module memory, causing repeated kernel call traces when monitoring tools read them. The source describes reliability impact, not remote compromise.

Executive priority

Treat this as a targeted stability fix for affected Linux network hosts, not an emergency internet-wide threat. Prioritize kernel updates during normal maintenance, faster for systems where NIC driver reloads are common.

Technical view

The ice driver initializes HWMON during feature init but previously cleaned it only during remove. Devlink reload can create a second HWMON instance, and driver unload can leave the first orphaned. The fix moves ice_hwmon_exit() into ice_deinit_features() to match the init path.

Likely exposure

Exposure is likely limited to Linux systems running affected kernels with the ice driver, using devlink reload, and later unloading the driver while monitoring reads HWMON sysfs attributes.

Exploitation context

No active exploitation is cited, and KEV is false. The described trigger is an operational sequence involving devlink reload, driver unload, and monitoring reads, which suggests local or administrative conditions rather than internet-facing exploitation.

Researcher notes

The public record provides the failure sequence and cleanup symmetry fix, but no CVSS, CWE, exploit report, or broader impact analysis. Avoid claiming privilege escalation or remote attack without additional vendor evidence.

Mitigation direction

  • Update to a Linux kernel build containing the referenced stable fixes.
  • Check Linux distribution advisories for the backported fix status.
  • Avoid unnecessary devlink reload and driver unload cycles until patched.
  • Review monitoring behavior that reads ice HWMON sysfs attributes.

Validation and detection

  • Inventory systems running affected Linux kernel versions and the ice driver.
  • Confirm whether deployed kernels include one of the referenced stable commits.
  • Review kernel logs for repeated ice, HWMON, sysfs, or call trace messages.
  • Check operational runbooks for devlink reload use on affected hosts.
Prepared
Confidence
high
Sources
5

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2026-23104 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
0ADP providers
4Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux4da71a77fc3be1fcb680c8d78e1a1fb8017905ad, 4da71a77fc3be1fcb680c8d78e1a1fb8017905ad, 4da71a77fc3be1fcb680c8d78e1a1fb8017905adunaffected
LinuxLinux6.8, 0, 6.12.78, 6.18.8, 6.19affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.