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

wifi: iwlwifi: mvm: Fix a memory corruption issue

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 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.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.6.5.8-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.64-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.5.8-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.5.8-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 6 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-2023-52531 · CSAF 2.0 · revision 66 · interimSUSE Product Security TeamCVE-2023-52531
150 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: wifi: iwlwifi: mvm: Fix a memory corruption issue A few lines above, space is kzalloc()'ed for: sizeof(struct iwl_nvm_data) + sizeof(struct ieee80211_channel) + sizeof(struct ieee80211_rate) 'mvm->nvm_data' is a 'struct iwl_nvm_data', so it is fine. At the end of this structure, there is the 'channels' flex array. Each element is of type 'struct ieee80211_channel'. So only 1 element is allocated in this array. When doing: mvm->nvm_data->bands[0].channels = mvm->nvm_data->channels; We point at the first element of the 'channels' flex array. So this is fine. However, when doing: mvm->nvm_data->bands[0].bitrates = (void *)((u8 *)mvm->nvm_data->channels + 1); because of the "(u8 *)" cast, we add only 1 to the address of the beginning of the flex array. It is likely that we want point at the 'struct ieee80211_rate' allocated just after. Remove the spurious casting so that the pointer arithmetic works as expected.
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-2023-57156

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: wifi: iwlwifi: mvm: Fix a memory corruption issue A few lines above, space is kzalloc()'ed for: sizeof(struct iwl_nvm_data) + sizeof(struct ieee80211_channel) + sizeof(struct ieee80211_rate) 'mvm->nvm_data' is a 'struct iwl_nvm_data', so it is fine. At the end of this structure, there is the 'channels' flex array. Each element is of type 'struct ieee80211_channel'. So only 1 element is allocated in this array. When doing: mvm->nvm_data->bands[0].channels = mvm->nvm_data->channels; We point at the first element of the 'channels' flex array. So this is fine. However, when doing: mvm->nvm_data->bands[0].bitrates = (void *)((u8 *)mvm->nvm_data->channels + 1); because of the "(u8 *)" cast, we add only 1 to the address of the beginning of the flex array. It is likely that we want point at the 'struct ieee80211_rate' allocated just after. Remove the spurious casting so that the pointer arithmetic works as expected.

What

In the Linux kernel, the following vulnerability has been resolved: wifi: iwlwifi: mvm: Fix a memory corruption issue A few lines above, space is kzalloc()'ed for: sizeof(struct iwl_nvm_data) + sizeof(struct ieee80211_channel) + sizeof(struct ieee80211_rate) 'mvm->nvm_data' is a 'struct iwl_nvm_data', so it is fine. At the end of this structure, there is the 'channels' flex array. Each element is of type 'struct ieee80211_channel'. So only 1 element is allocated in this array. When doing: mvm->nvm_data->bands[0].channels = mvm->nvm_data->channels; We point at the first element of the 'channels' flex array. So this is fine. However, when doing: mvm->nvm_data->bands[0].bitrates = (void *)((u8 *)mvm->nvm_data->channels + 1); because of the "(u8 *)" cast, we add only 1 to the address of the beginning of the flex array. It is likely that we want point at the 'struct ieee80211_rate' allocated just after. Remove the spurious casting so that the pointer arithmetic works as expected.

Why

A bounds error lets data be written beyond the intended memory region, potentially corrupting control data.

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: wifi: iwlwifi: mvm: Fix a memory corruption issue A few lines above, space is kzalloc()'ed for: sizeof(struct iwl_nvm_data) + sizeof(struct ieee80211_channel) + sizeof(struct ieee80211_rate) 'mvm->nvm_data' is a 'struct iwl_nvm_data', so it is fine. At the end of this structure, there is the 'channels' flex array. Each element is of type 'struct ieee80211_channel'. So only 1 element is allocated in this array. When doing: mvm->nvm_data->bands[0].channels = mvm->nvm_data->channels; We point at the first element of the 'channels' flex array. So this is fine. However, when doing: mvm->nvm_data->bands[0].bitrates = (void *)((u8 *)mvm->nvm_data->channels + 1); because of the "(u8 *)" cast, we add only 1 to the address of the beginning of the flex array. It is likely that we want point at the 'struct ieee80211_rate' allocated just after. Remove the spurious casting so that the pointer arithmetic works as expected.

