CVE-2025-21876 (GCVE-0-2025-21876)
Vulnerability from cvelistv5
Published
2025-03-27 14:57
Modified
2026-10-15 21:51
Severity ?
8.8 (High) - CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
Summary
In the Linux kernel, the following vulnerability has been resolved: iommu/vt-d: Fix suspicious RCU usage Commit <d74169ceb0d2> ("iommu/vt-d: Allocate DMAR fault interrupts locally") moved the call to enable_drhd_fault_handling() to a code path that does not hold any lock while traversing the drhd list. Fix it by ensuring the dmar_global_lock lock is held when traversing the drhd list. Without this fix, the following warning is triggered: ============================= WARNING: suspicious RCU usage 6.14.0-rc3 #55 Not tainted ----------------------------- drivers/iommu/intel/dmar.c:2046 RCU-list traversed in non-reader section!! other info that might help us debug this: rcu_scheduler_active = 1, debug_locks = 1 2 locks held by cpuhp/1/23: #0: ffffffff84a67c50 (cpu_hotplug_lock){++++}-{0:0}, at: cpuhp_thread_fun+0x87/0x2c0 #1: ffffffff84a6a380 (cpuhp_state-up){+.+.}-{0:0}, at: cpuhp_thread_fun+0x87/0x2c0 stack backtrace: CPU: 1 UID: 0 PID: 23 Comm: cpuhp/1 Not tainted 6.14.0-rc3 #55 Call Trace: <TASK> dump_stack_lvl+0xb7/0xd0 lockdep_rcu_suspicious+0x159/0x1f0 ? __pfx_enable_drhd_fault_handling+0x10/0x10 enable_drhd_fault_handling+0x151/0x180 cpuhp_invoke_callback+0x1df/0x990 cpuhp_thread_fun+0x1ea/0x2c0 smpboot_thread_fn+0x1f5/0x2e0 ? __pfx_smpboot_thread_fn+0x10/0x10 kthread+0x12a/0x2d0 ? __pfx_kthread+0x10/0x10 ret_from_fork+0x4a/0x60 ? __pfx_kthread+0x10/0x10 ret_from_fork_asm+0x1a/0x30 </TASK> Holding the lock in enable_drhd_fault_handling() triggers a lockdep splat about a possible deadlock between dmar_global_lock and cpu_hotplug_lock. This is avoided by not holding dmar_global_lock when calling iommu_device_register(), which initiates the device probe process.
References
Impacted products
Vendor Product Version
Linux Linux Version: d74169ceb0d2e32438946a2f1f9fc8c803304bd6
Version: d74169ceb0d2e32438946a2f1f9fc8c803304bd6
Version: d74169ceb0d2e32438946a2f1f9fc8c803304bd6
 Create a notification for this product.
Show details on NVD website

To clipboard 

