{
  "id": "CVE-2026-98507",
  "url": "https://poc.griffinguard.io/cve/CVE-2026-98507",
  "published_at": "2026-10-18T15:17:13.767Z",
  "title": "mm/rmap: fix missing barrier between anon_vma init and vma-\u003eanon_vma publish",
  "vendor": "Linux",
  "product": "Linux",
  "cvss": {
    "score": 7.8,
    "source": "cna",
    "vector": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/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\nmm/rmap: fix missing barrier between anon_vma init and vma-\u003eanon_vma publish\n\nOn arm64 server, we find that a task trying to grab the anon_vma lock\ntriggers hungtask.\n\nINFO: task main:2354726 blocked for more than 120 seconds.\n      Tainted: G            E     5.10.0-0021.aarch64 #1\n\"echo 0 \u003e /proc/sys/kernel/hung_task_timeout_secs\" disables this message.\ntask:main            state:D stack:    0 pid:2354726 ppid:2350673 flags:0x00000a01\nCall trace:\n __switch_to+0x7c/0xbc\n __schedule+0x3b4/0x8a0\n schedule+0x50/0xe0\n rwsem_down_write_slowpath+0x3cc/0x6cc\n down_write+0x60/0x260\n __anon_vma_prepare+0x6c/0x210\n do_anonymous_page+0x258/0x660\n handle_pte_fault+0x188/0x214\n __handle_mm_fault+0x1b0/0x380\n handle_mm_fault+0xf4/0x284\n do_page_fault+0x19c/0x494\n do_translation_fault+0xcc/0xf8\n do_mem_abort+0x48/0xac\n el0_da+0x44/0x80\n el0_sync_handler+0x88/0xb4\n el0_sync+0x160/0x180\n\nAfter analyzing the vmcore, we found the anon_vma-\u003eroot-\u003erwsem.count is\n-1.  There is another anon_vma whose anon_vma-\u003eroot-\u003erwsem.count is 1, the\nanon_vma-\u003eroot-\u003erwsem.owner shows the lock is held, but the stack of the\ntask shows the task doesn't hold the anon_vma lock.\n\nAfter adding more debugging info, we found __anon_vma_prepare() reuses\nanon_vma and triggers the UAF of anon_vma-\u003eroot due to missing memory\nbarrier, leading to locking and unlocking two different anon_vma-\u003eroot,\nthus leading to an anon_vma will never be unlocked, and another anon_vma\ncouldn't be locked anymore.\n\nThis race requires two adjacent VMAs that are not merged but are\nanon_vma-compatible (e.g., they differ in VMA_ACCESS_FLAGS that can be\nchanged by mprotect()).  Two threads fault on each VMA concurrently, both\ncalling __anon_vma_prepare() with only mmap_lock held for reading.\n\n    THREAD A                             THREAD B\n__anon_vma_prepare                __anon_vma_prepare\n find_mergeable_anon_vma() -\u003e NULL\n anon_vma = anon_vma_alloc();\n   anon_vma-\u003eroot = anon_vma;\n // the two stores may be reordered\n vma-\u003eanon_vma = anon_vma;\n                                   // finds A's anon_vma\n                                   anon_vma = find_mergeable_anon_vma(vma);\n                                   anon_vma_lock_write(anon_vma);\n                                     // may still see the old root\n                                     down_write(\u0026anon_vma-\u003eroot-\u003erwsem);\n                                   anon_vma_unlock_write(anon_vma);\n                                     // see the new root, never unlock old\n                                     up_write(\u0026anon_vma-\u003eroot-\u003erwsem);\n\nthread A triggers page fault and calls __anon_vma_prepare() to prepare\nanon_vma for the faulting vma.  __anon_vma_prepare() allocates and\ninitializes a new anon_vma, and then publishes it to the vma with a plain\nstore.  anon_vma_prepare() only requires the mmap_lock to be held for\nreading, so two threads can fault on adjacent VMAs at the same time. \nWhile thread A publishes a new anon_vma, thread B could find the anon_vma\nvia find_mergeable_anon_vma() and then locks anon_vma-\u003eroot-\u003erwsem.\n\nThe store to anon_vma-\u003eroot in anon_vma_alloc() and the store to\nvma-\u003eanon_vma can be reordered.  The anon_vma_lock_write() and spin_lock()\nonly provide acquire semantics, which do not prevent prior stores from\nbeing reordered after them.  The release semantics of the corresponding\nspin_unlock() and anon_vma_unlock_write() come too late, the store to\nvma-\u003eanon_vma is already published before they take effect.  As a result,\nthread B can observe the following order:\n\n    vma-\u003eanon_vma = anon_vma;\n    anon_vma-\u003eroot = anon_vma;\n\nThe anon_vma slab is SLAB_TYPESAFE_BY_RCU, so a newly allocated anon_vma\nmay reuse memory from a previously freed one.  The constructor\n(anon_vma_ctor) does not reset anon_vma-\u003eroot, and __put_anon_vma()\ndoesn't clear it either, so the old root value persists until\nanon_vma_alloc() overwrites it.  If that store isn't v\n---truncated---",
  "cvss_by_source": {
    "cna": 7.8
  },
  "repos": [],
  "remediation": {
    "affected": [
      {
        "vendor": "Linux",
        "product": "Linux",
        "ranges": [
          "\u003e= 5c341ee1dfc8fe69d66b1c8b19e463c6d7201ae1, \u003c badedec499f6320742368c73fa77cd63dcf8ca55",
          "\u003e= 5c341ee1dfc8fe69d66b1c8b19e463c6d7201ae1, \u003c aef0f69b515af1c8a4147f68a46b6b81854f46f7",
          "\u003e= 5c341ee1dfc8fe69d66b1c8b19e463c6d7201ae1, \u003c 7d103fc7b836084af585d9d3471334624354cf26",
          "\u003e= 5c341ee1dfc8fe69d66b1c8b19e463c6d7201ae1, \u003c 465e222815c8839445d09028fa4c77e70f7f1c7d",
          "\u003e= 5c341ee1dfc8fe69d66b1c8b19e463c6d7201ae1, \u003c a500df43cde075f6ea4b8bae495d89f2c35b3e16",
          "\u003e= 5c341ee1dfc8fe69d66b1c8b19e463c6d7201ae1, \u003c 4cef512a955e4008ae4436a4fc97726976df1fdf",
          "\u003e= 5c341ee1dfc8fe69d66b1c8b19e463c6d7201ae1, \u003c d348a715380bfcc6a611bdf722169d53fd01e735",
          "\u003e= 5c341ee1dfc8fe69d66b1c8b19e463c6d7201ae1, \u003c b6ac0b3f6013c168f22cad97e79967accacb08e1"
        ],
        "fixed_in": [
          "badedec499f6320742368c73fa77cd63dcf8ca55",
          "aef0f69b515af1c8a4147f68a46b6b81854f46f7",
          "7d103fc7b836084af585d9d3471334624354cf26",
          "465e222815c8839445d09028fa4c77e70f7f1c7d",
          "a500df43cde075f6ea4b8bae495d89f2c35b3e16",
          "4cef512a955e4008ae4436a4fc97726976df1fdf",
          "d348a715380bfcc6a611bdf722169d53fd01e735",
          "b6ac0b3f6013c168f22cad97e79967accacb08e1"
        ]
      },
      {
        "vendor": "Linux",
        "product": "Linux",
        "ranges": [
          "2.6.36"
        ],
        "fixed_in": [
          "0",
          "5.10.273",
          "5.15.224",
          "6.1.191",
          "6.6.160",
          "6.12.112",
          "6.18.55",
          "7.2.9",
          "7.3"
        ]
      }
    ],
    "upgrade": [
      "Upgrade Linux to badedec499f6320742368c73fa77cd63dcf8ca55 or aef0f69b515af1c8a4147f68a46b6b81854f46f7 or 7d103fc7b836084af585d9d3471334624354cf26 or 465e222815c8839445d09028fa4c77e70f7f1c7d or a500df43cde075f6ea4b8bae495d89f2c35b3e16 or 4cef512a955e4008ae4436a4fc97726976df1fdf or d348a715380bfcc6a611bdf722169d53fd01e735 or b6ac0b3f6013c168f22cad97e79967accacb08e1 or later.",
      "Upgrade Linux to 0 or 5.10.273 or 5.15.224 or 6.1.191 or 6.6.160 or 6.12.112 or 6.18.55 or 7.2.9 or 7.3 or later."
    ]
  },
  "exploit_refs": [],
  "hunt_profile": [],
  "rules": []
}
