Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2025-22111: net: Remove RTNL dance for SIOCBRADDIF and SIOCBRDELIF.

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.20% (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 00fe0ac64efd1f5373b3dd9f1f84b19235371e39, 338a0f3c66aef4ee13052880d02200aae8f2d8a8, 4888e1dcc341e9a132ef7b8516234b3c3296de56; azl3 kernel 6.6.121.1-1 on Azure Linux 3.0 6.6.121.1-1.

Low priority for now. Upgrade to Linux Linux 00fe0ac64efd1f5373b3dd9f1f84b19235371e39, 338a0f3c66aef4ee13052880d02200aae8f2d8a8, 4888e1dcc341e9a132ef7b8516234b3c3296de56; azl3 kernel 6.6.121.1-1 on Azure Linux 3.0 6.6.121.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: net: Remove RTNL dance for SIOCBRADDIF and SIOCBRDELIF. SIOCBRDELIF is passed to dev_ioctl() first and later forwarded to br_ioctl_call(), which causes unnecessary RTNL dance and the splat below [0] under RTNL pressure. Let's say Thread A is trying to detach a device from a bridge and Thread B is trying to remove the bridge. In dev_ioctl(), Thread A bumps the bridge device's refcnt by netdev_hold() and releases RTNL because the following br_ioctl_call() also re-acquires RTNL. In the race window, Thread B could acquire RTNL and try to remove the bridge device. Then, rtnl_unlock() by Thread B will release RTNL and wait for netdev_put() by Thread A. Thread A, however, must hold RTNL after the unlock in dev_ifsioc(), which may take long under RTNL pressure, resulting in the splat by Thread B. Thread A (SIOCBRDELIF) Thread B (SIOCBRDELBR) ---------------------- ---------------------- sock_ioctl sock_ioctl `- sock_do_ioctl `- br_ioctl_call `- dev_ioctl `- br_ioctl_stub |- rtnl_lock | |- dev_ifsioc ' ' |- dev = __dev_get_by_name(...) |- netdev_hold(dev, ...) . / |- rtnl_unlock ------. | | |- br_ioctl_call `---> |- rtnl_lock Race | | `- br_ioctl_stub |- br_del_bridge Window | | | |- dev = __dev_get_by_name(...) | | | May take long | `- br_dev_delete(dev, ...) | | | under RTNL pressure | `- unregister_netdevice_queue(dev, ...) | | | | `- rtnl_unlock \ | |- rtnl_lock <-' `- netdev_run_todo | |- ... `- netdev_run_todo | `- rtnl_unlock |- __rtnl_unlock | |- netdev_wait_allrefs_any |- netdev_put(dev, ...) <----------------' Wait refcnt decrement and log splat below To avoid blocking SIOCBRDELBR unnecessarily, let's not call dev_ioctl() for SIOCBRADDIF and SIOCBRDELIF. In the dev_ioctl() path, we do the following: 1. Copy struct ifreq by get_user_ifreq in sock_do_ioctl() 2. Check CAP_NET_ADMIN in dev_ioctl() 3. Call dev_load() in dev_ioctl() 4. Fetch the master dev from ifr.ifr_name in dev_ifsioc() 3. can be done by request_module() in br_ioctl_call(), so we move 1., 2., and 4. to br_ioctl_stub(). Note that 2. is also checked later in add_del_if(), but it's better performed before RTNL. SIOCBRADDIF and SIOCBRDELIF have been processed in dev_ioctl() since the pre-git era, and there seems to be no specific reason to process them there. [0]: unregister_netdevice: waiting for wpan3 to become free. Usage count = 2 ref_tracker: wpan3@ffff8880662d8608 has 1/1 users at __netdev_tracker_alloc include/linux/netdevice.h:4282 [inline] netdev_hold include/linux/netdevice.h:4311 [inline] dev_ifsioc+0xc6a/0x1160 net/core/dev_ioctl.c:624 dev_ioctl+0x255/0x10c0 net/core/dev_ioctl.c:826 sock_do_ioctl+0x1ca/0x260 net/socket.c:1213 sock_ioctl+0x23a/0x6c0 net/socket.c:1318 vfs_ioctl fs/ioctl.c:51 [inline] __do_sys_ioctl fs/ioctl.c:906 [inline] __se_sys_ioctl fs/ioctl.c:892 [inline] __x64_sys_ioctl+0x1a4/0x210 fs/ioctl.c:892 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xcb/0x250 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f

MediumCVSS 5.5 · v3.1—No exploit Fix available
Published
Apr 16, 2025
Updated
Oct 15, 2026
EPSS
0.2% · 10th percentile
CWE
—

Report tools

JSON

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.

Follow CVE-2025-22111

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

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.

VendorProduct
linuxlinux kernel

Affected versions

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

  • linux linux kernel5.15 and later · before 6.14.2

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

    • 5.15affected
    • 893b195875340cb44b54c9db99e708145f1210e8 and later · before f51e471cb1577d510c3096e126678e1ea20d2efdaffected · git
    • 893b195875340cb44b54c9db99e708145f1210e8 and later · before 338a0f3c66aef4ee13052880d02200aae8f2d8a8affected · git
    • 893b195875340cb44b54c9db99e708145f1210e8 and later · before d767ce15045df510f55cdd2af5df0eee71f928d0affected · git
    • 893b195875340cb44b54c9db99e708145f1210e8 and later · before 4888e1dcc341e9a132ef7b8516234b3c3296de56affected · git
    • 893b195875340cb44b54c9db99e708145f1210e8 and later · before 00fe0ac64efd1f5373b3dd9f1f84b19235371e39affected · git
    • 893b195875340cb44b54c9db99e708145f1210e8 and later · before ed3ba9b6e280e14cc3148c1b226ba453f02fa76caffected · git
    • before 5.15not affected · semver
    • 5.15.198 and later · up to and including 5.15.*not affected · semver
    • 6.1.160 and later · up to and including 6.1.*not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:11linux-6.1before 6.1.162-1~deb11u16.1.162-1~deb11u1
Debian:12linuxbefore 6.1.162-16.1.162-1
Debian:13linuxbefore 6.12.69-16.12.69-1
Debian:14linuxbefore 6.16.3-16.16.3-1
openSUSE:Leap 15.6dtb-aarch64before 6.4.0-150600.23.60.36.4.0-150600.23.60.3
openSUSE:Leap 15.6kernel-64kbbefore 6.4.0-150600.23.60.46.4.0-150600.23.60.4
openSUSE:Leap 15.6kernel-azurebefore 6.4.0-150600.8.43.16.4.0-150600.8.43.1
openSUSE:Leap 15.6kernel-debugbefore 6.4.0-150600.23.60.46.4.0-150600.23.60.4
openSUSE:Leap 15.6kernel-defaultbefore 6.4.0-150600.23.60.56.4.0-150600.23.60.5
openSUSE:Leap 15.6kernel-default-basebefore 6.4.0-150600.23.60.5.150600.12.26.46.4.0-150600.23.60.5.150600.12.26.4
openSUSE:Leap 15.6kernel-docsbefore 6.4.0-150600.23.60.36.4.0-150600.23.60.3
openSUSE:Leap 15.6kernel-kvmsmallbefore 6.4.0-150600.23.60.46.4.0-150600.23.60.4
openSUSE:Leap 15.6kernel-obs-buildbefore 6.4.0-150600.23.60.36.4.0-150600.23.60.3
openSUSE:Leap 15.6kernel-obs-qabefore 6.4.0-150600.23.60.26.4.0-150600.23.60.2
openSUSE:Leap 15.6kernel-rtbefore 6.4.0-150600.10.44.16.4.0-150600.10.44.1
openSUSE:Leap 15.6kernel-rt_debugbefore 6.4.0-150600.10.44.16.4.0-150600.10.44.1
openSUSE:Leap 15.6kernel-sourcebefore 6.4.0-150600.23.60.46.4.0-150600.23.60.4
openSUSE:Leap 15.6kernel-source-azurebefore 6.4.0-150600.8.43.16.4.0-150600.8.43.1
openSUSE:Leap 15.6kernel-source-rtbefore 6.4.0-150600.10.44.16.4.0-150600.10.44.1
openSUSE:Leap 15.6kernel-symsbefore 6.4.0-150600.23.60.46.4.0-150600.23.60.4
openSUSE:Leap 15.6kernel-syms-azurebefore 6.4.0-150600.8.43.16.4.0-150600.8.43.1
openSUSE:Leap 15.6kernel-syms-rtbefore 6.4.0-150600.10.44.16.4.0-150600.10.44.1
openSUSE:Leap 15.6kernel-zfcpdumpbefore 6.4.0-150600.23.60.46.4.0-150600.23.60.4
SUSE:Linux Enterprise Live Patching 15 SP6kernel-livepatch-SLE15-SP6_Update_13before 1-150600.13.6.41-150600.13.6.4

+22

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-22107Apr 16, 2025 · net: dsa: sja1105: fix kasan out-of-bounds warning in sja1105_table_delete_entry()
    28Monitor
  • ← EarlierCVE-2025-22109Apr 16, 2025 · ax25: Remove broken autobind
    22Monitor
  • Later →CVE-2025-22113Apr 16, 2025 · ext4: avoid journaling sb update on error if journal is destroying
    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 / packageFixed versionSource
Linux Linux00fe0ac64efd1f5373b3dd9f1f84b19235371e39Vendor (CNA)
Linux Linux338a0f3c66aef4ee13052880d02200aae8f2d8a8Vendor (CNA)
Linux Linux4888e1dcc341e9a132ef7b8516234b3c3296de56Vendor (CNA)
Linux Linuxd767ce15045df510f55cdd2af5df0eee71f928d0Vendor (CNA)
Linux Linuxed3ba9b6e280e14cc3148c1b226ba453f02fa76cVendor (CNA)
Linux Linuxf51e471cb1577d510c3096e126678e1ea20d2efdVendor (CNA)
azl3 kernel 6.6.121.1-1 on Azure Linux 3.06.6.121.1-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
cbl2 kernel 5.15.202.1-1 on CBL-Mariner 2.0—Microsoft (MSRC)
debian:linux6.1.162-1 · Debian:12Package registry (OSV)
debian:linux-6.16.1.162-1~deb11u1 · Debian:11Package registry (OSV)
opensuse:dtb-aarch646.4.0-150600.23.60.3 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-64kb6.4.0-150600.23.60.4 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-azure6.4.0-150600.8.43.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-debug6.4.0-150600.23.60.4 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-default6.4.0-150600.23.60.5 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-default-base6.4.0-150600.23.60.5.150600.12.26.4 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-rt6.4.0-150600.10.44.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-rt_debug6.4.0-150600.10.44.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-source-azure6.4.0-150600.8.43.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-source-rt6.4.0-150600.10.44.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-syms-azure6.4.0-150600.8.43.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-syms-rt6.4.0-150600.10.44.1 · openSUSE:Leap 15.6Package registry (OSV)
suse:kernel-64kb6.4.0-150600.23.60.4 · SUSE:Linux Enterprise Module for Basesystem 15 SP6Package registry (OSV)
suse:kernel-azure6.4.0-150600.8.43.1 · SUSE:Linux Enterprise Module for Public Cloud 15 SP6Package registry (OSV)
suse:kernel-default6.4.0-150600.23.60.5 · SUSE:Linux Enterprise Module for Basesystem 15 SP6Package registry (OSV)
suse:kernel-default-base6.4.0-150600.23.60.5.150600.12.26.4 · SUSE:Linux Enterprise Module for Basesystem 15 SP6Package registry (OSV)
suse:kernel-livepatch-SLE15-SP6-RT_Update_131-150600.1.5.1 · SUSE:Linux Enterprise Live Patching 15 SP6Package registry (OSV)
suse:kernel-rt6.4.0-150600.10.44.1 · SUSE:Real Time Module 15 SP6Package registry (OSV)
suse:kernel-rt_debug6.4.0-150600.10.44.1 · SUSE:Real Time Module 15 SP6Package registry (OSV)
suse:kernel-source6.4.0-150600.23.60.4 · SUSE:Linux Enterprise Module for Basesystem 15 SP6Package registry (OSV)

+4

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.

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

  1. Fix✗ → ✓

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

References

All records