CVE-2023-53148
igb: Fix igb_down hung on surprise removal
- Published
- Updated
- Reserved
- Assigned by
- Linux
Description
In the Linux kernel, the following vulnerability has been resolved: igb: Fix igb_down hung on surprise removal In a setup where a Thunderbolt hub connects to Ethernet and a display through USB Type-C, users may experience a hung task timeout when they remove the cable between the PC and the Thunderbolt hub. This is because the igb_down function is called multiple times when the Thunderbolt hub is unplugged. For example, the igb_io_error_detected triggers the first call, and the igb_remove triggers the second call. The second call to igb_down will block at napi_synchronize. Here's the call trace: __schedule+0x3b0/0xddb ? __mod_timer+0x164/0x5d3 schedule+0x44/0xa8 schedule_timeout+0xb2/0x2a4 ? run_local_timers+0x4e/0x4e msleep+0x31/0x38 igb_down+0x12c/0x22a [igb 6615058754948bfde0bf01429257eb59f13030d4] __igb_close+0x6f/0x9c [igb 6615058754948bfde0bf01429257eb59f13030d4] igb_close+0x23/0x2b [igb 6615058754948bfde0bf01429257eb59f13030d4] __dev_close_many+0x95/0xec dev_close_many+0x6e/0x103 unregister_netdevice_many+0x105/0x5b1 unregister_netdevice_queue+0xc2/0x10d unregister_netdev+0x1c/0x23 igb_remove+0xa7/0x11c [igb 6615058754948bfde0bf01429257eb59f13030d4] pci_device_remove+0x3f/0x9c device_release_driver_internal+0xfe/0x1b4 pci_stop_bus_device+0x5b/0x7f pci_stop_bus_device+0x30/0x7f pci_stop_bus_device+0x30/0x7f pci_stop_and_remove_bus_device+0x12/0x19 pciehp_unconfigure_device+0x76/0xe9 pciehp_disable_slot+0x6e/0x131 pciehp_handle_presence_or_link_change+0x7a/0x3f7 pciehp_ist+0xbe/0x194 irq_thread_fn+0x22/0x4d ? irq_thread+0x1fd/0x1fd irq_thread+0x17b/0x1fd ? irq_forced_thread_fn+0x5f/0x5f kthread+0x142/0x153 ? __irq_get_irqchip_state+0x46/0x46 ? kthread_associate_blkcg+0x71/0x71 ret_from_fork+0x1f/0x30 In this case, igb_io_error_detected detaches the network interface and requests a PCIE slot reset, however, the PCIE reset callback is not being invoked and thus the Ethernet connection breaks down. As the PCIE error in this case is a non-fatal one, requesting a slot reset can be avoided. This patch fixes the task hung issue and preserves Ethernet connection by ignoring non-fatal PCIE errors.
Timeline
ID reserved
By Linux
- 5 months later
· 5 months later
Published
- 8 months later
· 8 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| NVDNVD · Analyzed | 3.1 | High7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
- EPSS (exploitation in 30 days)
- 0.17% · top 94% of all CVEs (7 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.
Weakness
Affected products
- affected 9d5c824399dea881779d78a6c147288bf2dccb6b – < c2312e1d12b1c3ee4100c173131b102e2aed4d04
- affected 9d5c824399dea881779d78a6c147288bf2dccb6b – < 124e39a734cb90658b8f0dc110847bbfc6e33792
- affected 9d5c824399dea881779d78a6c147288bf2dccb6b – < c9f56f3c7bc908caa772112d3ae71cdd5d18c257
- affected 9d5c824399dea881779d78a6c147288bf2dccb6b – < 994c2ceb70ea99264ccc6f09e6703ca267dad63c
- affected 9d5c824399dea881779d78a6c147288bf2dccb6b – < fa92c463eba75dcedbd8d689ffdcb83293aaa0c3
- affected 9d5c824399dea881779d78a6c147288bf2dccb6b – < 39695e87d86f0e7d897fba1d2559f825aa20caeb
- affected 9d5c824399dea881779d78a6c147288bf2dccb6b – < 41f63b72a01c0e0ac59ab83fd2d921fcce0f602d
- affected 9d5c824399dea881779d78a6c147288bf2dccb6b – < 004d25060c78fc31f66da0fa439c544dda1ac9d5
- affected 2.6.25
- unaffected < 2.6.25
- unaffected 4.14.322 – ≤ 4.14.*
- unaffected 4.19.291 – ≤ 4.19.*
- unaffected 5.4.251 – ≤ 5.4.*
- unaffected 5.10.188 – ≤ 5.10.*
- unaffected 5.15.150 – ≤ 5.15.*
- unaffected 6.1.42 – ≤ 6.1.*
- unaffected 6.4.7 – ≤ 6.4.*
- unaffected 6.5 – ≤ *
References (8)
- https://git.kernel.org/stable/c/c2312e1d12b1c3ee4100c173131b102e2aed4d04 (opens in a new tab)
- https://git.kernel.org/stable/c/124e39a734cb90658b8f0dc110847bbfc6e33792 (opens in a new tab)
- https://git.kernel.org/stable/c/c9f56f3c7bc908caa772112d3ae71cdd5d18c257 (opens in a new tab)
- https://git.kernel.org/stable/c/994c2ceb70ea99264ccc6f09e6703ca267dad63c (opens in a new tab)
- https://git.kernel.org/stable/c/fa92c463eba75dcedbd8d689ffdcb83293aaa0c3 (opens in a new tab)
- https://git.kernel.org/stable/c/39695e87d86f0e7d897fba1d2559f825aa20caeb (opens in a new tab)
- https://git.kernel.org/stable/c/41f63b72a01c0e0ac59ab83fd2d921fcce0f602d (opens in a new tab)
- https://git.kernel.org/stable/c/004d25060c78fc31f66da0fa439c544dda1ac9d5 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://trackcve.app/cve/CVE-2023-53148)Record last updated .