Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2025-37749: net: ppp: Add bound checking for skb data on ppp_sync_txmung

Noroxi assessment

Priority: Monitor (action score 28/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.39% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 1f6eb9fa87a781d5370c0de7794ae242f1a95ee5, 529401c8f12ecc35f9ea5d946d5a5596cf172b48, 6e8a6bf43cea4347121ab21bb1ed8d7bef7e732e; azl3 kernel 6.6.85.1-4 on Azure Linux 3.0 6.6.92.2-1; azl3 kernel 6.6.92.2-1 on Azure Linux 3.0 6.6.92.2-1.

Low priority for now. Upgrade to Linux Linux 1f6eb9fa87a781d5370c0de7794ae242f1a95ee5, 529401c8f12ecc35f9ea5d946d5a5596cf172b48, 6e8a6bf43cea4347121ab21bb1ed8d7bef7e732e; azl3 kernel 6.6.85.1-4 on Azure Linux 3.0 6.6.92.2-1; azl3 kernel 6.6.92.2-1 on Azure Linux 3.0 6.6.92.2-1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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]

HighCVSS 7.1 · v3.1—No exploit Fix available
Published
May 1, 2025
Updated
Aug 5, 2026
EPSS
0.3% · 33th percentile

Report tools

JSON

Action score

28

Monitor

Low priority for now.

CVSS
28 / 40 · 7.1 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.3%

CNA vs NVD score

NVD
7.1
CNA · Linux
8.2
1.1 point gap

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

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2025-37749

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel
debiandebian linux

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • debian debian linux11.0
  • linux linux kernel5.5 and later · before 5.10.237
  • linux linux kernel5.11 and later · before 5.15.181
  • linux linux kernel5.16 and later · before 6.1.135
  • linux linux kernel6.2 and later · before 6.6.88
  • linux linux kernel2.6.13 and later · before 5.4.293
  • linux linux kernel6.13 and later · before 6.13.12
  • linux linux kernel6.14 and later · before 6.14.3
  • linux linux kernel6.7 and later · before 6.12.24
  • linux linux kernel2.6.12
  • linux linux kernel6.15

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 2.6.12affected
    • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 529401c8f12ecc35f9ea5d946d5a5596cf172b48affected · git
    • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before de5a4f0cba58625e88b7bebd88f780c8c0150997affected · git
    • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 99aa698dec342a07125d733e39aab4394b3b7e05affected · git
    • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before b78f2b458f56a5a4d976c8e01c43dbf58d3ea2caaffected · git
    • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before fbaffe8bccf148ece8ad67eb5d7aa852cabf59c8affected · git
    • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before b4c836d33ca888695b2f2665f948bc1b34fbd533affected · git
    • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 1f6eb9fa87a781d5370c0de7794ae242f1a95ee5affected · git
    • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 6e8a6bf43cea4347121ab21bb1ed8d7bef7e732eaffected · git
    • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before aabc6596ffb377c4c9c8f335124b92ea282c9821affected · git

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
AlmaLinux:9kernelbefore 5.14.0-570.17.1.el9_65.14.0-570.17.1.el9_6
AlmaLinux:9kernel-64kbefore 5.14.0-570.17.1.el9_65.14.0-570.17.1.el9_6
AlmaLinux:9kernel-64k-corebefore 5.14.0-570.17.1.el9_65.14.0-570.17.1.el9_6
AlmaLinux:9kernel-64k-debugbefore 5.14.0-570.17.1.el9_65.14.0-570.17.1.el9_6
AlmaLinux:9kernel-64k-debug-corebefore 5.14.0-570.17.1.el9_65.14.0-570.17.1.el9_6
AlmaLinux:9kernel-64k-debug-develbefore 5.14.0-570.17.1.el9_65.14.0-570.17.1.el9_6
AlmaLinux:9kernel-64k-debug-devel-matchedbefore 5.14.0-570.17.1.el9_65.14.0-570.17.1.el9_6
AlmaLinux:9kernel-64k-debug-modulesbefore 5.14.0-570.17.1.el9_65.14.0-570.17.1.el9_6
AlmaLinux:9kernel-64k-debug-modules-corebefore 5.14.0-570.17.1.el9_65.14.0-570.17.1.el9_6
AlmaLinux:9kernel-64k-debug-modules-extrabefore 5.14.0-570.17.1.el9_65.14.0-570.17.1.el9_6
AlmaLinux:9kernel-64k-develbefore 5.14.0-570.17.1.el9_65.14.0-570.17.1.el9_6
AlmaLinux:9kernel-64k-devel-matchedbefore 5.14.0-570.17.1.el9_65.14.0-570.17.1.el9_6
AlmaLinux:9kernel-64k-modulesbefore 5.14.0-570.17.1.el9_65.14.0-570.17.1.el9_6
AlmaLinux:9kernel-64k-modules-corebefore 5.14.0-570.17.1.el9_65.14.0-570.17.1.el9_6
AlmaLinux:9kernel-64k-modules-extrabefore 5.14.0-570.17.1.el9_65.14.0-570.17.1.el9_6
AlmaLinux:9kernel-abi-stablelistsbefore 5.14.0-570.17.1.el9_65.14.0-570.17.1.el9_6
AlmaLinux:9kernel-corebefore 5.14.0-570.17.1.el9_65.14.0-570.17.1.el9_6
AlmaLinux:9kernel-cross-headersbefore 5.14.0-570.17.1.el9_65.14.0-570.17.1.el9_6
AlmaLinux:9kernel-debugbefore 5.14.0-570.17.1.el9_65.14.0-570.17.1.el9_6
AlmaLinux:9kernel-debug-corebefore 5.14.0-570.17.1.el9_65.14.0-570.17.1.el9_6
AlmaLinux:9kernel-debug-develbefore 5.14.0-570.17.1.el9_65.14.0-570.17.1.el9_6
AlmaLinux:9kernel-debug-devel-matchedbefore 5.14.0-570.17.1.el9_65.14.0-570.17.1.el9_6
AlmaLinux:9kernel-debug-modulesbefore 5.14.0-570.17.1.el9_65.14.0-570.17.1.el9_6
AlmaLinux:9kernel-debug-modules-corebefore 5.14.0-570.17.1.el9_65.14.0-570.17.1.el9_6

