Security readout for executives and security teams
Plain-English summary
A Linux networking flaw can panic affected systems using the MediaTek Ethernet driver when reset handling interacts with systems having 4GB or more RAM. The directly described business impact is service interruption or device reboot. The supplied 9.8 score also claims confidentiality and integrity impact, but the source bundle does not explain those impacts.
Executive priority
Treat this as urgent for network-facing appliances or infrastructure matching the driver and memory conditions because a kernel panic can interrupt critical services. Prioritize inventory immediately and patch confirmed matches through normal vendor channels. Systems without the MediaTek driver are not shown to be exposed by these sources.
Technical view
When mtk_poll_rx() detects MTK_RESETTING, it enters descriptor-release handling and incorrectly refills the high word of the SDP for the 4GB receive buffer. mtk_rx_clean() later processes the incorrect SDP, causing a kernel panic. Linux stable commits incorporate a MediaTek SDK patch.
Likely exposure
Exposure appears limited to Linux systems running affected kernel versions, using the MediaTek mtk_eth_soc Ethernet driver, and having 4GB or more RAM. The supplied version data is not presented as unambiguous ranges, so distribution backport status must be checked before declaring a system vulnerable.
Exploitation context
CISA KEV status is false, and the supplied sources provide no evidence of active exploitation or a public exploit. Although the CVSS vector identifies network reachability, the bundle does not establish how reliably an unauthenticated remote party can trigger the reset condition.
Researcher notes
The documented failure is an incorrect DMA descriptor address followed by a kernel panic, supporting availability impact. The source bundle does not substantiate its claimed confidentiality or integrity consequences. Exact vulnerable version boundaries and triggerability remain unclear; use commit-level backport verification and avoid inferring that every listed Linux release is uniformly affected.
Mitigation direction
- Identify systems using the mtk_eth_soc driver with 4GB or more RAM.
- Apply a vendor or distribution kernel containing the applicable Linux stable fix.
- Confirm downstream kernels backported the fix; version numbers alone may be insufficient.
- If no update is available, request explicit interim guidance from the system vendor.
Validation and detection
- Record each candidate system's kernel build, hardware platform, RAM, and active Ethernet driver.
- Compare distribution patch notes against the four referenced Linux stable commits.
- Verify the installed kernel package contains the relevant backport or successor fix.
- Test reset and recovery behavior safely in staging after updating.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-2025-37935 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
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.
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9LinuxVulnerability scoring details
Base CVSS 3.1 score
9.8CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
Source materials
- CVE List V5 sourceCVE List V5
- https://git.kernel.org/stable/c/cb625f783f70dc6614f03612b8e64ad99cb0a13cCVE reference, Linux
- https://git.kernel.org/stable/c/317013d1ad13524be02d60b9e98f08fbd13f8c14CVE reference, Linux
- https://git.kernel.org/stable/c/67619cf69dec5d1d7792808dfa548616742dd51dCVE reference, Linux
- https://git.kernel.org/stable/c/6e0490fc36cdac696f96e57b61d93b9ae32e0f4cCVE reference, Linux
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.