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

perf/x86/lbr: Filter vsyscall addresses

Linux · Linux

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

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

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • Exploitation requires an existing local or physical foothold with privileges.
  • EPSS is 0.23% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict local access and enforce least privilege on affected hosts.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs Linux Linux and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: No default targetRemediation target: Normal maintenance

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 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 5 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.64-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.5.8-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.5.8-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-2023-52476 · CSAF 2.0 · revision 79 · interimSUSE Product Security TeamCVE-2023-52476
149 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: perf/x86/lbr: Filter vsyscall addresses We found that a panic can occur when a vsyscall is made while LBR sampling is active. If the vsyscall is interrupted (NMI) for perf sampling, this call sequence can occur (most recent at top): __insn_get_emulate_prefix() insn_get_emulate_prefix() insn_get_prefixes() insn_get_opcode() decode_branch_type() get_branch_type() intel_pmu_lbr_filter() intel_pmu_handle_irq() perf_event_nmi_handler() Within __insn_get_emulate_prefix() at frame 0, a macro is called: peek_nbyte_next(insn_byte_t, insn, i) Within this macro, this dereference occurs: (insn)->next_byte Inspecting registers at this point, the value of the next_byte field is the address of the vsyscall made, for example the location of the vsyscall version of gettimeofday() at 0xffffffffff600000. The access to an address in the vsyscall region will trigger an oops due to an unhandled page fault. To fix the bug, filtering for vsyscalls can be done when determining the branch type. This patch will return a "none" branch if a kernel address if found to lie in the vsyscall region.
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-57101

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 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: perf/x86/lbr: Filter vsyscall addresses We found that a panic can occur when a vsyscall is made while LBR sampling is active. If the vsyscall is interrupted (NMI) for perf sampling, this call sequence can occur (most recent at top): __insn_get_emulate_prefix() insn_get_emulate_prefix() insn_get_prefixes() insn_get_opcode() decode_branch_type() get_branch_type() intel_pmu_lbr_filter() intel_pmu_handle_irq() perf_event_nmi_handler() Within __insn_get_emulate_prefix() at frame 0, a macro is called: peek_nbyte_next(insn_byte_t, insn, i) Within this macro, this dereference occurs: (insn)->next_byte Inspecting registers at this point, the value of the next_byte field is the address of the vsyscall made, for example the location of the vsyscall version of gettimeofday() at 0xffffffffff600000. The access to an address in the vsyscall region will trigger an oops due to an unhandled page fault. To fix the bug, filtering for vsyscalls can be done when determining the branch type. This patch will return a "none" branch if a kernel address if found to lie in the vsyscall region.

What

In the Linux kernel, the following vulnerability has been resolved: perf/x86/lbr: Filter vsyscall addresses We found that a panic can occur when a vsyscall is made while LBR sampling is active. If the vsyscall is interrupted (NMI) for perf sampling, this call sequence can occur (most recent at top): __insn_get_emulate_prefix() insn_get_emulate_prefix() insn_get_prefixes() insn_get_opcode() decode_branch_type() get_branch_type() intel_pmu_lbr_filter() intel_pmu_handle_irq() perf_event_nmi_handler() Within __insn_get_emulate_prefix() at frame 0, a macro is called: peek_nbyte_next(insn_byte_t, insn, i) Within this macro, this dereference occurs: (insn)->next_byte Inspecting registers at this point, the value of the next_byte field is the address of the vsyscall made, for example the location of the vsyscall version of gettimeofday() at 0xffffffffff600000. The access to an address in the vsyscall region will trigger an oops due to an unhandled page fault. To fix the bug, filtering for vsyscalls can be done when determining the branch type. This patch will return a "none" branch if a kernel address if found to lie in the vsyscall region.

Why

