CVE-2021-47137: net: lantiq: fix memory corruption in RX ring
In the Linux kernel, the following vulnerability has been resolved:
net: lantiq: fix memory corruption in RX ring
In a situation where memory allocation or dma mapping fails, an
invalid address is programmed into the descriptor. This can lead
to memory corruption. If the memory allocation fails, DMA should
reuse the previous skb and mapping and drop the packet. This patch
also increments rx drop counter.
Security readout for executives and security teams
Plain-English summary
This is a Linux kernel memory corruption issue in the Lantiq network driver receive ring. Under allocation or DMA mapping failure, the driver could program an invalid descriptor address. The published severity is high because successful exploitation could affect confidentiality, integrity, and availability, but the CVSS vector is local and requires low privileges.
Executive priority
Treat as high priority where Lantiq driver systems remain on affected kernels, especially infrastructure with local user access. Broader enterprise urgency depends on whether those kernels and that driver are actually deployed. No cited source confirms exploitation in the wild.
Technical view
The flaw is in Linux net/lantiq RX ring handling. When skb allocation or DMA mapping fails, an invalid address may be placed into a descriptor instead of reusing the previous skb and mapping while dropping the packet. Stable kernel commits resolve the behavior and increment the RX drop counter.
Likely exposure
Exposure is most likely on Linux systems running affected kernel versions with the Lantiq network driver in use. The source bundle lists Linux kernel versions including 4.20, 5.4.124, 5.10.42, 5.12.9, and 5.13 as affected, but downstream backport status must be checked per vendor distribution.
Exploitation context
The provided sources do not show active exploitation, and KEV is false. CVSS indicates local attack vector, low privileges required, no user interaction, and high potential impact across confidentiality, integrity, and availability. Evidence in the bundle does not establish remote exploitability.
Researcher notes
The key evidence is the kernel fix description: allocation or DMA mapping failure could write an invalid descriptor address, causing memory corruption. The affected-version data is sparse and downstream kernels may be patched independently, so validation should focus on commit or package-fix presence, not version strings alone.
Mitigation direction
Apply Linux stable kernel updates containing the referenced Lantiq RX ring fix.
Check distribution advisories for backported fixes in supported kernel packages.
Prioritize systems using the Lantiq network driver on affected kernel builds.
If patch status is unclear, request guidance from the kernel or distribution vendor.
Validation and detection
Inventory Linux kernel versions on systems using the Lantiq network driver.
Compare installed kernel changelogs against the referenced stable commits.
Confirm vendor packages include the RX ring memory corruption fix.
Document systems still running affected kernels for remediation tracking.
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.
cwe · low confidence lookup
CWE-770: 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.
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.
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.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-770 · source CWE mapping
Allocation of Resources Without Limits or Throttling
Allocation of Resources Without Limits or Throttling represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.