CVE-2025-38574: pptp: ensure minimal skb length in pptp_xmit()
In the Linux kernel, the following vulnerability has been resolved:
pptp: ensure minimal skb length in pptp_xmit()
Commit aabc6596ffb3 ("net: ppp: Add bound checking for skb data
on ppp_sync_txmung") fixed ppp_sync_txmunge()
We need a similar fix in pptp_xmit(), otherwise we might
read uninit data as reported by syzbot.
BUG: KMSAN: uninit-value in pptp_xmit+0xc34/0x2720 drivers/net/ppp/pptp.c:193
pptp_xmit+0xc34/0x2720 drivers/net/ppp/pptp.c:193
ppp_channel_bridge_input drivers/net/ppp/ppp_generic.c:2290 [inline]
ppp_input+0x1d6/0xe60 drivers/net/ppp/ppp_generic.c:2314
pppoe_rcv_core+0x1e8/0x760 drivers/net/ppp/pppoe.c:379
sk_backlog_rcv+0x142/0x420 include/net/sock.h:1148
__release_sock+0x1d3/0x330 net/core/sock.c:3213
release_sock+0x6b/0x270 net/core/sock.c:3767
pppoe_sendmsg+0x15d/0xcb0 drivers/net/ppp/pppoe.c:904
sock_sendmsg_nosec net/socket.c:712 [inline]
__sock_sendmsg+0x330/0x3d0 net/socket.c:727
____sys_sendmsg+0x893/0xd80 net/socket.c:2566
___sys_sendmsg+0x271/0x3b0 net/socket.c:2620
__sys_sendmmsg+0x2d9/0x7c0 net/socket.c:2709
Security readout for executives and security teams
Plain-English summary
A Linux kernel flaw in PPTP packet transmission can read uninitialized memory when processing an undersized network buffer. The supplied CVSS 8.6 rating indicates possible confidentiality, integrity, and serious availability effects. Exposure is concentrated in systems using the kernel PPTP/PPP functionality, not every Linux host equally.
Executive priority
Treat as a high-priority infrastructure patch where PPTP is enabled or used. Accelerate remediation for exposed gateways and VPN systems. For hosts without this functionality, first validate applicability rather than initiating emergency-wide disruption. No supplied evidence supports declaring an active exploitation emergency.
Technical view
pptp_xmit() lacked a minimum socket-buffer length check before reading packet data. Kernel fuzzing with KMSAN detected an uninitialized-value read at drivers/net/ppp/pptp.c:193 through a PPP/PPPoE processing path. Linux stable commits add the missing validation; the bundle lists affected kernel series but does not provide unambiguous range notation.
Likely exposure
Prioritize Linux systems where PPTP kernel support is present and actively used, especially VPN, routing, gateway, or PPP infrastructure. The supplied version data spans numerous kernel generations, but its flattened representation makes exact affected and fixed boundaries unclear. Confirm status against distribution or kernel-vendor advisories.
Exploitation context
The issue was found by syzbot and demonstrated through a KMSAN uninitialized-memory report. The bundle marks it absent from KEV and provides no evidence of active exploitation or a public weaponized exploit. Network reachability is asserted by the CVSS vector, although practical prerequisites are not fully documented here.
Researcher notes
The observable defect is an undersized skb reaching pptp_xmit(), producing an uninitialized-value read. The trace traverses PPP bridge input and PPPoE receive/send paths, but the bundle does not establish all remotely controllable conditions. No CWE is assigned. Stable commits are available across kernel branches; exact branch mapping requires vendor confirmation.
Mitigation direction
Install a vendor-supported kernel containing the applicable Linux stable fix.
Check Linux distribution advisories for the corrected package version.
If PPTP is unnecessary, evaluate disabling it under vendor guidance.
Prioritize externally reachable VPN, gateway, and PPP systems.
Validation and detection
Inventory kernel versions and systems using PPTP or related PPP functionality.
Compare installed packages with distribution security advisories.
Verify the applicable stable fix commit is included in the running kernel.
After updating, confirm systems booted into the corrected kernel.
Monitor kernel logs for PPTP, PPP, memory-safety, or crash indicators.
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.
cve · low confidence lookup
CVE-2025-38574 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
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.
1CVSS vectors
3Timeline events
1ADP providers
12Source links
CVSS vector scores
1 official score
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.