CVE-2024-50304: ipv4: ip_tunnel: Fix suspicious RCU usage warning in ip_tunnel_find()
Noroxi assessment
Priority: Monitor (action score 22/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.24% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 31bd7378c6fe100a8af0e996ea0b5dafd3579df6, 6ac5dfa575136da8dd8a9e7c1437c41f3a593993, 90e0569dd3d32f4f4d2ca691d3fa5a8a14a13c12; azl3 kernel 6.6.76.1-1 on Azure Linux 3.0 6.6.76.1-1; azl3 kernel 6.6.92.2-1 on Azure Linux 3.0 6.6.76.1-1.
Low priority for now. Upgrade to Linux Linux 31bd7378c6fe100a8af0e996ea0b5dafd3579df6, 6ac5dfa575136da8dd8a9e7c1437c41f3a593993, 90e0569dd3d32f4f4d2ca691d3fa5a8a14a13c12; azl3 kernel 6.6.76.1-1 on Azure Linux 3.0 6.6.76.1-1; azl3 kernel 6.6.92.2-1 on Azure Linux 3.0 6.6.76.1-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
In the Linux kernel, the following vulnerability has been resolved: ipv4: ip_tunnel: Fix suspicious RCU usage warning in ip_tunnel_find() The per-netns IP tunnel hash table is protected by the RTNL mutex and ip_tunnel_find() is only called from the control path where the mutex is taken. Add a lockdep expression to hlist_for_each_entry_rcu() in ip_tunnel_find() in order to validate that the mutex is held and to silence the suspicious RCU usage warning [1]. [1] WARNING: suspicious RCU usage 6.12.0-rc3-custom-gd95d9a31aceb #139 Not tainted ----------------------------- net/ipv4/ip_tunnel.c:221 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/362: #0: ffffffff86fc7cb0 (rtnl_mutex){+.+.}-{3:3}, at: rtnetlink_rcv_msg+0x377/0xf60 stack backtrace: CPU: 12 UID: 0 PID: 362 Comm: ip Not tainted 6.12.0-rc3-custom-gd95d9a31aceb #139 Hardware name: Bochs Bochs, BIOS Bochs 01/01/2011 Call Trace: <TASK> dump_stack_lvl+0xba/0x110 lockdep_rcu_suspicious.cold+0x4f/0xd6 ip_tunnel_find+0x435/0x4d0 ip_tunnel_newlink+0x517/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
- Published
- Nov 19, 2024
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 15th percentile
- CWE
- —
Report tools
Action score
22
Monitor
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel3.10.12 and later · before 6.11.7
- linux linux kernel6.12
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 3.10affected
- c54419321455631079c7d6e60bc732dd0c5914c5 and later · before 31bd7378c6fe100a8af0e996ea0b5dafd3579df6affected · git
- c54419321455631079c7d6e60bc732dd0c5914c5 and later · before 6ac5dfa575136da8dd8a9e7c1437c41f3a593993affected · git
- c54419321455631079c7d6e60bc732dd0c5914c5 and later · before ce11424026cbf87d5861b09e5e33565ff7f2ec8daffected · git
- c54419321455631079c7d6e60bc732dd0c5914c5 and later · before e0500e4373cd3d5eace1f1712444ab830b82c114affected · git
- c54419321455631079c7d6e60bc732dd0c5914c5 and later · before f20fe2cfe06ca1b008b09da4f2b4e0c5547ccef6affected · git
- c54419321455631079c7d6e60bc732dd0c5914c5 and later · before 90e0569dd3d32f4f4d2ca691d3fa5a8a14a13c12affected · git
- before 3.10not affected · semver
- 5.10.234 and later · up to and including 5.10.*not affected · semver
- 5.15.178 and later · up to and including 5.15.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.128-1 | 6.1.128-1 |
| Debian:13 | linux | before 6.11.7-1 | 6.11.7-1 |
| SUSE:Linux Enterprise Module for Confidential Computing Technical Preview 15 SP6 | kernel-coco | before 6.4.0-15061.15.coco15sp6.1 | 6.4.0-15061.15.coco15sp6.1 |
| SUSE:Linux Enterprise Module for Confidential Computing Technical Preview 15 SP6 | kernel-coco_debug | before 6.4.0-15061.15.coco15sp6.1 | 6.4.0-15061.15.coco15sp6.1 |
| SUSE:Linux Enterprise Module for Confidential Computing Technical Preview 15 SP6 | kernel-source-coco | before 6.4.0-15061.15.coco15sp6.1 | 6.4.0-15061.15.coco15sp6.1 |
| SUSE:Linux Enterprise Module for Confidential Computing Technical Preview 15 SP6 | kernel-syms-coco | before 6.4.0-15061.15.coco15sp6.1 | 6.4.0-15061.15.coco15sp6.1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2024-50302Nov 19, 2024 · HID: core: zero-initialize the report bufferKEV52Plan
- ← EarlierCVE-2024-50303Nov 19, 2024 · resource,kexec: walk_system_ram_res_rev must retain resource flags22Monitor
- Later →CVE-2024-53043Nov 19, 2024 · mctp i2c: handle NULL header address22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 31bd7378c6fe100a8af0e996ea0b5dafd3579df6 | Vendor (CNA) |
| Linux Linux | 6ac5dfa575136da8dd8a9e7c1437c41f3a593993 | Vendor (CNA) |
| Linux Linux | 90e0569dd3d32f4f4d2ca691d3fa5a8a14a13c12 | Vendor (CNA) |
| Linux Linux | ce11424026cbf87d5861b09e5e33565ff7f2ec8d | Vendor (CNA) |
| Linux Linux | e0500e4373cd3d5eace1f1712444ab830b82c114 | Vendor (CNA) |
| Linux Linux | f20fe2cfe06ca1b008b09da4f2b4e0c5547ccef6 | Vendor (CNA) |
| azl3 kernel 6.6.76.1-1 on Azure Linux 3.0 | 6.6.76.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| azl3 kernel 6.6.92.2-1 on Azure Linux 3.0 | 6.6.76.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| cbl2 kernel 5.15.179.1-1 on CBL Mariner 2.0 | 5.15.179.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| cbl2 kernel 5.15.182.1-1 on CBL Mariner 2.0 | CBL-Mariner Releases | Microsoft (MSRC) |
| cbl2 kernel 5.15.182.1-1 on CBL-Mariner 2.0 | 5.15.179.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| debian:linux | 6.1.128-1 · Debian:12 | Package registry (OSV) |
| suse:kernel-coco | 6.4.0-15061.15.coco15sp6.1 · SUSE:Linux Enterprise Module for Confidential Computing Technical Preview 15 SP6 | Package registry (OSV) |
| suse:kernel-coco_debug | 6.4.0-15061.15.coco15sp6.1 · SUSE:Linux Enterprise Module for Confidential Computing Technical Preview 15 SP6 | Package registry (OSV) |
| suse:kernel-source-coco | 6.4.0-15061.15.coco15sp6.1 · SUSE:Linux Enterprise Module for Confidential Computing Technical Preview 15 SP6 | Package registry (OSV) |
| suse:kernel-syms-coco | 6.4.0-15061.15.coco15sp6.1 · SUSE:Linux Enterprise Module for Confidential Computing Technical Preview 15 SP6 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/6ac5dfa575136da8dd8a9e7c1437c41f3a593993
- git.kernel.org/stable/c/90e0569dd3d32f4f4d2ca691d3fa5a8a14a13c12
- git.kernel.org/stable/c/ce11424026cbf87d5861b09e5e33565ff7f2ec8d
- git.kernel.org/stable/c/e0500e4373cd3d5eace1f1712444ab830b82c114
- git.kernel.org/stable/c/f20fe2cfe06ca1b008b09da4f2b4e0c5547ccef6
- lists.debian.org/debian-lts-announce/2025/03/msg00001.html
- lists.debian.org/debian-lts-announce/2025/03/msg00002.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.