The current structured CVE record identifies a security weakness, but the root cause requires confirmation in the linked vendor material.

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: perf/x86/lbr: Filter vsyscall addresses We found that a panic can occur when a vsyscall is made while LBR sampling is active. If the vsyscall is interrupted (NMI) for perf sampling, this call sequence can occur (most recent at top): __insn_get_emulate_prefix() insn_get_emulate_prefix() insn_get_prefixes() insn_get_opcode() decode_branch_type() get_branch_type() intel_pmu_lbr_filter() intel_pmu_handle_irq() perf_event_nmi_handler() Within __insn_get_emulate_prefix() at frame 0, a macro is called: peek_nbyte_next(insn_byte_t, insn, i) Within this macro, this dereference occurs: (insn)->next_byte Inspecting registers at this point, the value of the next_byte field is the address of the vsyscall made, for example the location of the vsyscall version of gettimeofday() at 0xffffffffff600000. The access to an address in the vsyscall region will trigger an oops due to an unhandled page fault. To fix the bug, filtering for vsyscalls can be done when determining the branch type. This patch will return a "none" branch if a kernel address if found to lie in the vsyscall region.

Why

The current structured CVE record identifies a security weakness, but the root cause requires confirmation in the linked vendor material.

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 → vulnerable operation → 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.
CWE not yet assigned
CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRLowPrivileges required: The attacker needs basic user-level privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CNoneConfidentiality impact: No direct loss is represented by this metric.INoneIntegrity impact: No direct loss is represented by this metric.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.
A

Official authority intelligence

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

BSI · German · WID-SEC-2024-1226Red Hat OpenShift: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in Red Hat OpenShift ausnutzen, um Dateien zu manipulieren, einen Denial-of-Service-Zustand zu verursachen, beliebigen Code auszuführen, vertrauliche Informationen offenzulegen, seine Privilegien zu erweitern oder um weitere nicht spezifizierte Angriffe auszuführen.

Official advisory ↗
BSI · German · WID-SEC-2024-0511Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service und unspezifische Angriffe

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-2026-AVI-1165Multiples vulnérabilités dans les produits IBM

rd?id=CVE-2023-5090 Référence CVE CVE-2023-51074 https://www.cve.org/CVERecord?id=CVE-2023-51074 Référence CVE CVE-2023-52428 https://www.cve.org/CVERecord?id=CVE-2023-52428 Référence CVE CVE-2023-52451 https://www.cve.org/CVERecord?id=CVE-2023-52451 Référence CVE CVE-2023-52463 https://www.cve.org/CVERecord?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-52469 https://www.cve.org/CVERecord?id=CVE-2023-52469 Référence CVE CVE-2023-52470 https://www.cve.org/CVERecord?id=CVE-2023-52470 Référence CVE CVE-2023-52471 https://www.cve.org/CVERecord?id=CVE-2023-52471 Référence CVE CVE-2023-52476 https://www.cve.org/CVERecord?id=CVE-2023-52476 Référence CVE CVE-2023-52478 https://www.cve.org/CVERecord?id=CVE-2023-52478 Référence CVE CVE-2023-52486 https://www.cve.org/CVERecord?id=CVE-2023-52486 Référence CVE CVE-2023-52492 https://www.cve.org/CVERecord?id=CVE-2023-52492 Référence CVE CVE-2023-52522 https://www.cve.org/CVERecord?id=CVE-2023-52522 Référence CVE CVE-2023-52530 https://www.cve.org/CVERecord?id=CVE-2023-52530 Référence CVE CVE-2023-52560 https://www.cve.org/CVERecord?id=CVE-2023-52560 Référence CVE CVE-2023-52615 https://www.cve.org/CVERecord?id=CVE-2023-52615 Référence CVE CVE-2023-52619 https://www.cve.org/CVERecord?id=

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

