Review reviewHigh

CVE-2025-37749

Linux Linux, linux kernel, debian linux

In the Linux kernel, the following vulnerability has been resolved: net: ppp: Add bound checking for skb data on ppp_sync_txmung Ensure we have enough data in linear buffer from skb before accessing initial bytes. This prevents potential out-of-bounds accesses when processing short packets. When ppp_sync_txmung receives an incoming package with an empty payload: (remote) gef➤ p *(struct pppoe_hdr *) (skb->head + skb->network_header) $18 = { type = 0x1, ver = 0x1, code = 0x0, sid = 0x2, length = 0x0, tag = 0xffff8880371cdb96 } from the skb struct (trimmed) tail = 0x16, end = 0x140, head = 0x...

CVSS
7.1
EPSS
0.37%
30.0% percentile
CISA KEV
Not listed
Published
2025.05.01
PRIORITY ASSESSMENT

Review review

The CVSS severity warrants an early asset and exposure review.

Known exploitationNot established by KEV
Exploit probability0.37%
Technical severityCVSS 7.1

Vulnerability overview

In the Linux kernel, the following vulnerability has been resolved: net: ppp: Add bound checking for skb data on ppp_sync_txmung Ensure we have enough data in linear buffer from skb before accessing initial bytes. This prevents potential out-of-bounds accesses when processing short packets. When ppp_sync_txmung receives an incoming package with an empty payload: (remote) gef➤ p *(struct pppoe_hdr *) (skb->head + skb->network_header) $18 = { type = 0x1, ver = 0x1, code = 0x0, sid = 0x2, length = 0x0, tag = 0xffff8880371cdb96 } from the skb struct (trimmed) tail = 0x16, end = 0x140, head = 0x...

Affected product and versions

Product
Linux Linux, linux kernel, debian linux
Affected versions
>= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 529401c8f12ecc35f9ea5d946d5a5596cf172b48, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < de5a4f0cba58625e88b7bebd88f780c8c0150997, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 99aa698dec342a07125d733e39aab4394b3b7e05, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < b78f2b458f56a5a4d976c8e01c43dbf58d3ea2ca, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < fbaffe8bccf148ece8ad67eb5d7aa852cabf59c8, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < b4c836d33ca888695b2f2665f948bc1b34fbd533, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 1f6eb9fa87a781d5370c0de7794ae242f1a95ee5, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 6e8a6bf43cea4347121ab21bb1ed8d7bef7e732e, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < aabc6596ffb377c4c9c8f335124b92ea282c9821, >= 2.6.12, >= 2.6.13 < 5.4.293, >= 5.5 < 5.10.237, >= 5.11 < 5.15.181, >= 5.16 < 6.1.135, >= 6.2 < 6.6.88, >= 6.7 < 6.12.24, >= 6.13 < 6.13.12, >= 6.14 < 6.14.3, 2.6.12, 6.15
Fixed versions
5.4.293, 5.10.237, 5.15.181, 6.1.135, 6.6.88, 6.12.24, 6.13.12, 6.14.3

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:N/A:H
CWE
CWE-125