Why

A bounds error lets data be written beyond the intended memory region, potentially corrupting control data.

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 Write → 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-787 ↗

CWE-787: Out-of-bounds Write. The product writes 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: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-787
A

Official authority intelligence

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

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

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

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20240306Security Bulletin 06 Mar 2024

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

Official advisory ↗
CERT-FR · French · CERTFR-2024-AVI-1080Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2022-24448 Référence CVE CVE-2022-48666 https://www.cve.org/CVERecord?id=CVE-2022-48666 Référence CVE CVE-2022-48733 https://www.cve.org/CVERecord?id=CVE-2022-48733 Référence CVE CVE-2022-48938 https://www.cve.org/CVERecord?id=CVE-2022-48938 Référence CVE CVE-2022-48943 https://www.cve.org/CVERecord?id=CVE-2022-48943 Référence CVE CVE-2023-52488 https://www.cve.org/CVERecord?id=CVE-2023-52488 Référence CVE CVE-2023-52497 https://www.cve.org/CVERecord?id=CVE-2023-52497 Référence CVE CVE-2023-52498 https://www.cve.org/CVERecord?id=CVE-2023-52498 Référence CVE CVE-2023-52502 https://www.cve.org/CVERecord?id=CVE-2023-52502 Référence CVE CVE-2023-52531 https://www.cve.org/CVERecord?id=CVE-2023-52531 Référence CVE CVE-2023-52578 https://www.cve.org/CVERecord?id=CVE-2023-52578 Référence CVE CVE-2023-52599 https://www.cve.org/CVERecord?id=CVE-2023-52599 Référence CVE CVE-2023-52614 https://www.cve.org/CVERecord?id=CVE-2023-52614 Référence CVE CVE-2023-52639 https://www.cve.org/CVERecord?id=CVE-2023-52639 Référence CVE CVE-2023-52887 https://www.cve.org/CVERecord?id=CVE-2023-52887 Référence CVE CVE-2023-52888 https://www.cve.org/CVERecord?id=CVE-2023-52888 Référence CVE CVE-2023-52889 https://www.cve.org/CVERecord?id=CVE-2023-52889 Référence CVE CVE-2023-52918 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2024-AVI-1049Multiples vulnérabilités dans le noyau Linux d'Ubuntu

une atteinte à la confidentialité des données et une atteinte à l'intégrité des donné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é Ubuntu USN-7121-3 du 25 novembre 2024 https://ubuntu.com/security/notices/USN-7121-3 Référence CVE CVE-2022-48733 https://www.cve.org/CVERecord?id=CVE-2022-48733 Référence CVE CVE-2022-48938 https://www.cve.org/CVERecord?id=CVE-2022-48938 Référence CVE CVE-2022-48943 https://www.cve.org/CVERecord?id=CVE-2022-48943 Référence CVE CVE-2023-52502 https://www.cve.org/CVERecord?id=CVE-2023-52502 Référence CVE CVE-2023-52531 https://www.cve.org/CVERecord?id=CVE-2023-52531 Référence CVE CVE-2023-52578 https://www.cve.org/CVERecord?id=CVE-2023-52578 Référence CVE CVE-2023-52599 https://www.cve.org/CVERecord?id=CVE-2023-52599 Référence CVE CVE-2023-52612 https://www.cve.org/CVERecord?id=CVE-2023-52612 Référence CVE CVE-2023-52614 https://www.cve.org/CVERecord?id=CVE-2023-52614 Référence CVE CVE-2023-52639 https://www.cve.org/CVERecord?id=CVE-2023-52639 Référence CVE CVE-2024-26633 https://www.cve.org/CVERecord?id=CVE-2024-26633 Référence CVE CVE-2024-26636 https://www.cve.org/CVERecord?id=CVE-2024-26636 Référence CVE CVE-2024-26668 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2024-AVI-1013Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2022-36402 Référence CVE CVE-2022-48666 https://www.cve.org/CVERecord?id=CVE-2022-48666 Référence CVE CVE-2022-48733 https://www.cve.org/CVERecord?id=CVE-2022-48733 Référence CVE CVE-2022-48791 https://www.cve.org/CVERecord?id=CVE-2022-48791 Référence CVE CVE-2022-48863 https://www.cve.org/CVERecord?id=CVE-2022-48863 Référence CVE CVE-2022-48938 https://www.cve.org/CVERecord?id=CVE-2022-48938 Référence CVE CVE-2022-48943 https://www.cve.org/CVERecord?id=CVE-2022-48943 Référence CVE CVE-2023-52434 https://www.cve.org/CVERecord?id=CVE-2023-52434 Référence CVE CVE-2023-52502 https://www.cve.org/CVERecord?id=CVE-2023-52502 Référence CVE CVE-2023-52531 https://www.cve.org/CVERecord?id=CVE-2023-52531 Référence CVE CVE-2023-52572 https://www.cve.org/CVERecord?id=CVE-2023-52572 Référence CVE CVE-2023-52578 https://www.cve.org/CVERecord?id=CVE-2023-52578 Référence CVE CVE-2023-52599 https://www.cve.org/CVERecord?id=CVE-2023-52599 Référence CVE CVE-2023-52612 https://www.cve.org/CVERecord?id=CVE-2023-52612 Référence CVE CVE-2023-52614 https://www.cve.org/CVERecord?id=CVE-2023-52614 Référence CVE CVE-2023-52639 https://www.cve.org/CVERecord?id=CVE-2023-52639 Référence CVE CVE-2023-52751 https://www.cve.org/CVERecord?id=CVE-2023-52751 Référence CVE CVE-2023-52757 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2024-AVI-0997Multiples vulnérabilités dans le noyau Linux d'Ubuntu

