GHSA-QW5W-3H38-X8HG

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:

mm/khugepaged: preserve dirty bits when collapsing PTE-mapped THPs

try_collapse_pte_mapped_thp() clears PTEs without transferring their dirty bits to the folio. A shmem read fault can map a clean folio writable, so a later store only dirties the PTE. Losing that dirty bit allows reclaim to discard modified data.

The assumption that regular files are read-only is also obsolete since commit 1b6444331bebb ("mm/khugepaged: enable clean pagecache folio collapse for writable files"). In any case, transferring PTE dirty bits to the folio when removing mappings (and while the folio is still mapped) is the right thing to do.

Use get_and_clear_ptes() to collect the dirty bits and mark the folio dirty before unmapping it. Update the comment.

This was reproduced with shmem using MADV_COLLAPSE followed by MADV_PAGEOUT.

Fix generated by an LLM and sent by Chris Mason in private.

[ david: adjust comment; simplify description; cover file-thp as well ]

Show details on source website

{
  "affected": [],
  "aliases": [
    "CVE-2026-99665"
  ],
  "database_specific": {
    "cwe_ids": [],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2026-11-20T06:18:00Z",
    "severity": null
  },
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nmm/khugepaged: preserve dirty bits when collapsing PTE-mapped THPs\n\ntry_collapse_pte_mapped_thp() clears PTEs without transferring their dirty\nbits to the folio. A shmem read fault can map a clean folio writable, so\na later store only dirties the PTE. Losing that dirty bit allows reclaim\nto discard modified data.\n\nThe assumption that regular files are read-only is also obsolete since\ncommit 1b6444331bebb (\"mm/khugepaged: enable clean pagecache folio collapse\nfor writable files\"). In any case, transferring PTE dirty bits to the folio\nwhen removing mappings (and while the folio is still mapped) is the right\nthing to do.\n\nUse get_and_clear_ptes() to collect the dirty bits and mark the folio\ndirty before unmapping it. Update the comment.\n\nThis was reproduced with shmem using MADV_COLLAPSE followed by\nMADV_PAGEOUT.\n\nFix generated by an LLM and sent by Chris Mason in private.\n\n[ david: adjust comment; simplify description; cover file-thp as well ]",
  "id": "GHSA-qw5w-3h38-x8hg",
  "modified": "2026-11-20T06:32:06Z",
  "published": "2026-11-20T06:32:06Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-99665"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/0af947ae4d91af0c6e9573220a1298cd8302b6c3"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/1f54708f40b8dea6951426ca567fc96160693388"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/fe2817e3d5ea347214342c9a5cd8bcbff20c0574"
    }
  ],
  "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.