Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2021-46921: locking/qrwlock: Fix ordering in queued_write_lock_slowpath()

MediumCVSS 5.5 · v3.1—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 22/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.23% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 5902f9453a313be8fe78cbd7e7ca9dba9319fc6e, 82808cc026811fbc3ecf0c0b267a12a339eead56, 82fa9ced35d88581cffa4a1c856fc41fca96d80a.
  • Severity is disputed: the assigning authority (CNA) scores it 7.8, NVD 5.5.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 5902f9453a313be8fe78cbd7e7ca9dba9319fc6e, 82808cc026811fbc3ecf0c0b267a12a339eead56, 82fa9ced35d88581cffa4a1c856fc41fca96d80a 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: 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()]

Published
Feb 27, 2024
Updated
Aug 5, 2026
EPSS
0.2% · 14th percentile

Report tools

JSON

Action score

22

Monitor

Low priority for now.

CVSS
22 / 40 · 5.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
5.5
CNA · Linux
7.8
2.3 point gap

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

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.

Follow CVE-2021-46921

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools
Is your version affected? Check it

Noroxi 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 help

Affected 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.

VendorProduct
linuxlinux kernel

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

    • 4.15affected
    • b519b56e378ee82caf9b079b04f5db87dedc3251 and later · before 5902f9453a313be8fe78cbd7e7ca9dba9319fc6eaffected · git
    • b519b56e378ee82caf9b079b04f5db87dedc3251 and later · before 82808cc026811fbc3ecf0c0b267a12a339eead56affected · git
    • b519b56e378ee82caf9b079b04f5db87dedc3251 and later · before 82fa9ced35d88581cffa4a1c856fc41fca96d80aaffected · git
    • b519b56e378ee82caf9b079b04f5db87dedc3251 and later · before d558fcdb17139728347bccc60a16af3e639649d2affected · git
    • b519b56e378ee82caf9b079b04f5db87dedc3251 and later · before 84a24bf8c52e66b7ac89ada5e3cfbe72d65c1896affected · git
    • before 4.15not affected · semver
    • 4.19.189 and later · up to and including 4.19.*not affected · semver
    • 5.4.115 and later · up to and including 5.4.*not affected · semver
    • 5.10.33 and later · up to and including 5.10.*not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 5.10.38-15.10.38-1
SUSE:Linux Enterprise High Availability Extension 12 SP5kernel-defaultbefore 4.12.14-122.201.14.12.14-122.201.1
SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSSkernel-default-basebefore 5.3.18-150200.24.188.1.150200.9.95.35.3.18-150200.24.188.1.150200.9.95.3
SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSSkernel-docsbefore 5.3.18-150200.24.188.15.3.18-150200.24.188.1
SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSSkernel-obs-buildbefore 5.3.18-150200.24.188.15.3.18-150200.24.188.1
SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSSkernel-preemptbefore 5.3.18-150200.24.188.15.3.18-150200.24.188.1
SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSSkernel-sourcebefore 5.3.18-150200.24.188.15.3.18-150200.24.188.1
SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSSkernel-symsbefore 5.3.18-150200.24.188.15.3.18-150200.24.188.1
SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSSkernel-64kbbefore 5.3.18-150300.59.158.15.3.18-150300.59.158.1
SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSSkernel-default-basebefore 5.3.18-150300.59.158.1.150300.18.92.55.3.18-150300.59.158.1.150300.18.92.5
SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSSkernel-docsbefore 5.3.18-150300.59.158.15.3.18-150300.59.158.1
SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSSkernel-obs-buildbefore 5.3.18-150300.59.158.15.3.18-150300.59.158.1
SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSSkernel-preemptbefore 5.3.18-150300.59.158.15.3.18-150300.59.158.1
SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSSkernel-sourcebefore 5.3.18-150300.59.158.15.3.18-150300.59.158.1
SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSSkernel-symsbefore 5.3.18-150300.59.158.15.3.18-150300.59.158.1
SUSE:Linux Enterprise Live Patching 12 SP5kgraft-patch-SLE12-SP5_Update_54before 1-8.7.11-8.7.1
SUSE:Linux Enterprise Live Patching 15 SP2kernel-defaultbefore 5.3.18-150200.24.188.15.3.18-150200.24.188.1
SUSE:Linux Enterprise Live Patching 15 SP2kernel-livepatch-SLE15-SP2_Update_47before 1-150200.5.3.31-150200.5.3.3
SUSE:Linux Enterprise Live Patching 15 SP3kernel-defaultbefore 5.3.18-150300.59.158.15.3.18-150300.59.158.1
SUSE:Linux Enterprise Live Patching 15 SP3kernel-livepatch-SLE15-SP3_Update_43before 1-150300.7.3.51-150300.7.3.5
SUSE:Linux Enterprise Micro 5.1kernel-rtbefore 5.3.18-150300.166.15.3.18-150300.166.1
SUSE:Linux Enterprise Micro 5.1kernel-source-rtbefore 5.3.18-150300.166.15.3.18-150300.166.1
SUSE:Linux Enterprise Real Time 12 SP5kernel-rtbefore 4.12.14-10.171.14.12.14-10.171.1
SUSE:Linux Enterprise Real Time 12 SP5kernel-rt_debugbefore 4.12.14-10.171.14.12.14-10.171.1

