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-54117s390/dcssblk: fix kernel crash with list_add corruption

Description

In the Linux kernel, the following vulnerability has been resolved: s390/dcssblk: fix kernel crash with list_add corruption Commit fb08a1908cb1 ("dax: simplify the dax_device <-> gendisk association") introduced new logic for gendisk association, requiring drivers to explicitly call dax_add_host() and dax_remove_host(). For dcssblk driver, some dax_remove_host() calls were missing, e.g. in device remove path. The commit also broke error handling for out_dax case in device add path, resulting in an extra put_device() w/o the previous get_device() in that case. This lead to stale xarray entries after device add / remove cycles. In the case when a previously used struct gendisk pointer (xarray index) would be used again, because blk_alloc_disk() happened to return such a pointer, the xa_insert() in dax_add_host() would fail and go to out_dax, doing the extra put_device() in the error path. In combination with an already flawed error handling in dcssblk (device_register() cleanup), which needs to be addressed in a separate patch, this resulted in a missing device_del() / klist_del(), and eventually in the kernel crash with list_add corruption on a subsequent device_add() / klist_add(). Fix this by adding the missing dax_remove_host() calls, and also move the put_device() in the error path to restore the previous logic.

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 (18 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 fb08a1908cb119a4585611d91461ab6d27756b14 – < 6489ec0107860345bc57dcde39e63dfb05ac5c11
    • affected fb08a1908cb119a4585611d91461ab6d27756b14 – < b7ad75c77349beb4983b9f27108d9b3f33ae1413
    • affected fb08a1908cb119a4585611d91461ab6d27756b14 – < b5c531a9a7d8e047c90c909f09cef06a9f8e62f4
    • affected fb08a1908cb119a4585611d91461ab6d27756b14 – < c8f40a0bccefd613748d080147469a4652d6e74c
  • Linux · Linux

    • affected 5.17
    • unaffected < 5.17
    • unaffected 6.1.53 – ≤ 6.1.*
    • unaffected 6.4.16 – ≤ 6.4.*
    • unaffected 6.5.3 – ≤ 6.5.*
    • unaffected 6.6 – ≤ *

References

References4

Sources

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

Badge for a README or a ticket

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

Record last updated .