CVE-2023-54118: serial: sc16is7xx: setup GPIO controller later in probe
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.20% (FIRST EPSS).
- Fixed version: Linux Linux 17b96b5c19bec791b433890549e44ca523dc82aa, 49b326ce8a686428d8cbb82ed74fc88ed3f95a51, b71ff206707855ce73c04794c76f7b678b2d4f72.
Low priority for now. Upgrade to Linux Linux 17b96b5c19bec791b433890549e44ca523dc82aa, 49b326ce8a686428d8cbb82ed74fc88ed3f95a51, b71ff206707855ce73c04794c76f7b678b2d4f72 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Dec 24, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 11th percentile
- CWE
- —
Report tools
Action score
0
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 3.16affected
- dfeae619d781dee61666d5551b93ba3be755a86b and later · before 17b96b5c19bec791b433890549e44ca523dc82aaaffected · git
- dfeae619d781dee61666d5551b93ba3be755a86b and later · before 49b326ce8a686428d8cbb82ed74fc88ed3f95a51affected · git
- dfeae619d781dee61666d5551b93ba3be755a86b and later · before f57c2164d082a36d177ab7fbf54c18970df89c22affected · git
- dfeae619d781dee61666d5551b93ba3be755a86b and later · before b71ff206707855ce73c04794c76f7b678b2d4f72affected · git
- dfeae619d781dee61666d5551b93ba3be755a86b and later · before c8f71b49ee4d28930c4a6798d1969fa91dc4ef3eaffected · git
- before 3.16not affected · semver
- 5.10.173 and later · up to and including 5.10.*not affected · semver
- 5.15.100 and later · up to and including 5.15.*not affected · semver
- 6.1.18 and later · up to and including 6.1.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.20-1 | 6.1.20-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2023-54115Dec 24, 2025 · pcmcia: rsrc_nonstatic: Fix memory leak in nonstatic_release_resource_db()0Monitor
- ← EarlierCVE-2023-54117Dec 24, 2025 · s390/dcssblk: fix kernel crash with list_add corruption0Monitor
- Later →CVE-2023-54119Dec 24, 2025 · inotify: Avoid reporting event with invalid wd0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 17b96b5c19bec791b433890549e44ca523dc82aa | Vendor (CNA) |
| Linux Linux | 49b326ce8a686428d8cbb82ed74fc88ed3f95a51 | Vendor (CNA) |
| Linux Linux | b71ff206707855ce73c04794c76f7b678b2d4f72 | Vendor (CNA) |
| Linux Linux | c8f71b49ee4d28930c4a6798d1969fa91dc4ef3e | Vendor (CNA) |
| Linux Linux | f57c2164d082a36d177ab7fbf54c18970df89c22 | Vendor (CNA) |
| debian:linux | 6.1.20-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (4 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.