LiveActive security incident?Get immediate response
CVE Record

CVE-2021-47010: net: Only allow init netns to set default tcp cong to a restricted algo

In the Linux kernel, the following vulnerability has been resolved: net: Only allow init netns to set default tcp cong to a restricted algo tcp_set_default_congestion_control() is netns-safe in that it writes to &net->ipv4.tcp_congestion_control, but it also sets ca->flags |= TCP_CONG_NON_RESTRICTED which is not namespaced. This has the unintended side-effect of changing the global net.ipv4.tcp_allowed_congestion_control sysctl, despite the fact that it is read-only: 97684f0970f6 ("net: Make tcp_allowed_congestion_control readonly in non-init netns") Resolve this netns "leak" by only allowing the init netns to set the default algorithm to one that is restricted. This restriction could be removed if tcp_allowed_congestion_control were namespace-ified in the future. This bug was uncovered with https://github.com/JonathonReinhart/linux-netns-sysctl-verify

HighCVSS 7.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A low-privileged local user in a non-initial Linux network namespace could trigger a kernel namespace leak that changes a global TCP congestion-control allowance. The sources rate this high because the CVSS impact claims confidentiality, integrity, and availability risk, but they do not show internet-remote exploitation.

Executive priority

Treat as a high-priority kernel maintenance issue for shared Linux infrastructure. It is not evidenced as actively exploited, but local privilege requirements still matter on container hosts, developer systems, and multi-tenant environments.

Technical view

tcp_set_default_congestion_control() updates a per-network-namespace default but also sets TCP_CONG_NON_RESTRICTED on a global congestion-control algorithm object. That can unintentionally alter the global net.ipv4.tcp_allowed_congestion_control behavior from a non-init namespace, bypassing the intended read-only protection there.

Likely exposure

Exposure is limited to Linux systems running affected kernel versions where an attacker already has local low-privileged access. Risk is more relevant on multi-user hosts and container or namespace-heavy environments using affected kernels.

Exploitation context

The CVE record lists local attack vector, low complexity, low privileges, and no user interaction. The bundle says KEV is false, and no provided source states active exploitation in the wild.

Researcher notes

The core issue is a namespace boundary violation: per-netns default selection has a global side effect on congestion-control restriction flags. The provided sources do not include exploit mechanics, distribution package mappings, or additional mitigations beyond applying fixed kernel code.

Mitigation direction

  • Update to a kernel containing the referenced stable fixes.
  • Prioritize multi-user and container-host kernels before single-purpose appliances.
  • Check distribution vendor advisories for exact fixed package versions.
  • Restrict untrusted local access where kernel updates are delayed.

Validation and detection

  • Inventory Linux kernel versions across servers and container hosts.
  • Compare running kernels against vendor fixed versions or referenced stable commits.
  • Identify systems permitting untrusted local users or namespace creation.
  • Confirm post-update kernels include the congestion-control namespace fix.
Prepared
Confidence
medium
Sources
8

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-400: 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 lookup
cve · low confidence lookup

CVE-2021-47010 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

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.

1CVSS vectors
3Timeline events
2ADP providers
7Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total

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.

ScoreVersionSeverityVectorExploitImpactSource
7.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9CISA-ADP

Vulnerability scoring details

Base CVSS 3.1 score

7.8High
CVSS 3.1 vector shape for CVE-2021-47010Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CVECVE Program Container
CISA-ADPCISA ADP Vulnrichment
cvssV3_1other:ssvc
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux6670e152447732ba90626f36dfc015a13fbf150e, 6670e152447732ba90626f36dfc015a13fbf150e, 6670e152447732ba90626f36dfc015a13fbf150e, 6670e152447732ba90626f36dfc015a13fbf150e, 6670e152447732ba90626f36dfc015a13fbf150e, 6670e152447732ba90626f36dfc015a13fbf150eunaffected
LinuxLinux4.15, 0, 4.19.191, 5.4.119, 5.10.37, 5.11.21, 5.12.4, 5.13affected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-400 · source CWE mapping

Uncontrolled Resource Consumption

Uncontrolled Resource Consumption represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.