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-72177mm/damon/sysfs-schemes: fix dir put orders in access_pattern_add_dirs()

Description

In the Linux kernel, the following vulnerability has been resolved: mm/damon/sysfs-schemes: fix dir put orders in access_pattern_add_dirs() Patch series "mm/damon/sysfs-schemes: fix wrong directories put orders in error paths". Error paths of damon_sysfs_access_pattern_add_dirs() and damon_sysfs_scheme_add_dirs() functions put references to directories in wrong orders. As a result, uninitialized memory dereference and/or memory leak can happen. Fix those. This patch (of 2): In access_pattern_add_dirs(), error handling path puts references starting from setup failed directories. If the failure happpened from the initial allication in the setup functions, uninitialized memory dereference happen. The allocation failures will not commonly happen, but the consequence is quite bad. Fix the wrong reference put orders. The issue was discovered [1] by Sashiko.

Timeline

  1. ID reserved

    By Linux

  2. · 6 days later

    Published

  3. · 3 months 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 88% of all CVEs (18 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
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 7e84b1f8212a038ebeee06de56db7181148fa0cd – < 0710cc97962ca3bcabaa15ce7fead300faf726cd
    • affected 7e84b1f8212a038ebeee06de56db7181148fa0cd – < a8c0592a80e954825f2ba29e7f32893f1df762f2
    • affected 7e84b1f8212a038ebeee06de56db7181148fa0cd – < e03442b0c48bdb034f5b7cf9f3b76d8025576071
    • affected 7e84b1f8212a038ebeee06de56db7181148fa0cd – < f18c561eb9c51f1ba3adb6117926a98a66599848
    • affected 7e84b1f8212a038ebeee06de56db7181148fa0cd – < ee59df7a886a35113f309e3eb791060c46f79bb1
    • affected 7e84b1f8212a038ebeee06de56db7181148fa0cd – < d58fdbe37a829fd2e5803dd4e5a72992dd8c5368
  • Linux · Linux

    • affected 5.18
    • unaffected < 5.18
    • unaffected 6.1.178 – ≤ 6.1.*
    • unaffected 6.6.145 – ≤ 6.6.*
    • unaffected 6.12.97 – ≤ 6.12.*
    • unaffected 6.18.40 – ≤ 6.18.*
    • unaffected 7.1.5 – ≤ 7.1.*
    • unaffected 7.2 – ≤ *

References

References6

Sources

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

Badge for a README or a ticket

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

Record last updated .