GHSA-QPC9-3GVW-7VFQ

Vulnerability from github – Published: 2026-05-27 15:33 – Updated: 2026-05-27 15:33
VLAI
Details

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

mm/damon/core: validate damos_quota_goal->nid for node_mem_{used,free}_bp

Patch series "mm/damon/core: validate damos_quota_goal->nid".

node_mem[cg]_{used,free}_bp DAMOS quota goals receive the node id. The node id is used for si_meminfo_node() and NODE_DATA() without proper validation. As a result, privileged users can trigger an out of bounds memory access using DAMON_SYSFS. Fix the issues.

The issue was originally reported [1] with a fix by another author. The original author announced [2] that they will stop working including the fix that was still in the review stage. Hence I'm restarting this.

This patch (of 2):

Users can set damos_quota_goal->nid with arbitrary value for node_mem_{used,free}_bp. But DAMON core is using those for si_meminfo_node() without the validation of the value. This can result in out of bounds memory access. The issue can actually triggered using DAMON user-space tool (damo), like below.

$ sudo ./damo start --damos_action stat \
    --damos_quota_goal node_mem_used_bp 50% -1 \
    --damos_quota_interval 1s
$ sudo dmesg
[...]
[   65.565986] Unable to handle kernel NULL pointer dereference at virtual address 0000000000000098

Fix this issue by adding the validation of the given node. If an invalid node id is given, it returns 0% for used memory ratio, and 100% for free memory ratio.

Show details on source website

{
  "affected": [],
  "aliases": [
    "CVE-2026-46020"
  ],
  "database_specific": {
    "cwe_ids": [],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2026-05-27T14:17:20Z",
    "severity": null
  },
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nmm/damon/core: validate damos_quota_goal-\u003enid for node_mem_{used,free}_bp\n\nPatch series \"mm/damon/core: validate damos_quota_goal-\u003enid\".\n\nnode_mem[cg]_{used,free}_bp DAMOS quota goals receive the node id.  The\nnode id is used for si_meminfo_node() and NODE_DATA() without proper\nvalidation.  As a result, privileged users can trigger an out of bounds\nmemory access using DAMON_SYSFS.  Fix the issues.\n\nThe issue was originally reported [1] with a fix by another author.  The\noriginal author announced [2] that they will stop working including the\nfix that was still in the review stage.  Hence I\u0027m restarting this.\n\n\nThis patch (of 2):\n\nUsers can set damos_quota_goal-\u003enid with arbitrary value for\nnode_mem_{used,free}_bp.  But DAMON core is using those for\nsi_meminfo_node() without the validation of the value.  This can result in\nout of bounds memory access.  The issue can actually triggered using DAMON\nuser-space tool (damo), like below.\n\n    $ sudo ./damo start --damos_action stat \\\n    \t--damos_quota_goal node_mem_used_bp 50% -1 \\\n    \t--damos_quota_interval 1s\n    $ sudo dmesg\n    [...]\n    [   65.565986] Unable to handle kernel NULL pointer dereference at virtual address 0000000000000098\n\nFix this issue by adding the validation of the given node.  If an invalid\nnode id is given, it returns 0% for used memory ratio, and 100% for free\nmemory ratio.",
  "id": "GHSA-qpc9-3gvw-7vfq",
  "modified": "2026-05-27T15:33:21Z",
  "published": "2026-05-27T15:33:20Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-46020"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/40250b2dded0604a112be605f3828700d80ad7c2"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/b09958e235f2b9cd3898b85a8529172afa80d212"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/bcad74078708f2330a45b55358ebc38f8f4b1127"
    }
  ],
  "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…

Detection rules are retrieved from Rulezet.

Loading…

Loading…