{
  "containers": {
    "adp": [
      {
        "metrics": [
          {
            "other": {
              "content": {
                "id": "CVE-2025-21876",
                "options": [
                  {
                    "Exploitation": "none"
                  },
                  {
                    "Automatable": "no"
                  },
                  {
                    "Technical Impact": "total"
                  }
                ],
                "role": "CISA Coordinator",
                "timestamp": "2026-10-15T21:43:25.342939Z",
                "version": "2.0.3"
              },
              "type": "ssvc"
            }
          }
        ],
        "providerMetadata": {
          "dateUpdated": "2026-10-15T21:51:54.560Z",
          "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
          "shortName": "CISA-ADP"
        },
        "title": "CISA ADP Vulnrichment"
      }
    ],
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "drivers/iommu/intel/dmar.c",
            "drivers/iommu/intel/iommu.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "4117c72938493a77ab53cc4b8284be8fb6ec8065",
              "status": "affected",
              "version": "d74169ceb0d2e32438946a2f1f9fc8c803304bd6",
              "versionType": "git"
            },
            {
              "lessThan": "c603ccbe91d189849e1439134598ec567088dcec",
              "status": "affected",
              "version": "d74169ceb0d2e32438946a2f1f9fc8c803304bd6",
              "versionType": "git"
            },
            {
              "lessThan": "b150654f74bf0df8e6a7936d5ec51400d9ec06d8",
              "status": "affected",
              "version": "d74169ceb0d2e32438946a2f1f9fc8c803304bd6",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "drivers/iommu/intel/dmar.c",
            "drivers/iommu/intel/iommu.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "6.10"
            },
            {
              "lessThan": "6.10",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.12.*",
              "status": "unaffected",
              "version": "6.12.18",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.13.*",
              "status": "unaffected",
              "version": "6.13.6",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "6.14",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.12.18",
                  "versionStartIncluding": "6.10",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.13.6",
                  "versionStartIncluding": "6.10",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.14",
                  "versionStartIncluding": "6.10",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\niommu/vt-d: Fix suspicious RCU usage\n\nCommit \u003cd74169ceb0d2\u003e (\"iommu/vt-d: Allocate DMAR fault interrupts\nlocally\") moved the call to enable_drhd_fault_handling() to a code\npath that does not hold any lock while traversing the drhd list. Fix\nit by ensuring the dmar_global_lock lock is held when traversing the\ndrhd list.\n\nWithout this fix, the following warning is triggered:\n =============================\n WARNING: suspicious RCU usage\n 6.14.0-rc3 #55 Not tainted\n -----------------------------\n drivers/iommu/intel/dmar.c:2046 RCU-list traversed in non-reader section!!\n               other info that might help us debug this:\n               rcu_scheduler_active = 1, debug_locks = 1\n 2 locks held by cpuhp/1/23:\n #0: ffffffff84a67c50 (cpu_hotplug_lock){++++}-{0:0}, at: cpuhp_thread_fun+0x87/0x2c0\n #1: ffffffff84a6a380 (cpuhp_state-up){+.+.}-{0:0}, at: cpuhp_thread_fun+0x87/0x2c0\n stack backtrace:\n CPU: 1 UID: 0 PID: 23 Comm: cpuhp/1 Not tainted 6.14.0-rc3 #55\n Call Trace:\n  \u003cTASK\u003e\n  dump_stack_lvl+0xb7/0xd0\n  lockdep_rcu_suspicious+0x159/0x1f0\n  ? __pfx_enable_drhd_fault_handling+0x10/0x10\n  enable_drhd_fault_handling+0x151/0x180\n  cpuhp_invoke_callback+0x1df/0x990\n  cpuhp_thread_fun+0x1ea/0x2c0\n  smpboot_thread_fn+0x1f5/0x2e0\n  ? __pfx_smpboot_thread_fn+0x10/0x10\n  kthread+0x12a/0x2d0\n  ? __pfx_kthread+0x10/0x10\n  ret_from_fork+0x4a/0x60\n  ? __pfx_kthread+0x10/0x10\n  ret_from_fork_asm+0x1a/0x30\n  \u003c/TASK\u003e\n\nHolding the lock in enable_drhd_fault_handling() triggers a lockdep splat\nabout a possible deadlock between dmar_global_lock and cpu_hotplug_lock.\nThis is avoided by not holding dmar_global_lock when calling\niommu_device_register(), which initiates the device probe process."
        }
      ],
      "metrics": [
        {
          "cvssV3_1": {
            "baseScore": 8.8,
            "baseSeverity": "HIGH",
            "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H",
            "version": "3.1"
          },
          "scenarios": [
            {
              "lang": "en",
              "value": "AV:L - The vulnerable code is an Intel VT-d CPU-hotplug startup callback reached only through local machine state transitions (sysfs CPU online, suspend/resume), with no network-facing input path.\nAC:L - The unsynchronized RCU-list traversal executes on every CPU-online event, which a local attacker can trigger repeatedly and at will via CPU hotplug or suspend/resume cycles, so the unprotected window is reached reliably rather than depending on chance.\nPR:L - Writing /sys/devices/system/cpu/N/online needs root, but the same callback runs on every resume from suspend, and on typical desktop/laptop deployments an unprivileged local session can request suspend through logind, so no elevated privileges are strictly required.\nUI:N - The attacker initiates the CPU-online or suspend/resume transition themselves; no action by any other user is needed.\nS:C - The corrupted object is the Intel IOMMU descriptor, and writes through a dangling iommu-\u003ereg reach DMAR hardware register windows, so the impact extends past the kernel\u0027s own authority into the DMA-isolation boundary that protects host memory from devices and assigned-device guests.\nC:H - Traversing a freed dmar_drhd_unit/intel_iommu yields a use-after-free whose reclaimed contents supply the MMIO base used by readl() in dmar_fault(), giving an arbitrary kernel/MMIO read primitive.\nI:H - The same stale iommu-\u003ereg is used for writel() to DMAR_FSTS_REG and the fault-event registers, providing an attacker-influenced arbitrary write that can corrupt kernel data or IOMMU control state.\nA:H - Dereferencing the freed DMAR unit oopses the kernel, and a non-zero return from the callback aborts the CPU-online operation, so the bug causes crashes and denial of service even when not fully exploited."
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-08-05T11:55:03.667Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/4117c72938493a77ab53cc4b8284be8fb6ec8065"
        },
        {
          "url": "https://git.kernel.org/stable/c/c603ccbe91d189849e1439134598ec567088dcec"
        },
        {
          "url": "https://git.kernel.org/stable/c/b150654f74bf0df8e6a7936d5ec51400d9ec06d8"
        }
      ],
      "title": "iommu/vt-d: Fix suspicious RCU usage",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2025-21876",
    "datePublished": "2025-03-27T14:57:06.802Z",
    "dateReserved": "2024-12-29T08:45:45.781Z",
    "dateUpdated": "2026-10-15T21:51:54.560Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2",
  "vulnerability-lookup:meta": {
    "vulnrichment": {
      "containers": "{\"adp\": [{\"title\": \"CISA ADP Vulnrichment\", \"metrics\": [{\"other\": {\"type\": \"ssvc\", \"content\": {\"id\": \"CVE-2025-21876\", \"role\": \"CISA Coordinator\", \"options\": [{\"Exploitation\": \"none\"}, {\"Automatable\": \"no\"}, {\"Technical Impact\": \"total\"}], \"version\": \"2.0.3\", \"timestamp\": \"2026-10-15T21:43:25.342939Z\"}}}], \"providerMetadata\": {\"orgId\": \"134c704f-9b21-4f2e-91b3-4a467353bcc0\", \"shortName\": \"CISA-ADP\", \"dateUpdated\": \"2026-10-15T21:43:25.818Z\"}}], \"cna\": {\"title\": \"iommu/vt-d: Fix suspicious RCU usage\", \"metrics\": [{\"cvssV3_1\": {\"version\": \"3.1\", \"baseScore\": 8.8, \"baseSeverity\": \"HIGH\", \"vectorString\": \"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H\"}, \"scenarios\": [{\"lang\": \"en\", \"value\": \"AV:L - The vulnerable code is an Intel VT-d CPU-hotplug startup callback reached only through local machine state transitions (sysfs CPU online, suspend/resume), with no network-facing input path.\\nAC:L - The unsynchronized RCU-list traversal executes on every CPU-online event, which a local attacker can trigger repeatedly and at will via CPU hotplug or suspend/resume cycles, so the unprotected window is reached reliably rather than depending on chance.\\nPR:L - Writing /sys/devices/system/cpu/N/online needs root, but the same callback runs on every resume from suspend, and on typical desktop/laptop deployments an unprivileged local session can request suspend through logind, so no elevated privileges are strictly required.\\nUI:N - The attacker initiates the CPU-online or suspend/resume transition themselves; no action by any other user is needed.\\nS:C - The corrupted object is the Intel IOMMU descriptor, and writes through a dangling iommu-\u003ereg reach DMAR hardware register windows, so the impact extends past the kernel\u0027s own authority into the DMA-isolation boundary that protects host memory from devices and assigned-device guests.\\nC:H - Traversing a freed dmar_drhd_unit/intel_iommu yields a use-after-free whose reclaimed contents supply the MMIO base used by readl() in dmar_fault(), giving an arbitrary kernel/MMIO read primitive.\\nI:H - The same stale iommu-\u003ereg is used for writel() to DMAR_FSTS_REG and the fault-event registers, providing an attacker-influenced arbitrary write that can corrupt kernel data or IOMMU control state.\\nA:H - Dereferencing the freed DMAR unit oopses the kernel, and a non-zero return from the callback aborts the CPU-online operation, so the bug causes crashes and denial of service even when not fully exploited.\"}]}], \"affected\": [{\"repo\": \"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git\", \"vendor\": \"Linux\", \"product\": \"Linux\", \"versions\": [{\"status\": \"affected\", \"version\": \"d74169ceb0d2e32438946a2f1f9fc8c803304bd6\", \"lessThan\": \"4117c72938493a77ab53cc4b8284be8fb6ec8065\", \"versionType\": \"git\"}, {\"status\": \"affected\", \"version\": \"d74169ceb0d2e32438946a2f1f9fc8c803304bd6\", \"lessThan\": \"c603ccbe91d189849e1439134598ec567088dcec\", \"versionType\": \"git\"}, {\"status\": \"affected\", \"version\": \"d74169ceb0d2e32438946a2f1f9fc8c803304bd6\", \"lessThan\": \"b150654f74bf0df8e6a7936d5ec51400d9ec06d8\", \"versionType\": \"git\"}], \"programFiles\": [\"drivers/iommu/intel/dmar.c\", \"drivers/iommu/intel/iommu.c\"], \"defaultStatus\": \"unaffected\"}, {\"repo\": \"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git\", \"vendor\": \"Linux\", \"product\": \"Linux\", \"versions\": [{\"status\": \"affected\", \"version\": \"6.10\"}, {\"status\": \"unaffected\", \"version\": \"0\", \"lessThan\": \"6.10\", \"versionType\": \"semver\"}, {\"status\": \"unaffected\", \"version\": \"6.12.18\", \"versionType\": \"semver\", \"lessThanOrEqual\": \"6.12.*\"}, {\"status\": \"unaffected\", \"version\": \"6.13.6\", \"versionType\": \"semver\", \"lessThanOrEqual\": \"6.13.*\"}, {\"status\": \"unaffected\", \"version\": \"6.14\", \"versionType\": \"original_commit_for_fix\", \"lessThanOrEqual\": \"*\"}], \"programFiles\": [\"drivers/iommu/intel/dmar.c\", \"drivers/iommu/intel/iommu.c\"], \"defaultStatus\": \"affected\"}], \"references\": [{\"url\": \"https://git.kernel.org/stable/c/4117c72938493a77ab53cc4b8284be8fb6ec8065\"}, {\"url\": \"https://git.kernel.org/stable/c/c603ccbe91d189849e1439134598ec567088dcec\"}, {\"url\": \"https://git.kernel.org/stable/c/b150654f74bf0df8e6a7936d5ec51400d9ec06d8\"}], \"x_generator\": {\"engine\": \"bippy-1.2.0\"}, \"descriptions\": [{\"lang\": \"en\", \"value\": \"In the Linux kernel, the following vulnerability has been resolved:\\n\\niommu/vt-d: Fix suspicious RCU usage\\n\\nCommit \u003cd74169ceb0d2\u003e (\\\"iommu/vt-d: Allocate DMAR fault interrupts\\nlocally\\\") moved the call to enable_drhd_fault_handling() to a code\\npath that does not hold any lock while traversing the drhd list. Fix\\nit by ensuring the dmar_global_lock lock is held when traversing the\\ndrhd list.\\n\\nWithout this fix, the following warning is triggered:\\n =============================\\n WARNING: suspicious RCU usage\\n 6.14.0-rc3 #55 Not tainted\\n -----------------------------\\n drivers/iommu/intel/dmar.c:2046 RCU-list traversed in non-reader section!!\\n               other info that might help us debug this:\\n               rcu_scheduler_active = 1, debug_locks = 1\\n 2 locks held by cpuhp/1/23:\\n #0: ffffffff84a67c50 (cpu_hotplug_lock){++++}-{0:0}, at: cpuhp_thread_fun+0x87/0x2c0\\n #1: ffffffff84a6a380 (cpuhp_state-up){+.+.}-{0:0}, at: cpuhp_thread_fun+0x87/0x2c0\\n stack backtrace:\\n CPU: 1 UID: 0 PID: 23 Comm: cpuhp/1 Not tainted 6.14.0-rc3 #55\\n Call Trace:\\n  \u003cTASK\u003e\\n  dump_stack_lvl+0xb7/0xd0\\n  lockdep_rcu_suspicious+0x159/0x1f0\\n  ? __pfx_enable_drhd_fault_handling+0x10/0x10\\n  enable_drhd_fault_handling+0x151/0x180\\n  cpuhp_invoke_callback+0x1df/0x990\\n  cpuhp_thread_fun+0x1ea/0x2c0\\n  smpboot_thread_fn+0x1f5/0x2e0\\n  ? __pfx_smpboot_thread_fn+0x10/0x10\\n  kthread+0x12a/0x2d0\\n  ? __pfx_kthread+0x10/0x10\\n  ret_from_fork+0x4a/0x60\\n  ? __pfx_kthread+0x10/0x10\\n  ret_from_fork_asm+0x1a/0x30\\n  \u003c/TASK\u003e\\n\\nHolding the lock in enable_drhd_fault_handling() triggers a lockdep splat\\nabout a possible deadlock between dmar_global_lock and cpu_hotplug_lock.\\nThis is avoided by not holding dmar_global_lock when calling\\niommu_device_register(), which initiates the device probe process.\"}], \"cpeApplicability\": [{\"nodes\": [{\"negate\": false, \"cpeMatch\": [{\"criteria\": \"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\", \"vulnerable\": true, \"versionEndExcluding\": \"6.12.18\", \"versionStartIncluding\": \"6.10\"}, {\"criteria\": \"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\", \"vulnerable\": true, \"versionEndExcluding\": \"6.13.6\", \"versionStartIncluding\": \"6.10\"}, {\"criteria\": \"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\", \"vulnerable\": true, \"versionEndExcluding\": \"6.14\", \"versionStartIncluding\": \"6.10\"}], \"operator\": \"OR\"}]}], \"providerMetadata\": {\"orgId\": \"416baaa9-dc9f-4396-8d5f-8c081fb06d67\", \"shortName\": \"Linux\", \"dateUpdated\": \"2026-08-05T11:55:03.667Z\"}}}",
      "cveMetadata": "{\"cveId\": \"CVE-2025-21876\", \"state\": \"PUBLISHED\", \"dateUpdated\": \"2026-10-15T21:51:54.560Z\", \"dateReserved\": \"2024-12-29T08:45:45.781Z\", \"assignerOrgId\": \"416baaa9-dc9f-4396-8d5f-8c081fb06d67\", \"datePublished\": \"2025-03-27T14:57:06.802Z\", \"assignerShortName\": \"Linux\"}",
      "dataType": "CVE_RECORD",
      "dataVersion": "5.2"
    }
  }
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
  • Confirmed: The vulnerability is confirmed from an analyst perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
  • Patched: This vulnerability was successfully patched by the user reporting the sighting.
  • Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
  • Not confirmed: The user expresses doubt about the veracity of the vulnerability.
  • Not patched: This vulnerability was not successfully patched by the user reporting the sighting.