In the Linux kernel, the following vulnerability has been resolved:
net: libwx: handle page_pool_dev_alloc_pages error
page_pool_dev_alloc_pages could return NULL. There was a WARN_ON(!page)
but it would still proceed to use the NULL pointer and then crash.
This is similar to commit 001ba0902046
("net: fec: handle page_pool_dev_alloc_pages error").
This is found by our static analysis tool KNighter.
Security readout for executives and security teams
Plain-English summary
A Linux network-driver error can crash an affected system when a memory-page allocation fails. The documented impact is loss of availability, not data theft or modification. Business risk is concentrated in systems that use the affected libwx networking code.
Executive priority
Treat as an expedited availability risk for critical or externally reachable Linux systems using libwx. Confirm actual driver use before emergency action, then patch through supported distribution channels. The supplied evidence does not justify claims of active attacks or confidentiality impact.
Technical view
The libwx receive path failed to stop when page_pool_dev_alloc_pages returned NULL. Despite a warning check, execution continued and dereferenced the NULL page, causing a kernel crash. The issue was found through static analysis and resolved by referenced Linux stable commits.
Likely exposure
Potential exposure includes systems running listed affected Linux releases from 6.3 through 6.15 that use the libwx networking code. The supplied version data includes an unexplained โ0โ entry and does not map each release to a fixing commit, so distribution-specific status must be confirmed.
Exploitation context
The CVSS 3.1 score is 7.5 with network reachability, low complexity, and availability-only impact. The bundle does not establish how a remote party would force the allocation failure. KEV is false, and no supplied source reports active exploitation or a public exploit.
Researcher notes
The failure condition is a NULL return from page_pool_dev_alloc_pages followed by continued use. Source material identifies five stable commits but provides no branch-to-commit mapping here. The affected-version list is ambiguous, so authoritative distribution advisories and package backport records are necessary for precise exposure decisions.
Mitigation direction
Install a vendor-supported kernel containing the applicable referenced stable fix.
Check distribution security guidance for corrected package versions and backports.
Prioritize exposed or availability-critical systems that actively use libwx networking.
Use redundancy and recovery controls until affected kernels can be updated.
Validation and detection
Inventory kernel versions and compare them with vendor-specific affected and fixed package information.
Determine whether each system loads or depends on the libwx networking code.
Confirm installed kernel sources or package changelogs contain the applicable fixing commit.
Review kernel logs for related allocation warnings, NULL dereferences, panics, or unexpected reboots.
After updating, verify the corrected kernel is running and networking remains stable.
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-37755 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
0ADP providers
6Source 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.