CVE-2025-37749: net: ppp: Add bound checking for skb data on ppp_sync_txmung
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 = 0xffff88803346f400 "4",
data = 0xffff88803346f416 ":\377",
truesize = 0x380,
len = 0x0,
data_len = 0x0,
mac_len = 0xe,
hdr_len = 0x0,
it is not safe to access data[2].
[pabeni@redhat.com: fixed subj typo]
Security readout for executives and security teams
Plain-English summary
A malformed, very short packet can make the Linux kernel’s synchronous PPP networking code read beyond the available packet data. The supplied CVSS score is 8.2 because remote, unauthenticated triggering may cause serious availability impact and limited confidentiality impact. Systems not using the affected PPP path are less likely to be exposed.
Executive priority
Treat as a high-priority kernel update, especially for network-facing systems using PPP. Schedule expedited remediation through normal kernel maintenance and reboot procedures. Exposure should be validated before emergency disruption because the vulnerable path is specific, and the supplied evidence does not show active exploitation.
Technical view
ppp_sync_txmung accessed initial skb data bytes without first confirming that the linear buffer contained enough data. An incoming packet with an empty payload could therefore cause an out-of-bounds access. Linux stable fixes add the missing bounds check before those bytes are read.
Likely exposure
Exposure is most likely on listed affected Linux kernels where the synchronous PPP processing path is present and reachable by untrusted traffic. The bundle lists affected releases from 2.6.12 through 6.15, with several stable-series boundaries, but does not provide enough distribution-specific information to determine every vulnerable package.
Exploitation context
The supplied vector describes remote, low-complexity, unauthenticated exploitation without user interaction. However, KEV is false and no cited evidence reports active exploitation. The sources establish an out-of-bounds access and potential availability and confidentiality effects, but do not establish reliable code execution.
Researcher notes
The vulnerability is an skb bounds-validation failure in ppp_sync_txmung involving packets with insufficient linear data, including an empty payload. No CWE is supplied. The public record provides multiple stable-tree fix commits, but this bundle does not map each commit to a precise distribution package or prove exploitation beyond the out-of-bounds condition.
Mitigation direction
Install a vendor-supported kernel containing the cited Linux stable bounds-check fix.
Use distribution advisories to identify the corrected package for each deployed kernel.
Prioritize systems that use synchronous PPP or expose PPP processing to untrusted traffic.
If immediate updating is impossible, consult vendor guidance for supported exposure-reduction measures.
Validation and detection
Inventory running kernel versions and compare them with vendor CVE advisories.
Confirm installed kernel packages explicitly include the CVE-2025-37749 fix.
Determine whether synchronous PPP functionality is configured or operational on each system.
Review kernel logs and monitoring for unexplained networking faults or crashes.
Reboot into the corrected kernel and verify the running version after installation.
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-37749 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.