CVE-2025-39673
Last modified
CVE-2025-39673 is a medium-severity vulnerability rated 4.7/10 on the CVSS scale. In the Linux kernel, the following vulnerability has been resolved: ppp: fix race conditions in ppp_fill_forward_path ppp_fill_forward_path() has two race conditions: 1. The ppp->channels list can change between list_empty() and list_first_entry(), as ppp_lock() is not held. EPSS estimates a 0.10% chance of exploitation in the next 30 days.
Description
In the Linux kernel, the following vulnerability has been resolved: ppp: fix race conditions in ppp_fill_forward_path ppp_fill_forward_path() has two race conditions: 1. The ppp->channels list can change between list_empty() and list_first_entry(), as ppp_lock() is not held. If the only channel is deleted in ppp_disconnect_channel(), list_first_entry() may access an empty head or a freed entry, and trigger a panic. 2. pch->chan can be NULL. When ppp_unregister_channel() is called, pch->chan is set to NULL before pch is removed from ppp->channels. Fix these by using a lockless RCU approach: - Use list_first_or_null_rcu() to safely test and access the first list entry. - Convert list modifications on ppp->channels to their RCU variants and add synchronize_net() after removal. - Check for a NULL pch->chan before dereferencing it.
Metrics
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Linux | Linux Kernel | >= 5.13, < 5.15.190 | — |
| Linux | Linux Kernel | >= 5.16, < 6.1.149 | — |
| Linux | Linux Kernel | >= 6.2, < 6.6.103 | — |
| Linux | Linux Kernel | >= 6.7, < 6.12.44 | — |
| Linux | Linux Kernel | >= 6.13, < 6.16.4 | — |
| Linux | Linux Kernel | 6.17 | Rc1 |
| Debian | Debian Linux | 11.0 | — |
References
- https://lists.debian.org/debian-lts-announce/2025/10/msg00008.htmlThird Party Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2025-39673?
How severe is CVE-2025-39673?
How do I fix CVE-2025-39673?
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-3966A vulnerability was found in itwanger paicoding 1.0.3 and cl…5.3
- CVE-2025-39663Cross-Site Scripting (XSS) vulnerability in Checkmk's distri…8.4
- CVE-2025-39664Insufficient escaping in the report scheduler within Checkmk…6.5
- CVE-2025-39665User enumeration in Nagvis' Checkmk MultisiteAuth before ver…5.3
- CVE-2025-39666Local privilege escalation in Checkmk 2.2.0 (EOL), Checkmk 2…7.3
- CVE-2025-3967A vulnerability was found in itwanger paicoding 1.0.3. It ha…5.4
- CVE-2025-39674In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-39675In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-39676In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-39677In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-39678In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-39679In the Linux kernel, the following vulnerability has been re…5.5
Are you affected by CVE-2025-39673?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
