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

ALSA: emu10k1: Fix out of bounds access in snd_emu10k1_pcm_channel_alloc()

Linux · Linux

7.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 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 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.24% 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.19.11-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.5.19.11-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.5.19.11-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.5.19.11-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-48702 · CSAF 2.0 · revision 71 · interimSUSE Product Security TeamCVE-2022-48702
118 known affected

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

  • kernel-default as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • kernel-default-base as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • kernel-default-man as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • kernel-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • kernel-macros as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • kernel-source as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • reiserfs-kmp-default as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • kernel-default as component of SUSE Linux Enterprise High Performance Computing 15 SP2-LTSS
  • kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP2-LTSS
  • kernel-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP2-LTSS
  • kernel-macros as component of SUSE Linux Enterprise High Performance Computing 15 SP2-LTSS
Summary
In the Linux kernel, the following vulnerability has been resolved: ALSA: emu10k1: Fix out of bounds access in snd_emu10k1_pcm_channel_alloc() The voice allocator sometimes begins allocating from near the end of the array and then wraps around, however snd_emu10k1_pcm_channel_alloc() accesses the newly allocated voices as if it never wrapped around. This results in out of bounds access if the first voice has a high enough index so that first_voice + requested_voice_count > NUM_G (64). The more voices are requested, the more likely it is for this to occur. This was initially discovered using PipeWire, however it can be reproduced by calling aplay multiple times with 16 channels: aplay -r 48000 -D plughw:CARD=Live,DEV=3 -c 16 /dev/zero UBSAN: array-index-out-of-bounds in sound/pci/emu10k1/emupcm.c:127:40 index 65 is out of range for type 'snd_emu10k1_voice [64]' CPU: 1 PID: 31977 Comm: aplay Tainted: G W IOE 6.0.0-rc2-emu10k1+ #7 Hardware name: ASUSTEK COMPUTER INC P5W DH Deluxe/P5W DH Deluxe, BIOS 3002 07/22/2010 Call Trace: dump_stack_lvl+0x49/0x63 dump_stack+0x10/0x16 ubsan_epilogue+0x9/0x3f __ubsan_handle_out_of_bounds.cold+0x44/0x49 snd_emu10k1_playback_hw_params+0x3bc/0x420 [snd_emu10k1] snd_pcm_hw_params+0x29f/0x600 [snd_pcm] snd_pcm_common_ioctl+0x188/0x1410 [snd_pcm] ? exit_to_user_mode_prepare+0x35/0x170 ? do_syscall_64+0x69/0x90 ? syscall_exit_to_user_mode+0x26/0x50 ? do_syscall_64+0x69/0x90 ? exit_to_user_mode_prepare+0x35/0x170 snd_pcm_ioctl+0x27/0x40 [snd_pcm] __x64_sys_ioctl+0x95/0xd0 do_syscall_64+0x5c/0x90 ? do_syscall_64+0x69/0x90 ? do_syscall_64+0x69/0x90 entry_SYSCALL_64_after_hwframe+0x63/0xcd
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-53581

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: ALSA: emu10k1: Fix out of bounds access in snd_emu10k1_pcm_channel_alloc() The voice allocator sometimes begins allocating from near the end of the array and then wraps around, however snd_emu10k1_pcm_channel_alloc() accesses the newly allocated voices as if it never wrapped around. This results in out of bounds access if the first voice has a high enough index so that first_voice + requested_voice_count > NUM_G (64). The more voices are requested, the more likely it is for this to occur. This was initially discovered using PipeWire, however it can be reproduced by calling aplay multiple times with 16 channels: aplay -r 48000 -D plughw:CARD=Live,DEV=3 -c 16 /dev/zero UBSAN: array-index-out-of-bounds in sound/pci/emu10k1/emupcm.c:127:40 index 65 is out of range for type 'snd_emu10k1_voice [64]' CPU: 1 PID: 31977 Comm: aplay Tainted: G W IOE 6.0.0-rc2-emu10k1+ #7 Hardware name: ASUSTEK COMPUTER INC P5W DH Deluxe/P5W DH Deluxe, BIOS 3002 07/22/2010 Call Trace: <TASK> dump_stack_lvl+0x49/0x63 dump_stack+0x10/0x16 ubsan_epilogue+0x9/0x3f __ubsan_handle_out_of_bounds.cold+0x44/0x49 snd_emu10k1_playback_hw_params+0x3bc/0x420 [snd_emu10k1] snd_pcm_hw_params+0x29f/0x600 [snd_pcm] snd_pcm_common_ioctl+0x188/0x1410 [snd_pcm] ? exit_to_user_mode_prepare+0x35/0x170 ? do_syscall_64+0x69/0x90 ? syscall_exit_to_user_mode+0x26/0x50 ? do_syscall_64+0x69/0x90 ? exit_to_user_mode_prepare+0x35/0x170 snd_pcm_ioctl+0x27/0x40 [snd_pcm] __x64_sys_ioctl+0x95/0xd0 do_syscall_64+0x5c/0x90 ? do_syscall_64+0x69/0x90 ? do_syscall_64+0x69/0x90 entry_SYSCALL_64_after_hwframe+0x63/0xcd

