GCVE Workshop - 22 September 2026 (14:00-18:00), Luxembourg Before The Vulnopticon Conference - Registration

GHSA-8279-RM4W-J7MP

Vulnerability from github – Published: 2026-09-04 18:31 – Updated: 2026-09-11 12:33
VLAI
Details

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

fuse: fix race between interrupt and resend

After commit f8fce75fedf7 ("fuse: clear intr_entry in fuse_resend and fuse_remove_pending_req") the WARN_ON(!list_empty(&req->intr_entry)) in fuse_request_free() still triggers due to the following race:

In request_wait_answer() if (test_bit(FR_SENT, &req->flags)) -> returns true

In fuse_chan_resend() clear_bit(FR_SENT, &req->flags)

In request_wait_answer() queue_interrupt(req)

Fix by:

  • move clearing FR_SENT inside fpq->lock

  • move setting FR_PENDING inside fiq->lock

  • recheck FR_SENT after acquiring fiq->lock in fuse_dev_queue_interrupt()

Show details on source website

{
  "affected": [],
  "aliases": [
    "CVE-2026-80860"
  ],
  "database_specific": {
    "cwe_ids": [],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2026-09-04T16:18:15Z",
    "severity": null
  },
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nfuse: fix race between interrupt and resend\n\nAfter commit f8fce75fedf7 (\"fuse: clear intr_entry in fuse_resend and\nfuse_remove_pending_req\") the WARN_ON(!list_empty(\u0026req-\u003eintr_entry)) in\nfuse_request_free() still triggers due to the following race:\n\nIn request_wait_answer()\n  if (test_bit(FR_SENT, \u0026req-\u003eflags)) -\u003e returns true\n\nIn fuse_chan_resend()\n  clear_bit(FR_SENT, \u0026req-\u003eflags)\n\nIn request_wait_answer()\n  queue_interrupt(req)\n\nFix by:\n\n - move clearing FR_SENT inside fpq-\u003elock\n\n - move setting FR_PENDING inside fiq-\u003elock\n\n - recheck FR_SENT after acquiring fiq-\u003elock in fuse_dev_queue_interrupt()",
  "id": "GHSA-8279-rm4w-j7mp",
  "modified": "2026-09-11T12:33:24Z",
  "published": "2026-09-04T18:31:29Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-80860"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/0f930904452945f409eeeb0c9afa08bf27185cb1"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/26fbe4bc3ef3ab0200407681cbef182af5d151de"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/ed9c881f3b498383f73c42712b359419da42a7b0"
    }
  ],
  "schema_version": "1.4.0",
  "severity": []
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

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.

Loading…

Detection rules are retrieved from Rulezet.

Loading…

Loading…

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.


Loading…