UDP service disruption via wildcard bind conflict
Published Apr 22, 2026 · Updated Apr 22, 2026
Improper UDP bind handling in affected Linux Kernel releases allows local users to create conflicting wildcard socket bindings. The UDP bind path switches to hash2 after more than ten same-port sockets, then checks address-and-port keys without preserving the port-wide wildcard conflict test. A low-privilege local process can trigger the threshold and make an IPv4, IPv6, or IPv4-mapped wildcard bind succeed despite existing specific-address bindings, disrupting UDP service availability.
Summary
What happened
Improper UDP bind handling in affected Linux Kernel releases allows local users to create conflicting wildcard socket bindings. The UDP bind path switches to hash2 after more than ten same-port sockets, then checks address-and-port keys without preserving the port-wide wildcard conflict test. A low-privilege local process can trigger the threshold and make an IPv4, IPv6, or IPv4-mapped wildcard bind succeed despite existing specific-address bindings, disrupting UDP service availability.
The record
- CVE
- CVE-2026-31503
- Published
- Apr 22, 2026
- Updated
- Apr 22, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 22, 2026CVE publishedPublication date reported by the CVE source.
- Apr 22, 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=2.6.33
- Affected versionversion=30fff9231fad757c061285e347b33c5149c2c2e4 <0a360f7f73a06ac88f18917055fbcc79694252d7
- Affected versionversion=30fff9231fad757c061285e347b33c5149c2c2e4 <18d84c45def3671d5c89fbdd5d4ab8a3217fe4b4
- Affected versionversion=30fff9231fad757c061285e347b33c5149c2c2e4 <2297e38114316b26ae02f2d205c49b5511c5ed55
- Affected versionversion=30fff9231fad757c061285e347b33c5149c2c2e4 <d6ace0dbcbb7fd285738bb87b42b71b01858c952
- Affected versionversion=30fff9231fad757c061285e347b33c5149c2c2e4 <e537dd15d0d4ad989d56a1021290f0c674dd8b28
- Affected versionversion=30fff9231fad757c061285e347b33c5149c2c2e4 <f1bed05a832ae79be5f7a105da56810eaa59a5f1
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.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
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