What

In the Linux kernel, the following vulnerability has been resolved: ALSA: emu10k1: Fix out of bounds access in snd_emu10k1_pcm_channel_alloc() The voice allocator sometimes begins allocating from near the end of the array and then wraps around, however snd_emu10k1_pcm_channel_alloc() accesses the newly allocated voices as if it never wrapped around. This results in out of bounds access if the first voice has a high enough index so that first_voice + requested_voice_count > NUM_G (64). The more voices are requested, the more likely it is for this to occur. This was initially discovered using PipeWire, however it can be reproduced by calling aplay multiple times with 16 channels: aplay -r 48000 -D plughw:CARD=Live,DEV=3 -c 16 /dev/zero UBSAN: array-index-out-of-bounds in sound/pci/emu10k1/emupcm.c:127:40 index 65 is out of range for type 'snd_emu10k1_voice [64]' CPU: 1 PID: 31977 Comm: aplay Tainted: G W IOE 6.0.0-rc2-emu10k1+ #7 Hardware name: ASUSTEK COMPUTER INC P5W DH Deluxe/P5W DH Deluxe, BIOS 3002 07/22/2010 Call Trace: <TASK> dump_stack_lvl+0x49/0x63 dump_stack+0x10/0x16 ubsan_epilogue+0x9/0x3f __ubsan_handle_out_of_bounds.cold+0x44/0x49 snd_emu10k1_playback_hw_params+0x3bc/0x420 [snd_emu10k1] snd_pcm_hw_params+0x29f/0x600 [snd_pcm] snd_pcm_common_ioctl+0x188/0x1410 [snd_pcm] ? exit_to_user_mode_prepare+0x35/0x170 ? do_syscall_64+0x69/0x90 ? syscall_exit_to_user_mode+0x26/0x50 ? do_syscall_64+0x69/0x90 ? exit_to_user_mode_prepare+0x35/0x170 snd_pcm_ioctl+0x27/0x40 [snd_pcm] __x64_sys_ioctl+0x95/0xd0 do_syscall_64+0x5c/0x90 ? do_syscall_64+0x69/0x90 ? do_syscall_64+0x69/0x90 entry_SYSCALL_64_after_hwframe+0x63/0xcd

Why

