Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2023-54118serial: sc16is7xx: setup GPIO controller later in probe

Description

In the Linux kernel, the following vulnerability has been resolved: serial: sc16is7xx: setup GPIO controller later in probe The GPIO controller component of the sc16is7xx driver is setup too early, which can result in a race condition where another device tries to utilise the GPIO lines before the sc16is7xx device has finished initialising. This issue manifests itself as an Oops when the GPIO lines are configured: Unable to handle kernel read from unreadable memory at virtual address ... pc : sc16is7xx_gpio_direction_output+0x68/0x108 [sc16is7xx] lr : sc16is7xx_gpio_direction_output+0x4c/0x108 [sc16is7xx] ... Call trace: sc16is7xx_gpio_direction_output+0x68/0x108 [sc16is7xx] gpiod_direction_output_raw_commit+0x64/0x318 gpiod_direction_output+0xb0/0x170 create_gpio_led+0xec/0x198 gpio_led_probe+0x16c/0x4f0 platform_drv_probe+0x5c/0xb0 really_probe+0xe8/0x448 driver_probe_device+0xe8/0x138 __device_attach_driver+0x94/0x118 bus_for_each_drv+0x8c/0xe0 __device_attach+0x100/0x1b8 device_initial_probe+0x28/0x38 bus_probe_device+0xa4/0xb0 deferred_probe_work_func+0x90/0xe0 process_one_work+0x1c4/0x480 worker_thread+0x54/0x430 kthread+0x138/0x150 ret_from_fork+0x10/0x1c This patch moves the setup of the GPIO controller functions to later in the probe function, ensuring the sc16is7xx device has already finished initialising by the time other devices try to make use of the GPIO lines. The error handling has also been reordered to reflect the new initialisation order.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 5 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

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Deferred.

EPSS (exploitation in 30 days)
0.21% · top 89% of all CVEs (19 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected dfeae619d781dee61666d5551b93ba3be755a86b – < 17b96b5c19bec791b433890549e44ca523dc82aa
    • affected dfeae619d781dee61666d5551b93ba3be755a86b – < 49b326ce8a686428d8cbb82ed74fc88ed3f95a51
    • affected dfeae619d781dee61666d5551b93ba3be755a86b – < f57c2164d082a36d177ab7fbf54c18970df89c22
    • affected dfeae619d781dee61666d5551b93ba3be755a86b – < b71ff206707855ce73c04794c76f7b678b2d4f72
    • affected dfeae619d781dee61666d5551b93ba3be755a86b – < c8f71b49ee4d28930c4a6798d1969fa91dc4ef3e
  • Linux · Linux

    • affected 3.16
    • unaffected < 3.16
    • unaffected 5.10.173 – ≤ 5.10.*
    • unaffected 5.15.100 – ≤ 5.15.*
    • unaffected 6.1.18 – ≤ 6.1.*
    • unaffected 6.2.5 – ≤ 6.2.*
    • unaffected 6.3 – ≤ *

References

References5

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2023-54118 badge
[![CVE-2023-54118](https://cveledger.app/badge/CVE-2023-54118.svg)](https://cveledger.app/cve/CVE-2023-54118)

Record last updated .