{
  "id": "CVE-2026-93229",
  "url": "https://poc.griffinguard.io/cve/CVE-2026-93229",
  "published_at": "2026-09-24T15:29:14.322Z",
  "title": "nfsd: add missing read barrier to rpc_status_get dumpit seqcount retry",
  "vendor": "Linux",
  "product": "Linux",
  "cvss": {
    "score": 7.1,
    "source": "cna",
    "vector": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H"
  },
  "kev": {
    "in_kev": false,
    "added_at": null,
    "days_after_publication": null
  },
  "first_poc": null,
  "poc_repo_count": 0,
  "exploit_count": 0,
  "suspicious_repo_count": 0,
  "edge_device": null,
  "description": "In the Linux kernel, the following vulnerability has been resolved:\n\nnfsd: add missing read barrier to rpc_status_get dumpit seqcount retry\n\nThe hand-rolled seqcount-like protocol in nfsd_nl_rpc_status_get_dumpit()\nis missing a read memory barrier (smp_rmb) before its second counter\ncheck.  The standard kernel read_seqcount_retry() includes smp_rmb()\nto ensure that all data reads complete before the counter is re-checked.\n\nWithout this barrier, on weakly-ordered architectures (ARM, POWER),\nthe CPU may reorder field reads past the second counter check, making\nthe retry logic ineffective: it could observe a consistent counter pair\nwhile reading fields that have been concurrently modified by the writer.\n\nAdd smp_rmb() before the second counter check to order the field reads\nahead of it, matching the barrier semantics of the standard seqcount\nread-side.  The begin-side smp_load_acquire() already pairs with the\nsmp_store_release() in nfsd_dispatch(); with the smp_rmb() now ordering\nthe field reads, the retry check no longer needs acquire semantics and\nreads the counter with a plain READ_ONCE(), as read_seqcount_retry()\ndoes.\n\n[ cel: Use READ_ONCE instead of smp_load_acquire() ]",
  "cvss_by_source": {
    "cna": 7.1
  },
  "repos": [],
  "remediation": {
    "affected": [
      {
        "vendor": "Linux",
        "product": "Linux",
        "ranges": [
          "\u003e= bd9d6a3efa9709e653aafbeb859289feccb8e70c, \u003c f501f2f4ec1d2dfe39e21c98630314074a9b30b0",
          "\u003e= bd9d6a3efa9709e653aafbeb859289feccb8e70c, \u003c 1aea0482b98ecd7d0249204665f2ad4ad517f66b",
          "\u003e= bd9d6a3efa9709e653aafbeb859289feccb8e70c, \u003c 9b5f6475006cd8e3b5b99b8eb3cd74dbb1ce9df8",
          "\u003e= bd9d6a3efa9709e653aafbeb859289feccb8e70c, \u003c a71f161a857117e8e0264deb7d14fff5c98adcf5"
        ],
        "fixed_in": [
          "f501f2f4ec1d2dfe39e21c98630314074a9b30b0",
          "1aea0482b98ecd7d0249204665f2ad4ad517f66b",
          "9b5f6475006cd8e3b5b99b8eb3cd74dbb1ce9df8",
          "a71f161a857117e8e0264deb7d14fff5c98adcf5"
        ]
      },
      {
        "vendor": "Linux",
        "product": "Linux",
        "ranges": [
          "6.7"
        ],
        "fixed_in": [
          "0",
          "6.12.109",
          "6.18.50",
          "7.2.4",
          "7.3"
        ]
      }
    ],
    "upgrade": [
      "Upgrade Linux to f501f2f4ec1d2dfe39e21c98630314074a9b30b0 or 1aea0482b98ecd7d0249204665f2ad4ad517f66b or 9b5f6475006cd8e3b5b99b8eb3cd74dbb1ce9df8 or a71f161a857117e8e0264deb7d14fff5c98adcf5 or later.",
      "Upgrade Linux to 0 or 6.12.109 or 6.18.50 or 7.2.4 or 7.3 or later."
    ]
  },
  "exploit_refs": [],
  "hunt_profile": [],
  "rules": []
}
