Kernel warning via unrecognized RTNL protection
Published Nov 19, 2024 · Updated May 11, 2026
Locking validation in Linux 3.10 and later allows local users to trigger a kernel warning through IP tunnel control operations. In ip_tunnel_find(), hlist_for_each_entry_rcu() traverses the per-network-namespace tunnel table under the RTNL mutex without an expression informing lockdep that the mutex protects the traversal. Published evidence demonstrates a false-positive suspicious-RCU warning, not a resulting crash, data exposure, or privilege change.
Summary
What happened
Locking validation in Linux 3.10 and later allows local users to trigger a kernel warning through IP tunnel control operations. In ip_tunnel_find(), hlist_for_each_entry_rcu() traverses the per-network-namespace tunnel table under the RTNL mutex without an expression informing lockdep that the mutex protects the traversal. Published evidence demonstrates a false-positive suspicious-RCU warning, not a resulting crash, data exposure, or privilege change.
The record
- CVE
- CVE-2024-50304
- Published
- Nov 19, 2024
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Nov 19, 2024CVE publishedPublication date reported by the CVE source.
- May 11, 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=3.10
- Affected versionversion=c54419321455631079c7d6e60bc732dd0c5914c5 <31bd7378c6fe100a8af0e996ea0b5dafd3579df6
- Affected versionversion=c54419321455631079c7d6e60bc732dd0c5914c5 <6ac5dfa575136da8dd8a9e7c1437c41f3a593993
- Affected versionversion=c54419321455631079c7d6e60bc732dd0c5914c5 <90e0569dd3d32f4f4d2ca691d3fa5a8a14a13c12
- Affected versionversion=c54419321455631079c7d6e60bc732dd0c5914c5 <ce11424026cbf87d5861b09e5e33565ff7f2ec8d
- Affected versionversion=c54419321455631079c7d6e60bc732dd0c5914c5 <e0500e4373cd3d5eace1f1712444ab830b82c114
- Affected versionversion=c54419321455631079c7d6e60bc732dd0c5914c5 <f20fe2cfe06ca1b008b09da4f2b4e0c5547ccef6
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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.
Weakness, pattern, technique
No sourced classifications are available.
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