CVE-2025-39854: ice: fix NULL access of tx->in_use in ice_ll_ts_intr
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.
Security readout for executives and security teams
Plain-English summary
A flaw in the Linux Intel Ethernet “ice” driver can access timestamp-tracking memory before initialization or after teardown. On systems using relevant E810 firmware features, this may crash the kernel or corrupt memory. Exploitation requires local, low-privileged access according to the supplied CVSS assessment.
Executive priority
Prioritize remediation on production hosts with Intel E810 networking, especially where local users or workloads are less trusted. Treat exposed systems as a high-priority stability and memory-safety issue, while recognizing that the supplied evidence does not establish remote or active exploitation.
Technical view
The low-latency transmit-timestamp interrupt handler, ice_ll_ts_intr(), accessed ice_ptp_tx fields without verifying tracker initialization. Concurrent reset teardown could therefore produce a NULL dereference or use-after-free. The referenced kernel fixes gate field and bitmap access on the initialization state, which reset clears under lock before freeing the tracker.
Likely exposure
Exposure is limited to Linux systems using the ice driver with relevant Intel E810 firmware supporting the extra low-latency timestamp interrupt. The bundle lists Linux 6.8, 6.12.46, 6.16.6, and 6.17 as affected, but does not provide complete distribution-specific package mappings.
Exploitation context
The supplied CVSS 3.1 score is 7.8 with local access and low privileges required. The CVE is not listed as KEV, and the supplied sources provide no evidence of active exploitation or a public exploit. Practical reachability likely depends on affected hardware, firmware, driver state, and timestamp handling.
Researcher notes
The reported weakness is CWE-416, although the description covers both use-after-free and NULL access. Fix logic relies on an initialization flag synchronized with reset teardown under lock. Exact vulnerable commit ranges, firmware versions, distribution backports, and demonstrated security impact are not fully established by the bundle.
Mitigation direction
Upgrade to a vendor-supported kernel containing the referenced upstream or stable fix.
Check distribution and appliance advisories for corrected package versions and reboot requirements.
Prioritize systems using Intel E810 adapters and the Linux ice driver.
If immediate patching is unavailable, consult vendor guidance for supported feature-specific mitigations.
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.
cwe · low confidence lookup
CWE-416: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
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.
2CVSS vectors
3Timeline events
1ADP providers
4Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
2 official scores
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-416 · source CWE mapping
Use After Free
Use After Free represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.