GHSA-CQ67-V8MM-J2C8

Vulnerability from github – Published: 2026-11-20 06:32 – Updated: 2026-11-20 06:32
VLAI
Details

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

khugepaged: fix readahead lock inversion in collapse_file()

collapse_file() can call page_cache_sync_readahead() while still holding source folios locked. If truncate holds mapping->invalidate_lock exclusively and waits for one of those folios, readahead waits for invalidate_lock and neither side can make progress.

We need to release those folio locks before starting readahead. On a page cache miss, roll back first, populate the collapse range, and retry once. Doing readahead after rollback avoids an extra pass when all folios are already present. If another miss occurs on retry, give up rather than keep retrying while truncate or reclaim removes folios.

Keep page_cache_sync_readahead() and wait for read I/O with filemap_lock_folio(), releasing each folio before moving to the next. The existing uptodate check during collapse still handles read errors.

Shmem uses shmem_get_folio() for swapin and fallocated folios without taking mapping->invalidate_lock, so it is unaffected.

Show details on source website

{
  "affected": [],
  "aliases": [
    "CVE-2026-99643"
  ],
  "database_specific": {
    "cwe_ids": [],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2026-11-20T06:17:57Z",
    "severity": null
  },
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nkhugepaged: fix readahead lock inversion in collapse_file()\n\ncollapse_file() can call page_cache_sync_readahead() while still holding\nsource folios locked. If truncate holds mapping-\u003einvalidate_lock\nexclusively and waits for one of those folios, readahead waits for\ninvalidate_lock and neither side can make progress.\n\nWe need to release those folio locks before starting readahead. On a page\ncache miss, roll back first, populate the collapse range, and retry once.\nDoing readahead after rollback avoids an extra pass when all folios are\nalready present. If another miss occurs on retry, give up rather than keep\nretrying while truncate or reclaim removes folios.\n\nKeep page_cache_sync_readahead() and wait for read I/O with\nfilemap_lock_folio(), releasing each folio before moving to the next. The\nexisting uptodate check during collapse still handles read errors.\n\nShmem uses shmem_get_folio() for swapin and fallocated folios without\ntaking mapping-\u003einvalidate_lock, so it is unaffected.",
  "id": "GHSA-cq67-v8mm-j2c8",
  "modified": "2026-11-20T06:32:05Z",
  "published": "2026-11-20T06:32:05Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-99643"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/b9b3c367faf1929fb8192a846b3604ad7eced008"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/eadce52a9ef657d561b3e76c9b5f178bd99735f5"
    }
  ],
  "schema_version": "1.4.0",
  "severity": []
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.

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.
Vulnerability timeline

Sightings and recorded dates, grouped by day · UTC

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.

Events included in the timeline

Loading timeline…


    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.