GHSA-5X4G-X6MC-9FXQ
Vulnerability from github – Published: 2026-09-11 21:31 – Updated: 2026-09-11 21:31In the Linux kernel, the following vulnerability has been resolved:
net: dsa: realtek: use gpiod_set_value_cansleep for reset GPIO
rtl83xx_reset_assert() and rtl83xx_reset_deassert() are only called from the probe path, which may sleep and is not timing-critical. When the reset GPIO is provided by a sleeping controller such as an I2C I/O expander, gpiod_set_value() warns:
WARNING: drivers/gpio/gpiolib.c:4030 at gpiod_set_value+0x44/0x80, CPU#1: kworker/u16:4/61 Hardware name: B&O MAP CA33 Rev f (UNKNOWN) (DT) Workqueue: events_unbound deferred_probe_work_func pc : gpiod_set_value+0x44/0x80 lr : rtl83xx_probe+0x1d8/0x3a0 Call trace: gpiod_set_value+0x44/0x80 (P) rtl83xx_probe+0x1d8/0x3a0 realtek_mdio_probe+0x24/0xa0 mdio_probe+0x38/0x78 really_probe+0xc4/0x3e0 __driver_probe_device+0x15c/0x1b8 driver_probe_device+0xb4/0x120 __device_attach_driver+0xb8/0x1a0 bus_for_each_drv+0x88/0xf0 __device_attach+0xa0/0x1d8 device_initial_probe+0x54/0x68 bus_probe_device+0x38/0xa0 deferred_probe_work_func+0xb8/0x120 process_one_work+0x184/0x4e8 worker_thread+0x188/0x308 kthread+0x130/0x150 ret_from_fork+0x10/0x20
Switch both helpers to gpiod_set_value_cansleep() so such a reset GPIO can be used without triggering the warning.
The reset GPIO has been driven with the non-sleeping gpiod_set_value() since the driver was added in v4.19. The call has since been refactored across several files - from realtek-smi.c / realtek-mdio.c into the common rtl83xx.c module and then into the rtl83xx_reset_assert() and rtl83xx_reset_deassert() helpers (both in v6.9). This patch therefore applies as-is only to kernels that carry those helpers (v6.9+); older stable kernels need the same gpiod_set_value_cansleep() conversion at the corresponding open-coded call sites.
{
"affected": [],
"aliases": [
"CVE-2026-80999"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-09-11T20:19:07Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\nnet: dsa: realtek: use gpiod_set_value_cansleep for reset GPIO\n\nrtl83xx_reset_assert() and rtl83xx_reset_deassert() are only called from\nthe probe path, which may sleep and is not timing-critical. When the\nreset GPIO is provided by a sleeping controller such as an I2C I/O\nexpander, gpiod_set_value() warns:\n\n WARNING: drivers/gpio/gpiolib.c:4030 at gpiod_set_value+0x44/0x80, CPU#1: kworker/u16:4/61\n Hardware name: B\u0026O MAP CA33 Rev f (UNKNOWN) (DT)\n Workqueue: events_unbound deferred_probe_work_func\n pc : gpiod_set_value+0x44/0x80\n lr : rtl83xx_probe+0x1d8/0x3a0\n Call trace:\n gpiod_set_value+0x44/0x80 (P)\n rtl83xx_probe+0x1d8/0x3a0\n realtek_mdio_probe+0x24/0xa0\n mdio_probe+0x38/0x78\n really_probe+0xc4/0x3e0\n __driver_probe_device+0x15c/0x1b8\n driver_probe_device+0xb4/0x120\n __device_attach_driver+0xb8/0x1a0\n bus_for_each_drv+0x88/0xf0\n __device_attach+0xa0/0x1d8\n device_initial_probe+0x54/0x68\n bus_probe_device+0x38/0xa0\n deferred_probe_work_func+0xb8/0x120\n process_one_work+0x184/0x4e8\n worker_thread+0x188/0x308\n kthread+0x130/0x150\n ret_from_fork+0x10/0x20\n\nSwitch both helpers to gpiod_set_value_cansleep() so such a reset GPIO can\nbe used without triggering the warning.\n\nThe reset GPIO has been driven with the non-sleeping gpiod_set_value()\nsince the driver was added in v4.19. The call has since been refactored\nacross several files - from realtek-smi.c / realtek-mdio.c into the common\nrtl83xx.c module and then into the rtl83xx_reset_assert() and\nrtl83xx_reset_deassert() helpers (both in v6.9). This patch therefore\napplies as-is only to kernels that carry those helpers (v6.9+); older\nstable kernels need the same gpiod_set_value_cansleep() conversion at the\ncorresponding open-coded call sites.",
"id": "GHSA-5x4g-x6mc-9fxq",
"modified": "2026-09-11T21:31:23Z",
"published": "2026-09-11T21:31:23Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-80999"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/1610a8c2b93e815e3dc8643a2a69ab1c37975a6a"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/c32cf5292a0dd70c4afc138b4dc45743a190cd5a"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/f71087e7c63aa3e99bf65d7ddf91eb4fd3545778"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/fb58b6a696b30bcbfbe0cfc0a91b19c816a955fc"
}
],
"schema_version": "1.4.0",
"severity": []
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.