Answer in brief
CVE-2025-39854 records a Unknown severity vulnerability in ice: fix NULL access of tx->in_use in ice_ll_ts_intr. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=82e71b226e0ef770d7bc143701c8b4960b4eb3d5 <2cde98a02da958357fe240a6ba269b69d913b6ba || >=82e71b226e0ef770d7bc143701c8b4960b4eb3d5 <923c267bdbb64f65bc1149d184efcf8b047d7d64 || >=82e71b226e0ef770d7bc143701c8b4960b4eb3d5 <f6486338fde3f04ed0ec59fe67a69a208c32734f | 2cde98a02da958357fe240a6ba269b69d913b6ba, 923c267bdbb64f65bc1149d184efcf8b047d7d64, f6486338fde3f04ed0ec59fe67a69a208c32734f |
| Linux/Linuxgeneric | 6.8 | Not reported |
Published upstream
Sep 19, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
In the Linux kernel, the following vulnerability has been resolved: ice: fix NULL access of tx->in_use in ice_ll_ts_intr Recent versions of the E810 firmware have support for an extra interrupt to handle report of the "low latency" Tx timestamps coming from the specialized low latency firmware interface. Instead of polling the registers, software can wait until the low latency interrupt is fired. This logic makes use of the Tx timestamp tracking structure, ice_ptp_tx, as it uses the same "ready" bitmap to track which Tx timestamps complete. Unfortunately, the ice_ll_ts_intr() function does not check if the tracker is initialized before its first access. This results in NULL dereference or use-after-free bugs similar to the issues fixed in the ice_ptp_ts_irq() function. Fix this by only checking the in_use bitmap (and other fields) if the tracker is marked as initialized. The reset flow will clear the init field under lock before it tears the tracker down, thus preventing any use-after-free or NULL access.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2025-39854 records a Unknown severity vulnerability in ice: fix NULL access of tx->in_use in ice_ll_ts_intr. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=82e71b226e0ef770d7bc143701c8b4960b4eb3d5 <2cde98a02da958357fe240a6ba269b69d913b6ba || >=82e71b226e0ef770d7bc143701c8b4960b4eb3d5 <923c267bdbb64f65bc1149d184efcf8b047d7d64 || >=82e71b226e0ef770d7bc143701c8b4960b4eb3d5 <f6486338fde3f04ed0ec59fe67a69a208c32734f | 2cde98a02da958357fe240a6ba269b69d913b6ba, 923c267bdbb64f65bc1149d184efcf8b047d7d64, f6486338fde3f04ed0ec59fe67a69a208c32734f |
| Linux/Linuxgeneric | 6.8 | Not reported |
Published upstream
Sep 19, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
In the Linux kernel, the following vulnerability has been resolved: ice: fix NULL access of tx->in_use in ice_ll_ts_intr Recent versions of the E810 firmware have support for an extra interrupt to handle report of the "low latency" Tx timestamps coming from the specialized low latency firmware interface. Instead of polling the registers, software can wait until the low latency interrupt is fired. This logic makes use of the Tx timestamp tracking structure, ice_ptp_tx, as it uses the same "ready" bitmap to track which Tx timestamps complete. Unfortunately, the ice_ll_ts_intr() function does not check if the tracker is initialized before its first access. This results in NULL dereference or use-after-free bugs similar to the issues fixed in the ice_ptp_ts_irq() function. Fix this by only checking the in_use bitmap (and other fields) if the tracker is marked as initialized. The reset flow will clear the init field under lock before it tears the tracker down, thus preventing any use-after-free or NULL access.
Quoted source text, attributed separately from HOL analysis.