BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2024
CVE-2022-48991High confidence

mm/khugepaged: invoke MMU notifiers in shmem/file collapse paths

Linux · Linux

8.8HighCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 199 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityHighOperational priority:Medium, lowered one band.downgradedsince 5 Aug 2026

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • Exploitation requires an existing local or physical foothold with privileges.
  • EPSS is 0.25% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict local access and enforce least privilege on affected hosts.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs Linux Linux and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: As exposure requiresRemediation target: Within 365 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 199 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

5 package states
Package result overrides the generic status

BlackTree has verified remediation for at least one product or source, but the relevant distribution still reports no fixed package for 1 affected package state shown here. Treat those rows as affected with no fix until that distribution publishes a fixed version.

Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.4-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.4-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.4-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.4-1Debian Security Tracker ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-raspi-realtimeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

1 current
CVE-2022-48991 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitykernel: mm/khugepaged: invoke MMU notifiers in shmem/file collapse paths
198 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • kernel as a component of Red Hat Enterprise Linux 6
  • kernel-abi-whitelists as a component of Red Hat Enterprise Linux 6
  • kernel-bootwrapper as a component of Red Hat Enterprise Linux 6
  • kernel-debug as a component of Red Hat Enterprise Linux 6
  • kernel-debug-devel as a component of Red Hat Enterprise Linux 6
  • kernel-devel as a component of Red Hat Enterprise Linux 6
  • kernel-doc as a component of Red Hat Enterprise Linux 6
  • kernel-firmware as a component of Red Hat Enterprise Linux 6
  • kernel-headers as a component of Red Hat Enterprise Linux 6
  • kernel-kdump as a component of Red Hat Enterprise Linux 6
  • kernel-kdump-devel as a component of Red Hat Enterprise Linux 6
  • kernel.src as a component of Red Hat Enterprise Linux 6
Summary
A flaw was found in the Linux kernel. The memory management unit (MMU) notifiers were not properly invoked when page table entries were removed during certain memory collapse operations. This oversight could lead to a use-after-free vulnerability, where the system attempts to access deallocated memory. A local attacker could potentially exploit this flaw to cause a denial of service or achieve privilege escalation.
Remediation
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2022-53870

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 199 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

In the Linux kernel, the following vulnerability has been resolved: mm/khugepaged: invoke MMU notifiers in shmem/file collapse paths Any codepath that zaps page table entries must invoke MMU notifiers to ensure that secondary MMUs (like KVM) don't keep accessing pages which aren't mapped anymore. Secondary MMUs don't hold their own references to pages that are mirrored over, so failing to notify them can lead to page use-after-free. I'm marking this as addressing an issue introduced in commit f3f0e1d2150b ("khugepaged: add support of collapse for tmpfs/shmem pages"), but most of the security impact of this only came in commit 27e1f8273113 ("khugepaged: enable collapse pmd for pte-mapped THP"), which actually omitted flushes for the removal of present PTEs, not just for the removal of empty page tables.

What

In the Linux kernel, the following vulnerability has been resolved: mm/khugepaged: invoke MMU notifiers in shmem/file collapse paths Any codepath that zaps page table entries must invoke MMU notifiers to ensure that secondary MMUs (like KVM) don't keep accessing pages which aren't mapped anymore. Secondary MMUs don't hold their own references to pages that are mirrored over, so failing to notify them can lead to page use-after-free. I'm marking this as addressing an issue introduced in commit f3f0e1d2150b ("khugepaged: add support of collapse for tmpfs/shmem pages"), but most of the security impact of this only came in commit 27e1f8273113 ("khugepaged: enable collapse pmd for pte-mapped THP"), which actually omitted flushes for the removal of present PTEs, not just for the removal of empty page tables.

Why

The program can continue using memory after it has been released, producing unsafe and attacker-influenceable behaviour.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

In the Linux kernel, the following vulnerability has been resolved: mm/khugepaged: invoke MMU notifiers in shmem/file collapse paths Any codepath that zaps page table entries must invoke MMU notifiers to ensure that secondary MMUs (like KVM) don't keep accessing pages which aren't mapped anymore. Secondary MMUs don't hold their own references to pages that are mirrored over, so failing to notify them can lead to page use-after-free. I'm marking this as addressing an issue introduced in commit f3f0e1d2150b ("khugepaged: add support of collapse for tmpfs/shmem pages"), but most of the security impact of this only came in commit 27e1f8273113 ("khugepaged: enable collapse pmd for pte-mapped THP"), which actually omitted flushes for the removal of present PTEs, not just for the removal of empty page tables.

Why

The program can continue using memory after it has been released, producing unsafe and attacker-influenceable behaviour.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
local access → Use After Free → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Local
Privileges required
Low: a basic authenticated account is required
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Changed: exploitation can affect a different security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-416 ↗

CWE-416: Use After Free. The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory belongs to the code that operates on the new pointer.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRLowPrivileges required: The attacker needs basic user-level privileges.UINoneUser interaction: No action by another user is required.SChangedScope: The attack can affect a component governed by a different security authority.CHighConfidentiality impact: A successful attack can cause a major loss.IHighIntegrity impact: A successful attack can cause a major loss.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.
CWE-416
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

