nday
CVE-2026-97479

driver core: Avoid warning when removing a device while its supplier is unbinding

Linux / Linux

Disclosed . nday has no fix record for it yet; that does not mean no patch exists. None of the four PoC sources lists it. Not in CISA KEV.

tags productLinux kernel product typeoperating system
why these tags

nday derives these tags by fixed rules from the facts below; NVD, the CNA and other sources do not assign them. Vocabulary and rules: ~/tags.

Linux kernel
affected products in the CVE record: Linux · Linux
operating system
affected products in the CVE record: Linux · Linuxthe product type of Linux kernel in nday's product registry
stage
DIS
disclosed
cvss
no score yet

Lifecycle

x axis UTC; dot = exact minute, wide bar = date only, hollow = unknown or inferred.
time unknown
DISdisclosed
09-24T16:04Z
PATpatch
no record yet
ANAanalysis
no record yet
POCPoC
no record yet
ITWexploited
no record yet
KEVKEV
no record yet

Summary

In the Linux kernel, the following vulnerability has been resolved:

driver core: Avoid warning when removing a device while its supplier is unbinding

During driver removal, the following warning can appear:

WARNING: CPU: 1 PID: 139 at drivers/base/core.c:1497 __device_links_no_driver+0xcc/0xfc
...
Call trace:
  __device_links_no_driver+0xcc/0xfc (P)
  device_links_driver_cleanup+0xa8/0xf0
  device_release_driver_internal+0x208/0x23c
  device_links_unbind_consumers+0xe0/0x108
  device_release_driver_internal+0xec/0x23c
  device_links_unbind_consumers+0xe0/0x108
  device_release_driver_internal+0xec/0x23c
  device_links_unbind_consumers+0xe0/0x108
  device_release_driver_internal+0xec/0x23c
  driver_detach+0xa0/0x12c
  bus_remove_driver+0x6c/0xbc
  driver_unregister+0x30/0x60
  pci_unregister_driver+0x20/0x9c
  lan966x_pci_driver_exit+0x18/0xa90 [lan966x_pci]

This warning is triggered when a consumer is removed because the links status of its supplier is not DL_DEV_DRIVER_BOUND and the link flag DL_FLAG_SYNC_STATE_ONLY is not set.

The topology in terms of consumers/suppliers used was the following (consumer ---> supplier):

i2c -----------> OIC ----> PCI device
 |                ^
 |                |
 +---> pinctrl ---+

When the PCI device is removed, the OIC (interrupt controller) has to be removed. In order to remove the OIC, pinctrl and i2c need to be removed and to remove pinctrl, i2c need to be removed. The removal order is: 1) i2c 2) pinctrl 3) OIC 4) PCI device

In details, the removal sequence is the following (with 0000:01:00.0 the PCI device):

driver_detach: call device_release_driver_internal(0000:01:00.0)...
  device_links_busy(0000:01:00.0):
    links->status = DL_DEV_UNBINDING
  device_links_unbind_consumers(0000:01:00.0):
    0000:01:00.0--oic link->status = DL_STATE_SUPPLIER_UNBIND
    call device_release_driver_internal(oic)...
      device_links_busy(oic):
        links->status = DL_DEV_UNBINDING
      device_links_unbind_consumers(oic):
        oic--pinctrl link->status = DL_STATE_SUPPLIER_UNBIND
        call device_release_driver_internal(pinctrl)...
          device_links_busy(pinctrl):
            links->status = DL_DEV_UNBINDING
          device_links_unbind_consumers(pinctrl):
            pinctrl--i2c link->status = DL_STATE_SUPPLIER_UNBIND
            call device_release_driver_internal(i2c)...
              device_links_busy(i2c): links->status = DL_DEV_UNBINDING
              __device_links_no_driver(i2c)...
                pinctrl--i2c link->status is DL_STATE_SUPPLIER_UNBIND
                oic--i2c link->status is DL_STATE_ACTIVE
                oic--i2c link->supplier->links.status is DL_DEV_UNBINDING

The warning is triggered by the i2c removal because the OIC (supplier) links status is not DL_DEV_DRIVER_BOUND. Its links status is indeed set to DL_DEV_UNBINDING.

It is perfectly legit to have the links status set to DL_DEV_UNBINDING in that case. Indeed we had started to unbind the OIC which triggered the consumer unbinding and didn't finish yet when the i2c is unbound.

Avoid the warning when the supplier links status is set to DL_DEV_UNBINDING and thus support this removal sequence without any warnings.

Original text of the CVE record (cvelist), shown as published.

Event log

+DISdisclosed

CVE record published by Linux.

src cvelist · nday , bulk import · raw
{
  "id": 456965,
  "type": "disclosed",
  "source": "cvelist",
  "url": "https://www.cve.org/CVERecord?id=CVE-2026-97479",
  "occurred_at": "2026-09-24T16:04:21.956Z",
  "observed_at": "2026-11-13T05:40:20.493151Z",
  "is_backfill": true,
  "dedupe_key": "",
  "detail": {
    "state": "PUBLISHED",
    "date_published": "2026-09-24T16:04:21.956Z",
    "assigner_short_name": "Linux"
  }
}

Report an error

report an error or omission

Something on this page wrong or missing? Tell the editors; if they accept it, this page's revision log says so publicly. Upstream data is not changed.

Researcher discussion

0 researchers mentioned this in the last 7 days

Posts on X by researchers on nday's list that mention this CVE, shown as posted. nday does not check them.

nday has not collected any post on X by listed researchers that mentions this CVE.

Discussion

0 comments

No comments yet.