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-2021-46921locking/qrwlock: Fix ordering in queued_write_lock_slowpath()

Description

In the Linux kernel, the following vulnerability has been resolved: locking/qrwlock: Fix ordering in queued_write_lock_slowpath() While this code is executed with the wait_lock held, a reader can acquire the lock without holding wait_lock. The writer side loops checking the value with the atomic_cond_read_acquire(), but only truly acquires the lock when the compare-and-exchange is completed successfully which isn’t ordered. This exposes the window between the acquire and the cmpxchg to an A-B-A problem which allows reads following the lock acquisition to observe values speculatively before the write lock is truly acquired. We've seen a problem in epoll where the reader does a xchg while holding the read lock, but the writer can see a value change out from under it. Writer | Reader -------------------------------------------------------------------------------- ep_scan_ready_list() | |- write_lock_irq() | |- queued_write_lock_slowpath() | |- atomic_cond_read_acquire() | | read_lock_irqsave(&ep->lock, flags); --> (observes value before unlock) | chain_epi_lockless() | | epi->next = xchg(&ep->ovflist, epi); | | read_unlock_irqrestore(&ep->lock, flags); | | | atomic_cmpxchg_relaxed() | |-- READ_ONCE(ep->ovflist); | A core can order the read of the ovflist ahead of the atomic_cmpxchg_relaxed(). Switching the cmpxchg to use acquire semantics addresses this issue at which point the atomic_cond_read can be switched to use relaxed semantics. [peterz: use try_cmpxchg()]

Timeline

  1. ID reserved

    By Linux

  2. · 2 days later

    Published

  3. · 2 years 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-2021-46921, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
EPSS (exploitation in 30 days)
0.24% · top 85% of all CVEs (20 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: High 7.8.

Affected products

  • Linux · Linux

    • affected b519b56e378ee82caf9b079b04f5db87dedc3251 – < 5902f9453a313be8fe78cbd7e7ca9dba9319fc6e
    • affected b519b56e378ee82caf9b079b04f5db87dedc3251 – < 82808cc026811fbc3ecf0c0b267a12a339eead56
    • affected b519b56e378ee82caf9b079b04f5db87dedc3251 – < 82fa9ced35d88581cffa4a1c856fc41fca96d80a
    • affected b519b56e378ee82caf9b079b04f5db87dedc3251 – < d558fcdb17139728347bccc60a16af3e639649d2
    • affected b519b56e378ee82caf9b079b04f5db87dedc3251 – < 84a24bf8c52e66b7ac89ada5e3cfbe72d65c1896
  • Linux · Linux

    • affected 4.15
    • unaffected < 4.15
    • unaffected 4.19.189 – ≤ 4.19.*
    • unaffected 5.4.115 – ≤ 5.4.*
    • unaffected 5.10.33 – ≤ 5.10.*
    • unaffected 5.11.17 – ≤ 5.11.*
    • unaffected 5.12 – ≤ *

References

References5

Sources

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

Badge for a README or a ticket

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

Record last updated .