ord?id=CVE-2023-34455 Référence CVE CVE-2023-43642 https://www.cve.org/CVERecord?id=CVE-2023-43642 Référence CVE CVE-2023-44270 https://www.cve.org/CVERecord?id=CVE-2023-44270 Référence CVE CVE-2023-5072 https://www.cve.org/CVERecord?id=CVE-2023-5072 Référence CVE CVE-2023-52451 https://www.cve.org/CVERecord?id=CVE-2023-52451 Référence CVE CVE-2023-52463 https://www.cve.org/CVERecord?id=CVE-2023-52463 Référence CVE CVE-2023-52469 https://www.cve.org/CVERecord?id=CVE-2023-52469 Référence CVE CVE-2023-52470 https://www.cve.org/CVERecord?id=CVE-2023-52470 Référence CVE CVE-2023-52471 https://www.cve.org/CVERecord?id=CVE-2023-52471 Référence CVE CVE-2023-52476 https://www.cve.org/CVERecord?id=CVE-2023-52476 Référence CVE CVE-2023-52486 https://www.cve.org/CVERecord?id=CVE-2023-52486 Référence CVE CVE-2023-52530 https://www.cve.org/CVERecord?id=CVE-2023-52530 Référence CVE CVE-2023-52683 https://www.cve.org/CVERecord?id=CVE-2023-52683 Référence CVE CVE-2023-52730 https://www.cve.org/CVERecord?id=CVE-2023-52730 Référence CVE CVE-2023-52809 https://www.cve.org/CVERecord?id=CVE-2023-52809 Référence CVE CVE-2024-21538 https://www.cve.org/CVERecord?id=CVE-2024-21538 Référence CVE CVE-2024-22018 https://www.cve.org/CVERecord?id=CVE-2024-22018 Référence CVE CVE-2024-22020 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2022-48686 Référence CVE CVE-2022-48687 https://www.cve.org/CVERecord?id=CVE-2022-48687 Référence CVE CVE-2022-48754 https://www.cve.org/CVERecord?id=CVE-2022-48754 Référence CVE CVE-2022-48760 https://www.cve.org/CVERecord?id=CVE-2022-48760 Référence CVE CVE-2022-48804 https://www.cve.org/CVERecord?id=CVE-2022-48804 Référence CVE CVE-2022-48836 https://www.cve.org/CVERecord?id=CVE-2022-48836 Référence CVE CVE-2022-48866 https://www.cve.org/CVERecord?id=CVE-2022-48866 Référence CVE CVE-2023-52439 https://www.cve.org/CVERecord?id=CVE-2023-52439 Référence CVE CVE-2023-52470 https://www.cve.org/CVERecord?id=CVE-2023-52470 Référence CVE CVE-2023-52476 https://www.cve.org/CVERecord?id=CVE-2023-52476 Référence CVE CVE-2023-52478 https://www.cve.org/CVERecord?id=CVE-2023-52478 Référence CVE CVE-2023-52522 https://www.cve.org/CVERecord?id=CVE-2023-52522 Référence CVE CVE-2023-52605 https://www.cve.org/CVERecord?id=CVE-2023-52605 Référence CVE CVE-2023-52683 https://www.cve.org/CVERecord?id=CVE-2023-52683 Référence CVE CVE-2023-52817 https://www.cve.org/CVERecord?id=CVE-2023-52817 Référence CVE CVE-2023-52840 https://www.cve.org/CVERecord?id=CVE-2023-52840 Référence CVE CVE-2023-52880 https://www.cve.org/CVERecord?id=CVE-2023-52880 Référence CVE CVE-2023-52884 https://www.cve.org/CVERecord?id=

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

ord?id=CVE-2022-48695 Référence CVE CVE-2022-48701 https://www.cve.org/CVERecord?id=CVE-2022-48701 Référence CVE CVE-2023-0160 https://www.cve.org/CVERecord?id=CVE-2023-0160 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-52454 https://www.cve.org/CVERecord?id=CVE-2023-52454 Référence CVE CVE-2023-52469 https://www.cve.org/CVERecord?id=CVE-2023-52469 Référence CVE CVE-2023-52470 https://www.cve.org/CVERecord?id=CVE-2023-52470 Référence CVE CVE-2023-52474 https://www.cve.org/CVERecord?id=CVE-2023-52474 Référence CVE CVE-2023-52476 https://www.cve.org/CVERecord?id=CVE-2023-52476 Référence CVE CVE-2023-52477 https://www.cve.org/CVERecord?id=CVE-2023-52477 Référence CVE CVE-2023-52486 https://www.cve.org/CVERecord?id=CVE-2023-52486 Référence CVE CVE-2023-52488 https://www.cve.org/CVERecord?id=CVE-2023-52488 Référence CVE CVE-2023-52509 https://www.cve.org/CVERecord?id=CVE-2023-52509 Référence CVE CVE-2023-52515 https://www.cve.org/CVERecord?id=CVE-2023-52515 Référence CVE CVE-2023-52524 https://www.cve.org/CVERecord?id=CVE-2023-52524 Référence CVE CVE-2023-52528 https://www.cve.org/CVERecord?id=CVE-2023-52528 Référence CVE CVE-2023-52575 https://www.cve.org/CVERecord?id=

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