The product uses untrusted input when calculating or using an array index, but the product does not validate or incorrectly validates the index to ensure the index references a valid position within the array.

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: ALSA: emu10k1: Fix out of bounds access in snd_emu10k1_pcm_channel_alloc() The voice allocator sometimes begins allocating from near the end of the array and then wraps around, however snd_emu10k1_pcm_channel_alloc() accesses the newly allocated voices as if it never wrapped around. This results in out of bounds access if the first voice has a high enough index so that first_voice + requested_voice_count > NUM_G (64). The more voices are requested, the more likely it is for this to occur. This was initially discovered using PipeWire, however it can be reproduced by calling aplay multiple times with 16 channels: aplay -r 48000 -D plughw:CARD=Live,DEV=3 -c 16 /dev/zero UBSAN: array-index-out-of-bounds in sound/pci/emu10k1/emupcm.c:127:40 index 65 is out of range for type 'snd_emu10k1_voice [64]' CPU: 1 PID: 31977 Comm: aplay Tainted: G W IOE 6.0.0-rc2-emu10k1+ #7 Hardware name: ASUSTEK COMPUTER INC P5W DH Deluxe/P5W DH Deluxe, BIOS 3002 07/22/2010 Call Trace: <TASK> dump_stack_lvl+0x49/0x63 dump_stack+0x10/0x16 ubsan_epilogue+0x9/0x3f __ubsan_handle_out_of_bounds.cold+0x44/0x49 snd_emu10k1_playback_hw_params+0x3bc/0x420 [snd_emu10k1] snd_pcm_hw_params+0x29f/0x600 [snd_pcm] snd_pcm_common_ioctl+0x188/0x1410 [snd_pcm] ? exit_to_user_mode_prepare+0x35/0x170 ? do_syscall_64+0x69/0x90 ? syscall_exit_to_user_mode+0x26/0x50 ? do_syscall_64+0x69/0x90 ? exit_to_user_mode_prepare+0x35/0x170 snd_pcm_ioctl+0x27/0x40 [snd_pcm] __x64_sys_ioctl+0x95/0xd0 do_syscall_64+0x5c/0x90 ? do_syscall_64+0x69/0x90 ? do_syscall_64+0x69/0x90 entry_SYSCALL_64_after_hwframe+0x63/0xcd

Why

The product uses untrusted input when calculating or using an array index, but the product does not validate or incorrectly validates the index to ensure the index references a valid position within the array.

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 Array Index → 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-129 ↗

CWE-129: Improper Validation of Array Index. The product uses untrusted input when calculating or using an array index, but the product does not validate or incorrectly validates the index to ensure the index references a valid position within the array.

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: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.SUnchangedScope: The security impact remains within the vulnerable component's 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-129
A

Official authority intelligence

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

BSI · German · WID-SEC-2024-1025Linux Kernel: Mehrere Schwachstellen

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

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20240508Security Bulletin 08 May 2024

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

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

