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

um: Fix out-of-bounds read in LDT setup

Linux · Linux

7.1HighCVSS 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 1 structured product or package state 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 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.29% 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 1 structured product or package state 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.5.18.5-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.5.18.5-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.5.18.5-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.5.18.5-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
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-49395 · CSAF 2.0 · revision 42 · interimSUSE Product Security TeamCVE-2022-49395
285 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 Availability Extension 12 SP5
  • kernel-source as component of SUSE Linux Enterprise High Availability Extension 12 SP5
  • 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
Summary
In the Linux kernel, the following vulnerability has been resolved: um: Fix out-of-bounds read in LDT setup syscall_stub_data() expects the data_count parameter to be the number of longs, not bytes. ================================================================== BUG: KASAN: stack-out-of-bounds in syscall_stub_data+0x70/0xe0 Read of size 128 at addr 000000006411f6f0 by task swapper/1 CPU: 0 PID: 1 Comm: swapper Not tainted 5.18.0+ #18 Call Trace: show_stack.cold+0x166/0x2a7 __dump_stack+0x3a/0x43 dump_stack_lvl+0x1f/0x27 print_report.cold+0xdb/0xf81 kasan_report+0x119/0x1f0 kasan_check_range+0x3a3/0x440 memcpy+0x52/0x140 syscall_stub_data+0x70/0xe0 write_ldt_entry+0xac/0x190 init_new_ldt+0x515/0x960 init_new_context+0x2c4/0x4d0 mm_init.constprop.0+0x5ed/0x760 mm_alloc+0x118/0x170 0x60033f48 do_one_initcall+0x1d7/0x860 0x60003e7b kernel_init+0x6e/0x3d4 new_thread_handler+0x1e7/0x2c0 The buggy address belongs to stack of task swapper/1 and is located at offset 64 in frame: init_new_ldt+0x0/0x960 This frame has 2 objects: [32, 40) 'addr' [64, 80) 'desc' ==================================================================
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-54834

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 1 structured product or package state 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: um: Fix out-of-bounds read in LDT setup syscall_stub_data() expects the data_count parameter to be the number of longs, not bytes. ================================================================== BUG: KASAN: stack-out-of-bounds in syscall_stub_data+0x70/0xe0 Read of size 128 at addr 000000006411f6f0 by task swapper/1 CPU: 0 PID: 1 Comm: swapper Not tainted 5.18.0+ #18 Call Trace: show_stack.cold+0x166/0x2a7 __dump_stack+0x3a/0x43 dump_stack_lvl+0x1f/0x27 print_report.cold+0xdb/0xf81 kasan_report+0x119/0x1f0 kasan_check_range+0x3a3/0x440 memcpy+0x52/0x140 syscall_stub_data+0x70/0xe0 write_ldt_entry+0xac/0x190 init_new_ldt+0x515/0x960 init_new_context+0x2c4/0x4d0 mm_init.constprop.0+0x5ed/0x760 mm_alloc+0x118/0x170 0x60033f48 do_one_initcall+0x1d7/0x860 0x60003e7b kernel_init+0x6e/0x3d4 new_thread_handler+0x1e7/0x2c0 The buggy address belongs to stack of task swapper/1 and is located at offset 64 in frame: init_new_ldt+0x0/0x960 This frame has 2 objects: [32, 40) 'addr' [64, 80) 'desc' ==================================================================

What

