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-52774s390/dasd: protect device queue against concurrent access

Description

In the Linux kernel, the following vulnerability has been resolved: s390/dasd: protect device queue against concurrent access In dasd_profile_start() the amount of requests on the device queue are counted. The access to the device queue is unprotected against concurrent access. With a lot of parallel I/O, especially with alias devices enabled, the device queue can change while dasd_profile_start() is accessing the queue. In the worst case this leads to a kernel panic due to incorrect pointer accesses. Fix this by taking the device lock before accessing the queue and counting the requests. Additionally the check for a valid profile data pointer can be done earlier to avoid unnecessary locking in a hot path.

Timeline

  1. ID reserved

    By Linux

  2. Published

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

CVSS scores of CVE-2023-52774, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.24% · top 85% of all CVEs (18 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected 4fa52aa7a82f9226b3874a69816bda3af821f002 – < ebdc569a07a3e8dbe66b4184922ad6f88ac0b96f
    • affected 4fa52aa7a82f9226b3874a69816bda3af821f002 – < f75617cc8df4155374132f0b500b0b3ebb967458
    • affected 4fa52aa7a82f9226b3874a69816bda3af821f002 – < f1ac7789406e2ca9ac51c41ad2daa597f47bdd4d
    • affected 4fa52aa7a82f9226b3874a69816bda3af821f002 – < c841de6247e94e07566d57163d3c0d8b29278f7a
    • affected 4fa52aa7a82f9226b3874a69816bda3af821f002 – < 6062c527d0403cef27c54b91ac8390c3a497b250
    • affected 4fa52aa7a82f9226b3874a69816bda3af821f002 – < dc96fde8fcb2b896fd6c64802a7f4ece2e69b0be
    • affected 4fa52aa7a82f9226b3874a69816bda3af821f002 – < 9372aab5d0ff621ea203c8c603e7e5f75e888240
    • affected 4fa52aa7a82f9226b3874a69816bda3af821f002 – < db46cd1e0426f52999d50fa72cfa97fa39952885
  • Linux · Linux

    • affected 3.1
    • unaffected < 3.1
    • unaffected 4.14.332 – ≤ 4.14.*
    • unaffected 4.19.301 – ≤ 4.19.*
    • unaffected 5.4.263 – ≤ 5.4.*
    • unaffected 5.10.203 – ≤ 5.10.*
    • unaffected 5.15.141 – ≤ 5.15.*
    • unaffected 6.1.65 – ≤ 6.1.*
    • unaffected 6.6.4 – ≤ 6.6.*
    • unaffected 6.7 – ≤ *

References

References8

Sources

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

Badge for a README or a ticket

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

Record last updated .