cord?id=CVE-2023-0160 Référence CVE CVE-2023-1829 https://www.cve.org/CVERecord?id=CVE-2023-1829 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-52340 https://www.cve.org/CVERecord?id=CVE-2023-52340 Référence CVE CVE-2023-52454 https://www.cve.org/CVERecord?id=CVE-2023-52454 Référence CVE CVE-2023-52469 https://www.cve.org/CVERecord?id=CVE-2023-52469 Référence CVE CVE-2023-52470 https://www.cve.org/CVERecord?id=CVE-2023-52470 Référence CVE CVE-2023-52474 https://www.cve.org/CVERecord?id=CVE-2023-52474 Référence CVE CVE-2023-52476 https://www.cve.org/CVERecord?id=CVE-2023-52476 Référence CVE CVE-2023-52477 https://www.cve.org/CVERecord?id=CVE-2023-52477 Référence CVE CVE-2023-52486 https://www.cve.org/CVERecord?id=CVE-2023-52486 Référence CVE CVE-2023-52488 https://www.cve.org/CVERecord?id=CVE-2023-52488 Référence CVE CVE-2023-52502 https://www.cve.org/CVERecord?id=CVE-2023-52502 Référence CVE CVE-2023-52509 https://www.cve.org/CVERecord?id=CVE-2023-52509 Référence CVE CVE-2023-52515 https://www.cve.org/CVERecord?id=CVE-2023-52515 Référence CVE CVE-2023-52524 https://www.cve.org/CVERecord?id=CVE-2023-52524 Référence CVE CVE-2023-52528 https://www.cve.org/CVERecord?id=

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