/CVERecord?id=CVE-2020-7039 Référence CVE CVE-2020-8608 https://www.cve.org/CVERecord?id=CVE-2020-8608 Référence CVE CVE-2021-3592 https://www.cve.org/CVERecord?id=CVE-2021-3592 Référence CVE CVE-2021-3594 https://www.cve.org/CVERecord?id=CVE-2021-3594 Référence CVE CVE-2021-47212 https://www.cve.org/CVERecord?id=CVE-2021-47212 Référence CVE CVE-2022-36402 https://www.cve.org/CVERecord?id=CVE-2022-36402 Référence CVE CVE-2022-48666 https://www.cve.org/CVERecord?id=CVE-2022-48666 Référence CVE CVE-2023-3019 https://www.cve.org/CVERecord?id=CVE-2023-3019 Référence CVE CVE-2023-52528 https://www.cve.org/CVERecord?id=CVE-2023-52528 Référence CVE CVE-2023-52531 https://www.cve.org/CVERecord?id=CVE-2023-52531 Référence CVE CVE-2023-52614 https://www.cve.org/CVERecord?id=CVE-2023-52614 Référence CVE CVE-2023-52887 https://www.cve.org/CVERecord?id=CVE-2023-52887 Référence CVE CVE-2023-52888 https://www.cve.org/CVERecord?id=CVE-2023-52888 Référence CVE CVE-2023-52889 https://www.cve.org/CVERecord?id=CVE-2023-52889 Référence CVE CVE-2023-52918 https://www.cve.org/CVERecord?id=CVE-2023-52918 Référence CVE CVE-2024-25741 https://www.cve.org/CVERecord?id=CVE-2024-25741 Référence CVE CVE-2024-25744 https://www.cve.org/CVERecord?id=CVE-2024-25744 Référence CVE CVE-2024-26607 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2024-AVI-0957Multiples vulnérabilités dans le noyau Linux d'Ubuntu

