CVE-2025-38184: tipc: fix null-ptr-deref when acquiring remote ip of ethernet bearer
In the Linux kernel, the following vulnerability has been resolved:
tipc: fix null-ptr-deref when acquiring remote ip of ethernet bearer
The reproduction steps: 1. create a tun interface 2. enable l2 bearer 3. TIPCNLUDPGETREMOTEIP with media name set to tun
tipc: Started in network mode tipc: Node identity 8af312d38a21, cluster identity 4711 tipc: Enabled bearer <eth:syztun>, priority 1 Oops: general protection fault KASAN: null-ptr-deref in range CPU: 1 UID: 1000 PID: 559 Comm: poc Not tainted 6.16.0-rc1+ #117 PREEMPT Hardware name: QEMU Ubuntu 24.04 PC RIP: 0010:tipcudpnldumpremoteip+0x4a4/0x8f0
the ub was in fact a struct dev.
when bid != 0 && skipcnt != 0, bearerlist[bid] may be NULL or other media when other thread changes it.
fix this by checking mediaid.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 6.1.176-1Fixed in 6.1.190-1Fixed in 6.12.107-1Fixed in 6.12.113-1Fixed in 7.2.12-1Fixed in 7.2.13-1
Event History
Frequently Asked Questions
What is the severity of CVE-2025-38184?
CVE-2025-38184 has been classified as a moderate severity vulnerability due to the potential for null pointer dereference leading to application crashes.
How do I fix CVE-2025-38184?
To fix CVE-2025-38184, users must upgrade to a patched version of the Linux kernel that addresses the null pointer dereference issue.
Which versions of the Linux kernel are affected by CVE-2025-38184?
CVE-2025-38184 affects Linux kernel versions starting from 6.16.0-rc1 and potentially earlier versions.
What impact does CVE-2025-38184 have on systems?
CVE-2025-38184 can cause system instability by leading to application crashes when a null pointer dereference occurs.
Is there a workaround for CVE-2025-38184?
There is no official workaround for CVE-2025-38184; upgrading to a secure version of the Linux kernel is advised for mitigation.