Review reviewHigh

CVE-2025-38574

Linux Linux, linux kernel, debian linux

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/...

CVSS
7.8
EPSS
0.36%
28.5% percentile
CISA KEV
Not listed
Published
2025.08.20
PRIORITY ASSESSMENT

Review review

The CVSS severity warrants an early asset and exposure review.

Known exploitationNot established by KEV
Exploit probability0.36%
Technical severityCVSS 7.8

Vulnerability overview

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/...

Affected product and versions

Product
Linux Linux, linux kernel, debian linux
Affected versions
>= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 97b8c5d322c5c0038cac4bc56fdbe237d0be426f, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 26672f1679b143aa34fca0b6046b7fd0c184770d, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 5de7513f38f3c19c0610294ee478242bea356f8c, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 504cc4ab91073d2ac7404ad146139f86ecee7193, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 5005d24377378a20e5c0e53052fc4ebdcdcbc611, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < ea99b88b1999ebcb24d5d3a6b7910030f40d3bba, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < b7dcda76fd0615c0599c89f36873a6cd48e02dbb, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 1a04db0fd75cb6034fc27a56b67b3b8b9022a98c, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < de9c4861fb42f0cd72da844c3c34f692d5895b7b, >= 2.6.12, >= 2.6.13 < 5.4.297, >= 5.5 < 5.10.241, >= 5.11 < 5.15.190, >= 5.16 < 6.1.148, >= 6.2 < 6.6.102, >= 6.7 < 6.12.42, >= 6.13 < 6.15.10, >= 6.16 < 6.16.1, 2.6.12, 11.0
Fixed versions
5.4.297, 5.10.241, 5.15.190, 6.1.148, 6.6.102, 6.12.42, 6.15.10, 6.16.1

Recommended response sequence

Confirm exposure before applying a vendor-supported change.

Full remediation guide
  1. 1
    Identify

    Confirm that Linux Linux, linux kernel, debian linux and an affected version are present.

  2. 2
    Prioritize

    Combine exploitation signals with asset exposure and business criticality.

  3. 3
    Remediate

    Follow the vendor advisory or supported update path and preserve rollback options.

  4. 4
    Verify

    Recheck the version, service health, access paths, and relevant logs.

Technical data

CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CWE
CWE-908