CVE-2026-43101: ipv6: ioam: fix potential NULL dereferences in __ioam6_fill_trace_data()

Published May 6, 2026
·
Updated

In the Linux kernel, the following vulnerability has been resolved:

ipv6: ioam: fix potential NULL dereferences in ioam6filltracedata()

We need to check in6devget() for possible NULL value, as suggested by Yiming Qian.

Also add skbdstdevrcu() instead of skbdstdev(), and two missing READONCE().

Note that @dev can't be NULL.

Affected Software

10 affected components
Linux Linux kernel
Linux Linux kernel>=5.15<6.18.24
Linux Linux kernel>=6.19<6.19.14
Linux Linux kernel=7.0-rc1
Linux Linux kernel=7.0-rc2
Linux Linux kernel=7.0-rc3
Linux Linux kernel=7.0-rc4
Linux Linux kernel=7.0-rc5
Linux Linux kernel=7.0-rc6
Linux Linux kernel=7.0-rc7

Event History

May 6, 2026
CVE Published
via MITRE·07:40 AM
Data Sourced
via MITRE·07:40 AM
DescriptionSeverity
Data Sourced
via NVD·10:16 AM
RemedyDescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2026-43101?

CVE-2026-43101 has a medium severity level due to the potential for NULL dereferences affecting system stability.

2

How do I fix CVE-2026-43101?

To fix CVE-2026-43101, ensure you update to the latest version of the Linux kernel where the vulnerability has been patched.

3

What kind of systems are affected by CVE-2026-43101?

CVE-2026-43101 affects systems running the Linux kernel that utilize IPv6 and IOAM features.

4

What is the nature of the vulnerability in CVE-2026-43101?

CVE-2026-43101 involves potential NULL dereferences in the __ioam6_fill_trace_data() function.

5

Is there any workaround for CVE-2026-43101 before applying a patch?

Currently, there are no specific workarounds for CVE-2026-43101, and updating the kernel is the recommended solution.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203