Bug 2546470 (CVE-2026-98359) - CVE-2026-98359 kernel: RDMA/core: Reject unregistering netdevs in ib_get_eth_speed
Summary: CVE-2026-98359 kernel: RDMA/core: Reject unregistering netdevs in ib_get_eth_...
Keywords:
Status: NEW
Alias: CVE-2026-98359
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-10-06 09:25 UTC by OSIDB Bzimport
Modified: 2026-10-07 08:04 UTC (History)
17 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-10-06 09:25:58 UTC
In the Linux kernel, the following vulnerability has been resolved:

RDMA/core: Reject unregistering netdevs in ib_get_eth_speed

ib_device_get_netdev() intentionally returns a referenced net_device even
when it is unregistering, so matching and cleanup callers can still find
the association. The reference keeps struct net_device allocated, but does
not guarantee that the device remains operational.

ib_get_eth_speed() uses the returned device operationally by invoking its
ethtool callback. Although that call is made under RTNL, the function does
not verify the registration state first. An asynchronous RDMA port query
can therefore call into a netdev after NETDEV_UNREGISTER and ndo_uninit
have completed.

Check for NETREG_REGISTERED while holding RTNL and return -ENODEV for a
device which is being unregistered. Keeping RTNL across the check and the
ethtool operation prevents unregister from starting between them.

Keep the speed fallback and warning under RTNL as well, so the warning can
safely read netdev->name. Drop the netdev reference before releasing RTNL
once all accesses to the device are complete.


Note You need to log in before you can comment on or make changes to this bug.