embre 2024 https://ubuntu.com/security/notices/LSN-0107-1 Bulletin de sécurité Ubuntu USN-7088-3 du 06 novembre 2024 https://ubuntu.com/security/notices/USN-7088-3 Bulletin de sécurité Ubuntu USN-7088-4 du 07 novembre 2024 https://ubuntu.com/security/notices/USN-7088-4 Bulletin de sécurité Ubuntu USN-7089-3 du 07 novembre 2024 https://ubuntu.com/security/notices/USN-7089-3 Bulletin de sécurité Ubuntu USN-7095-1 du 07 novembre 2024 https://ubuntu.com/security/notices/USN-7095-1 Référence CVE CVE-2021-47212 https://www.cve.org/CVERecord?id=CVE-2021-47212 Référence CVE CVE-2022-36402 https://www.cve.org/CVERecord?id=CVE-2022-36402 Référence CVE CVE-2023-52531 https://www.cve.org/CVERecord?id=CVE-2023-52531 Référence CVE CVE-2023-52614 https://www.cve.org/CVERecord?id=CVE-2023-52614 Référence CVE CVE-2023-52887 https://www.cve.org/CVERecord?id=CVE-2023-52887 Référence CVE CVE-2023-52888 https://www.cve.org/CVERecord?id=CVE-2023-52888 Référence CVE CVE-2023-52918 https://www.cve.org/CVERecord?id=CVE-2023-52918 Référence CVE CVE-2024-25741 https://www.cve.org/CVERecord?id=CVE-2024-25741 Référence CVE CVE-2024-26607 https://www.cve.org/CVERecord?id=CVE-2024-26607 Référence CVE CVE-2024-26640 https://www.cve.org/CVERecord?id=CVE-2024-26640 Référence CVE CVE-2024-26641 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2023-52518 Référence CVE CVE-2023-52519 https://www.cve.org/CVERecord?id=CVE-2023-52519 Référence CVE CVE-2023-52520 https://www.cve.org/CVERecord?id=CVE-2023-52520 Référence CVE CVE-2023-52523 https://www.cve.org/CVERecord?id=CVE-2023-52523 Référence CVE CVE-2023-52524 https://www.cve.org/CVERecord?id=CVE-2023-52524 Référence CVE CVE-2023-52525 https://www.cve.org/CVERecord?id=CVE-2023-52525 Référence CVE CVE-2023-52528 https://www.cve.org/CVERecord?id=CVE-2023-52528 Référence CVE CVE-2023-52529 https://www.cve.org/CVERecord?id=CVE-2023-52529 Référence CVE CVE-2023-52530 https://www.cve.org/CVERecord?id=CVE-2023-52530 Référence CVE CVE-2023-52531 https://www.cve.org/CVERecord?id=CVE-2023-52531 Référence CVE CVE-2023-52532 https://www.cve.org/CVERecord?id=CVE-2023-52532 Référence CVE CVE-2023-52559 https://www.cve.org/CVERecord?id=CVE-2023-52559 Référence CVE CVE-2023-52561 https://www.cve.org/CVERecord?id=CVE-2023-52561 Référence CVE CVE-2023-52563 https://www.cve.org/CVERecord?id=CVE-2023-52563 Référence CVE CVE-2023-52564 https://www.cve.org/CVERecord?id=CVE-2023-52564 Référence CVE CVE-2023-52566 https://www.cve.org/CVERecord?id=CVE-2023-52566 Référence CVE CVE-2023-52567 https://www.cve.org/CVERecord?id=CVE-2023-52567 Référence CVE CVE-2023-52569 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2023-52518 Référence CVE CVE-2023-52519 https://www.cve.org/CVERecord?id=CVE-2023-52519 Référence CVE CVE-2023-52520 https://www.cve.org/CVERecord?id=CVE-2023-52520 Référence CVE CVE-2023-52523 https://www.cve.org/CVERecord?id=CVE-2023-52523 Référence CVE CVE-2023-52524 https://www.cve.org/CVERecord?id=CVE-2023-52524 Référence CVE CVE-2023-52525 https://www.cve.org/CVERecord?id=CVE-2023-52525 Référence CVE CVE-2023-52528 https://www.cve.org/CVERecord?id=CVE-2023-52528 Référence CVE CVE-2023-52529 https://www.cve.org/CVERecord?id=CVE-2023-52529 Référence CVE CVE-2023-52530 https://www.cve.org/CVERecord?id=CVE-2023-52530 Référence CVE CVE-2023-52531 https://www.cve.org/CVERecord?id=CVE-2023-52531 Référence CVE CVE-2023-52532 https://www.cve.org/CVERecord?id=CVE-2023-52532 Référence CVE CVE-2023-52559 https://www.cve.org/CVERecord?id=CVE-2023-52559 Référence CVE CVE-2023-52563 https://www.cve.org/CVERecord?id=CVE-2023-52563 Référence CVE CVE-2023-52564 https://www.cve.org/CVERecord?id=CVE-2023-52564 Référence CVE CVE-2023-52566 https://www.cve.org/CVERecord?id=CVE-2023-52566 Référence CVE CVE-2023-52567 https://www.cve.org/CVERecord?id=CVE-2023-52567 Référence CVE CVE-2023-52569 https://www.cve.org/CVERecord?id=CVE-2023-52569 Référence CVE CVE-2023-52574 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2023-52463 Référence CVE CVE-2023-52464 https://www.cve.org/CVERecord?id=CVE-2023-52464 Référence CVE CVE-2023-52467 https://www.cve.org/CVERecord?id=CVE-2023-52467 Référence CVE CVE-2023-52475 https://www.cve.org/CVERecord?id=CVE-2023-52475 Référence CVE CVE-2023-52478 https://www.cve.org/CVERecord?id=CVE-2023-52478 Référence CVE CVE-2023-52482 https://www.cve.org/CVERecord?id=CVE-2023-52482 Référence CVE CVE-2023-52484 https://www.cve.org/CVERecord?id=CVE-2023-52484 Référence CVE CVE-2023-52502 https://www.cve.org/CVERecord?id=CVE-2023-52502 Référence CVE CVE-2023-52530 https://www.cve.org/CVERecord?id=CVE-2023-52530 Référence CVE CVE-2023-52531 https://www.cve.org/CVERecord?id=CVE-2023-52531 Référence CVE CVE-2023-52532 https://www.cve.org/CVERecord?id=CVE-2023-52532 Référence CVE CVE-2023-52559 https://www.cve.org/CVERecord?id=CVE-2023-52559 Référence CVE CVE-2023-52569 https://www.cve.org/CVERecord?id=CVE-2023-52569 Référence CVE CVE-2023-52574 https://www.cve.org/CVERecord?id=CVE-2023-52574 Référence CVE CVE-2023-52597 https://www.cve.org/CVERecord?id=CVE-2023-52597 Référence CVE CVE-2023-52605 https://www.cve.org/CVERecord?id=CVE-2023-52605 Référence CVE CVE-2023-6270 https://www.cve.org/CVERecord?id=CVE-2023-6270 Référence CVE CVE-2023-6356 https://www.cve.org/CVERecord?id=CVE

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

