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

ath5k: fix OOB in ath5k_eeprom_read_pcal_info_5111

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.26% 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.17.3-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.5.17.3-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.5.17.3-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.5.17.3-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-2021-47633 · CSAF 2.0 · revision 61 · interimSUSE Product Security TeamCVE-2021-47633
162 known affected

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

  • 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
  • kernel-default-man as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • kernel-devel as component of SUSE Linux Enterprise High Performance Computing 12 SP4
Summary
In the Linux kernel, the following vulnerability has been resolved: ath5k: fix OOB in ath5k_eeprom_read_pcal_info_5111 The bug was found during fuzzing. Stacktrace locates it in ath5k_eeprom_convert_pcal_info_5111. When none of the curve is selected in the loop, idx can go up to AR5K_EEPROM_N_PD_CURVES. The line makes pd out of bound. pd = &chinfo[pier].pd_curves[idx]; There are many OOB writes using pd later in the code. So I added a sanity check for idx. Checks for other loops involving AR5K_EEPROM_N_PD_CURVES are not needed as the loop index is not used outside the loops. The patch is NOT tested with real device. The following is the fuzzing report BUG: KASAN: slab-out-of-bounds in ath5k_eeprom_read_pcal_info_5111+0x126a/0x1390 [ath5k] Write of size 1 at addr ffff8880174a4d60 by task modprobe/214 CPU: 0 PID: 214 Comm: modprobe Not tainted 5.6.0 #1 Call Trace: dump_stack+0x76/0xa0 print_address_description.constprop.0+0x16/0x200 ? ath5k_eeprom_read_pcal_info_5111+0x126a/0x1390 [ath5k] ? ath5k_eeprom_read_pcal_info_5111+0x126a/0x1390 [ath5k] __kasan_report.cold+0x37/0x7c ? ath5k_eeprom_read_pcal_info_5111+0x126a/0x1390 [ath5k] kasan_report+0xe/0x20 ath5k_eeprom_read_pcal_info_5111+0x126a/0x1390 [ath5k] ? apic_timer_interrupt+0xa/0x20 ? ath5k_eeprom_init_11a_pcal_freq+0xbc0/0xbc0 [ath5k] ? ath5k_pci_eeprom_read+0x228/0x3c0 [ath5k] ath5k_eeprom_init+0x2513/0x6290 [ath5k] ? ath5k_eeprom_init_11a_pcal_freq+0xbc0/0xbc0 [ath5k] ? usleep_range+0xb8/0x100 ? apic_timer_interrupt+0xa/0x20 ? ath5k_eeprom_read_pcal_info_2413+0x2f20/0x2f20 [ath5k] ath5k_hw_init+0xb60/0x1970 [ath5k] ath5k_init_ah+0x6fe/0x2530 [ath5k] ? kasprintf+0xa6/0xe0 ? ath5k_stop+0x140/0x140 [ath5k] ? _dev_notice+0xf6/0xf6 ? apic_timer_interrupt+0xa/0x20 ath5k_pci_probe.cold+0x29a/0x3d6 [ath5k] ? ath5k_pci_eeprom_read+0x3c0/0x3c0 [ath5k] ? mutex_lock+0x89/0xd0 ? ath5k_pci_eeprom_read+0x3c0/0x3c0 [ath5k] local_pci_probe+0xd3/0x160 pci_device_probe+0x23f/0x3e0 ? pci_device_remove+0x280/0x280 ? pci_device_remove+0x280/0x280 really_probe+0x209/0x5d0
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-2021-34671

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: ath5k: fix OOB in ath5k_eeprom_read_pcal_info_5111 The bug was found during fuzzing. Stacktrace locates it in ath5k_eeprom_convert_pcal_info_5111. When none of the curve is selected in the loop, idx can go up to AR5K_EEPROM_N_PD_CURVES. The line makes pd out of bound. pd = &chinfo[pier].pd_curves[idx]; There are many OOB writes using pd later in the code. So I added a sanity check for idx. Checks for other loops involving AR5K_EEPROM_N_PD_CURVES are not needed as the loop index is not used outside the loops. The patch is NOT tested with real device. The following is the fuzzing report BUG: KASAN: slab-out-of-bounds in ath5k_eeprom_read_pcal_info_5111+0x126a/0x1390 [ath5k] Write of size 1 at addr ffff8880174a4d60 by task modprobe/214 CPU: 0 PID: 214 Comm: modprobe Not tainted 5.6.0 #1 Call Trace: dump_stack+0x76/0xa0 print_address_description.constprop.0+0x16/0x200 ? ath5k_eeprom_read_pcal_info_5111+0x126a/0x1390 [ath5k] ? ath5k_eeprom_read_pcal_info_5111+0x126a/0x1390 [ath5k] __kasan_report.cold+0x37/0x7c ? ath5k_eeprom_read_pcal_info_5111+0x126a/0x1390 [ath5k] kasan_report+0xe/0x20 ath5k_eeprom_read_pcal_info_5111+0x126a/0x1390 [ath5k] ? apic_timer_interrupt+0xa/0x20 ? ath5k_eeprom_init_11a_pcal_freq+0xbc0/0xbc0 [ath5k] ? ath5k_pci_eeprom_read+0x228/0x3c0 [ath5k] ath5k_eeprom_init+0x2513/0x6290 [ath5k] ? ath5k_eeprom_init_11a_pcal_freq+0xbc0/0xbc0 [ath5k] ? usleep_range+0xb8/0x100 ? apic_timer_interrupt+0xa/0x20 ? ath5k_eeprom_read_pcal_info_2413+0x2f20/0x2f20 [ath5k] ath5k_hw_init+0xb60/0x1970 [ath5k] ath5k_init_ah+0x6fe/0x2530 [ath5k] ? kasprintf+0xa6/0xe0 ? ath5k_stop+0x140/0x140 [ath5k] ? _dev_notice+0xf6/0xf6 ? apic_timer_interrupt+0xa/0x20 ath5k_pci_probe.cold+0x29a/0x3d6 [ath5k] ? ath5k_pci_eeprom_read+0x3c0/0x3c0 [ath5k] ? mutex_lock+0x89/0xd0 ? ath5k_pci_eeprom_read+0x3c0/0x3c0 [ath5k] local_pci_probe+0xd3/0x160 pci_device_probe+0x23f/0x3e0 ? pci_device_remove+0x280/0x280 ? pci_device_remove+0x280/0x280 really_probe+0x209/0x5d0

