CVE-2026-98812
Last modified
CVE-2026-98812 is a vulnerability of currently unknown severity. In the Linux kernel, the following vulnerability has been resolved: net/mctp: publish the mctp_dev only after it is initialised mctp_add_dev() links the new mctp_dev into dev->mctp_ptr before mdev->dev is assigned, so a reader that picks the device up in that window dereferences a net_device pointer that is still NULL: KASAN: null-ptr-deref in range [0x00000000000000b0-0x00000000000000b7] Call Trace: <TASK> ? __pfx_mctp_sendmsg (./include/linux/sockptr.h:49) ? __pfx_mctp_dst_output (net/mctp/route.c:41) ? selinux_socket_sendmsg (security/selinux/hooks.c:5278) ____sys_sendmsg (net/socket.c:775 (discriminator 1) net/socket.c:790 (discriminator 1) net/socket.c:2684 (discriminator 1)) ? __pfx_____sys_sendmsg (net/socket.c:1131) ? __pfx_copy_msghdr_from_user (net/socket.c:2590) ? update_cfs_rq_load_avg (kernel/sched/fair.c:5478) ___sys_sendmsg (net/socket.c:2738) ? __pfx____sys_sendmsg (net/socket.c:2625) ? perf_event_task_tick (./include/linux/rcupdate.h:838) ? sched_tick (kernel/sched/core.c:5818) ? clockevents_program_event (kernel/time/clockevents.c:372) ? fdget (./include/linux/rcupdate.h:873 fs/file.c:1100) __sys_sendmsg (net/socket.c:2770) ? __pfx___sys_sendmsg (net/socket.c:2751) do_syscall_64 (arch/x86/entry/syscall_64.c:63) entry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:121) </TASK> Fix by publishing only once the object is fully initialised: __mctp_dev_get() runs under rcu_read_lock() only and hands this object to readers as soon as mctp_ptr is assigned, so they must never observe mdev->dev == NULL.. EPSS estimates a 0.18% chance of exploitation in the next 30 days.
Description
In the Linux kernel, the following vulnerability has been resolved: net/mctp: publish the mctp_dev only after it is initialised mctp_add_dev() links the new mctp_dev into dev->mctp_ptr before mdev->dev is assigned, so a reader that picks the device up in that window dereferences a net_device pointer that is still NULL: KASAN: null-ptr-deref in range [0x00000000000000b0-0x00000000000000b7] Call Trace: <TASK> ? __pfx_mctp_sendmsg (./include/linux/sockptr.h:49) ? __pfx_mctp_dst_output (net/mctp/route.c:41) ? selinux_socket_sendmsg (security/selinux/hooks.c:5278) ____sys_sendmsg (net/socket.c:775 (discriminator 1) net/socket.c:790 (discriminator 1) net/socket.c:2684 (discriminator 1)) ? __pfx_____sys_sendmsg (net/socket.c:1131) ? __pfx_copy_msghdr_from_user (net/socket.c:2590) ? update_cfs_rq_load_avg (kernel/sched/fair.c:5478) ___sys_sendmsg (net/socket.c:2738) ? __pfx____sys_sendmsg (net/socket.c:2625) ? perf_event_task_tick (./include/linux/rcupdate.h:838) ? sched_tick (kernel/sched/core.c:5818) ? clockevents_program_event (kernel/time/clockevents.c:372) ? fdget (./include/linux/rcupdate.h:873 fs/file.c:1100) __sys_sendmsg (net/socket.c:2770) ? __pfx___sys_sendmsg (net/socket.c:2751) do_syscall_64 (arch/x86/entry/syscall_64.c:63) entry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:121) </TASK> Fix by publishing only once the object is fully initialised: __mctp_dev_get() runs under rcu_read_lock() only and hands this object to readers as soon as mctp_ptr is assigned, so they must never observe mdev->dev == NULL.
Metrics
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= 583be982d93479ea3d85091b0fd0b01201ede87d, < 58a270b5ecd8629114a4754d642bad6a33bef493; >= 583be982d93479ea3d85091b0fd0b01201ede87d, < fdf09d0fa2fb639950bede185d22689f68df140e; >= 583be982d93479ea3d85091b0fd0b01201ede87d, < 288ef37e0c463192dbb6436e61cdc07ce666dcb9; >= 583be982d93479ea3d85091b0fd0b01201ede87d, < af6e4f931afc2d670d133aa2bedc8b6e3753c618; >= 583be982d93479ea3d85091b0fd0b01201ede87d, < 63120572edde85bb2b70b0ed4d4817ed52247613; >= 583be982d93479ea3d85091b0fd0b01201ede87d, < f37f42e6e039a48c2dcf6c079b9f7fbc864ab7ef; >= 583be982d93479ea3d85091b0fd0b01201ede87d, < aadf655e8ea9a8ffa24bb8d69f504572e8d18181 |
| Linux | Linux | 5.15 |
References
Timeline
- Published
- Last Modified
- Status
- Received
Frequently Asked Questions
What is CVE-2026-98812?
How severe is CVE-2026-98812?
How do I fix CVE-2026-98812?
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-98807In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98808In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98809In the Linux kernel, the following vulnerability has been re…
- CVE-2026-9881Use after free in Bluetooth in Google Chrome on Mac prior to…9
- CVE-2026-98810In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98811In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98813In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98814In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98815In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98816In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98817In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98818In the Linux kernel, the following vulnerability has been re…
Are you affected by CVE-2026-98812?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