In the Linux kernel, the following vulnerability has been resolved: um: Fix out-of-bounds read in LDT setup syscall_stub_data() expects the data_count parameter to be the number of longs, not bytes. ================================================================== BUG: KASAN: stack-out-of-bounds in syscall_stub_data+0x70/0xe0 Read of size 128 at addr 000000006411f6f0 by task swapper/1 CPU: 0 PID: 1 Comm: swapper Not tainted 5.18.0+ #18 Call Trace: show_stack.cold+0x166/0x2a7 __dump_stack+0x3a/0x43 dump_stack_lvl+0x1f/0x27 print_report.cold+0xdb/0xf81 kasan_report+0x119/0x1f0 kasan_check_range+0x3a3/0x440 memcpy+0x52/0x140 syscall_stub_data+0x70/0xe0 write_ldt_entry+0xac/0x190 init_new_ldt+0x515/0x960 init_new_context+0x2c4/0x4d0 mm_init.constprop.0+0x5ed/0x760 mm_alloc+0x118/0x170 0x60033f48 do_one_initcall+0x1d7/0x860 0x60003e7b kernel_init+0x6e/0x3d4 new_thread_handler+0x1e7/0x2c0 The buggy address belongs to stack of task swapper/1 and is located at offset 64 in frame: init_new_ldt+0x0/0x960 This frame has 2 objects: [32, 40) 'addr' [64, 80) 'desc' ==================================================================

Why

The product reads data past the end, or before the beginning, of the intended buffer.

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: um: Fix out-of-bounds read in LDT setup syscall_stub_data() expects the data_count parameter to be the number of longs, not bytes. ================================================================== BUG: KASAN: stack-out-of-bounds in syscall_stub_data+0x70/0xe0 Read of size 128 at addr 000000006411f6f0 by task swapper/1 CPU: 0 PID: 1 Comm: swapper Not tainted 5.18.0+ #18 Call Trace: show_stack.cold+0x166/0x2a7 __dump_stack+0x3a/0x43 dump_stack_lvl+0x1f/0x27 print_report.cold+0xdb/0xf81 kasan_report+0x119/0x1f0 kasan_check_range+0x3a3/0x440 memcpy+0x52/0x140 syscall_stub_data+0x70/0xe0 write_ldt_entry+0xac/0x190 init_new_ldt+0x515/0x960 init_new_context+0x2c4/0x4d0 mm_init.constprop.0+0x5ed/0x760 mm_alloc+0x118/0x170 0x60033f48 do_one_initcall+0x1d7/0x860 0x60003e7b kernel_init+0x6e/0x3d4 new_thread_handler+0x1e7/0x2c0 The buggy address belongs to stack of task swapper/1 and is located at offset 64 in frame: init_new_ldt+0x0/0x960 This frame has 2 objects: [32, 40) 'addr' [64, 80) 'desc' ==================================================================

Why

The product reads data past the end, or before the beginning, of the intended buffer.

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 → Out-of-bounds Read → 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-125 ↗

CWE-125: Out-of-bounds Read. The product reads data past the end, or before the beginning, of the intended buffer.

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:H/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.CHighConfidentiality impact: A successful attack can cause a major loss.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-125
A

Official authority intelligence

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

BSI · German · WID-SEC-2025-1271Linux Kernel: Schwachstelle ermöglicht Denial of Service und Offenlegung von Informationen

Ein lokaler Angreifer kann eine Schwachstelle in Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen und um Informationen offenzulegen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20250305Security Bulletin 5 March 2025

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

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

025:13030 du 05 août 2025 https://access.redhat.com/errata/RHSA-2025:13030 Bulletin de sécurité Red Hat RHSA-2025:13061 du 05 août 2025 https://access.redhat.com/errata/RHSA-2025:13061 Bulletin de sécurité Red Hat RHSA-2025:13120 du 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=

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0667Multiples vulnérabilités dans Juniper Secure Analytics

De multiples vulnérabilités ont été découvertes dans Juniper Secure Analytics. Elle permet à un attaquant de provoquer un déni de service à distance, une atteinte à la confidentialité des données et une atteinte à l'intégrité des données.

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0626Multiples 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. Elles permettent à un attaquant de provoquer un déni de service à distance, une atteinte à la confidentialité des données et un contournement de la politique de sécurité.

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

