CVE-2026-23104
ice: fix devlink reload call trace
Reported by linux · Published February 4, 2026
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().
EPSS 0.14% · 2.9th percentile
Fixed versions
Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.
| Package | Ecosystem | Fixed in |
|---|---|---|
| linux-gcp-6.12 | Chainguard | 6.12.80-r0 |
| linux-azure-6.12 | Chainguard | 6.12.80-r0 |
| linux-aws-6.12 | Chainguard | 6.12.80-r0 |
| Linux | Linux | d3f867e7a04678640ebcbfb81893c59f4af48586, 8ac7dd0f813fb65ff2fd9543900c3009f8e84110 |
Risk scores
Affected products
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | 4da71a77fc3be1fcb680c8d78e1a1fb8017905ad, 4da71a77fc3be1fcb680c8d78e1a1fb8017905ad, 4da71a77fc3be1fcb680c8d78e1a1fb8017905ad |
| Linux | Linux | 6.8, 0, 6.12.78 |
| Linux | Linux | 6.19, 0, 6.12.78 |
| linux | linux_kernel | 6.8, 6.8, 6.8 |
Timeline
- Feb 4, 2026 CVE Published
- Feb 4, 2026 PoC Published
- Feb 5, 2026 EPSS Score (30 in total, the first dated here)
- Feb 12, 2026 Security Advisory (130 in total, the first dated here)
- Mar 22, 2026 Coalition ESS Score (2 in total, the first dated here)
- Mar 25, 2026 CVE Updated
- Sep 26, 2026 Distribution Patch (128 in total, the first dated here)
Query this with the API
The same record, from the CLI:
vulnetix vdb vuln CVE-2026-23104
vulnetix vdb fixes CVE-2026-23104
Or with curl, using the org id and key from your account page:
curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
"https://api.vdb.vulnetix.com/v2/vuln/CVE-2026-23104/fixes/registry"
The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart