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

ext4: avoid resizing to a partial cluster size

Linux · Linux

5.5MediumCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 3 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 severityMediumOperational priority:Low, lowered one band.downgradedsince 11 May 2026

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • Exploitation requires an existing local or physical foothold with privileges.
  • EPSS is 0.20% 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: No default targetRemediation target: Normal maintenance

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 3 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.

7 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 3 affected package states 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.0.2-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.0.2-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.0.2-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.0.2-1Debian Security Tracker ↗Source updated 5 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
Ubuntu 24.04 LTSnoble · standard archivelinux-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
Ubuntu 24.04 LTSnoble · standard archivelinux-riscvAffected, 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-50020 · CSAF 2.0 · revision 59 · interimSUSE Product Security TeamCVE-2022-50020
201 known affected

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

  • kernel-default as component of SLES-LTSS-TERADATA 15 SP2
  • kernel-source as component of SLES-LTSS-TERADATA 15 SP2
  • kernel-default as component of SUSE Linux Enterprise High Performance Computing 12 SP2
  • kernel-default-base as component of SUSE Linux Enterprise High Performance Computing 12 SP2
  • kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 12 SP2
  • kernel-default-man as component of SUSE Linux Enterprise High Performance Computing 12 SP2
  • kernel-devel as component of SUSE Linux Enterprise High Performance Computing 12 SP2
  • kernel-macros as component of SUSE Linux Enterprise High Performance Computing 12 SP2
  • kernel-source as component of SUSE Linux Enterprise High Performance Computing 12 SP2
  • kernel-default as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • kernel-default-base as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 12 SP4
Summary
In the Linux kernel, the following vulnerability has been resolved: ext4: avoid resizing to a partial cluster size This patch avoids an attempt to resize the filesystem to an unaligned cluster boundary. An online resize to a size that is not integral to cluster size results in the last iteration attempting to grow the fs by a negative amount, which trips a BUG_ON and leaves the fs with a corrupted in-memory superblock.
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
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-55296

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

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 3 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: ext4: avoid resizing to a partial cluster size This patch avoids an attempt to resize the filesystem to an unaligned cluster boundary. An online resize to a size that is not integral to cluster size results in the last iteration attempting to grow the fs by a negative amount, which trips a BUG_ON and leaves the fs with a corrupted in-memory superblock.

What

In the Linux kernel, the following vulnerability has been resolved: ext4: avoid resizing to a partial cluster size This patch avoids an attempt to resize the filesystem to an unaligned cluster boundary. An online resize to a size that is not integral to cluster size results in the last iteration attempting to grow the fs by a negative amount, which trips a BUG_ON and leaves the fs with a corrupted in-memory superblock.

Why

The product receives input that is expected to specify a quantity (such as size or length), but it does not validate or incorrectly validates that the quantity has the required properties.

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: ext4: avoid resizing to a partial cluster size This patch avoids an attempt to resize the filesystem to an unaligned cluster boundary. An online resize to a size that is not integral to cluster size results in the last iteration attempting to grow the fs by a negative amount, which trips a BUG_ON and leaves the fs with a corrupted in-memory superblock.

Why

The product receives input that is expected to specify a quantity (such as size or length), but it does not validate or incorrectly validates that the quantity has the required properties.

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 → Improper Validation of Specified Quantity in Input → 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
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-1284 ↗

CWE-1284: Improper Validation of Specified Quantity in Input. The product receives input that is expected to specify a quantity (such as size or length), but it does not validate or incorrectly validates that the quantity has the required properties.

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:U/C:N/I:N/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.SUnchangedScope: The security impact remains within the vulnerable component's authority.CNoneConfidentiality impact: No direct loss is represented by this metric.INoneIntegrity impact: No direct loss is represented by this metric.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-1284
A

Official authority intelligence

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

BSI · German · WID-SEC-2025-1905IBM QRadar SIEM Komponente: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in IBM QRadar SIEM Komponenten ausnutzen, um Daten zu manipulieren, um einen Denial of Service Angriff durchzuführen, um beliebigen Programmcode auszuführen, um Sicherheitsvorkehrungen zu umgehen, und um Informationen offenzulegen.

Official advisory ↗
BSI · German · WID-SEC-2025-1350Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service

Ein lokaler Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20250625Security Bulletin 25 Jun 2025

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 25 Jun 2025, published on 25 June 2025. Open the linked bulletin for the product, severity and reference information published in that issue.

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