What

In the Linux kernel, the following vulnerability has been resolved: ath5k: fix OOB in ath5k_eeprom_read_pcal_info_5111 The bug was found during fuzzing. Stacktrace locates it in ath5k_eeprom_convert_pcal_info_5111. When none of the curve is selected in the loop, idx can go up to AR5K_EEPROM_N_PD_CURVES. The line makes pd out of bound. pd = &chinfo[pier].pd_curves[idx]; There are many OOB writes using pd later in the code. So I added a sanity check for idx. Checks for other loops involving AR5K_EEPROM_N_PD_CURVES are not needed as the loop index is not used outside the loops. The patch is NOT tested with real device. The following is the fuzzing report BUG: KASAN: slab-out-of-bounds in ath5k_eeprom_read_pcal_info_5111+0x126a/0x1390 [ath5k] Write of size 1 at addr ffff8880174a4d60 by task modprobe/214 CPU: 0 PID: 214 Comm: modprobe Not tainted 5.6.0 #1 Call Trace: dump_stack+0x76/0xa0 print_address_description.constprop.0+0x16/0x200 ? ath5k_eeprom_read_pcal_info_5111+0x126a/0x1390 [ath5k] ? ath5k_eeprom_read_pcal_info_5111+0x126a/0x1390 [ath5k] __kasan_report.cold+0x37/0x7c ? ath5k_eeprom_read_pcal_info_5111+0x126a/0x1390 [ath5k] kasan_report+0xe/0x20 ath5k_eeprom_read_pcal_info_5111+0x126a/0x1390 [ath5k] ? apic_timer_interrupt+0xa/0x20 ? ath5k_eeprom_init_11a_pcal_freq+0xbc0/0xbc0 [ath5k] ? ath5k_pci_eeprom_read+0x228/0x3c0 [ath5k] ath5k_eeprom_init+0x2513/0x6290 [ath5k] ? ath5k_eeprom_init_11a_pcal_freq+0xbc0/0xbc0 [ath5k] ? usleep_range+0xb8/0x100 ? apic_timer_interrupt+0xa/0x20 ? ath5k_eeprom_read_pcal_info_2413+0x2f20/0x2f20 [ath5k] ath5k_hw_init+0xb60/0x1970 [ath5k] ath5k_init_ah+0x6fe/0x2530 [ath5k] ? kasprintf+0xa6/0xe0 ? ath5k_stop+0x140/0x140 [ath5k] ? _dev_notice+0xf6/0xf6 ? apic_timer_interrupt+0xa/0x20 ath5k_pci_probe.cold+0x29a/0x3d6 [ath5k] ? ath5k_pci_eeprom_read+0x3c0/0x3c0 [ath5k] ? mutex_lock+0x89/0xd0 ? ath5k_pci_eeprom_read+0x3c0/0x3c0 [ath5k] local_pci_probe+0xd3/0x160 pci_device_probe+0x23f/0x3e0 ? pci_device_remove+0x280/0x280 ? pci_device_remove+0x280/0x280 really_probe+0x209/0x5d0

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: ath5k: fix OOB in ath5k_eeprom_read_pcal_info_5111 The bug was found during fuzzing. Stacktrace locates it in ath5k_eeprom_convert_pcal_info_5111. When none of the curve is selected in the loop, idx can go up to AR5K_EEPROM_N_PD_CURVES. The line makes pd out of bound. pd = &chinfo[pier].pd_curves[idx]; There are many OOB writes using pd later in the code. So I added a sanity check for idx. Checks for other loops involving AR5K_EEPROM_N_PD_CURVES are not needed as the loop index is not used outside the loops. The patch is NOT tested with real device. The following is the fuzzing report BUG: KASAN: slab-out-of-bounds in ath5k_eeprom_read_pcal_info_5111+0x126a/0x1390 [ath5k] Write of size 1 at addr ffff8880174a4d60 by task modprobe/214 CPU: 0 PID: 214 Comm: modprobe Not tainted 5.6.0 #1 Call Trace: dump_stack+0x76/0xa0 print_address_description.constprop.0+0x16/0x200 ? ath5k_eeprom_read_pcal_info_5111+0x126a/0x1390 [ath5k] ? ath5k_eeprom_read_pcal_info_5111+0x126a/0x1390 [ath5k] __kasan_report.cold+0x37/0x7c ? ath5k_eeprom_read_pcal_info_5111+0x126a/0x1390 [ath5k] kasan_report+0xe/0x20 ath5k_eeprom_read_pcal_info_5111+0x126a/0x1390 [ath5k] ? apic_timer_interrupt+0xa/0x20 ? ath5k_eeprom_init_11a_pcal_freq+0xbc0/0xbc0 [ath5k] ? ath5k_pci_eeprom_read+0x228/0x3c0 [ath5k] ath5k_eeprom_init+0x2513/0x6290 [ath5k] ? ath5k_eeprom_init_11a_pcal_freq+0xbc0/0xbc0 [ath5k] ? usleep_range+0xb8/0x100 ? apic_timer_interrupt+0xa/0x20 ? ath5k_eeprom_read_pcal_info_2413+0x2f20/0x2f20 [ath5k] ath5k_hw_init+0xb60/0x1970 [ath5k] ath5k_init_ah+0x6fe/0x2530 [ath5k] ? kasprintf+0xa6/0xe0 ? ath5k_stop+0x140/0x140 [ath5k] ? _dev_notice+0xf6/0xf6 ? apic_timer_interrupt+0xa/0x20 ath5k_pci_probe.cold+0x29a/0x3d6 [ath5k] ? ath5k_pci_eeprom_read+0x3c0/0x3c0 [ath5k] ? mutex_lock+0x89/0xd0 ? ath5k_pci_eeprom_read+0x3c0/0x3c0 [ath5k] local_pci_probe+0xd3/0x160 pci_device_probe+0x23f/0x3e0 ? pci_device_remove+0x280/0x280 ? pci_device_remove+0x280/0x280 really_probe+0x209/0x5d0

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.

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-2026-AVI-0128Multiples vulnérabilités dans le noyau Linux de SUSE

2026 https://www.suse.com/support/update/announcement/2026/suse-su-202620207-1 Bulletin de sécurité SUSE SUSE-SU-2026:20220-1 du 02 février 2026 https://www.suse.com/support/update/announcement/2026/suse-su-202620220-1 Bulletin de sécurité SUSE SUSE-SU-2026:20228-1 du 02 février 2026 https://www.suse.com/support/update/announcement/2026/suse-su-202620228-1 Bulletin de sécurité SUSE SUSE-SU-2026:0369-1 du 03 février 2026 https://www.suse.com/support/update/announcement/2026/suse-su-20260369-1 Bulletin de sécurité SUSE SUSE-SU-2026:0385-1 du 04 février 2026 https://www.suse.com/support/update/announcement/2026/suse-su-20260385-1 Référence CVE CVE-2021-47633 https://www.cve.org/CVERecord?id=CVE-2021-47633 Référence CVE CVE-2022-0854 https://www.cve.org/CVERecord?id=CVE-2022-0854 Référence CVE CVE-2022-1048 https://www.cve.org/CVERecord?id=CVE-2022-1048 Référence CVE CVE-2022-3303 https://www.cve.org/CVERecord?id=CVE-2022-3303 Référence CVE CVE-2022-48853 https://www.cve.org/CVERecord?id=CVE-2022-48853 Référence CVE CVE-2022-49272 https://www.cve.org/CVERecord?id=CVE-2022-49272 Référence CVE CVE-2022-49288 https://www.cve.org/CVERecord?id=CVE-2022-49288 Référence CVE CVE-2022-49291 https://www.cve.org/CVERecord?id=CVE-2022-49291 Référence CVE CVE-2022-49545 https://www.cve.org/CVERecord?id=CVE-20

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

Record?id=CVE-2017-5753 Référence CVE CVE-2020-27835 https://www.cve.org/CVERecord?id=CVE-2020-27835 Référence CVE CVE-2021-4453 https://www.cve.org/CVERecord?id=CVE-2021-4453 Référence CVE CVE-2021-4454 https://www.cve.org/CVERecord?id=CVE-2021-4454 Référence CVE CVE-2021-46925 https://www.cve.org/CVERecord?id=CVE-2021-46925 Référence CVE CVE-2021-47248 https://www.cve.org/CVERecord?id=CVE-2021-47248 Référence CVE CVE-2021-47517 https://www.cve.org/CVERecord?id=CVE-2021-47517 Référence CVE CVE-2021-47631 https://www.cve.org/CVERecord?id=CVE-2021-47631 Référence CVE CVE-2021-47632 https://www.cve.org/CVERecord?id=CVE-2021-47632 Référence CVE CVE-2021-47633 https://www.cve.org/CVERecord?id=CVE-2021-47633 Référence CVE CVE-2021-47635 https://www.cve.org/CVERecord?id=CVE-2021-47635 Référence CVE CVE-2021-47636 https://www.cve.org/CVERecord?id=CVE-2021-47636 Référence CVE CVE-2021-47637 https://www.cve.org/CVERecord?id=CVE-2021-47637 Référence CVE CVE-2021-47638 https://www.cve.org/CVERecord?id=CVE-2021-47638 Référence CVE CVE-2021-47639 https://www.cve.org/CVERecord?id=CVE-2021-47639 Référence CVE CVE-2021-47641 https://www.cve.org/CVERecord?id=CVE-2021-47641 Référence CVE CVE-2021-47642 https://www.cve.org/CVERecord?id=CVE-2021-47642 Référence CVE CVE-2021-47643 https://www.cve.org/CVERecord?id=

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

t/2025/suse-su-20251195-1 Référence CVE CVE-2017-5753 https://www.cve.org/CVERecord?id=CVE-2017-5753 Référence CVE CVE-2020-27835 https://www.cve.org/CVERecord?id=CVE-2020-27835 Référence CVE CVE-2021-4453 https://www.cve.org/CVERecord?id=CVE-2021-4453 Référence CVE CVE-2021-4454 https://www.cve.org/CVERecord?id=CVE-2021-4454 Référence CVE CVE-2021-47248 https://www.cve.org/CVERecord?id=CVE-2021-47248 Référence CVE CVE-2021-47517 https://www.cve.org/CVERecord?id=CVE-2021-47517 Référence CVE CVE-2021-47631 https://www.cve.org/CVERecord?id=CVE-2021-47631 Référence CVE CVE-2021-47632 https://www.cve.org/CVERecord?id=CVE-2021-47632 Référence CVE CVE-2021-47633 https://www.cve.org/CVERecord?id=CVE-2021-47633 Référence CVE CVE-2021-47635 https://www.cve.org/CVERecord?id=CVE-2021-47635 Référence CVE CVE-2021-47636 https://www.cve.org/CVERecord?id=CVE-2021-47636 Référence CVE CVE-2021-47637 https://www.cve.org/CVERecord?id=CVE-2021-47637 Référence CVE CVE-2021-47638 https://www.cve.org/CVERecord?id=CVE-2021-47638 Référence CVE CVE-2021-47639 https://www.cve.org/CVERecord?id=CVE-2021-47639 Référence CVE CVE-2021-47641 https://www.cve.org/CVERecord?id=CVE-2021-47641 Référence CVE CVE-2021-47642 https://www.cve.org/CVERecord?id=CVE-2021-47642 Référence CVE CVE-2021-47643 https://www.cve.org/CVERecord?id=

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

es. Solutions Se référer au bulletin de sécurité de l'éditeur pour l'obtention des correctifs (cf. section Documentation). Documentation Bulletin de sécurité SUSE SUSE-SU-2025:0983-1 du 21 mars 2025 https://www.suse.com/support/update/announcement/2025/suse-su-20250983-1 Bulletin de sécurité SUSE SUSE-SU-2025:1027-1 du 26 mars 2025 https://www.suse.com/support/update/announcement/2025/suse-su-20251027-1 Référence CVE CVE-2021-4453 https://www.cve.org/CVERecord?id=CVE-2021-4453 Référence CVE CVE-2021-47631 https://www.cve.org/CVERecord?id=CVE-2021-47631 Référence CVE CVE-2021-47632 https://www.cve.org/CVERecord?id=CVE-2021-47632 Référence CVE CVE-2021-47633 https://www.cve.org/CVERecord?id=CVE-2021-47633 Référence CVE CVE-2021-47635 https://www.cve.org/CVERecord?id=CVE-2021-47635 Référence CVE CVE-2021-47636 https://www.cve.org/CVERecord?id=CVE-2021-47636 Référence CVE CVE-2021-47637 https://www.cve.org/CVERecord?id=CVE-2021-47637 Référence CVE CVE-2021-47638 https://www.cve.org/CVERecord?id=CVE-2021-47638 Référence CVE CVE-2021-47639 https://www.cve.org/CVERecord?id=CVE-2021-47639 Référence CVE CVE-2021-47641 https://www.cve.org/CVERecord?id=CVE-2021-47641 Référence CVE CVE-2021-47642 https://www.cve.org/CVERecord?id=CVE-2021-47642 Référence CVE CVE-2021-47643 https://www.cve.org/CVERecord?id=

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

