Host-wide policy modification via non-namespaced flag write
Published Feb 28, 2024 · Updated May 11, 2026
Improper namespace isolation in Linux kernel 4.15 allows local users to alter a host-wide TCP congestion-control policy. In tcp_set_default_congestion_control(), the code marks a restricted algorithm TCP_CONG_NON_RESTRICTED through a global ca->flags field rather than namespace-scoped state. A local user able to set the default algorithm inside a non-initial network namespace can thereby change the host-wide read-only allowed-congestion-control list.
Summary
What happened
Improper namespace isolation in Linux kernel 4.15 allows local users to alter a host-wide TCP congestion-control policy. In tcp_set_default_congestion_control(), the code marks a restricted algorithm TCP_CONG_NON_RESTRICTED through a global ca->flags field rather than namespace-scoped state. A local user able to set the default algorithm inside a non-initial network namespace can thereby change the host-wide read-only allowed-congestion-control list.
The record
- CVE
- CVE-2021-47010
- Published
- Feb 28, 2024
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-400, T1611
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 28, 2024CVE publishedPublication date reported by the CVE source.
- May 11, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=4.15
- Affected versionversion=6670e152447732ba90626f36dfc015a13fbf150e <6c1ea8bee75df8fe2184a50fcd0f70bf82986f42
- Affected versionversion=6670e152447732ba90626f36dfc015a13fbf150e <8d432592f30fcc34ef5a10aac4887b4897884493
- Affected versionversion=6670e152447732ba90626f36dfc015a13fbf150e <9884f745108f7d25b189bbcd6754e284fb29ab68
- Affected versionversion=6670e152447732ba90626f36dfc015a13fbf150e <992de06308d9a9584d59b96d294ac676f924e437
- Affected versionversion=6670e152447732ba90626f36dfc015a13fbf150e <e7d7bedd507bb732e600403b7a96f9fe48d0ca31
- Affected versionversion=6670e152447732ba90626f36dfc015a13fbf150e <efe1532a6e1a8e3c343d04fff510f0ed80328f9c
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
- Linux network namespace sysctl safety verifierproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo