Linux KernelOperating system · Linux
CVE-2026-53077
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedIn the Linux kernel, the following vulnerability has been resolved: net/rds: Restrict use of RDS/IB to the initial network namespace Prevent using RDS/IB in network namespaces other than the initial one. The existing RDS/IB code will not work properly in non-initial network namespaces.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThe RDS/IB (Reliable Datagram Sockets over InfiniBand) implementation in the Linux kernel does not properly function when used in non-initial network namespaces. The code will not work correctly outside the initial namespace, potentially causing improper operation or security issues.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Linux KernelOperating system
>= 4.3, < 5.10.258>= 5.11, < 5.15.209>= 5.16, < 6.1.175>= 6.2, < 6.6.141>= 6.7, < 6.12.91>= 6.13, < 6.18.33>= 6.19, < 7.0.10CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify if RDS kernel module is loadedRun 'lsmod | grep rds' to see if the RDS module is loaded, or check /proc/modules for 'rds'Affected if The RDS module is loaded and the system uses non-initial network namespaces (containers)
-
Check for InfiniBand hardware or software RDMA stackRun 'ls -la /sys/class/infiniband/' or check if 'rdma_ucm' or 'ib_uverbs' modules are loaded via lsmodAffected if InfiniBand or RDMA software stack is present and RDS/IB could be used
-
Identify active non-initial network namespacesRun 'ip netns list' to list non-initial network namespaces, or check 'ls -la /var/run/netns/'Affected if Non-initial network namespaces exist on the system
-
Detect RDS socket usage in non-initial namespacesRun 'ss -x | grep rds' or examine /proc/net/rds/* to see if RDS sockets are active; combine with 'ip netns exec <ns> ss -x' for each namespaceAffected if RDS sockets are actively used in non-initial network namespaces
-
Check container runtime network namespace usageQuery container runtime (docker ps, crictl, or ctr) for running containers and inspect their network namespaces, or check 'ls -la /var/run/docker/netns/' for DockerAffected if Containers are running with custom network namespaces and RDS/IB is accessible within them
A system is affected if the RDS kernel module is loaded and any non-initial network namespace (containers) is actively using RDS/IB sockets, since the lack of namespace isolation causes incorrect behavior in those contexts.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor data5.10.2585.15.2096.1.175
Apply the kernel patch to restrict RDS/IB to the initial network namespace only, preventing its use in non-initial namespaces where it is known to malfunction.
Fix this in Linux Kernel
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,096.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-53077 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-53077 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data