+96

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2025-37745May 1, 2025 · PM: hibernate: Avoid deadlock in hibernate_compressor_param_set()
    22Monitor
  • ← EarlierCVE-2025-37748May 1, 2025 · iommu/mediatek: Fix NULL pointer deference in mtk_iommu_device_group
    22Monitor
  • Later →CVE-2025-37751May 1, 2025 · x86/cpu: Avoid running off the end of an AMD erratum table
    22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux1f6eb9fa87a781d5370c0de7794ae242f1a95ee5Vendor (CNA)
Linux Linux529401c8f12ecc35f9ea5d946d5a5596cf172b48Vendor (CNA)
Linux Linux6e8a6bf43cea4347121ab21bb1ed8d7bef7e732eVendor (CNA)
Linux Linux99aa698dec342a07125d733e39aab4394b3b7e05Vendor (CNA)
Linux Linuxaabc6596ffb377c4c9c8f335124b92ea282c9821Vendor (CNA)
Linux Linuxb4c836d33ca888695b2f2665f948bc1b34fbd533Vendor (CNA)
Linux Linuxb78f2b458f56a5a4d976c8e01c43dbf58d3ea2caVendor (CNA)
Linux Linuxde5a4f0cba58625e88b7bebd88f780c8c0150997Vendor (CNA)
Linux Linuxfbaffe8bccf148ece8ad67eb5d7aa852cabf59c8Vendor (CNA)
azl3 kernel 6.6.85.1-4 on Azure Linux 3.06.6.92.2-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
azl3 kernel 6.6.92.2-1 on Azure Linux 3.06.6.92.2-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
almalinux:kernel5.14.0-570.17.1.el9_6 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k5.14.0-570.17.1.el9_6 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-core5.14.0-570.17.1.el9_6 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug5.14.0-570.17.1.el9_6 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-core5.14.0-570.17.1.el9_6 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel5.14.0-570.17.1.el9_6 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel-matched5.14.0-570.17.1.el9_6 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules5.14.0-570.17.1.el9_6 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-core5.14.0-570.17.1.el9_6 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-extra5.14.0-570.17.1.el9_6 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-devel5.14.0-570.17.1.el9_6 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-devel-matched5.14.0-570.17.1.el9_6 · AlmaLinux:9Package registry (OSV)
debian:linux6.1.135-1 · Debian:12Package registry (OSV)
red hat:kernel-64k-debug-debuginfo0:5.14.0-570.17.1.el9_6 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel0:5.14.0-570.17.1.el9_6 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel-matched0:5.14.0-570.17.1.el9_6 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debuginfo0:5.14.0-570.17.1.el9_6 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-devel0:5.14.0-570.17.1.el9_6 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-devel-matched0:5.14.0-570.17.1.el9_6 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)

+6

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
None
Availability impact
High

Weakness class (CWE)

CWE-125 · Out-of-bounds Read

CVSS vector

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

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

ATT&CK techniques

—

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (10 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records