CVE-2026-93229
CVE CVE-2026-93229EUVD EUVD-2026-86234Published 2026-09-24T15:29:14.000ZLast changed 2026-09-25T05:09:49.000ZCVSS 7.1
What the advisory describes
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() ]
Source: EUVD (ENISA), in the words of the advisory.
Products the advisory names
These come from the advisory itself, not from any check we performed.
- Linux — Linux bd9d6a3efa9709e653aafbeb859289feccb8e70c <9b5f6475006cd8e3b5b99b8eb3cd74dbb1ce9df8; patch: 6.18.50; patch: 6.12.109; patch: 7.2.4; patch: 0; patch: 7.3-rc1; 6.7; bd9d6a3efa9709e653aafbeb859289feccb8e70c <f501f2f4ec1d2dfe39e21c98630314074a9b30b0; bd9d6a3efa9709e653aafbeb859289feccb8e70c <a71f161a857117e8e0264deb7d14fff5c98adcf5; bd9d6a3efa9709e653aafbeb859289feccb8e70c <1aea0482b98ecd7d0249204665f2ad4ad517f66b
The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.
Carried in the product catalogue
An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.
- Linux — Linux
Does this concern one of your customers?
This page cannot answer that — it does not know your estate. Whoever has recorded their environments gets the answer the morning after publication, together with a paragraph they can forward to the customer unedited.
Try it for 28 daysPatchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.