d?id=CVE-2022-49995 Référence CVE CVE-2022-49999 https://www.cve.org/CVERecord?id=CVE-2022-49999 Référence CVE CVE-2022-50005 https://www.cve.org/CVERecord?id=CVE-2022-50005 Référence CVE CVE-2022-50006 https://www.cve.org/CVERecord?id=CVE-2022-50006 Référence CVE CVE-2022-50008 https://www.cve.org/CVERecord?id=CVE-2022-50008 Référence CVE CVE-2022-50010 https://www.cve.org/CVERecord?id=CVE-2022-50010 Référence CVE CVE-2022-50011 https://www.cve.org/CVERecord?id=CVE-2022-50011 Référence CVE CVE-2022-50012 https://www.cve.org/CVERecord?id=CVE-2022-50012 Référence CVE CVE-2022-50019 https://www.cve.org/CVERecord?id=CVE-2022-50019 Référence CVE CVE-2022-50020 https://www.cve.org/CVERecord?id=CVE-2022-50020 Référence CVE CVE-2022-50021 https://www.cve.org/CVERecord?id=CVE-2022-50021 Référence CVE CVE-2022-50022 https://www.cve.org/CVERecord?id=CVE-2022-50022 Référence CVE CVE-2022-50023 https://www.cve.org/CVERecord?id=CVE-2022-50023 Référence CVE CVE-2022-50024 https://www.cve.org/CVERecord?id=CVE-2022-50024 Référence CVE CVE-2022-50026 https://www.cve.org/CVERecord?id=CVE-2022-50026 Référence CVE CVE-2022-50027 https://www.cve.org/CVERecord?id=CVE-2022-50027 Référence CVE CVE-2022-50028 https://www.cve.org/CVERecord?id=CVE-2022-50028 Référence CVE CVE-2022-50029 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2022-50005 Référence CVE CVE-2022-50006 https://www.cve.org/CVERecord?id=CVE-2022-50006 Référence CVE CVE-2022-50008 https://www.cve.org/CVERecord?id=CVE-2022-50008 Référence CVE CVE-2022-50010 https://www.cve.org/CVERecord?id=CVE-2022-50010 Référence CVE CVE-2022-50011 https://www.cve.org/CVERecord?id=CVE-2022-50011 Référence CVE CVE-2022-50012 https://www.cve.org/CVERecord?id=CVE-2022-50012 Référence CVE CVE-2022-50015 https://www.cve.org/CVERecord?id=CVE-2022-50015 Référence CVE CVE-2022-50016 https://www.cve.org/CVERecord?id=CVE-2022-50016 Référence CVE CVE-2022-50019 https://www.cve.org/CVERecord?id=CVE-2022-50019 Référence CVE CVE-2022-50020 https://www.cve.org/CVERecord?id=CVE-2022-50020 Référence CVE CVE-2022-50021 https://www.cve.org/CVERecord?id=CVE-2022-50021 Référence CVE CVE-2022-50022 https://www.cve.org/CVERecord?id=CVE-2022-50022 Référence CVE CVE-2022-50023 https://www.cve.org/CVERecord?id=CVE-2022-50023 Référence CVE CVE-2022-50024 https://www.cve.org/CVERecord?id=CVE-2022-50024 Référence CVE CVE-2022-50026 https://www.cve.org/CVERecord?id=CVE-2022-50026 Référence CVE CVE-2022-50027 https://www.cve.org/CVERecord?id=CVE-2022-50027 Référence CVE CVE-2022-50028 https://www.cve.org/CVERecord?id=CVE-2022-50028 Référence CVE CVE-2022-50029 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0746Multiples vulnérabilités dans les produits IBM

ecord?id=CVE-2019-17543 Référence CVE CVE-2019-5427 https://www.cve.org/CVERecord?id=CVE-2019-5427 Référence CVE CVE-2020-5260 https://www.cve.org/CVERecord?id=CVE-2020-5260 Référence CVE CVE-2022-49058 https://www.cve.org/CVERecord?id=CVE-2022-49058 Référence CVE CVE-2022-49111 https://www.cve.org/CVERecord?id=CVE-2022-49111 Référence CVE CVE-2022-49136 https://www.cve.org/CVERecord?id=CVE-2022-49136 Référence CVE CVE-2022-49788 https://www.cve.org/CVERecord?id=CVE-2022-49788 Référence CVE CVE-2022-49846 https://www.cve.org/CVERecord?id=CVE-2022-49846 Référence CVE CVE-2022-49977 https://www.cve.org/CVERecord?id=CVE-2022-49977 Référence CVE CVE-2022-50020 https://www.cve.org/CVERecord?id=CVE-2022-50020 Référence CVE CVE-2024-10917 https://www.cve.org/CVERecord?id=CVE-2024-10917 Référence CVE CVE-2024-13009 https://www.cve.org/CVERecord?id=CVE-2024-13009 Référence CVE CVE-2024-21131 https://www.cve.org/CVERecord?id=CVE-2024-21131 Référence CVE CVE-2024-21144 https://www.cve.org/CVERecord?id=CVE-2024-21144 Référence CVE CVE-2024-23337 https://www.cve.org/CVERecord?id=CVE-2024-23337 Référence CVE CVE-2024-28956 https://www.cve.org/CVERecord?id=CVE-2024-28956 Référence CVE CVE-2024-34397 https://www.cve.org/CVERecord?id=CVE-2024-34397 Référence CVE CVE-2024-43420 https://www.cve.org/CVERecord?id=

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

hat.com/errata/RHSA-2025:14746 Bulletin de sécurité Red Hat RHSA-2025:14748 du 27 août 2025 https://access.redhat.com/errata/RHSA-2025:14748 Bulletin de sécurité Red Hat RHSA-2025:14749 du 27 août 2025 https://access.redhat.com/errata/RHSA-2025:14749 Référence CVE CVE-2021-47670 https://www.cve.org/CVERecord?id=CVE-2021-47670 Référence CVE CVE-2022-49385 https://www.cve.org/CVERecord?id=CVE-2022-49385 Référence CVE CVE-2022-49788 https://www.cve.org/CVERecord?id=CVE-2022-49788 Référence CVE CVE-2022-49977 https://www.cve.org/CVERecord?id=CVE-2022-49977 Référence CVE CVE-2022-49991 https://www.cve.org/CVERecord?id=CVE-2022-49991 Référence CVE CVE-2022-50020 https://www.cve.org/CVERecord?id=CVE-2022-50020 Référence CVE CVE-2022-50022 https://www.cve.org/CVERecord?id=CVE-2022-50022 Référence CVE CVE-2022-50044 https://www.cve.org/CVERecord?id=CVE-2022-50044 Référence CVE CVE-2023-53047 https://www.cve.org/CVERecord?id=CVE-2023-53047 Référence CVE CVE-2024-57980 https://www.cve.org/CVERecord?id=CVE-2024-57980 Référence CVE CVE-2025-21867 https://www.cve.org/CVERecord?id=CVE-2025-21867 Référence CVE CVE-2025-21919 https://www.cve.org/CVERecord?id=CVE-2025-21919 Référence CVE CVE-2025-21928 https://www.cve.org/CVERecord?id=CVE-2025-21928 Référence CVE CVE-2025-22020 https://www.cve.org/CVERecord?id=

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

/access.redhat.com/errata/RHSA-2025:14009 Bulletin de sécurité Red Hat RHSA-2025:14054 du 19 août 2025 https://access.redhat.com/errata/RHSA-2025:14054 Bulletin de sécurité Red Hat RHSA-2025:14082 du 19 août 2025 https://access.redhat.com/errata/RHSA-2025:14082 Bulletin de sécurité Red Hat RHSA-2025:14094 du 19 août 2025 https://access.redhat.com/errata/RHSA-2025:14094 Bulletin de sécurité Red Hat RHSA-2025:14136 du 20 août 2025 https://access.redhat.com/errata/RHSA-2025:14136 Référence CVE CVE-2021-47670 https://www.cve.org/CVERecord?id=CVE-2021-47670 Référence CVE CVE-2022-49788 https://www.cve.org/CVERecord?id=CVE-2022-49788 Référence CVE CVE-2022-50020 https://www.cve.org/CVERecord?id=CVE-2022-50020 Référence CVE CVE-2022-50022 https://www.cve.org/CVERecord?id=CVE-2022-50022 Référence CVE CVE-2022-50200 https://www.cve.org/CVERecord?id=CVE-2022-50200 Référence CVE CVE-2023-53047 https://www.cve.org/CVERecord?id=CVE-2023-53047 Référence CVE CVE-2024-28956 https://www.cve.org/CVERecord?id=CVE-2024-28956 Référence CVE CVE-2024-57980 https://www.cve.org/CVERecord?id=CVE-2024-57980 Référence CVE CVE-2025-21727 https://www.cve.org/CVERecord?id=CVE-2025-21727 Référence CVE CVE-2025-21867 https://www.cve.org/CVERecord?id=CVE-2025-21867 Référence CVE CVE-2025-21928 https://www.cve.org/CVERecord?id=

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