d?id=CVE-2021-43797 Référence CVE CVE-2021-44531 https://www.cve.org/CVERecord?id=CVE-2021-44531 Référence CVE CVE-2021-44532 https://www.cve.org/CVERecord?id=CVE-2021-44532 Référence CVE CVE-2021-44533 https://www.cve.org/CVERecord?id=CVE-2021-44533 Référence CVE CVE-2022-21803 https://www.cve.org/CVERecord?id=CVE-2022-21803 Référence CVE CVE-2022-21824 https://www.cve.org/CVERecord?id=CVE-2022-21824 Référence CVE CVE-2022-29078 https://www.cve.org/CVERecord?id=CVE-2022-29078 Référence CVE CVE-2022-30614 https://www.cve.org/CVERecord?id=CVE-2022-30614 Référence CVE CVE-2022-36773 https://www.cve.org/CVERecord?id=CVE-2022-36773 Référence CVE CVE-2022-49395 https://www.cve.org/CVERecord?id=CVE-2022-49395 Référence CVE CVE-2023-32732 https://www.cve.org/CVERecord?id=CVE-2023-32732 Référence CVE CVE-2023-33953 https://www.cve.org/CVERecord?id=CVE-2023-33953 Référence CVE CVE-2023-44487 https://www.cve.org/CVERecord?id=CVE-2023-44487 Référence CVE CVE-2024-52005 https://www.cve.org/CVERecord?id=CVE-2024-52005 Référence CVE CVE-2025-21587 https://www.cve.org/CVERecord?id=CVE-2025-21587 Référence CVE CVE-2025-22869 https://www.cve.org/CVERecord?id=CVE-2025-22869 Référence CVE CVE-2025-2900 https://www.cve.org/CVERecord?id=CVE-2025-2900 Référence CVE CVE-2025-30698 https://www.cve.org/CVERecord?id=CV

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0606Multiples 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, une atteinte à l'intégrité des données et un contournement de la politique de sécurité.

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

at.com/errata/RHSA-2025:10671 Bulletin de sécurité Red Hat RHSA-2025:10673 du 09 juillet 2025 https://access.redhat.com/errata/RHSA-2025:10673 Bulletin de sécurité Red Hat RHSA-2025:10675 du 09 juillet 2025 https://access.redhat.com/errata/RHSA-2025:10675 Bulletin de sécurité Red Hat RHSA-2025:10701 du 09 juillet 2025 https://access.redhat.com/errata/RHSA-2025:10701 Bulletin de sécurité Red Hat RHSA-2025:10761 du 10 juillet 2025 https://access.redhat.com/errata/RHSA-2025:10761 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-49395 https://www.cve.org/CVERecord?id=CVE-2022-49395 Référence CVE CVE-2022-49846 https://www.cve.org/CVERecord?id=CVE-2022-49846 Référence CVE CVE-2022-50066 https://www.cve.org/CVERecord?id=CVE-2022-50066 Référence CVE CVE-2023-1652 https://www.cve.org/CVERecord?id=CVE-2023-1652 Référence CVE CVE-2023-52477 https://www.cve.org/CVERecord?id=CVE-2023-52477 Référence CVE CVE-2023-52565 https://www.cve.org/CVERecord?id=CVE-2023-52565 Référence CVE CVE-2023-52595 https://www.cve.org/CVERecord?id=CVE-2023-52595 Référence CVE CVE-2023-52781 https://www.cve.org/CVERecord?id=CVE-2023-52781 Référence CVE CVE-2023-52834 https://www.cve.org/CVERecord?id=CV

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