Record?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-2023-52454 Référence CVE CVE-2023-52469 https://www.cve.org/CVERecord?id=CVE-2023-52469 Référence CVE CVE-2023-52470 https://www.cve.org/CVERecord?id=CVE-2023-52470 Référence CVE CVE-2023-52474 https://www.cve.org/CVERecord?id=CVE-2023-52474 Référence CVE CVE-2023-52476 https://www.cve.org/CVERecord?id=CVE-2023-52476 Référence CVE CVE-2023-52477 https://www.cve.org/CVERecord?id=CVE-2023-52477 Référence CVE CVE-2023-52486 https://www.cve.org/CVERecord?id=CVE-2023-52486 Référence CVE CVE-2023-52488 https://www.cve.org/CVERecord?id=CVE-2023-52488 Référence CVE CVE-2023-52500 https://www.cve.org/CVERecord?id=CVE-2023-52500 Référence CVE CVE-2023-52503 https://www.cve.org/CVERecord?id=CVE-2023-52503 Référence CVE CVE-2023-52509 https://www.cve.org/CVERecord?id=CVE-2023-52509 Référence CVE CVE-2023-52515 https://www.cve.org/CVERecord?id=CVE-2023-52515 Référence CVE CVE-2023-52524 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2023-42754 Référence CVE CVE-2023-42756 https://www.cve.org/CVERecord?id=CVE-2023-42756 Référence CVE CVE-2023-45863 https://www.cve.org/CVERecord?id=CVE-2023-45863 Référence CVE CVE-2023-46862 https://www.cve.org/CVERecord?id=CVE-2023-46862 Référence CVE CVE-2023-51043 https://www.cve.org/CVERecord?id=CVE-2023-51043 Référence CVE CVE-2023-51779 https://www.cve.org/CVERecord?id=CVE-2023-51779 Référence CVE CVE-2023-51780 https://www.cve.org/CVERecord?id=CVE-2023-51780 Référence CVE CVE-2023-52434 https://www.cve.org/CVERecord?id=CVE-2023-52434 Référence CVE CVE-2023-52448 https://www.cve.org/CVERecord?id=CVE-2023-52448 Référence CVE CVE-2023-52476 https://www.cve.org/CVERecord?id=CVE-2023-52476 Référence CVE CVE-2023-52489 https://www.cve.org/CVERecord?id=CVE-2023-52489 Référence CVE CVE-2023-52522 https://www.cve.org/CVERecord?id=CVE-2023-52522 Référence CVE CVE-2023-52529 https://www.cve.org/CVERecord?id=CVE-2023-52529 Référence CVE CVE-2023-52574 https://www.cve.org/CVERecord?id=CVE-2023-52574 Référence CVE CVE-2023-52578 https://www.cve.org/CVERecord?id=CVE-2023-52578 Référence CVE CVE-2023-52580 https://www.cve.org/CVERecord?id=CVE-2023-52580 Référence CVE CVE-2023-52581 https://www.cve.org/CVERecord?id=CVE-2023-52581 Référence CVE CVE-2023-52610 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-52450 Référence CVE CVE-2023-52453 https://www.cve.org/CVERecord?id=CVE-2023-52453 Référence CVE CVE-2023-52454 https://www.cve.org/CVERecord?id=CVE-2023-52454 Référence CVE CVE-2023-52462 https://www.cve.org/CVERecord?id=CVE-2023-52462 Référence CVE CVE-2023-52463 https://www.cve.org/CVERecord?id=CVE-2023-52463 Référence CVE CVE-2023-52467 https://www.cve.org/CVERecord?id=CVE-2023-52467 Référence CVE CVE-2023-52469 https://www.cve.org/CVERecord?id=CVE-2023-52469 Référence CVE CVE-2023-52470 https://www.cve.org/CVERecord?id=CVE-2023-52470 Référence CVE CVE-2023-52474 https://www.cve.org/CVERecord?id=CVE-2023-52474 Référence CVE CVE-2023-52476 https://www.cve.org/CVERecord?id=CVE-2023-52476 Référence CVE CVE-2023-52477 https://www.cve.org/CVERecord?id=CVE-2023-52477 Référence CVE CVE-2023-52481 https://www.cve.org/CVERecord?id=CVE-2023-52481 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-52486 https://www.cve.org/CVERecord?id=CVE-2023-52486 Référence CVE CVE-2023-52488 https://www.cve.org/CVERecord?id=CVE-2023-52488 Référence CVE CVE-2023-52492 https://www.cve.org/CVERecord?id=CVE-2023-52492 Référence CVE CVE-2023-52493 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-52450 Référence CVE CVE-2023-52453 https://www.cve.org/CVERecord?id=CVE-2023-52453 Référence CVE CVE-2023-52454 https://www.cve.org/CVERecord?id=CVE-2023-52454 Référence CVE CVE-2023-52462 https://www.cve.org/CVERecord?id=CVE-2023-52462 Référence CVE CVE-2023-52463 https://www.cve.org/CVERecord?id=CVE-2023-52463 Référence CVE CVE-2023-52467 https://www.cve.org/CVERecord?id=CVE-2023-52467 Référence CVE CVE-2023-52469 https://www.cve.org/CVERecord?id=CVE-2023-52469 Référence CVE CVE-2023-52470 https://www.cve.org/CVERecord?id=CVE-2023-52470 Référence CVE CVE-2023-52474 https://www.cve.org/CVERecord?id=CVE-2023-52474 Référence CVE CVE-2023-52476 https://www.cve.org/CVERecord?id=CVE-2023-52476 Référence CVE CVE-2023-52477 https://www.cve.org/CVERecord?id=CVE-2023-52477 Référence CVE CVE-2023-52481 https://www.cve.org/CVERecord?id=CVE-2023-52481 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-52486 https://www.cve.org/CVERecord?id=CVE-2023-52486 Référence CVE CVE-2023-52492 https://www.cve.org/CVERecord?id=CVE-2023-52492 Référence CVE CVE-2023-52493 https://www.cve.org/CVERecord?id=CVE-2023-52493 Référence CVE CVE-2023-52494 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2023-027846Linux の 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: < 5.16, 6.1.59 ≤ 6.1.*, 6.5.8 ≤ 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 29 Feb 2024 · Last source change 11 May 2026, 19:28 UTC · CWE not yet assigned

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-57101
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceUnavailable
NVD statusNVD modified after enrichment

Missing structured fields: CWE classification. Missing data is not evidence of low risk; review the primary advisory.

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-57101↗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-52476 · cve.blacktree.nl