BSI · German · WID-SEC-2024-3251Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service

Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder andere, nicht näher bekannte Auswirkungen zu erzielen..

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20241023Security Bulletin 23 Oct 2024

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 23 Oct 2024, published on 23 October 2024. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0024Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2022-48966 Référence CVE CVE-2022-48967 https://www.cve.org/CVERecord?id=CVE-2022-48967 Référence CVE CVE-2022-48969 https://www.cve.org/CVERecord?id=CVE-2022-48969 Référence CVE CVE-2022-48971 https://www.cve.org/CVERecord?id=CVE-2022-48971 Référence CVE CVE-2022-48972 https://www.cve.org/CVERecord?id=CVE-2022-48972 Référence CVE CVE-2022-48973 https://www.cve.org/CVERecord?id=CVE-2022-48973 Référence CVE CVE-2022-48978 https://www.cve.org/CVERecord?id=CVE-2022-48978 Référence CVE CVE-2022-48985 https://www.cve.org/CVERecord?id=CVE-2022-48985 Référence CVE CVE-2022-48988 https://www.cve.org/CVERecord?id=CVE-2022-48988 Référence CVE CVE-2022-48991 https://www.cve.org/CVERecord?id=CVE-2022-48991 Référence CVE CVE-2022-48992 https://www.cve.org/CVERecord?id=CVE-2022-48992 Référence CVE CVE-2022-48997 https://www.cve.org/CVERecord?id=CVE-2022-48997 Référence CVE CVE-2022-49000 https://www.cve.org/CVERecord?id=CVE-2022-49000 Référence CVE CVE-2022-49002 https://www.cve.org/CVERecord?id=CVE-2022-49002 Référence CVE CVE-2022-49010 https://www.cve.org/CVERecord?id=CVE-2022-49010 Référence CVE CVE-2022-49011 https://www.cve.org/CVERecord?id=CVE-2022-49011 Référence CVE CVE-2022-49014 https://www.cve.org/CVERecord?id=CVE-2022-49014 Référence CVE CVE-2022-49015 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2024-AVI-1102Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2022-48980 Référence CVE CVE-2022-48981 https://www.cve.org/CVERecord?id=CVE-2022-48981 Référence CVE CVE-2022-48982 https://www.cve.org/CVERecord?id=CVE-2022-48982 Référence CVE CVE-2022-48983 https://www.cve.org/CVERecord?id=CVE-2022-48983 Référence CVE CVE-2022-48985 https://www.cve.org/CVERecord?id=CVE-2022-48985 Référence CVE CVE-2022-48987 https://www.cve.org/CVERecord?id=CVE-2022-48987 Référence CVE CVE-2022-48988 https://www.cve.org/CVERecord?id=CVE-2022-48988 Référence CVE CVE-2022-48989 https://www.cve.org/CVERecord?id=CVE-2022-48989 Référence CVE CVE-2022-48990 https://www.cve.org/CVERecord?id=CVE-2022-48990 Référence CVE CVE-2022-48991 https://www.cve.org/CVERecord?id=CVE-2022-48991 Référence CVE CVE-2022-48992 https://www.cve.org/CVERecord?id=CVE-2022-48992 Référence CVE CVE-2022-48994 https://www.cve.org/CVERecord?id=CVE-2022-48994 Référence CVE CVE-2022-48995 https://www.cve.org/CVERecord?id=CVE-2022-48995 Référence CVE CVE-2022-48997 https://www.cve.org/CVERecord?id=CVE-2022-48997 Référence CVE CVE-2022-48999 https://www.cve.org/CVERecord?id=CVE-2022-48999 Référence CVE CVE-2022-49000 https://www.cve.org/CVERecord?id=CVE-2022-49000 Référence CVE CVE-2022-49002 https://www.cve.org/CVERecord?id=CVE-2022-49002 Référence CVE CVE-2022-49003 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2024-AVI-1048Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2022-48972 Référence CVE CVE-2022-48973 https://www.cve.org/CVERecord?id=CVE-2022-48973 Référence CVE CVE-2022-48975 https://www.cve.org/CVERecord?id=CVE-2022-48975 Référence CVE CVE-2022-48977 https://www.cve.org/CVERecord?id=CVE-2022-48977 Référence CVE CVE-2022-48978 https://www.cve.org/CVERecord?id=CVE-2022-48978 Référence CVE CVE-2022-48981 https://www.cve.org/CVERecord?id=CVE-2022-48981 Référence CVE CVE-2022-48985 https://www.cve.org/CVERecord?id=CVE-2022-48985 Référence CVE CVE-2022-48987 https://www.cve.org/CVERecord?id=CVE-2022-48987 Référence CVE CVE-2022-48988 https://www.cve.org/CVERecord?id=CVE-2022-48988 Référence CVE CVE-2022-48991 https://www.cve.org/CVERecord?id=CVE-2022-48991 Référence CVE CVE-2022-48992 https://www.cve.org/CVERecord?id=CVE-2022-48992 Référence CVE CVE-2022-48994 https://www.cve.org/CVERecord?id=CVE-2022-48994 Référence CVE CVE-2022-48995 https://www.cve.org/CVERecord?id=CVE-2022-48995 Référence CVE CVE-2022-48997 https://www.cve.org/CVERecord?id=CVE-2022-48997 Référence CVE CVE-2022-48999 https://www.cve.org/CVERecord?id=CVE-2022-48999 Référence CVE CVE-2022-49000 https://www.cve.org/CVERecord?id=CVE-2022-49000 Référence CVE CVE-2022-49002 https://www.cve.org/CVERecord?id=CVE-2022-49002 Référence CVE CVE-2022-49003 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2024-AVI-1033Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2022-48972 Référence CVE CVE-2022-48973 https://www.cve.org/CVERecord?id=CVE-2022-48973 Référence CVE CVE-2022-48975 https://www.cve.org/CVERecord?id=CVE-2022-48975 Référence CVE CVE-2022-48977 https://www.cve.org/CVERecord?id=CVE-2022-48977 Référence CVE CVE-2022-48978 https://www.cve.org/CVERecord?id=CVE-2022-48978 Référence CVE CVE-2022-48981 https://www.cve.org/CVERecord?id=CVE-2022-48981 Référence CVE CVE-2022-48985 https://www.cve.org/CVERecord?id=CVE-2022-48985 Référence CVE CVE-2022-48987 https://www.cve.org/CVERecord?id=CVE-2022-48987 Référence CVE CVE-2022-48988 https://www.cve.org/CVERecord?id=CVE-2022-48988 Référence CVE CVE-2022-48991 https://www.cve.org/CVERecord?id=CVE-2022-48991 Référence CVE CVE-2022-48992 https://www.cve.org/CVERecord?id=CVE-2022-48992 Référence CVE CVE-2022-48994 https://www.cve.org/CVERecord?id=CVE-2022-48994 Référence CVE CVE-2022-48995 https://www.cve.org/CVERecord?id=CVE-2022-48995 Référence CVE CVE-2022-48997 https://www.cve.org/CVERecord?id=CVE-2022-48997 Référence CVE CVE-2022-48999 https://www.cve.org/CVERecord?id=CVE-2022-48999 Référence CVE CVE-2022-49000 https://www.cve.org/CVERecord?id=CVE-2022-49000 Référence CVE CVE-2022-49002 https://www.cve.org/CVERecord?id=CVE-2022-49002 Référence CVE CVE-2022-49003 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2024-AVI-0999Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2022-48973 Référence CVE CVE-2022-48975 https://www.cve.org/CVERecord?id=CVE-2022-48975 Référence CVE CVE-2022-48977 https://www.cve.org/CVERecord?id=CVE-2022-48977 Référence CVE CVE-2022-48978 https://www.cve.org/CVERecord?id=CVE-2022-48978 Référence CVE CVE-2022-48980 https://www.cve.org/CVERecord?id=CVE-2022-48980 Référence CVE CVE-2022-48981 https://www.cve.org/CVERecord?id=CVE-2022-48981 Référence CVE CVE-2022-48985 https://www.cve.org/CVERecord?id=CVE-2022-48985 Référence CVE CVE-2022-48987 https://www.cve.org/CVERecord?id=CVE-2022-48987 Référence CVE CVE-2022-48988 https://www.cve.org/CVERecord?id=CVE-2022-48988 Référence CVE CVE-2022-48991 https://www.cve.org/CVERecord?id=CVE-2022-48991 Référence CVE CVE-2022-48992 https://www.cve.org/CVERecord?id=CVE-2022-48992 Référence CVE CVE-2022-48994 https://www.cve.org/CVERecord?id=CVE-2022-48994 Référence CVE CVE-2022-48995 https://www.cve.org/CVERecord?id=CVE-2022-48995 Référence CVE CVE-2022-48997 https://www.cve.org/CVERecord?id=CVE-2022-48997 Référence CVE CVE-2022-48999 https://www.cve.org/CVERecord?id=CVE-2022-48999 Référence CVE CVE-2022-49000 https://www.cve.org/CVERecord?id=CVE-2022-49000 Référence CVE CVE-2022-49002 https://www.cve.org/CVERecord?id=CVE-2022-49002 Référence CVE CVE-2022-49003 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2022-025553Linux の Linux Kernel における解放済みメモリの使用に関する脆弱性

Linux の Linux Kernel には、解放済みメモリの使用に関する脆弱性が存在します。

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix availability varies by product
Affected
Fixed
Linux: < 4.8, 4.9.337 ≤ 4.9.*, 4.14.303 ≤ 4.14.*, 4.19.270 ≤ 4.19.*, 5.4.227 ≤ 5.4.*, 5.10.159 ≤ 5.10.*, 5.15.83 ≤ 5.15.*, 6.0.13 ≤ 6.0.*, 6.1 ≤ *
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
Workaround
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.
04

Evidence and provenance

Published 21 Oct 2024 · Last source change 5 Aug 2026, 08:53 UTC · CWE-416 · Use After Free

CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2022-53870
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceNIST NVD
NVD statusNVD modified after enrichment

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗

No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.

Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2022-48991 · cve.blacktree.nl