CVE-2026-23104
Last modified
CVE-2026-23104 is a medium-severity vulnerability rated 5.5/10 on the CVSS scale. 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(). EPSS estimates a 0.11% chance of exploitation in the next 30 days.
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().
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Linux | Linux Kernel | >= 6.8, < 6.18.8 | — |
| Linux | Linux Kernel | 6.19 | Rc1 |
References
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2026-23104?
How severe is CVE-2026-23104?
How do I fix CVE-2026-23104?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-23098In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-23099In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2026-23100In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-23101In the Linux kernel, the following vulnerability has been re…4.7
- CVE-2026-23102In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2026-23103In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-23105In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-23106In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-23107In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-23108In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-23109In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-2311IBM i 7.6, 7.5, 7.4, 7.3, and 7.2 s vulnerable to privilege …9.8
Are you affected by CVE-2026-23104?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
