GHSA-QVC7-5G9J-C6V2

Vulnerability from github – Published: 2026-11-02 18:32 – Updated: 2026-11-02 18:32
VLAI
Details

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

fork: release the files of a failed fork after sched_cancel_fork()

Reorder copy_process() cleanup so sched_fork() taking scx_fork_rwsem scx_pre_fork() is safe and isn't held around exiting files. Right now, a fork that fails while another thread closed the bpf link fd will deadlock against its own read side. It also blocks every fork on the system:

copy_process()                  holds scx_fork_rwsem for read
  exit_files()
    close_files()
      filp_close_sync()
        bpf_scx_unreg()
          kthread_flush_work()  waits for the disable work
            scx_root_disable()
              percpu_down_write(&scx_fork_rwsem)

Simply release the child's files after sched_cancel_fork() dropped the lock. The task starts out as a copy of its parent so p->files points to the parent's table until copy_files() replaces it. exit_files() must not run for a fork that failed before that. Clear p->files up front so exit_files() is a no-op for those and make copy_files() set it explicitly for CLONE_FILES.

Show details on source website

{
  "affected": [],
  "aliases": [
    "CVE-2026-99217"
  ],
  "database_specific": {
    "cwe_ids": [],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2026-11-02T16:17:45Z",
    "severity": null
  },
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nfork: release the files of a failed fork after sched_cancel_fork()\n\nReorder copy_process() cleanup so sched_fork() taking scx_fork_rwsem\nscx_pre_fork() is safe and isn\u0027t held around exiting files. Right now, a\nfork that fails while another thread closed the bpf link fd will\ndeadlock against its own read side. It also blocks every fork on the\nsystem:\n\n    copy_process()                  holds scx_fork_rwsem for read\n      exit_files()\n        close_files()\n          filp_close_sync()\n            bpf_scx_unreg()\n              kthread_flush_work()  waits for the disable work\n                scx_root_disable()\n                  percpu_down_write(\u0026scx_fork_rwsem)\n\nSimply release the child\u0027s files after sched_cancel_fork() dropped the\nlock. The task starts out as a copy of its parent so p-\u003efiles points to\nthe parent\u0027s table until copy_files() replaces it. exit_files() must not\nrun for a fork that failed before that. Clear p-\u003efiles up front so\nexit_files() is a no-op for those and make copy_files() set it\nexplicitly for CLONE_FILES.",
  "id": "GHSA-qvc7-5g9j-c6v2",
  "modified": "2026-11-02T18:32:26Z",
  "published": "2026-11-02T18:32:26Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-99217"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/14c7de6ca239326b79fd3f7aee55dfada1bb72ab"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/27e1cbf8ec5f7117f6bb2d2e44030ac055f09097"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/afa8eb069694bd9f845e5e44eac6e81cbc06780e"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/f7ac8500d58e7684d37403553b1dea90ee2b27b1"
    }
  ],
  "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…

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…