LiveActive security incident?Get immediate response
CVE Record

CVE-2022-48996: mm/damon/sysfs: fix wrong empty schemes assumption under online tuning in damon_sysfs_set_schemes()

In the Linux kernel, the following vulnerability has been resolved: mm/damon/sysfs: fix wrong empty schemes assumption under online tuning in damon_sysfs_set_schemes() Commit da87878010e5 ("mm/damon/sysfs: support online inputs update") made 'damon_sysfs_set_schemes()' to be called for running DAMON context, which could have schemes. In the case, DAMON sysfs interface is supposed to update, remove, or add schemes to reflect the sysfs files. However, the code is assuming the DAMON context wouldn't have schemes at all, and therefore creates and adds new schemes. As a result, the code doesn't work as intended for online schemes tuning and could have more than expected memory footprint. The schemes are all in the DAMON context, so it doesn't leak the memory, though. Remove the wrong asssumption (the DAMON context wouldn't have schemes) in 'damon_sysfs_set_schemes()' to fix the bug.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysislow

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel DAMON sysfs bug in online tuning. When changing DAMON schemes while monitoring is running, the kernel may add duplicate schemes instead of updating existing ones. The documented impact is incorrect tuning behavior and higher-than-expected memory footprint, not a memory leak or confirmed compromise path.

Executive priority

Handle through normal kernel maintenance unless DAMON sysfs tuning is actively used on sensitive production systems. There is no cited evidence of active exploitation or severe security impact in the provided sources.

Technical view

damon_sysfs_set_schemes() wrongly assumed a running DAMON context had no schemes after online input updates were introduced. During online sysfs tuning it could create and attach new schemes instead of updating, removing, or adding only as needed. The fix removes that empty-schemes assumption.

Likely exposure

Exposure appears limited to Linux systems running affected kernels and using the DAMON sysfs interface for online schemes tuning. Systems not using DAMON sysfs tuning are less likely to experience the documented impact.

Exploitation context

The source bundle does not show active exploitation, public exploit activity, or KEV listing. The described issue is operational correctness and memory footprint growth during online tuning, with no documented privilege escalation or remote attack vector.

Researcher notes

Evidence is narrow: the CVE text describes a DAMON sysfs logic bug and memory-footprint side effect. No CVSS, CWE, exploitability analysis, or downstream vendor advisories are included. Treat product impact beyond Linux kernel DAMON as unproven.

Mitigation direction

  • Apply a vendor kernel update that includes the referenced stable fixes.
  • Prioritize systems using DAMON sysfs online scheme tuning.
  • Check Linux distribution advisories before assuming upstream version mapping applies.
  • Avoid online DAMON scheme changes on affected kernels where operationally feasible.

Validation and detection

  • Inventory kernel versions against the affected 5.19 through 6.1 range stated in the CVE data.
  • Confirm whether DAMON sysfs is enabled or used in production workflows.
  • Verify patched kernels include the referenced stable commit fixes.
  • Monitor DAMON-managed hosts for unexpected memory footprint during tuning changes.
Prepared
Confidence
medium
Sources
4

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2022-48996 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
1ADP providers
3Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxda87878010e59869d4d27b3c01ecc8ec06ff4a20, da87878010e59869d4d27b3c01ecc8ec06ff4a20unaffected
LinuxLinux5.19, 0, 6.0.12, 6.1affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.