CVE-2026-68335 Linux CVE debrief

Who should care

Linux kernel developers and maintainers, Linux distribution maintainers, and users of Linux systems that use the RDS service should assess exposure and apply patches or mitigations as needed. Additionally, operators and security teams responsible for managing Linux systems and ensuring the security of RDS deployments should be aware of this vulnerability and take necessary actions to mitigate potential risks. This includes reviewing compensating controls,

Why it matters

This vulnerability allows for potential code execution or denial of service in the Linux kernel's RDS implementation. Linux kernel developers and maintainers, Linux distribution maintainers, and users of Linux systems that use the RDS service should assess exposure and apply patches or mitigations as needed.

• Potential code execution or denial of service due to use-after-free condition
• Elevation of privileges within the Linux kernel
• Disruption of RDS service on affected systems
• Potential for data tampering or unauthorized access

Technical summary

The Linux kernel's RDS implementation does not properly handle incoming messages that cross network namespace boundaries. This allows for a use-after-free condition when the connection is freed, potentially leading to code execution or denial of service. The rds_find_bound() function looks up the destination socket using a global rhashtable keyed solely on (addr, port, scope_id), without considering network namespaces. This enables a sender in one network namespace to deliver a message to a socket in a different namespace, resulting in a use-after-free condition when the connection is freed. To address this issue, it is essential to review and apply the provided patches to the Linux kernel, restrict access to

Defensive priority

High

Recommended defensive actions

• Review and apply the provided patches to the Linux kernel
• Restrict access to the RDS service to trusted network namespaces
• Monitor for potential exploitation attempts
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The vulnerability is caused by the rds_find_bound() function looking up the destination socket using a global rhashtable keyed solely on (addr, port, scope_id), without considering network namespaces. This allows a sender in one network namespace to deliver a message to a socket in a different namespace, leading to a use-after-free condition when the connection is freed.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.