CVE-2024-53042: ipv4: ip_tunnel: Fix suspicious RCU usage warning in ip_tunnel_init_flow()
In the Linux kernel, the following vulnerability has been resolved:
ipv4: ip_tunnel: Fix suspicious RCU usage warning in ip_tunnel_init_flow()
There are code paths from which the function is called without holding
the RCU read lock, resulting in a suspicious RCU usage warning [1].
Fix by using l3mdev_master_upper_ifindex_by_index() which will acquire
the RCU read lock before calling
l3mdev_master_upper_ifindex_by_index_rcu().
[1]
WARNING: suspicious RCU usage
6.12.0-rc3-custom-gac8f72681cf2 #141 Not tainted
-----------------------------
net/core/dev.c:876 RCU-list traversed in non-reader section!!
other info that might help us debug this:
rcu_scheduler_active = 2, debug_locks = 1
1 lock held by ip/361:
#0: ffffffff86fc7cb0 (rtnl_mutex){+.+.}-{3:3}, at: rtnetlink_rcv_msg+0x377/0xf60
stack backtrace:
CPU: 3 UID: 0 PID: 361 Comm: ip Not tainted 6.12.0-rc3-custom-gac8f72681cf2 #141
Hardware name: Bochs Bochs, BIOS Bochs 01/01/2011
Call Trace:
<TASK>
dump_stack_lvl+0xba/0x110
lockdep_rcu_suspicious.cold+0x4f/0xd6
dev_get_by_index_rcu+0x1d3/0x210
l3mdev_master_upper_ifindex_by_index_rcu+0x2b/0xf0
ip_tunnel_bind_dev+0x72f/0xa00
ip_tunnel_newlink+0x368/0x7a0
ipgre_newlink+0x14c/0x170
__rtnl_newlink+0x1173/0x19c0
rtnl_newlink+0x6c/0xa0
rtnetlink_rcv_msg+0x3cc/0xf60
netlink_rcv_skb+0x171/0x450
netlink_unicast+0x539/0x7f0
netlink_sendmsg+0x8c1/0xd80
____sys_sendmsg+0x8f9/0xc20
___sys_sendmsg+0x197/0x1e0
__sys_sendmsg+0x122/0x1f0
do_syscall_64+0xbb/0x1d0
entry_SYSCALL_64_after_hwframe+0x77/0x7f
Security readout for executives and security teams
Plain-English summary
CVE-2024-53042 is a Linux kernel networking flaw in IPv4 tunnel handling. The public record describes a kernel RCU locking misuse that can be triggered through local networking operations and is scored for high availability impact, not data theft or tampering.
Executive priority
Treat this as a routine but time-bound kernel patching item. It is not supported by evidence of active exploitation, but availability impact and local multi-user or containerized environments make delayed remediation risky.
Technical view
The issue is in ipv4 ip_tunnel handling, where some call paths reached l3mdev_master_upper_ifindex_by_index_rcu() without holding the RCU read lock. The fix changes the helper to l3mdev_master_upper_ifindex_by_index(), which acquires the needed RCU read lock before traversal.
Likely exposure
Exposure is most likely on Linux systems running affected kernel versions with IPv4 tunnel functionality available. Systems where untrusted local users or containers can perform network configuration actions deserve closer review. The bundle names Linux kernel versions and downstream Debian and Siemens advisories.
Exploitation context
The CVSS vector is local, low-complexity, low-privilege, no user interaction, with availability impact only. KEV is false, and the provided sources do not show active exploitation, public exploit code, or remote exploitability.
Researcher notes
The source evidence supports an RCU misuse fix in the Linux IPv4 tunnel path. The record provides stack trace context and stable kernel commits, but not a complete exploit narrative. Avoid assuming remote exposure or specific appliance impact unless a vendor advisory confirms it.
Mitigation direction
Update affected Linux kernels using vendor-supported packages or stable kernel fixes.
Prioritize hosts allowing local users, containers, or tenants to influence network tunnel configuration.
Review Debian LTS and Siemens advisories if those distributions or products are in use.
Track vendor guidance for exact fixed package versions before making production changes.
Validation and detection
Inventory Linux kernel versions across servers, appliances, containers, and embedded products.
Check whether IPv4 tunnel, GRE, or related network tunnel features are enabled or exposed.
Confirm vendor advisories map your installed kernel package to a fixed release.
Review kernel logs for suspicious RCU usage warnings in ip_tunnel or rtnetlink paths.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2024-53042 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.