uillet 2025 https://access.redhat.com/errata/RHSA-2025:10193 Bulletin de sécurité Red Hat RHSA-2025:10211 du 02 juillet 2025 https://access.redhat.com/errata/RHSA-2025:10211 Référence CVE CVE-2022-48919 https://www.cve.org/CVERecord?id=CVE-2022-48919 Référence CVE CVE-2022-49111 https://www.cve.org/CVERecord?id=CVE-2022-49111 Référence CVE CVE-2022-49114 https://www.cve.org/CVERecord?id=CVE-2022-49114 Référence CVE CVE-2022-49122 https://www.cve.org/CVERecord?id=CVE-2022-49122 Référence CVE CVE-2022-49328 https://www.cve.org/CVERecord?id=CVE-2022-49328 Référence CVE CVE-2022-49377 https://www.cve.org/CVERecord?id=CVE-2022-49377 Référence CVE CVE-2022-49395 https://www.cve.org/CVERecord?id=CVE-2022-49395 Référence CVE CVE-2022-49407 https://www.cve.org/CVERecord?id=CVE-2022-49407 Référence CVE CVE-2023-1652 https://www.cve.org/CVERecord?id=CVE-2023-1652 Référence CVE CVE-2023-52623 https://www.cve.org/CVERecord?id=CVE-2023-52623 Référence CVE CVE-2023-52662 https://www.cve.org/CVERecord?id=CVE-2023-52662 Référence CVE CVE-2023-52933 https://www.cve.org/CVERecord?id=CVE-2023-52933 Référence CVE CVE-2024-26638 https://www.cve.org/CVERecord?id=CVE-2024-26638 Référence CVE CVE-2024-26669 https://www.cve.org/CVERecord?id=CVE-2024-26669 Référence CVE CVE-2024-26939 https://www.cve.org/CVERecord?id=CV

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0510Multiples 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. Elles permettent à un attaquant de provoquer une atteinte à la confidentialité des données et un déni de service.

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

d?id=CVE-2022-49382 Référence CVE CVE-2022-49384 https://www.cve.org/CVERecord?id=CVE-2022-49384 Référence CVE CVE-2022-49385 https://www.cve.org/CVERecord?id=CVE-2022-49385 Référence CVE CVE-2022-49386 https://www.cve.org/CVERecord?id=CVE-2022-49386 Référence CVE CVE-2022-49388 https://www.cve.org/CVERecord?id=CVE-2022-49388 Référence CVE CVE-2022-49389 https://www.cve.org/CVERecord?id=CVE-2022-49389 Référence CVE CVE-2022-49390 https://www.cve.org/CVERecord?id=CVE-2022-49390 Référence CVE CVE-2022-49392 https://www.cve.org/CVERecord?id=CVE-2022-49392 Référence CVE CVE-2022-49394 https://www.cve.org/CVERecord?id=CVE-2022-49394 Référence CVE CVE-2022-49395 https://www.cve.org/CVERecord?id=CVE-2022-49395 Référence CVE CVE-2022-49396 https://www.cve.org/CVERecord?id=CVE-2022-49396 Référence CVE CVE-2022-49397 https://www.cve.org/CVERecord?id=CVE-2022-49397 Référence CVE CVE-2022-49398 https://www.cve.org/CVERecord?id=CVE-2022-49398 Référence CVE CVE-2022-49399 https://www.cve.org/CVERecord?id=CVE-2022-49399 Référence CVE CVE-2022-49400 https://www.cve.org/CVERecord?id=CVE-2022-49400 Référence CVE CVE-2022-49402 https://www.cve.org/CVERecord?id=CVE-2022-49402 Référence CVE CVE-2022-49404 https://www.cve.org/CVERecord?id=CVE-2022-49404 Référence CVE CVE-2022-49406 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2022-026106Linux の 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: < 2.6.15, 4.9.318 ≤ 4.9.*, 4.14.283 ≤ 4.14.*, 4.19.247 ≤ 4.19.*, 5.4.198 ≤ 5.4.*, 5.10.121 ≤ 5.10.*, 5.15.46 ≤ 5.15.*, 5.17.14 ≤ 5.17.*, 5.18.3 ≤ 5.18.*, 5.19 ≤ *
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 26 Feb 2025 · Last source change 11 May 2026, 18:58 UTC · CWE-125 · Out-of-bounds Read

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-54834
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceCISA ADP
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
CVE published
Fixed release or patch reference recorded
ENISA EUVD · EUVD-2022-54834↗Vendor CSAF · SUSE Product Security Team↗CVE authority or vendor reference↗Patch or update reference↗Patch or update reference↗Patch or update reference↗Official CVE record (CNA and ADP data)↗NVD record↗
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-49395 · cve.blacktree.nl