Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2021-46912net: Make tcp_allowed_congestion_control readonly in non-init netns

Description

In the Linux kernel, the following vulnerability has been resolved: net: Make tcp_allowed_congestion_control readonly in non-init netns Currently, tcp_allowed_congestion_control is global and writable; writing to it in any net namespace will leak into all other net namespaces. tcp_available_congestion_control and tcp_allowed_congestion_control are the only sysctls in ipv4_net_table (the per-netns sysctl table) with a NULL data pointer; their handlers (proc_tcp_available_congestion_control and proc_allowed_congestion_control) have no other way of referencing a struct net. Thus, they operate globally. Because ipv4_net_table does not use designated initializers, there is no easy way to fix up this one "bad" table entry. However, the data pointer updating logic shouldn't be applied to NULL pointers anyway, so we instead force these entries to be read-only. These sysctls used to exist in ipv4_table (init-net only), but they were moved to the per-net ipv4_net_table, presumably without realizing that tcp_allowed_congestion_control was writable and thus introduced a leak. Because the intent of that commit was only to know (i.e. read) "which congestion algorithms are available or allowed", this read-only solution should be sufficient. The logic added in recent commit 31c4d2f160eb: ("net: Ensure net namespace isolation of sysctls") does not and cannot check for NULL data pointers, because other table entries (e.g. /proc/sys/net/netfilter/nf_log/) have .data=NULL but use other methods (.extra2) to access the struct net.

Timeline

  1. ID reserved

    By Linux

  2. · 2 days later

    Published

  3. · 2 years later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2021-46912, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.3CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:L
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.24% · top 85% of all CVEs (19 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.3.

Affected products

  • Linux · Linux

    • affected 9cb8e048e5d93825ec5e8dfb5b8df4987ea25745 – < 35d7491e2f77ce480097cabcaf93ed409e916e12
    • affected 9cb8e048e5d93825ec5e8dfb5b8df4987ea25745 – < 1ccdf1bed140820240e383ba0accc474ffc7f006
    • affected 9cb8e048e5d93825ec5e8dfb5b8df4987ea25745 – < 97684f0970f6e112926de631fdd98d9693c7e5c1
  • Linux · Linux

    • affected 5.7
    • unaffected < 5.7
    • unaffected 5.10.32 – ≤ 5.10.*
    • unaffected 5.11.16 – ≤ 5.11.*
    • unaffected 5.12 – ≤ *

References

References3

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2021-46912 badge
[![CVE-2021-46912](https://cveledger.app/badge/CVE-2021-46912.svg)](https://cveledger.app/cve/CVE-2021-46912)

Record last updated .