{"dataType":"CVE_RECORD","dataVersion":"5.2","cveMetadata":{"cveId":"CVE-2025-37935","assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","state":"PUBLISHED","assignerShortName":"Linux","dateReserved":"2025-04-16T04:51:23.971Z","datePublished":"2025-05-20T15:21:59.381Z","dateUpdated":"2026-08-05T11:58:28.431Z"},"containers":{"cna":{"providerMetadata":{"orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux","dateUpdated":"2026-08-05T11:58:28.431Z"},"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\nnet: ethernet: mtk_eth_soc: fix SER panic with 4GB+ RAM\n\nIf the mtk_poll_rx() function detects the MTK_RESETTING flag, it will\njump to release_desc and refill the high word of the SDP on the 4GB RFB.\nSubsequently, mtk_rx_clean will process an incorrect SDP, leading to a\npanic.\n\nAdd patch from MediaTek's SDK to resolve this."}],"metrics":[{"cvssV3_1":{"version":"3.1","vectorString":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","baseScore":9.8,"baseSeverity":"CRITICAL"},"scenarios":[{"lang":"en","value":"AV:N - The vulnerable code is the ethernet RX NAPI descriptor-recycling path, executed for every frame received on a WAN/LAN-facing port of an MT7988 router SoC, and the state that triggers it (RX FIFO overflow, free-queue-empty, DMA hang, atomic allocation failure) is produced by a sustained inbound packet flood that can be routed from anywhere. No local access or L2 adjacency is required to deliver the traffic.\nAC:L - An attacker driving sustained traffic reliably produces the RFIFO_OV/FQ_EMPTY/DMA-hang conditions that schedule SER, and once MTK_RESETTING is set every in-flight NAPI descriptor deterministically takes the release_desc path and gets its ADDR64 clobbered; the 4GB-straddling buffer placement that makes the corruption harmful is the default state on any affected 4GB+ board.\nPR:N - Triggering requires only sending network frames to the device — there is no credential check, socket ownership, or capability gate anywhere between packet arrival and mtk_poll_rx().\nUI:N - The corruption occurs entirely within the driver's receive and reset paths with no victim action required.\nS:U - The corrupted DMA address and the resulting panic stay within the kernel's own security authority; no hypervisor, IOMMU, or sandbox boundary is crossed.\nC:H - Because the re-armed descriptor points at the wrong physical page, the buffer handed up as an skb contains stale kernel memory rather than the received frame, and on a router that content can be forwarded back onto the wire; the bogus dma_unmap_single() over unrelated physical memory compounds the exposure.\nI:H - The RX DMA engine is handed a descriptor whose 36-bit address is off by up to 4GB, so the NIC writes attacker-supplied packet bytes into arbitrary unrelated kernel memory — an out-of-bounds DMA write with attacker-controlled contents that is leverageable for control-flow hijacking.\nA:H - The documented symptom is a kernel panic when mtk_rx_clean() unmaps the corrupted SDP during system error recovery, taking the entire device down."}]}],"affected":[{"product":"Linux","vendor":"Linux","defaultStatus":"unaffected","repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","programFiles":["drivers/net/ethernet/mediatek/mtk_eth_soc.c"],"versions":[{"version":"2d75891ebc09ba9cf30697dfd54497ef0220308f","lessThan":"cb625f783f70dc6614f03612b8e64ad99cb0a13c","status":"affected","versionType":"git"},{"version":"2d75891ebc09ba9cf30697dfd54497ef0220308f","lessThan":"317013d1ad13524be02d60b9e98f08fbd13f8c14","status":"affected","versionType":"git"},{"version":"2d75891ebc09ba9cf30697dfd54497ef0220308f","lessThan":"67619cf69dec5d1d7792808dfa548616742dd51d","status":"affected","versionType":"git"},{"version":"2d75891ebc09ba9cf30697dfd54497ef0220308f","lessThan":"6e0490fc36cdac696f96e57b61d93b9ae32e0f4c","status":"affected","versionType":"git"}]},{"product":"Linux","vendor":"Linux","defaultStatus":"affected","repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","programFiles":["drivers/net/ethernet/mediatek/mtk_eth_soc.c"],"versions":[{"version":"6.6","status":"affected"},{"version":"0","lessThan":"6.6","status":"unaffected","versionType":"semver"},{"version":"6.6.90","lessThanOrEqual":"6.6.*","status":"unaffected","versionType":"semver"},{"version":"6.12.28","lessThanOrEqual":"6.12.*","status":"unaffected","versionType":"semver"},{"version":"6.14.6","lessThanOrEqual":"6.14.*","status":"unaffected","versionType":"semver"},{"version":"6.15","lessThanOrEqual":"*","status":"unaffected","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"operator":"OR","negate":false,"cpeMatch":[{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"6.6","versionEndExcluding":"6.6.90"},{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"6.6","versionEndExcluding":"6.12.28"},{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"6.6","versionEndExcluding":"6.14.6"},{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"6.6","versionEndExcluding":"6.15"}]}]}],"references":[{"url":"https://git.kernel.org/stable/c/cb625f783f70dc6614f03612b8e64ad99cb0a13c"},{"url":"https://git.kernel.org/stable/c/317013d1ad13524be02d60b9e98f08fbd13f8c14"},{"url":"https://git.kernel.org/stable/c/67619cf69dec5d1d7792808dfa548616742dd51d"},{"url":"https://git.kernel.org/stable/c/6e0490fc36cdac696f96e57b61d93b9ae32e0f4c"}],"title":"net: ethernet: mtk_eth_soc: fix SER panic with 4GB+ RAM","x_generator":{"engine":"bippy-1.2.0"}}}}