d?id=CVE-2022-48660 Référence CVE CVE-2022-48662 https://www.cve.org/CVERecord?id=CVE-2022-48662 Référence CVE CVE-2022-48672 https://www.cve.org/CVERecord?id=CVE-2022-48672 Référence CVE CVE-2022-48675 https://www.cve.org/CVERecord?id=CVE-2022-48675 Référence CVE CVE-2022-48689 https://www.cve.org/CVERecord?id=CVE-2022-48689 Référence CVE CVE-2022-48690 https://www.cve.org/CVERecord?id=CVE-2022-48690 Référence CVE CVE-2022-48691 https://www.cve.org/CVERecord?id=CVE-2022-48691 Référence CVE CVE-2022-48694 https://www.cve.org/CVERecord?id=CVE-2022-48694 Référence CVE CVE-2022-48701 https://www.cve.org/CVERecord?id=CVE-2022-48701 Référence CVE CVE-2022-48702 https://www.cve.org/CVERecord?id=CVE-2022-48702 Référence CVE CVE-2022-48704 https://www.cve.org/CVERecord?id=CVE-2022-48704 Référence CVE CVE-2022-48705 https://www.cve.org/CVERecord?id=CVE-2022-48705 Référence CVE CVE-2022-48707 https://www.cve.org/CVERecord?id=CVE-2022-48707 Référence CVE CVE-2022-48709 https://www.cve.org/CVERecord?id=CVE-2022-48709 Référence CVE CVE-2022-48710 https://www.cve.org/CVERecord?id=CVE-2022-48710 Référence CVE CVE-2022-48712 https://www.cve.org/CVERecord?id=CVE-2022-48712 Référence CVE CVE-2022-48713 https://www.cve.org/CVERecord?id=CVE-2022-48713 Référence CVE CVE-2022-48714 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2022-48688 Référence CVE CVE-2022-48692 https://www.cve.org/CVERecord?id=CVE-2022-48692 Référence CVE CVE-2022-48693 https://www.cve.org/CVERecord?id=CVE-2022-48693 Référence CVE CVE-2022-48694 https://www.cve.org/CVERecord?id=CVE-2022-48694 Référence CVE CVE-2022-48695 https://www.cve.org/CVERecord?id=CVE-2022-48695 Référence CVE CVE-2022-48697 https://www.cve.org/CVERecord?id=CVE-2022-48697 Référence CVE CVE-2022-48699 https://www.cve.org/CVERecord?id=CVE-2022-48699 Référence CVE CVE-2022-48700 https://www.cve.org/CVERecord?id=CVE-2022-48700 Référence CVE CVE-2022-48701 https://www.cve.org/CVERecord?id=CVE-2022-48701 Référence CVE CVE-2022-48702 https://www.cve.org/CVERecord?id=CVE-2022-48702 Référence CVE CVE-2022-48703 https://www.cve.org/CVERecord?id=CVE-2022-48703 Référence CVE CVE-2022-48704 https://www.cve.org/CVERecord?id=CVE-2022-48704 Référence CVE CVE-2022-48742 https://www.cve.org/CVERecord?id=CVE-2022-48742 Référence CVE CVE-2022-48956 https://www.cve.org/CVERecord?id=CVE-2022-48956 Référence CVE CVE-2022-49033 https://www.cve.org/CVERecord?id=CVE-2022-49033 Référence CVE CVE-2022-49035 https://www.cve.org/CVERecord?id=CVE-2022-49035 Référence CVE CVE-2023-0160 https://www.cve.org/CVERecord?id=CVE-2023-0160 Référence CVE CVE-2023-1382 https://www.cve.org/CVERecord?id=CVE

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

d?id=CVE-2022-48691 Référence CVE CVE-2022-48692 https://www.cve.org/CVERecord?id=CVE-2022-48692 Référence CVE CVE-2022-48693 https://www.cve.org/CVERecord?id=CVE-2022-48693 Référence CVE CVE-2022-48694 https://www.cve.org/CVERecord?id=CVE-2022-48694 Référence CVE CVE-2022-48695 https://www.cve.org/CVERecord?id=CVE-2022-48695 Référence CVE CVE-2022-48697 https://www.cve.org/CVERecord?id=CVE-2022-48697 Référence CVE CVE-2022-48699 https://www.cve.org/CVERecord?id=CVE-2022-48699 Référence CVE CVE-2022-48700 https://www.cve.org/CVERecord?id=CVE-2022-48700 Référence CVE CVE-2022-48701 https://www.cve.org/CVERecord?id=CVE-2022-48701 Référence CVE CVE-2022-48702 https://www.cve.org/CVERecord?id=CVE-2022-48702 Référence CVE CVE-2022-48703 https://www.cve.org/CVERecord?id=CVE-2022-48703 Référence CVE CVE-2022-48704 https://www.cve.org/CVERecord?id=CVE-2022-48704 Référence CVE CVE-2022-48705 https://www.cve.org/CVERecord?id=CVE-2022-48705 Référence CVE CVE-2022-48708 https://www.cve.org/CVERecord?id=CVE-2022-48708 Référence CVE CVE-2022-48709 https://www.cve.org/CVERecord?id=CVE-2022-48709 Référence CVE CVE-2022-48710 https://www.cve.org/CVERecord?id=CVE-2022-48710 Référence CVE CVE-2023-0160 https://www.cve.org/CVERecord?id=CVE-2023-0160 Référence CVE CVE-2023-1829 https://www.cve.org/CVERecord?id=CVE

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

