NVD / CVE Program· CNA Linux

CVE-2025-38324: mpls: Use rcu_dereference_rtnl() in mpls_route_input_rcu().

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.21% (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 2919297b18e5a5fb7e643f9e32c12c0b17cce1be, 36af82f25fbdcd719eb947c15ea874bf80bcf229, 49b8a9d7d44401a186e20b1aaf591d2e62727aeb; azl3 kernel 6.6.92.2-2 on Azure Linux 3.0 6.6.96.1-1; azl3 kernel 6.6.96.1-1 on Azure Linux 3.0 6.6.96.1-1.

Low priority for now. Upgrade to Linux Linux 2919297b18e5a5fb7e643f9e32c12c0b17cce1be, 36af82f25fbdcd719eb947c15ea874bf80bcf229, 49b8a9d7d44401a186e20b1aaf591d2e62727aeb; azl3 kernel 6.6.92.2-2 on Azure Linux 3.0 6.6.96.1-1; azl3 kernel 6.6.96.1-1 on Azure Linux 3.0 6.6.96.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: mpls: Use rcu_dereference_rtnl() in mpls_route_input_rcu(). As syzbot reported [0], mpls_route_input_rcu() can be called from mpls_getroute(), where is under RTNL. net->mpls.platform_label is only updated under RTNL. Let's use rcu_dereference_rtnl() in mpls_route_input_rcu() to silence the splat. [0]: WARNING: suspicious RCU usage 6.15.0-rc7-syzkaller-00082-g5cdb2c77c4c3 #0 Not tainted ---------------------------- net/mpls/af_mpls.c:84 suspicious rcu_dereference_check() usage! other info that might help us debug this: rcu_scheduler_active = 2, debug_locks = 1 1 lock held by syz.2.4451/17730: #0: ffffffff9012a3e8 (rtnl_mutex){+.+.}-{4:4}, at: rtnl_lock net/core/rtnetlink.c:80 [inline] #0: ffffffff9012a3e8 (rtnl_mutex){+.+.}-{4:4}, at: rtnetlink_rcv_msg+0x371/0xe90 net/core/rtnetlink.c:6961 stack backtrace: CPU: 1 UID: 0 PID: 17730 Comm: syz.2.4451 Not tainted 6.15.0-rc7-syzkaller-00082-g5cdb2c77c4c3 #0 PREEMPT(full) Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025 Call Trace: <TASK> __dump_stack lib/dump_stack.c:94 [inline] dump_stack_lvl+0x16c/0x1f0 lib/dump_stack.c:120 lockdep_rcu_suspicious+0x166/0x260 kernel/locking/lockdep.c:6865 mpls_route_input_rcu+0x1d4/0x200 net/mpls/af_mpls.c:84 mpls_getroute+0x621/0x1ea0 net/mpls/af_mpls.c:2381 rtnetlink_rcv_msg+0x3c9/0xe90 net/core/rtnetlink.c:6964 netlink_rcv_skb+0x16d/0x440 net/netlink/af_netlink.c:2534 netlink_unicast_kernel net/netlink/af_netlink.c:1313 [inline] netlink_unicast+0x53a/0x7f0 net/netlink/af_netlink.c:1339 netlink_sendmsg+0x8d1/0xdd0 net/netlink/af_netlink.c:1883 sock_sendmsg_nosec net/socket.c:712 [inline] __sock_sendmsg net/socket.c:727 [inline] ____sys_sendmsg+0xa98/0xc70 net/socket.c:2566 ___sys_sendmsg+0x134/0x1d0 net/socket.c:2620 __sys_sendmmsg+0x200/0x420 net/socket.c:2709 __do_sys_sendmmsg net/socket.c:2736 [inline] __se_sys_sendmmsg net/socket.c:2733 [inline] __x64_sys_sendmmsg+0x9c/0x100 net/socket.c:2733 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xcd/0x230 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7f0a2818e969 Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 a8 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007f0a28f52038 EFLAGS: 00000246 ORIG_RAX: 0000000000000133 RAX: ffffffffffffffda RBX: 00007f0a283b5fa0 RCX: 00007f0a2818e969 RDX: 0000000000000003 RSI: 0000200000000080 RDI: 0000000000000003 RBP: 00007f0a28210ab1 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 0000000000000000 R14: 00007f0a283b5fa0 R15: 00007ffce5e9f268 </TASK>

MediumCVSS 5.5 · v3.1—No exploit Fix available

Denial of service

BDU:2025-10737

Published: Jul 10, 2025
Updated: Nov 5, 2026
EPSS: 0.2% · 12th percentile
CWE: —

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 22 / 40 · 5.5 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.2%

CISA SSVC decision

Exploitation: none
Automatable: no
Technical impact: partial

Vulnrichment: CISA's decision-tree inputs.

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

Is your version affected? Check it

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 help

Affected 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
debian	debian linux	cpe:2.3:o:debian:debian_linux

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

debian debian linux11.0
linux linux kernel5.5 and later · before 5.10.239
linux linux kernel5.11 and later · before 5.15.186
linux linux kernel5.16 and later · before 6.1.142
linux linux kernel4.1 and later · before 5.4.295
linux linux kernel6.7 and later · before 6.12.35
linux linux kernel6.13 and later · before 6.15.4
linux linux kernel6.2 and later · before 6.6.95
linux linux kernel6.16

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
- 4.1affected
- 0189197f441602acdca3f97750d392a895b778fd and later · before 2919297b18e5a5fb7e643f9e32c12c0b17cce1beaffected · git
- 0189197f441602acdca3f97750d392a895b778fd and later · before 36af82f25fbdcd719eb947c15ea874bf80bcf229affected · git
- 0189197f441602acdca3f97750d392a895b778fd and later · before d8cd847fb8626872631cc22d44be5127b4ebfb74affected · git
- 0189197f441602acdca3f97750d392a895b778fd and later · before 49b8a9d7d44401a186e20b1aaf591d2e62727aebaffected · git
- 0189197f441602acdca3f97750d392a895b778fd and later · before a060781640012d5d5105072f4c44ed6ad6830ef9affected · git
- 0189197f441602acdca3f97750d392a895b778fd and later · before 517bc6836ee9fcffe2539f6f6aa3fdd9c7a7ae73affected · git
- 0189197f441602acdca3f97750d392a895b778fd and later · before f19cbd84e645e39bc3228e1191bb151ef0ffac8caffected · git
- 0189197f441602acdca3f97750d392a895b778fd and later · before 6dbb0d97c5096072c78a6abffe393584e57ae945affected · git
- before 4.1not 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.147-1	6.1.147-1
Debian:13	linux	before 6.12.35-1	6.12.35-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
90Now
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 KEV
89Now
CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
85Now

Published before and after this one in the same product

← EarlierCVE-2025-38322Jul 10, 2025 · perf/x86/intel: Fix crash in icl_update_topdown_event()
22Monitor
← EarlierCVE-2025-38323Jul 10, 2025 · net: atm: add lec_mutex
31Monitor
Later →CVE-2025-38334Jul 10, 2025 · x86/sgx: Prevent attempts to reclaim poisoned pages
22Monitor

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	2919297b18e5a5fb7e643f9e32c12c0b17cce1be	Vendor (CNA)
Linux Linux	36af82f25fbdcd719eb947c15ea874bf80bcf229	Vendor (CNA)
Linux Linux	49b8a9d7d44401a186e20b1aaf591d2e62727aeb	Vendor (CNA)
Linux Linux	517bc6836ee9fcffe2539f6f6aa3fdd9c7a7ae73	Vendor (CNA)
Linux Linux	6dbb0d97c5096072c78a6abffe393584e57ae945	Vendor (CNA)
Linux Linux	a060781640012d5d5105072f4c44ed6ad6830ef9	Vendor (CNA)
Linux Linux	d8cd847fb8626872631cc22d44be5127b4ebfb74	Vendor (CNA)
Linux Linux	f19cbd84e645e39bc3228e1191bb151ef0ffac8c	Vendor (CNA)
azl3 kernel 6.6.92.2-2 on Azure Linux 3.0	6.6.96.1-1 · CBL-Mariner Releases	Microsoft (MSRC)
azl3 kernel 6.6.96.1-1 on Azure Linux 3.0	6.6.96.1-1 · CBL-Mariner Releases	Microsoft (MSRC)
debian:linux	6.1.147-1 · Debian:12	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 researchers

Finders, 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

SSVC exploitation— → noneNov 5, 2026, 10:07 PM UTC
Fix✗ → ✓Sep 28, 2026, 10:08 PM UTC

For records you follow, these changes also arrive as notifications. →

References

git.kernel.org/stable/c/2919297b18e5a5fb7e643f9e32c12c0b17cce1be

Show all references (9 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records