Local kernel crash via TIPC bearer type confusion
Published Apr 2, 2024 · Updated Aug 5, 2026
Type confusion in TIPC in affected Linux kernels allows local users to crash the kernel through a crafted generic-netlink message. tipc_nl_bearer_add passes UDP options to tipc_udp_nl_bearer_add for a non-UDP bearer, causing tipc_udp_is_known_peer to interpret media_ptr as the wrong object type. A low-privileged local user can reach the path through a network namespace; successful triggering causes a kernel protection fault and system interruption.
Summary
What happened
Type confusion in TIPC in affected Linux kernels allows local users to crash the kernel through a crafted generic-netlink message. tipc_nl_bearer_add passes UDP options to tipc_udp_nl_bearer_add for a non-UDP bearer, causing tipc_udp_is_known_peer to interpret media_ptr as the wrong object type. A low-privileged local user can reach the path through a network namespace; successful triggering causes a kernel protection fault and system interruption.
The record
- CVE
- CVE-2024-26663
- Published
- Apr 2, 2024
- Updated
- Aug 5, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-476, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 2, 2024CVE publishedPublication date reported by the CVE source.
- Aug 5, 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=4.9
- Affected versionversion=ef20cd4dd1633987bcf46ac34ace2c8af212361f <0cd331dfd6023640c9669d0592bc0fd491205f87
- Affected versionversion=ef20cd4dd1633987bcf46ac34ace2c8af212361f <19d7314f2fb9515bdaac9829d4d8eb34edd1fe95
- Affected versionversion=ef20cd4dd1633987bcf46ac34ace2c8af212361f <24ec8f0da93b8a9fba11600be8a90f0d73fb46f1
- Affected versionversion=ef20cd4dd1633987bcf46ac34ace2c8af212361f <3871aa01e1a779d866fa9dfdd5a836f342f4eb87
- Affected versionversion=ef20cd4dd1633987bcf46ac34ace2c8af212361f <3d3a5b31b43515b5752ff282702ca546ec3e48b6
- Affected versionversion=ef20cd4dd1633987bcf46ac34ace2c8af212361f <6f70f0b412458c622a12d4292782c8e92e210c2f
- Affected versionversion=ef20cd4dd1633987bcf46ac34ace2c8af212361f <888e3524be87f3df9fa3c083484e4b62b3e3bb59
- Affected versionversion=ef20cd4dd1633987bcf46ac34ace2c8af212361f <c1701ea85ef0ec7be6a1b36c7da69f572ed2fd12
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.
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