Vulnerability-Lookup

GHSA-H4GF-5W5M-M3J2

Vulnerability from github – Published: 2026-09-24 18:31 – Updated: 2026-09-24 18:31

Details

In the Linux kernel, the following vulnerability has been resolved:

drm/amdgpu: flush pending RCU callbacks on module unload

Call rcu_barrier() in module exit to wait for outstanding call_rcu() callbacks before freeing module text, preventing late callback execution in freed memory.

BUG: unable to handle page fault for address: ffffffffc1d59c40 PGD 6a12067 P4D 6a12067 PUD 6a14067 PMD 13698b067 PTE 0 Oops: 0010 [#1] SMP NOPTI RIP: 0010:0xffffffffc1d59c40 Code: Unable to access opcode bytes at RIP 0xffffffffc1d59c16. RSP: 0018:ffffc900198c0f28 EFLAGS: 00010286 RAX: ffffffffc1d59c40 RBX: ffff897c7d6b61c0 RCX: ffff88826aff4590 RDX: ffff8884d8b35490 RSI: ffffc900198c0f30 RDI: ffff88812af67290 RBP: 000000000000000a (DONE segment entries) R08: 0000000000000000 R09: 0000000000000100 R10: 0000000000000000 R11: ffffffff82a06100 R12: ffff88811a4e3700 R13: 0000000000000000 R14: ffff897c7d6b6270 R15: 0000000000000000 FS: 0000000000000000(0000) GS:ffff897c7d680000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: ffffffffc1d59c16 CR3: 00000104a980a001 CR4: 0000000002770ee0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe07f0 DR7: 0000000000000400 PKRU: 55555554 Call Trace: ? rcu_do_batch+0x163/0x450 ? rcu_core+0x177/0x1c0 ? __do_softirq+0xc1/0x280 ? asm_call_irq_on_stack+0xf/0x20 ? do_softirq_own_stack+0x37/0x50 ? irq_exit_rcu+0xc4/0x100 ? sysvec_apic_timer_interrupt+0x36/0x80 ? asm_sysvec_apic_timer_interrupt+0x12/0x20 ? cpuidle_enter_state+0xd4/0x360 ? cpuidle_enter+0x29/0x40 ? cpuidle_idle_call+0x108/0x1a0 ? do_idle+0x77/0xf0 ? cpu_startup_entry+0x19/0x20 ? secondary_startup_64_no_verify+0xbf/0xcb

(cherry picked from commit feaa5039f6c12acc9aa934c2d45dcd251a12c69f)

Show details on source website

JSON

To clipboard

{
  "affected": [],
  "aliases": [
    "CVE-2026-93809"
  ],
  "database_specific": {
    "cwe_ids": [],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2026-09-24T17:17:13Z",
    "severity": null
  },
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/amdgpu: flush pending RCU callbacks on module unload\n\nCall rcu_barrier() in module exit to wait for outstanding call_rcu() callbacks\nbefore freeing module text, preventing late callback execution in freed memory.\n\nBUG: unable to handle page fault for address: ffffffffc1d59c40\nPGD 6a12067 P4D 6a12067 PUD 6a14067 PMD 13698b067 PTE 0\nOops: 0010 [#1] SMP NOPTI\nRIP: 0010:0xffffffffc1d59c40\nCode: Unable to access opcode bytes at RIP 0xffffffffc1d59c16.\nRSP: 0018:ffffc900198c0f28 EFLAGS: 00010286\nRAX: ffffffffc1d59c40 RBX: ffff897c7d6b61c0 RCX: ffff88826aff4590\nRDX: ffff8884d8b35490 RSI: ffffc900198c0f30 RDI: ffff88812af67290\nRBP: 000000000000000a (DONE segment entries) R08: 0000000000000000 R09: 0000000000000100\nR10: 0000000000000000 R11: ffffffff82a06100 R12: ffff88811a4e3700\nR13: 0000000000000000 R14: ffff897c7d6b6270 R15: 0000000000000000\nFS:  0000000000000000(0000) GS:ffff897c7d680000(0000) knlGS:0000000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: ffffffffc1d59c16 CR3: 00000104a980a001 CR4: 0000000002770ee0\nDR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\nDR3: 0000000000000000 DR6: 00000000fffe07f0 DR7: 0000000000000400\nPKRU: 55555554\nCall Trace:\n \u003cIRQ\u003e\n ? rcu_do_batch+0x163/0x450\n ? rcu_core+0x177/0x1c0\n ? __do_softirq+0xc1/0x280\n ? asm_call_irq_on_stack+0xf/0x20\n \u003c/IRQ\u003e\n ? do_softirq_own_stack+0x37/0x50\n ? irq_exit_rcu+0xc4/0x100\n ? sysvec_apic_timer_interrupt+0x36/0x80\n ? asm_sysvec_apic_timer_interrupt+0x12/0x20\n ? cpuidle_enter_state+0xd4/0x360\n ? cpuidle_enter+0x29/0x40\n ? cpuidle_idle_call+0x108/0x1a0\n ? do_idle+0x77/0xf0\n ? cpu_startup_entry+0x19/0x20\n ? secondary_startup_64_no_verify+0xbf/0xcb\n\n(cherry picked from commit feaa5039f6c12acc9aa934c2d45dcd251a12c69f)",
  "id": "GHSA-h4gf-5w5m-m3j2",
  "modified": "2026-09-24T18:31:30Z",
  "published": "2026-09-24T18:31:29Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-93809"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/27d43ad57759c73b8fad5b2bad62a0616e116bbc"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/5063ae84c45299a100bf1d6ed11945f688063649"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/67a654b41cfa73c3b83402c4a01b2689cad5b9bc"
    }
  ],
  "schema_version": "1.4.0",
  "severity": []
}

