Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-72169kho: make sure scratch size is always aligned by CMA_MIN_ALIGNMENT_BYTES

Description

In the Linux kernel, the following vulnerability has been resolved: kho: make sure scratch size is always aligned by CMA_MIN_ALIGNMENT_BYTES When using scratch_scale, the scratch sizes are rounded up to CMA_MIN_ALIGNMENT_BYTES since they will be released as MIGRATE_CMA. This is not done when using fixed scratch sizes via command line. This can result in user specifying a size which is not aligned, and thus kernel releasing a pageblock that is only partially scratch. Do the rounding up for both cases in scratch_size_update().

Timeline

  1. ID reserved

    By Linux

  2. · 6 days later

    Published

  3. · 2 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.21% · top 89% of all CVEs (15 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected 3dc92c311498c4d307cfdd0c6c3ac9355b50f683 – < b8271be34bce151597da5b5179e0648c281322a4
    • affected 3dc92c311498c4d307cfdd0c6c3ac9355b50f683 – < 9fefab759f59bf891bef7be15aee4bc7caec7ec3
    • affected 3dc92c311498c4d307cfdd0c6c3ac9355b50f683 – < 0e39380a7316122e1b00012b3f3cd3e318b3e7d3
  • Linux · Linux

    • affected 6.16
    • unaffected < 6.16
    • unaffected 6.18.42 – ≤ 6.18.*
    • unaffected 7.1.5 – ≤ 7.1.*
    • unaffected 7.2 – ≤ *

References

References3

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-72169 badge
[![CVE-2026-72169](https://cveledger.app/badge/CVE-2026-72169.svg)](https://cveledger.app/cve/CVE-2026-72169)

Record last updated .