Security readout for executives and security teams
Plain-English summary
A Linux MediaTek Ethernet driver can overwrite unrelated kernel memory while setting up DMA buffers. On affected systems, this could undermine confidentiality, integrity, or availability. Exposure is narrower than all Linux systems because the vulnerable mtk_eth_soc driver must be relevant to the device.
Executive priority
Treat remediation as urgent for business-critical devices using this MediaTek driver, particularly network infrastructure. Do not classify every Linux host as exposed. Require asset and vendor-build confirmation, then patch affected systems through supported update channels.
Technical view
During free-queue DMA initialization, an allocation loop can touch more descriptors than the number of buffers being allocated. This out-of-bounds write, classified as CWE-787, corrupts unrelated kernel memory. Upstream stable commits correct the loop iteration count.
Likely exposure
Prioritize Linux devices using the MediaTek mtk_eth_soc Ethernet driver. The supplied version data marks entries including 6.10, 6.11.6, and 6.12 as affected, but does not clearly express every range boundary or vendor backport. Confirm exposure against the device vendor's kernel build.
Exploitation context
The supplied CVSS 3.1 vector rates this 9.8 and network-accessible. However, the sources do not describe a remote trigger or required runtime conditions. The bundle marks it absent from KEV and provides no cited evidence of active exploitation.
Researcher notes
The core defect and correction are clear, but practical exploitability is not established by the supplied sources. Version interpretation requires care because the structured version entries are ambiguous and downstream kernels may carry backports without matching upstream version numbers.
Mitigation direction
- Inventory systems using the MediaTek mtk_eth_soc Ethernet driver.
- Apply a vendor-supported kernel containing the referenced stable fix.
- Confirm appliance vendors have backported the fix into their shipped kernels.
- If patching is delayed, consult vendor guidance; the supplied sources name no workaround.
Validation and detection
- Record each device's exact kernel build and vendor firmware version.
- Confirm the vendor build contains one of the referenced fixes or an equivalent backport.
- Verify MediaTek Ethernet initialization and normal network operation after updating.
- Recheck previously identified devices to ensure vulnerable builds are no longer deployed.
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.
CWE-787: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2024-50206 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.
SSVC decision data
CVSS vector scores
2 official scoresWe 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.9LinuxCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H1.83.6CISA-ADPVulnerability 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
Base CVSS 3.1 score
5.5MediumVector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://git.kernel.org/stable/c/68cd084e3ec1512cd383cb3e9cf0ab7ab413724cCVE reference, Linux
- https://git.kernel.org/stable/c/88806efc034a9830f483963326b99930ad519af1CVE 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.
Out-of-bounds Write
Out-of-bounds Write represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.