CVE-2026-93809 (GCVE-0-2026-93809)

Vulnerability from cvelistv5 – Published: 2026-09-24 16:02 – Updated: 2026-09-25 12:43

Title

drm/amdgpu: flush pending RCU callbacks on module unload

Summary

In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: flush pending RCU callbacks on module unload Call rcu_barrier() in module exit to wait for outstanding call_rcu() callbacks before freeing module text, preventing late callback execution in freed memory. BUG: unable to handle page fault for address: ffffffffc1d59c40 PGD 6a12067 P4D 6a12067 PUD 6a14067 PMD 13698b067 PTE 0 Oops: 0010 [#1] SMP NOPTI RIP: 0010:0xffffffffc1d59c40 Code: Unable to access opcode bytes at RIP 0xffffffffc1d59c16. RSP: 0018:ffffc900198c0f28 EFLAGS: 00010286 RAX: ffffffffc1d59c40 RBX: ffff897c7d6b61c0 RCX: ffff88826aff4590 RDX: ffff8884d8b35490 RSI: ffffc900198c0f30 RDI: ffff88812af67290 RBP: 000000000000000a (DONE segment entries) R08: 0000000000000000 R09: 0000000000000100 R10: 0000000000000000 R11: ffffffff82a06100 R12: ffff88811a4e3700 R13: 0000000000000000 R14: ffff897c7d6b6270 R15: 0000000000000000 FS: 0000000000000000(0000) GS:ffff897c7d680000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: ffffffffc1d59c16 CR3: 00000104a980a001 CR4: 0000000002770ee0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe07f0 DR7: 0000000000000400 PKRU: 55555554 Call Trace: <IRQ> ? rcu_do_batch+0x163/0x450 ? rcu_core+0x177/0x1c0 ? __do_softirq+0xc1/0x280 ? asm_call_irq_on_stack+0xf/0x20 </IRQ> ? do_softirq_own_stack+0x37/0x50 ? irq_exit_rcu+0xc4/0x100 ? sysvec_apic_timer_interrupt+0x36/0x80 ? asm_sysvec_apic_timer_interrupt+0x12/0x20 ? cpuidle_enter_state+0xd4/0x360 ? cpuidle_enter+0x29/0x40 ? cpuidle_idle_call+0x108/0x1a0 ? do_idle+0x77/0xf0 ? cpu_startup_entry+0x19/0x20 ? secondary_startup_64_no_verify+0xbf/0xcb (cherry picked from commit feaa5039f6c12acc9aa934c2d45dcd251a12c69f)

Severity

No CVSS data available.

Assigner

Linux CNA under the mitre root

CNA scorecard D 53/100 over 6641 records in the last 180 days details

References

1 reference

URL	Tags
https://git.kernel.org/stable/c/67a654b41cfa73c3b…

Impacted products

2 products

Vendor	Product	Version
Linux	Linux	Affected: 4e02e0afa95f691dc7cc17538cdd648089a843f0 , < 67a654b41cfa73c3b83402c4a01b2689cad5b9bc (git)
Linux	Linux	Affected: 7.1 Unaffected: 0 , < 7.1 (semver) Unaffected: 7.2 , ≤ * (original_commit_for_fix)

Show details on NVD website

JSON

To clipboard

{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "drivers/gpu/drm/amd/amdgpu/amdgpu_drv.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "67a654b41cfa73c3b83402c4a01b2689cad5b9bc",
              "status": "affected",
              "version": "4e02e0afa95f691dc7cc17538cdd648089a843f0",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "drivers/gpu/drm/amd/amdgpu/amdgpu_drv.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "7.1"
            },
            {
              "lessThan": "7.1",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "7.2",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.2",
                  "versionStartIncluding": "7.1",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/amdgpu: flush pending RCU callbacks on module unload\n\nCall rcu_barrier() in module exit to wait for outstanding call_rcu() callbacks\nbefore freeing module text, preventing late callback execution in freed memory.\n\nBUG: unable to handle page fault for address: ffffffffc1d59c40\nPGD 6a12067 P4D 6a12067 PUD 6a14067 PMD 13698b067 PTE 0\nOops: 0010 [#1] SMP NOPTI\nRIP: 0010:0xffffffffc1d59c40\nCode: Unable to access opcode bytes at RIP 0xffffffffc1d59c16.\nRSP: 0018:ffffc900198c0f28 EFLAGS: 00010286\nRAX: ffffffffc1d59c40 RBX: ffff897c7d6b61c0 RCX: ffff88826aff4590\nRDX: ffff8884d8b35490 RSI: ffffc900198c0f30 RDI: ffff88812af67290\nRBP: 000000000000000a (DONE segment entries) R08: 0000000000000000 R09: 0000000000000100\nR10: 0000000000000000 R11: ffffffff82a06100 R12: ffff88811a4e3700\nR13: 0000000000000000 R14: ffff897c7d6b6270 R15: 0000000000000000\nFS:  0000000000000000(0000) GS:ffff897c7d680000(0000) knlGS:0000000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: ffffffffc1d59c16 CR3: 00000104a980a001 CR4: 0000000002770ee0\nDR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\nDR3: 0000000000000000 DR6: 00000000fffe07f0 DR7: 0000000000000400\nPKRU: 55555554\nCall Trace:\n \u003cIRQ\u003e\n ? rcu_do_batch+0x163/0x450\n ? rcu_core+0x177/0x1c0\n ? __do_softirq+0xc1/0x280\n ? asm_call_irq_on_stack+0xf/0x20\n \u003c/IRQ\u003e\n ? do_softirq_own_stack+0x37/0x50\n ? irq_exit_rcu+0xc4/0x100\n ? sysvec_apic_timer_interrupt+0x36/0x80\n ? asm_sysvec_apic_timer_interrupt+0x12/0x20\n ? cpuidle_enter_state+0xd4/0x360\n ? cpuidle_enter+0x29/0x40\n ? cpuidle_idle_call+0x108/0x1a0\n ? do_idle+0x77/0xf0\n ? cpu_startup_entry+0x19/0x20\n ? secondary_startup_64_no_verify+0xbf/0xcb\n\n(cherry picked from commit feaa5039f6c12acc9aa934c2d45dcd251a12c69f)"
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-09-25T12:43:17.218Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/67a654b41cfa73c3b83402c4a01b2689cad5b9bc"
        }
      ],
      "title": "drm/amdgpu: flush pending RCU callbacks on module unload",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2026-93809",
    "datePublished": "2026-09-24T16:02:44.613Z",
    "dateReserved": "2026-09-18T17:59:28.790Z",
    "dateUpdated": "2026-09-25T12:43:17.218Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2"
}

Sightings

Author	Source	Type	Date	Other

Nomenclature

Seen: The vulnerability was mentioned, discussed, or observed by the user.
Confirmed: The vulnerability has been validated from an analyst's perspective.
Published Proof of Concept: A public proof of concept is available for this vulnerability.
Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
Not confirmed: The user expressed doubt about the validity of the vulnerability.
Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.

Vulnerability timeline

Sightings and recorded dates, grouped by day · UTC

Order JSON

How durations are calculated

Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.

Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.

Publication & reservation Sightings KEV catalogs Other timestamps

Loading timeline…

The MITRE ATT&CK techniques below are AI-generated suggestions, inferred from the description of the vulnerability by the CIRCL/vulnerability-attack-technique-classification-roberta-base model, served locally by ML-Gateway. They have not been verified by an analyst and are provided for guidance only.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.

Related by attack behaviour

Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.

Action not permitted