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.
Fix
Patch, vendor advisory and mitigation references on NVD 3
- https://git.kernel.org/stable/c/2cde98a02da958357fe240a6ba269b69d913b6ba Patch
- https://git.kernel.org/stable/c/923c267bdbb64f65bc1149d184efcf8b047d7d64 Patch
- https://git.kernel.org/stable/c/f6486338fde3f04ed0ec59fe67a69a208c32734f Patch
Every line above is quoted from NVD, CISA, Microsoft, the vendor's own advisory or DISA; nothing is generated.
Change history 1
- First seenCVSS 7.8 · linuxNVD modified 2026-10-19 21:10
Affected (CPE criteria) 5
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*cpe:2.3:o:linux:linux_kernel:6.17:rc1:*:*:*:*:*:*cpe:2.3:o:linux:linux_kernel:6.17:rc2:*:*:*:*:*:*cpe:2.3:o:linux:linux_kernel:6.17:rc3:*:*:*:*:*:*cpe:2.3:o:linux:linux_kernel:6.17:rc4:*:*:*:*:*:*