De multiples vulnérabilités ont été découvertes dans le noyau Linux de Red Hat. Certaines d'entre elles permettent à un attaquant de provoquer une atteinte à la confidentialité des données, un contournement de la politique de sécurité et un déni de service.

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

u 06 août 2025 https://access.redhat.com/errata/RHSA-2025:13120 Bulletin de sécurité Red Hat RHSA-2025:13135 du 06 août 2025 https://access.redhat.com/errata/RHSA-2025:13135 Référence CVE CVE-2021-47527 https://www.cve.org/CVERecord?id=CVE-2021-47527 Référence CVE CVE-2022-48669 https://www.cve.org/CVERecord?id=CVE-2022-48669 Référence CVE CVE-2022-49058 https://www.cve.org/CVERecord?id=CVE-2022-49058 Référence CVE CVE-2022-49395 https://www.cve.org/CVERecord?id=CVE-2022-49395 Référence CVE CVE-2022-49788 https://www.cve.org/CVERecord?id=CVE-2022-49788 Référence CVE CVE-2022-49995 https://www.cve.org/CVERecord?id=CVE-2022-49995 Référence CVE CVE-2022-50020 https://www.cve.org/CVERecord?id=CVE-2022-50020 Référence CVE CVE-2022-50022 https://www.cve.org/CVERecord?id=CVE-2022-50022 Référence CVE CVE-2023-52451 https://www.cve.org/CVERecord?id=CVE-2023-52451 Référence CVE CVE-2023-52764 https://www.cve.org/CVERecord?id=CVE-2023-52764 Référence CVE CVE-2023-52877 https://www.cve.org/CVERecord?id=CVE-2023-52877 Référence CVE CVE-2024-26659 https://www.cve.org/CVERecord?id=CVE-2024-26659 Référence CVE CVE-2024-26934 https://www.cve.org/CVERecord?id=CVE-2024-26934 Référence CVE CVE-2024-26964 https://www.cve.org/CVERecord?id=CVE-2024-26964 Référence CVE CVE-2024-27059 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2022-49995 Référence CVE CVE-2022-49999 https://www.cve.org/CVERecord?id=CVE-2022-49999 Référence CVE CVE-2022-50005 https://www.cve.org/CVERecord?id=CVE-2022-50005 Référence CVE CVE-2022-50006 https://www.cve.org/CVERecord?id=CVE-2022-50006 Référence CVE CVE-2022-50008 https://www.cve.org/CVERecord?id=CVE-2022-50008 Référence CVE CVE-2022-50010 https://www.cve.org/CVERecord?id=CVE-2022-50010 Référence CVE CVE-2022-50011 https://www.cve.org/CVERecord?id=CVE-2022-50011 Référence CVE CVE-2022-50012 https://www.cve.org/CVERecord?id=CVE-2022-50012 Référence CVE CVE-2022-50019 https://www.cve.org/CVERecord?id=CVE-2022-50019 Référence CVE CVE-2022-50020 https://www.cve.org/CVERecord?id=CVE-2022-50020 Référence CVE CVE-2022-50021 https://www.cve.org/CVERecord?id=CVE-2022-50021 Référence CVE CVE-2022-50022 https://www.cve.org/CVERecord?id=CVE-2022-50022 Référence CVE CVE-2022-50023 https://www.cve.org/CVERecord?id=CVE-2022-50023 Référence CVE CVE-2022-50024 https://www.cve.org/CVERecord?id=CVE-2022-50024 Référence CVE CVE-2022-50026 https://www.cve.org/CVERecord?id=CVE-2022-50026 Référence CVE CVE-2022-50027 https://www.cve.org/CVERecord?id=CVE-2022-50027 Référence CVE CVE-2022-50028 https://www.cve.org/CVERecord?id=CVE-2022-50028 Référence CVE CVE-2022-50029 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2022-50005 Référence CVE CVE-2022-50006 https://www.cve.org/CVERecord?id=CVE-2022-50006 Référence CVE CVE-2022-50008 https://www.cve.org/CVERecord?id=CVE-2022-50008 Référence CVE CVE-2022-50010 https://www.cve.org/CVERecord?id=CVE-2022-50010 Référence CVE CVE-2022-50011 https://www.cve.org/CVERecord?id=CVE-2022-50011 Référence CVE CVE-2022-50012 https://www.cve.org/CVERecord?id=CVE-2022-50012 Référence CVE CVE-2022-50015 https://www.cve.org/CVERecord?id=CVE-2022-50015 Référence CVE CVE-2022-50016 https://www.cve.org/CVERecord?id=CVE-2022-50016 Référence CVE CVE-2022-50019 https://www.cve.org/CVERecord?id=CVE-2022-50019 Référence CVE CVE-2022-50020 https://www.cve.org/CVERecord?id=CVE-2022-50020 Référence CVE CVE-2022-50021 https://www.cve.org/CVERecord?id=CVE-2022-50021 Référence CVE CVE-2022-50022 https://www.cve.org/CVERecord?id=CVE-2022-50022 Référence CVE CVE-2022-50023 https://www.cve.org/CVERecord?id=CVE-2022-50023 Référence CVE CVE-2022-50024 https://www.cve.org/CVERecord?id=CVE-2022-50024 Référence CVE CVE-2022-50026 https://www.cve.org/CVERecord?id=CVE-2022-50026 Référence CVE CVE-2022-50027 https://www.cve.org/CVERecord?id=CVE-2022-50027 Référence CVE CVE-2022-50028 https://www.cve.org/CVERecord?id=CVE-2022-50028 Référence CVE CVE-2022-50029 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2022-50005 Référence CVE CVE-2022-50006 https://www.cve.org/CVERecord?id=CVE-2022-50006 Référence CVE CVE-2022-50008 https://www.cve.org/CVERecord?id=CVE-2022-50008 Référence CVE CVE-2022-50010 https://www.cve.org/CVERecord?id=CVE-2022-50010 Référence CVE CVE-2022-50011 https://www.cve.org/CVERecord?id=CVE-2022-50011 Référence CVE CVE-2022-50012 https://www.cve.org/CVERecord?id=CVE-2022-50012 Référence CVE CVE-2022-50015 https://www.cve.org/CVERecord?id=CVE-2022-50015 Référence CVE CVE-2022-50016 https://www.cve.org/CVERecord?id=CVE-2022-50016 Référence CVE CVE-2022-50019 https://www.cve.org/CVERecord?id=CVE-2022-50019 Référence CVE CVE-2022-50020 https://www.cve.org/CVERecord?id=CVE-2022-50020 Référence CVE CVE-2022-50021 https://www.cve.org/CVERecord?id=CVE-2022-50021 Référence CVE CVE-2022-50022 https://www.cve.org/CVERecord?id=CVE-2022-50022 Référence CVE CVE-2022-50023 https://www.cve.org/CVERecord?id=CVE-2022-50023 Référence CVE CVE-2022-50024 https://www.cve.org/CVERecord?id=CVE-2022-50024 Référence CVE CVE-2022-50026 https://www.cve.org/CVERecord?id=CVE-2022-50026 Référence CVE CVE-2022-50027 https://www.cve.org/CVERecord?id=CVE-2022-50027 Référence CVE CVE-2022-50028 https://www.cve.org/CVERecord?id=CVE-2022-50028 Référence CVE CVE-2022-50029 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2022-026735Linux の 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.15, 4.19.256 ≤ 4.19.*, 5.4.211 ≤ 5.4.*, 5.10.138 ≤ 5.10.*, 5.15.63 ≤ 5.15.*, 5.19.4 ≤ 5.19.*, 6.0 ≤ *
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
No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04

Evidence and provenance

Published 18 Jun 2025 · Last source change 11 May 2026, 19:11 UTC · CWE-1284 · Improper Validation of Specified Quantity in Input

CVE recordCVE.org · 5.2
CVSS sourceNIST NVD
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-55296
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
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-50020 · cve.blacktree.nl