d?id=CVE-2022-48691 Référence CVE CVE-2022-48692 https://www.cve.org/CVERecord?id=CVE-2022-48692 Référence CVE CVE-2022-48693 https://www.cve.org/CVERecord?id=CVE-2022-48693 Référence CVE CVE-2022-48694 https://www.cve.org/CVERecord?id=CVE-2022-48694 Référence CVE CVE-2022-48695 https://www.cve.org/CVERecord?id=CVE-2022-48695 Référence CVE CVE-2022-48697 https://www.cve.org/CVERecord?id=CVE-2022-48697 Référence CVE CVE-2022-48699 https://www.cve.org/CVERecord?id=CVE-2022-48699 Référence CVE CVE-2022-48700 https://www.cve.org/CVERecord?id=CVE-2022-48700 Référence CVE CVE-2022-48701 https://www.cve.org/CVERecord?id=CVE-2022-48701 Référence CVE CVE-2022-48702 https://www.cve.org/CVERecord?id=CVE-2022-48702 Référence CVE CVE-2022-48703 https://www.cve.org/CVERecord?id=CVE-2022-48703 Référence CVE CVE-2022-48704 https://www.cve.org/CVERecord?id=CVE-2022-48704 Référence CVE CVE-2022-48705 https://www.cve.org/CVERecord?id=CVE-2022-48705 Référence CVE CVE-2022-48708 https://www.cve.org/CVERecord?id=CVE-2022-48708 Référence CVE CVE-2022-48709 https://www.cve.org/CVERecord?id=CVE-2022-48709 Référence CVE CVE-2022-48710 https://www.cve.org/CVERecord?id=CVE-2022-48710 Référence CVE CVE-2023-0160 https://www.cve.org/CVERecord?id=CVE-2023-0160 Référence CVE CVE-2023-1829 https://www.cve.org/CVERecord?id=CVE

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

d?id=CVE-2022-48692 Référence CVE CVE-2022-48693 https://www.cve.org/CVERecord?id=CVE-2022-48693 Référence CVE CVE-2022-48694 https://www.cve.org/CVERecord?id=CVE-2022-48694 Référence CVE CVE-2022-48695 https://www.cve.org/CVERecord?id=CVE-2022-48695 Référence CVE CVE-2022-48697 https://www.cve.org/CVERecord?id=CVE-2022-48697 Référence CVE CVE-2022-48698 https://www.cve.org/CVERecord?id=CVE-2022-48698 Référence CVE CVE-2022-48699 https://www.cve.org/CVERecord?id=CVE-2022-48699 Référence CVE CVE-2022-48700 https://www.cve.org/CVERecord?id=CVE-2022-48700 Référence CVE CVE-2022-48701 https://www.cve.org/CVERecord?id=CVE-2022-48701 Référence CVE CVE-2022-48702 https://www.cve.org/CVERecord?id=CVE-2022-48702 Référence CVE CVE-2022-48703 https://www.cve.org/CVERecord?id=CVE-2022-48703 Référence CVE CVE-2022-48704 https://www.cve.org/CVERecord?id=CVE-2022-48704 Référence CVE CVE-2023-0160 https://www.cve.org/CVERecord?id=CVE-2023-0160 Référence CVE CVE-2023-2860 https://www.cve.org/CVERecord?id=CVE-2023-2860 Référence CVE CVE-2023-28746 https://www.cve.org/CVERecord?id=CVE-2023-28746 Référence CVE CVE-2023-35827 https://www.cve.org/CVERecord?id=CVE-2023-35827 Référence CVE CVE-2023-4881 https://www.cve.org/CVERecord?id=CVE-2023-4881 Référence CVE CVE-2023-52454 https://www.cve.org/CVERecord?id=CVE-20

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2022-025650Linux の 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.12, 4.9.328 ≤ 4.9.*, 4.14.293 ≤ 4.14.*, 4.19.258 ≤ 4.19.*, 5.4.213 ≤ 5.4.*, 5.10.143 ≤ 5.10.*, 5.15.68 ≤ 5.15.*, 5.19.9 ≤ 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 3 May 2024 · Last source change 5 Aug 2026, 08:51 UTC · CWE-129 · Improper Validation of Array Index

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-53581
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
CVE published
Fixed release or patch reference recorded
ENISA EUVD · EUVD-2022-53581↗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-48702 · cve.blacktree.nl