025 https://www.suse.com/support/update/announcement/2025/suse-su-20250952-1 Bulletin de sécurité SUSE SUSE-SU-2025:0955-1 du 19 mars 2025 https://www.suse.com/support/update/announcement/2025/suse-su-20250955-1 Bulletin de sécurité SUSE SUSE-SU-2025:0961-1 du 19 mars 2025 https://www.suse.com/support/update/announcement/2025/suse-su-20250961-1 Bulletin de sécurité SUSE SUSE-SU-2025:0962-1 du 19 mars 2025 https://www.suse.com/support/update/announcement/2025/suse-su-20250962-1 Référence CVE CVE-2021-47261 https://www.cve.org/CVERecord?id=CVE-2021-47261 Référence CVE CVE-2021-47496 https://www.cve.org/CVERecord?id=CVE-2021-47496 Référence CVE CVE-2021-47633 https://www.cve.org/CVERecord?id=CVE-2021-47633 Référence CVE CVE-2022-48792 https://www.cve.org/CVERecord?id=CVE-2022-48792 Référence CVE CVE-2022-48911 https://www.cve.org/CVERecord?id=CVE-2022-48911 Référence CVE CVE-2022-49080 https://www.cve.org/CVERecord?id=CVE-2022-49080 Référence CVE CVE-2023-1192 https://www.cve.org/CVERecord?id=CVE-2023-1192 Référence CVE CVE-2023-4244 https://www.cve.org/CVERecord?id=CVE-2023-4244 Référence CVE CVE-2023-52572 https://www.cve.org/CVERecord?id=CVE-2023-52572 Référence CVE CVE-2023-52923 https://www.cve.org/CVERecord?id=CVE-2023-52923 Référence CVE CVE-2023-52924 https://www.cve.org/CVERecord?id=CVE-

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

Bulletin de sécurité SUSE SUSE-SU-2025:0853-1 du 13 mars 2025 https://www.suse.com/support/update/announcement/2025/suse-su-20250853-1 Bulletin de sécurité SUSE SUSE-SU-2025:0855-1 du 13 mars 2025 https://www.suse.com/support/update/announcement/2025/suse-su-20250855-1 Bulletin de sécurité SUSE SUSE-SU-2025:0856-1 du 13 mars 2025 https://www.suse.com/support/update/announcement/2025/suse-su-20250856-1 Référence CVE CVE-2021-22543 https://www.cve.org/CVERecord?id=CVE-2021-22543 Référence CVE CVE-2021-37159 https://www.cve.org/CVERecord?id=CVE-2021-37159 Référence CVE CVE-2021-47202 https://www.cve.org/CVERecord?id=CVE-2021-47202 Référence CVE CVE-2021-47633 https://www.cve.org/CVERecord?id=CVE-2021-47633 Référence CVE CVE-2021-47634 https://www.cve.org/CVERecord?id=CVE-2021-47634 Référence CVE CVE-2021-47644 https://www.cve.org/CVERecord?id=CVE-2021-47644 Référence CVE CVE-2022-2991 https://www.cve.org/CVERecord?id=CVE-2022-2991 Référence CVE CVE-2022-36280 https://www.cve.org/CVERecord?id=CVE-2022-36280 Référence CVE CVE-2022-48636 https://www.cve.org/CVERecord?id=CVE-2022-48636 Référence CVE CVE-2022-48650 https://www.cve.org/CVERecord?id=CVE-2022-48650 Référence CVE CVE-2022-48664 https://www.cve.org/CVERecord?id=CVE-2022-48664 Référence CVE CVE-2022-48742 https://www.cve.org/CVERecord?id=CV

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2021-021982Linux の 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.30, 4.9.311 ≤ 4.9.*, 4.14.276 ≤ 4.14.*, 4.19.238 ≤ 4.19.*, 5.4.189 ≤ 5.4.*, 5.10.111 ≤ 5.10.*, 5.15.34 ≤ 5.15.*, 5.16.20 ≤ 5.16.*, 5.17.3 ≤ 5.17.*, 5.18 ≤ *
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, 13: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-2021-34671
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceNIST NVD
NVD statusNVD enriched

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-2021-34671↗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-2021-47633 · cve.blacktree.nl