Skip to main content
VulnerabilityPublished Updated

CVE-2026-31503: Linux kernel · udp: Fix wildcard bind conflict check when using hash2

Affects Linux kernelSource CVE Database V5

0
Compare

Not known to be exploited · fixed in f1bed05a832ae79be5f7a105da56810eaa59a5f1 : update Linux kernel when convenient.

Data as of 5 Nov 2026, 22:18 UTC

Severity
Medium

Rated Medium by Threat Radar's AI analysis · No CVSS score from NVD or the CNA

Thin evidence

One scorer or none
CISA SSVC
Exploitation
No evidence of active exploitation and no public proof of concept
Automatable
Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact
Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-11-05.

Patch
Available – fixed in f1bed05a832ae79be5f7a105da56810eaa59a5f1, e537dd15d0d4ad989d56a1021290f0c674dd8b28, d6ace0dbcbb7fd285738bb87b42b71b01858c952 +3

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 22 Apr 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 5 Nov 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 30fff9231fad757c061285e347b33c5149c2c2e4, < f1bed05a832ae79be5f7a105da56810eaa59a5f1
Fixed in
  • f1bed05a832ae79be5f7a105da56810eaa59a5f1
LinuxLinuxAffected
  • ≥ 30fff9231fad757c061285e347b33c5149c2c2e4, < e537dd15d0d4ad989d56a1021290f0c674dd8b28
Fixed in
  • e537dd15d0d4ad989d56a1021290f0c674dd8b28
LinuxLinuxAffected
  • ≥ 30fff9231fad757c061285e347b33c5149c2c2e4, < d6ace0dbcbb7fd285738bb87b42b71b01858c952
Fixed in
  • d6ace0dbcbb7fd285738bb87b42b71b01858c952
LinuxLinuxAffected
  • ≥ 30fff9231fad757c061285e347b33c5149c2c2e4, < 2297e38114316b26ae02f2d205c49b5511c5ed55
Fixed in
  • 2297e38114316b26ae02f2d205c49b5511c5ed55
LinuxLinuxAffected
  • ≥ 30fff9231fad757c061285e347b33c5149c2c2e4, < 18d84c45def3671d5c89fbdd5d4ab8a3217fe4b4
Fixed in
  • 18d84c45def3671d5c89fbdd5d4ab8a3217fe4b4
LinuxLinuxAffected
  • ≥ 30fff9231fad757c061285e347b33c5149c2c2e4, < 0a360f7f73a06ac88f18917055fbcc79694252d7
Fixed in
  • 0a360f7f73a06ac88f18917055fbcc79694252d7

AI-suggested

A fix is available and has been applied in the Linux kernel source code as indicated by the fixed commit hashes. Users should update their Linux kernel to a version that includes these fixes to resolve the issue. No additional mitigation steps are indicated or required beyond applying the official patch.

Description

A vulnerability in the Linux kernel's UDP socket binding logic allows a wildcard bind conflict check to be bypassed when using the secondary hash table (hash2) for collision detection. This occurs when more than 10 sockets are bound to different local addresses but the same port, causing the kernel to switch to hash2, which can miss conflicts with wildcard addresses. This affects both IPv6 and IPv4 wildcard addresses, potentially allowing multiple sockets to bind to the same port unexpectedly.

References

Community reviews

Loading reviews…