d?id=CVE-2023-52463 Référence CVE CVE-2023-52464 https://www.cve.org/CVERecord?id=CVE-2023-52464 Référence CVE CVE-2023-52467 https://www.cve.org/CVERecord?id=CVE-2023-52467 Référence CVE CVE-2023-52475 https://www.cve.org/CVERecord?id=CVE-2023-52475 Référence CVE CVE-2023-52478 https://www.cve.org/CVERecord?id=CVE-2023-52478 Référence CVE CVE-2023-52482 https://www.cve.org/CVERecord?id=CVE-2023-52482 Référence CVE CVE-2023-52484 https://www.cve.org/CVERecord?id=CVE-2023-52484 Référence CVE CVE-2023-52502 https://www.cve.org/CVERecord?id=CVE-2023-52502 Référence CVE CVE-2023-52530 https://www.cve.org/CVERecord?id=CVE-2023-52530 Référence CVE CVE-2023-52531 https://www.cve.org/CVERecord?id=CVE-2023-52531 Référence CVE CVE-2023-52532 https://www.cve.org/CVERecord?id=CVE-2023-52532 Référence CVE CVE-2023-52559 https://www.cve.org/CVERecord?id=CVE-2023-52559 Référence CVE CVE-2023-52569 https://www.cve.org/CVERecord?id=CVE-2023-52569 Référence CVE CVE-2023-52574 https://www.cve.org/CVERecord?id=CVE-2023-52574 Référence CVE CVE-2023-52597 https://www.cve.org/CVERecord?id=CVE-2023-52597 Référence CVE CVE-2023-52605 https://www.cve.org/CVERecord?id=CVE-2023-52605 Référence CVE CVE-2023-6270 https://www.cve.org/CVERecord?id=CVE-2023-6270 Référence CVE CVE-2023-6817 https://www.cve.org/CVERecord?id=CVE

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2023-027586Linux の 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: < 3.9, 5.15.135 ≤ 5.15.*, 6.1.57 ≤ 6.1.*, 6.5.7 ≤ 6.5.*, 6.6 ≤ *
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 2 Mar 2024 · Last source change 11 May 2026, 19:29 UTC · CWE-787 · Out-of-bounds Write

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-2023-57156
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-2023-57156↗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-2023-52531 · cve.blacktree.nl