CVE-2026-23331
Last modified
CVE-2026-23331 is a medium-severity vulnerability rated 5.5/10 on the CVSS scale. In the Linux kernel, the following vulnerability has been resolved: udp: Unhash auto-bound connected sk from 4-tuple hash table when disconnected. Let's say we bind() an UDP socket to the wildcard address with a non-zero port, connect() it to an address, and disconnect it from the address. bind() sets SOCK_BINDPORT_LOCK on sk->sk_userlocks (but not SOCK_BINDADDR_LOCK), and connect() calls udp_lib_hash4() to put the socket into the 4-tuple hash table. Then, __udp_disconnect() calls sk->sk_prot->rehash(sk). It computes a new hash based on the wildcard address and moves the socket to a new slot in the 4-tuple hash table, leaving a garbage in the chain that no packet hits. Let's remove such a socket from 4-tuple hash table when disconnected. Note that udp_sk(sk)->udp_portaddr_hash needs to be udpated after udp_hash4_dec(hslot2) in udp_unhash4().. EPSS estimates a 0.12% chance of exploitation in the next 30 days.
Description
In the Linux kernel, the following vulnerability has been resolved: udp: Unhash auto-bound connected sk from 4-tuple hash table when disconnected. Let's say we bind() an UDP socket to the wildcard address with a non-zero port, connect() it to an address, and disconnect it from the address. bind() sets SOCK_BINDPORT_LOCK on sk->sk_userlocks (but not SOCK_BINDADDR_LOCK), and connect() calls udp_lib_hash4() to put the socket into the 4-tuple hash table. Then, __udp_disconnect() calls sk->sk_prot->rehash(sk). It computes a new hash based on the wildcard address and moves the socket to a new slot in the 4-tuple hash table, leaving a garbage in the chain that no packet hits. Let's remove such a socket from 4-tuple hash table when disconnected. Note that udp_sk(sk)->udp_portaddr_hash needs to be udpated after udp_hash4_dec(hslot2) in udp_unhash4().
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Linux | Linux Kernel | >= 6.13.1, < 6.18.17 | — |
| Linux | Linux Kernel | >= 6.19, < 6.19.7 | — |
| Linux | Linux Kernel | 6.13 | — |
| Linux | Linux Kernel | 7.0 | Rc1 |
References
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2026-23331?
How severe is CVE-2026-23331?
How do I fix CVE-2026-23331?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-23326In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-23327In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2026-23328In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-23329In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-2333Improper Neutralization of Special Elements used in a Comman…9.8
- CVE-2026-23330In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-23332In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-23333Rejected reason: This CVE ID has been rejected or withdrawn …
- CVE-2026-23334In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-23335In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-23336In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-23337In the Linux kernel, the following vulnerability has been re…5.5
Are you affected by CVE-2026-23331?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
