CVE-2025-39854
Last modified
CVE-2025-39854 is a high-severity vulnerability rated 7.8/10 on the CVSS scale. 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. EPSS estimates a 0.14% chance of exploitation in the next 30 days.
Description
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.
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Linux | Linux Kernel | >= 6.8, < 6.12.46 | — |
| Linux | Linux Kernel | >= 6.13, < 6.16.6 | — |
| Linux | Linux Kernel | 6.17 | Rc1 |
References
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2025-39854?
How severe is CVE-2025-39854?
How do I fix CVE-2025-39854?
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 2025
- CVE-2025-39849In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2025-3985A vulnerability was found in Apereo CAS 5.2.6. It has been c…4.9
- CVE-2025-39850In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-39851In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-39852In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-39853In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2025-39855In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2025-39856In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-39857In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-39858In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-39859In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2025-3986A vulnerability was found in Apereo CAS 5.2.6. It has been d…7.5
Are you affected by CVE-2025-39854?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
