LiveActive security incident?Get immediate response
CVE Record

CVE-2025-21801: net: ravb: Fix missing rtnl lock in suspend/resume path

In the Linux kernel, the following vulnerability has been resolved: net: ravb: Fix missing rtnl lock in suspend/resume path Fix the suspend/resume path by ensuring the rtnl lock is held where required. Calls to ravb_open, ravb_close and wol operations must be performed under the rtnl lock to prevent conflicts with ongoing ndo operations. Without this fix, the following warning is triggered: [ 39.032969] ============================= [ 39.032983] WARNING: suspicious RCU usage [ 39.033019] ----------------------------- [ 39.033033] drivers/net/phy/phy_device.c:2004 suspicious rcu_dereference_protected() usage! ... [ 39.033597] stack backtrace: [ 39.033613] CPU: 0 UID: 0 PID: 174 Comm: python3 Not tainted 6.13.0-rc7-next-20250116-arm64-renesas-00002-g35245dfdc62c #7 [ 39.033623] Hardware name: Renesas SMARC EVK version 2 based on r9a08g045s33 (DT) [ 39.033628] Call trace: [ 39.033633] show_stack+0x14/0x1c (C) [ 39.033652] dump_stack_lvl+0xb4/0xc4 [ 39.033664] dump_stack+0x14/0x1c [ 39.033671] lockdep_rcu_suspicious+0x16c/0x22c [ 39.033682] phy_detach+0x160/0x190 [ 39.033694] phy_disconnect+0x40/0x54 [ 39.033703] ravb_close+0x6c/0x1cc [ 39.033714] ravb_suspend+0x48/0x120 [ 39.033721] dpm_run_callback+0x4c/0x14c [ 39.033731] device_suspend+0x11c/0x4dc [ 39.033740] dpm_suspend+0xdc/0x214 [ 39.033748] dpm_suspend_start+0x48/0x60 [ 39.033758] suspend_devices_and_enter+0x124/0x574 [ 39.033769] pm_suspend+0x1ac/0x274 [ 39.033778] state_store+0x88/0x124 [ 39.033788] kobj_attr_store+0x14/0x24 [ 39.033798] sysfs_kf_write+0x48/0x6c [ 39.033808] kernfs_fop_write_iter+0x118/0x1a8 [ 39.033817] vfs_write+0x27c/0x378 [ 39.033825] ksys_write+0x64/0xf4 [ 39.033833] __arm64_sys_write+0x18/0x20 [ 39.033841] invoke_syscall+0x44/0x104 [ 39.033852] el0_svc_common.constprop.0+0xb4/0xd4 [ 39.033862] do_el0_svc+0x18/0x20 [ 39.033870] el0_svc+0x3c/0xf0 [ 39.033880] el0t_64_sync_handler+0xc0/0xc4 [ 39.033888] el0t_64_sync+0x154/0x158 [ 39.041274] ravb 11c30000.ethernet eth0: Link is Down

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel driver locking bug in the Renesas ravb Ethernet driver. During suspend or resume, network operations could run without the required RTNL lock, creating unsafe concurrency. The source shows a kernel warning, but does not prove data theft, remote compromise, or active exploitation.

Executive priority

Treat as targeted kernel maintenance for affected embedded or appliance fleets, not a broad internet emergency based on current evidence. Patch through normal kernel/vendor update channels, with priority for devices relying on suspend/resume reliability.

Technical view

The ravb suspend/resume path called ravb_open, ravb_close, and wake-on-LAN operations without holding rtnl_lock. This could conflict with ongoing ndo operations and trigger suspicious RCU usage around PHY detach/disconnect. Kernel stable commits are referenced as the fix source.

Likely exposure

Likely limited to Linux systems using the ravb Ethernet driver, commonly Renesas-based platforms, on affected kernel builds. Risk is most relevant where suspend/resume or wake-on-LAN paths are used. The bundle does not identify affected distributions or packaged kernel versions.

Exploitation context

The source bundle does not report exploitation in the wild, public weaponization, or KEV listing. Evidence shows a lockdep/RCU warning triggered during suspend on Renesas hardware. Practical security impact beyond unsafe kernel concurrency is not fully described.

Researcher notes

The CVE record provides commit references and a warning trace, but no CVSS, CWE, exploitability analysis, or complete downstream package mapping. Further assessment should focus on affected kernel branch backports and whether the race has crash, privilege, or reliability impact.

Mitigation direction

  • Update to a vendor kernel that includes the referenced stable fixes.
  • Check Linux distribution or device vendor advisories for packaged kernel status.
  • Prioritize Renesas-based devices that use suspend, resume, or wake-on-LAN.
  • Avoid inventing local workarounds; follow vendor guidance if patching is delayed.

Validation and detection

  • Inventory systems using the ravb Ethernet driver or Renesas Ethernet hardware.
  • Confirm running kernel builds include one of the referenced stable commits.
  • Review suspend/resume testing logs for RCU or ravb driver warnings.
  • Check vendor advisories for exact fixed package versions.
Prepared
Confidence
medium
Sources
5

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-2025-21801 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

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.

0CVSS vectors
3Timeline events
0ADP providers
4Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux0184165b2f42c4b032da9dd11546bfbaeb5afd4e, 0184165b2f42c4b032da9dd11546bfbaeb5afd4e, 0184165b2f42c4b032da9dd11546bfbaeb5afd4eunaffected
LinuxLinux4.9, 0, 6.12.13, 6.13.2, 6.14affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.