+10

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2021-46919Feb 27, 2024 · dmaengine: idxd: fix wq size store permission state
    22Monitor
  • ← EarlierCVE-2021-46920Feb 27, 2024 · dmaengine: idxd: Fix clobbering of SWERR overflow bit on writeback
    22Monitor
  • Later →CVE-2021-46922Feb 27, 2024 · KEYS: trusted: Fix TPM reservation for seal/unseal
    22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux5902f9453a313be8fe78cbd7e7ca9dba9319fc6eVendor (CNA)
Linux Linux82808cc026811fbc3ecf0c0b267a12a339eead56Vendor (CNA)
Linux Linux82fa9ced35d88581cffa4a1c856fc41fca96d80aVendor (CNA)
Linux Linux84a24bf8c52e66b7ac89ada5e3cfbe72d65c1896Vendor (CNA)
Linux Linuxd558fcdb17139728347bccc60a16af3e639649d2Vendor (CNA)
debian:linux5.10.38-1 · Debian:12Package registry (OSV)
suse:kernel-azure4.12.14-16.173.1 · SUSE:Linux Enterprise Server 12 SP5Package registry (OSV)
suse:kernel-default4.12.14-122.201.1 · SUSE:Linux Enterprise High Availability Extension 12 SP5Package registry (OSV)
suse:kernel-docs4.12.14-122.201.1 · SUSE:Linux Enterprise Software Development Kit 12 SP5Package registry (OSV)
suse:kernel-obs-build4.12.14-122.201.2 · SUSE:Linux Enterprise Software Development Kit 12 SP5Package registry (OSV)
suse:kernel-rt4.12.14-10.171.1 · SUSE:Linux Enterprise Real Time 12 SP5Package registry (OSV)
suse:kernel-rt_debug4.12.14-10.171.1 · SUSE:Linux Enterprise Real Time 12 SP5Package registry (OSV)
suse:kernel-source4.12.14-122.201.1 · SUSE:Linux Enterprise Server 12 SP5Package registry (OSV)
suse:kernel-source-azure4.12.14-16.173.1 · SUSE:Linux Enterprise Server 12 SP5Package registry (OSV)
suse:kernel-source-rt4.12.14-10.171.1 · SUSE:Linux Enterprise Real Time 12 SP5Package registry (OSV)
suse:kernel-syms4.12.14-122.201.1 · SUSE:Linux Enterprise Server 12 SP5Package registry (OSV)
suse:kernel-syms-azure4.12.14-16.173.1 · SUSE:Linux Enterprise Server 12 SP5Package registry (OSV)
suse:kgraft-patch-SLE12-SP5_Update_541-8.7.1 · SUSE:Linux Enterprise Live Patching 12 SP5Package 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.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2025-22069414 days apartriscv: fgraph: Fix stack layout to match __arch_ftrace_regs argument of ftrace_return_to_handler
    31Monitor
  • CVE-2024-3603293 days apartBluetooth: qca: fix info leak when fetching fw build id
    28Monitor
  • CVE-2024-3603393 days apartBluetooth: qca: fix info leak when fetching board id
    28Monitor
  • CVE-2022-48757114 days apartnet: fix information leakage in /proc/net/ptype
    28Monitor
  • CVE-2024-39499136 days apartvmci: prevent speculation leaks by sanitizing event in event_deliver()
    28Monitor
  • CVE-2024-43881175 days apartwifi: ath12k: change DMA direction while mapping reinjected packets
    28Monitor

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · public bounty program.

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
none
Availability
none
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
None
Availability impact
None

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

nvd-primary

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.

References

All records