CVE-2026-93229

nfsd: add missing read barrier to rpc_status_get dumpit seqcount retry

  • High 7.1

Description

In the Linux kernel, the following vulnerability has been resolved: nfsd: add missing read barrier to rpc_status_get dumpit seqcount retry The hand-rolled seqcount-like protocol in nfsd_nl_rpc_status_get_dumpit() is missing a read memory barrier (smp_rmb) before its second counter check. The standard kernel read_seqcount_retry() includes smp_rmb() to ensure that all data reads complete before the counter is re-checked. Without this barrier, on weakly-ordered architectures (ARM, POWER), the CPU may reorder field reads past the second counter check, making the retry logic ineffective: it could observe a consistent counter pair while reading fields that have been concurrently modified by the writer. Add smp_rmb() before the second counter check to order the field reads ahead of it, matching the barrier semantics of the standard seqcount read-side. The begin-side smp_load_acquire() already pairs with the smp_store_release() in nfsd_dispatch(); with the smp_rmb() now ordering the field reads, the retry check no longer needs acquire semantics and reads the counter with a plain READ_ONCE(), as read_seqcount_retry() does. [ cel: Use READ_ONCE instead of smp_load_acquire() ]

Key facts

Published
24 Sep 2026
Last changed
19 Oct 2026
Assigned by
Linux
EPSS
0.125% likely to be exploited in the next 30 days, higher than 2.261% of CVEs (scores for 17 Nov 2026)

Severity scores

Each score is shown as its source gave it. They are not averaged or merged.

  • 7.1CVSS 3.1, Highfrom the CNA (Linux)CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

No explicit remediation statement is available on this page yet. Consult the original record and vendor references before choosing a fix.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
LinuxLinux
  • Default status: unaffected
  • bd9d6a3efa9709e653aafbeb859289feccb8e70c up to but excluding f501f2f4ec1d2dfe39e21c98630314074a9b30b0 (affected)
  • bd9d6a3efa9709e653aafbeb859289feccb8e70c up to but excluding 1aea0482b98ecd7d0249204665f2ad4ad517f66b (affected)
  • bd9d6a3efa9709e653aafbeb859289feccb8e70c up to but excluding 9b5f6475006cd8e3b5b99b8eb3cd74dbb1ce9df8 (affected)
  • bd9d6a3efa9709e653aafbeb859289feccb8e70c up to but excluding a71f161a857117e8e0264deb7d14fff5c98adcf5 (affected)
LinuxLinux
  • Default status: affected
  • 6.7 (affected)
  • 0 up to but excluding 6.7 (unaffected)
  • 6.12.109 up to and including 6.12.* (unaffected)
  • 6.18.50 up to and including 6.18.* (unaffected)
  • 7.2.4 up to and including 7.2.* (unaffected)
  • 7.3 up to and including * (unaffected)

Timeline

  1. 24 Sep 2026 Published

References