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

crypto: pcrypt - Fix hungtask for PADATA_RESET

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.29% for the current model date.

Compensating controls

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

Verification

  1. Confirm that the asset runs Linux Linux and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: 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.6.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.6.8-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.6.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 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.

2 current
CVE-2023-52813 · CSAF 2.0 · revision 124 · interimSUSE Product Security TeamCVE-2023-52813
409 known affected

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

  • kernel-default as component of SUSE Enterprise Storage 7.1
  • kernel-default-devel as component of SUSE Enterprise Storage 7.1
  • kernel-devel as component of SUSE Enterprise Storage 7.1
  • kernel-macros as component of SUSE Enterprise Storage 7.1
  • kernel-source as component of SUSE Enterprise Storage 7.1
  • reiserfs-kmp-default as component of SUSE Enterprise Storage 7.1
  • kernel-default as component of SUSE Linux Enterprise Desktop 15 SP5
  • kernel-default-devel as component of SUSE Linux Enterprise Desktop 15 SP5
  • kernel-default-extra as component of SUSE Linux Enterprise Desktop 15 SP5
  • kernel-devel as component of SUSE Linux Enterprise Desktop 15 SP5
  • kernel-macros as component of SUSE Linux Enterprise Desktop 15 SP5
  • kernel-source as component of SUSE Linux Enterprise Desktop 15 SP5
Summary
In the Linux kernel, the following vulnerability has been resolved: crypto: pcrypt - Fix hungtask for PADATA_RESET We found a hungtask bug in test_aead_vec_cfg as follows: INFO: task cryptomgr_test:391009 blocked for more than 120 seconds. "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Call trace: __switch_to+0x98/0xe0 __schedule+0x6c4/0xf40 schedule+0xd8/0x1b4 schedule_timeout+0x474/0x560 wait_for_common+0x368/0x4e0 wait_for_completion+0x20/0x30 wait_for_completion+0x20/0x30 test_aead_vec_cfg+0xab4/0xd50 test_aead+0x144/0x1f0 alg_test_aead+0xd8/0x1e0 alg_test+0x634/0x890 cryptomgr_test+0x40/0x70 kthread+0x1e0/0x220 ret_from_fork+0x10/0x18 Kernel panic - not syncing: hung_task: blocked tasks For padata_do_parallel, when the return err is 0 or -EBUSY, it will call wait_for_completion(&wait->completion) in test_aead_vec_cfg. In normal case, aead_request_complete() will be called in pcrypt_aead_serial and the return err is 0 for padata_do_parallel. But, when pinst->flags is PADATA_RESET, the return err is -EBUSY for padata_do_parallel, and it won't call aead_request_complete(). Therefore, test_aead_vec_cfg will hung at wait_for_completion(&wait->completion), which will cause hungtask. The problem comes as following: (padata_do_parallel) | rcu_read_lock_bh(); | err = -EINVAL; | (padata_replace) | pinst->flags |= PADATA_RESET; err = -EBUSY | if (pinst->flags & PADATA_RESET) | rcu_read_unlock_bh() | return err In order to resolve the problem, we replace the return err -EBUSY with -EAGAIN, which means parallel_data is changing, and the caller should call it again. v3: remove retry and just change the return err. v2: introduce padata_try_do_parallel() in pcrypt_aead_encrypt and pcrypt_aead_decrypt to solve the hungtask.
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
SSA-613116 · CSAF 2.0 · revision 3 · interimSiemens ProductCERTSSA-613116: Multiple Vulnerabilities in Third-Party Components in SINEC OS before V3.1
3 known not affected

The vendor explicitly states that these products are not affected by this CVE.

  • RUGGEDCOM RST2428P (6GK6242-6PA00)
  • SCALANCE XC-300/XR-300/XC-400/XR-500WG/XR-500 family
  • SCALANCE XCM-/XRM-/XCH-/XRH-300 family
Summary
In the Linux kernel, the following vulnerability has been resolved: crypto: pcrypt - Fix hungtask for PADATA_RESET
Remediation
No remediation text is recorded.
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-59529

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: crypto: pcrypt - Fix hungtask for PADATA_RESET We found a hungtask bug in test_aead_vec_cfg as follows: INFO: task cryptomgr_test:391009 blocked for more than 120 seconds. "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Call trace: __switch_to+0x98/0xe0 __schedule+0x6c4/0xf40 schedule+0xd8/0x1b4 schedule_timeout+0x474/0x560 wait_for_common+0x368/0x4e0 wait_for_completion+0x20/0x30 wait_for_completion+0x20/0x30 test_aead_vec_cfg+0xab4/0xd50 test_aead+0x144/0x1f0 alg_test_aead+0xd8/0x1e0 alg_test+0x634/0x890 cryptomgr_test+0x40/0x70 kthread+0x1e0/0x220 ret_from_fork+0x10/0x18 Kernel panic - not syncing: hung_task: blocked tasks For padata_do_parallel, when the return err is 0 or -EBUSY, it will call wait_for_completion(&wait->completion) in test_aead_vec_cfg. In normal case, aead_request_complete() will be called in pcrypt_aead_serial and the return err is 0 for padata_do_parallel. But, when pinst->flags is PADATA_RESET, the return err is -EBUSY for padata_do_parallel, and it won't call aead_request_complete(). Therefore, test_aead_vec_cfg will hung at wait_for_completion(&wait->completion), which will cause hungtask. The problem comes as following: (padata_do_parallel) | rcu_read_lock_bh(); | err = -EINVAL; | (padata_replace) | pinst->flags |= PADATA_RESET; err = -EBUSY | if (pinst->flags & PADATA_RESET) | rcu_read_unlock_bh() | return err In order to resolve the problem, we replace the return err -EBUSY with -EAGAIN, which means parallel_data is changing, and the caller should call it again. v3: remove retry and just change the return err. v2: introduce padata_try_do_parallel() in pcrypt_aead_encrypt and pcrypt_aead_decrypt to solve the hungtask.

What

In the Linux kernel, the following vulnerability has been resolved: crypto: pcrypt - Fix hungtask for PADATA_RESET We found a hungtask bug in test_aead_vec_cfg as follows: INFO: task cryptomgr_test:391009 blocked for more than 120 seconds. "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Call trace: __switch_to+0x98/0xe0 __schedule+0x6c4/0xf40 schedule+0xd8/0x1b4 schedule_timeout+0x474/0x560 wait_for_common+0x368/0x4e0 wait_for_completion+0x20/0x30 wait_for_completion+0x20/0x30 test_aead_vec_cfg+0xab4/0xd50 test_aead+0x144/0x1f0 alg_test_aead+0xd8/0x1e0 alg_test+0x634/0x890 cryptomgr_test+0x40/0x70 kthread+0x1e0/0x220 ret_from_fork+0x10/0x18 Kernel panic - not syncing: hung_task: blocked tasks For padata_do_parallel, when the return err is 0 or -EBUSY, it will call wait_for_completion(&wait->completion) in test_aead_vec_cfg. In normal case, aead_request_complete() will be called in pcrypt_aead_serial and the return err is 0 for padata_do_parallel. But, when pinst->flags is PADATA_RESET, the return err is -EBUSY for padata_do_parallel, and it won't call aead_request_complete(). Therefore, test_aead_vec_cfg will hung at wait_for_completion(&wait->completion), which will cause hungtask. The problem comes as following: (padata_do_parallel) | rcu_read_lock_bh(); | err = -EINVAL; | (padata_replace) | pinst->flags |= PADATA_RESET; err = -EBUSY | if (pinst->flags & PADATA_RESET) | rcu_read_unlock_bh() | return err In order to resolve the problem, we replace the return err -EBUSY with -EAGAIN, which means parallel_data is changing, and the caller should call it again. v3: remove retry and just change the return err. v2: introduce padata_try_do_parallel() in pcrypt_aead_encrypt and pcrypt_aead_decrypt to solve the hungtask.

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: crypto: pcrypt - Fix hungtask for PADATA_RESET We found a hungtask bug in test_aead_vec_cfg as follows: INFO: task cryptomgr_test:391009 blocked for more than 120 seconds. "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Call trace: __switch_to+0x98/0xe0 __schedule+0x6c4/0xf40 schedule+0xd8/0x1b4 schedule_timeout+0x474/0x560 wait_for_common+0x368/0x4e0 wait_for_completion+0x20/0x30 wait_for_completion+0x20/0x30 test_aead_vec_cfg+0xab4/0xd50 test_aead+0x144/0x1f0 alg_test_aead+0xd8/0x1e0 alg_test+0x634/0x890 cryptomgr_test+0x40/0x70 kthread+0x1e0/0x220 ret_from_fork+0x10/0x18 Kernel panic - not syncing: hung_task: blocked tasks For padata_do_parallel, when the return err is 0 or -EBUSY, it will call wait_for_completion(&wait->completion) in test_aead_vec_cfg. In normal case, aead_request_complete() will be called in pcrypt_aead_serial and the return err is 0 for padata_do_parallel. But, when pinst->flags is PADATA_RESET, the return err is -EBUSY for padata_do_parallel, and it won't call aead_request_complete(). Therefore, test_aead_vec_cfg will hung at wait_for_completion(&wait->completion), which will cause hungtask. The problem comes as following: (padata_do_parallel) | rcu_read_lock_bh(); | err = -EINVAL; | (padata_replace) | pinst->flags |= PADATA_RESET; err = -EBUSY | if (pinst->flags & PADATA_RESET) | rcu_read_unlock_bh() | return err In order to resolve the problem, we replace the return err -EBUSY with -EAGAIN, which means parallel_data is changing, and the caller should call it again. v3: remove retry and just change the return err. v2: introduce padata_try_do_parallel() in pcrypt_aead_encrypt and pcrypt_aead_decrypt to solve the hungtask.

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-1905IBM QRadar SIEM: Mehrere Schwachstellen

Ein entfernter, anonymer oder lokaler Angreifer kann mehrere Schwachstellen in IBM QRadar SIEM ausnutzen, um seine Privilegien zu erhöhen, beliebigen Code auszuführen, Daten zu manipulieren, vertrauliche Informationen offenzulegen, eine Man-in-the-Middle-Situation zu schaffen, Sicherheitsmaßnahmen zu umgehen oder eine Denial-of-Service-Situation zu schaffen.

Official advisory ↗
BSI · German · WID-SEC-2024-1197Linux 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 zu erzeugen oder unspezifische Angriffe durchzuführen.

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

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 22 May 2024, published on 22 May 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

d?id=CVE-2023-52781 Référence CVE CVE-2023-52784 https://www.cve.org/CVERecord?id=CVE-2023-52784 Référence CVE CVE-2023-52791 https://www.cve.org/CVERecord?id=CVE-2023-52791 Référence CVE CVE-2023-52796 https://www.cve.org/CVERecord?id=CVE-2023-52796 Référence CVE CVE-2023-52798 https://www.cve.org/CVERecord?id=CVE-2023-52798 Référence CVE CVE-2023-52800 https://www.cve.org/CVERecord?id=CVE-2023-52800 Référence CVE CVE-2023-52803 https://www.cve.org/CVERecord?id=CVE-2023-52803 Référence CVE CVE-2023-52809 https://www.cve.org/CVERecord?id=CVE-2023-52809 Référence CVE CVE-2023-52811 https://www.cve.org/CVERecord?id=CVE-2023-52811 Référence CVE CVE-2023-52813 https://www.cve.org/CVERecord?id=CVE-2023-52813 Référence CVE CVE-2023-52817 https://www.cve.org/CVERecord?id=CVE-2023-52817 Référence CVE CVE-2023-52832 https://www.cve.org/CVERecord?id=CVE-2023-52832 Référence CVE CVE-2023-52834 https://www.cve.org/CVERecord?id=CVE-2023-52834 Référence CVE CVE-2023-52835 https://www.cve.org/CVERecord?id=CVE-2023-52835 Référence CVE CVE-2023-52840 https://www.cve.org/CVERecord?id=CVE-2023-52840 Référence CVE CVE-2023-52845 https://www.cve.org/CVERecord?id=CVE-2023-52845 Référence CVE CVE-2023-52847 https://www.cve.org/CVERecord?id=CVE-2023-52847 Référence CVE CVE-2023-52864 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2023-52787 Référence CVE CVE-2023-52788 https://www.cve.org/CVERecord?id=CVE-2023-52788 Référence CVE CVE-2023-52791 https://www.cve.org/CVERecord?id=CVE-2023-52791 Référence CVE CVE-2023-52792 https://www.cve.org/CVERecord?id=CVE-2023-52792 Référence CVE CVE-2023-52794 https://www.cve.org/CVERecord?id=CVE-2023-52794 Référence CVE CVE-2023-52795 https://www.cve.org/CVERecord?id=CVE-2023-52795 Référence CVE CVE-2023-52796 https://www.cve.org/CVERecord?id=CVE-2023-52796 Référence CVE CVE-2023-52803 https://www.cve.org/CVERecord?id=CVE-2023-52803 Référence CVE CVE-2023-52806 https://www.cve.org/CVERecord?id=CVE-2023-52806 Référence CVE CVE-2023-52813 https://www.cve.org/CVERecord?id=CVE-2023-52813 Référence CVE CVE-2023-52814 https://www.cve.org/CVERecord?id=CVE-2023-52814 Référence CVE CVE-2023-52817 https://www.cve.org/CVERecord?id=CVE-2023-52817 Référence CVE CVE-2023-52818 https://www.cve.org/CVERecord?id=CVE-2023-52818 Référence CVE CVE-2023-52828 https://www.cve.org/CVERecord?id=CVE-2023-52828 Référence CVE CVE-2023-52833 https://www.cve.org/CVERecord?id=CVE-2023-52833 Référence CVE CVE-2023-52835 https://www.cve.org/CVERecord?id=CVE-2023-52835 Référence CVE CVE-2023-52837 https://www.cve.org/CVERecord?id=CVE-2023-52837 Référence CVE CVE-2023-52840 https://www.cve.org/CVERecord?id=

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

ERecord?id=CVE-2022-50162 Référence CVE CVE-2022-50185 https://www.cve.org/CVERecord?id=CVE-2022-50185 Référence CVE CVE-2022-50191 https://www.cve.org/CVERecord?id=CVE-2022-50191 Référence CVE CVE-2022-50211 https://www.cve.org/CVERecord?id=CVE-2022-50211 Référence CVE CVE-2022-50228 https://www.cve.org/CVERecord?id=CVE-2022-50228 Référence CVE CVE-2022-50229 https://www.cve.org/CVERecord?id=CVE-2022-50229 Référence CVE CVE-2023-3867 https://www.cve.org/CVERecord?id=CVE-2023-3867 Référence CVE CVE-2023-4130 https://www.cve.org/CVERecord?id=CVE-2023-4130 Référence CVE CVE-2023-4515 https://www.cve.org/CVERecord?id=CVE-2023-4515 Référence CVE CVE-2023-52813 https://www.cve.org/CVERecord?id=CVE-2023-52813 Référence CVE CVE-2023-53020 https://www.cve.org/CVERecord?id=CVE-2023-53020 Référence CVE CVE-2023-53117 https://www.cve.org/CVERecord?id=CVE-2023-53117 Référence CVE CVE-2024-26661 https://www.cve.org/CVERecord?id=CVE-2024-26661 Référence CVE CVE-2024-28956 https://www.cve.org/CVERecord?id=CVE-2024-28956 Référence CVE CVE-2024-46733 https://www.cve.org/CVERecord?id=CVE-2024-46733 Référence CVE CVE-2024-47674 https://www.cve.org/CVERecord?id=CVE-2024-47674 Référence CVE CVE-2024-47706 https://www.cve.org/CVERecord?id=CVE-2024-47706 Référence CVE CVE-2024-49867 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2023-52789 Référence CVE CVE-2023-52791 https://www.cve.org/CVERecord?id=CVE-2023-52791 Référence CVE CVE-2023-52796 https://www.cve.org/CVERecord?id=CVE-2023-52796 Référence CVE CVE-2023-52799 https://www.cve.org/CVERecord?id=CVE-2023-52799 Référence CVE CVE-2023-52804 https://www.cve.org/CVERecord?id=CVE-2023-52804 Référence CVE CVE-2023-52805 https://www.cve.org/CVERecord?id=CVE-2023-52805 Référence CVE CVE-2023-52806 https://www.cve.org/CVERecord?id=CVE-2023-52806 Référence CVE CVE-2023-52809 https://www.cve.org/CVERecord?id=CVE-2023-52809 Référence CVE CVE-2023-52810 https://www.cve.org/CVERecord?id=CVE-2023-52810 Référence CVE CVE-2023-52813 https://www.cve.org/CVERecord?id=CVE-2023-52813 Référence CVE CVE-2023-52817 https://www.cve.org/CVERecord?id=CVE-2023-52817 Référence CVE CVE-2023-52818 https://www.cve.org/CVERecord?id=CVE-2023-52818 Référence CVE CVE-2023-52819 https://www.cve.org/CVERecord?id=CVE-2023-52819 Référence CVE CVE-2023-52832 https://www.cve.org/CVERecord?id=CVE-2023-52832 Référence CVE CVE-2023-52835 https://www.cve.org/CVERecord?id=CVE-2023-52835 Référence CVE CVE-2023-52836 https://www.cve.org/CVERecord?id=CVE-2023-52836 Référence CVE CVE-2023-52838 https://www.cve.org/CVERecord?id=CVE-2023-52838 Référence CVE CVE-2023-52840 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2023-52615 Référence CVE CVE-2023-52626 https://www.cve.org/CVERecord?id=CVE-2023-52626 Référence CVE CVE-2023-52667 https://www.cve.org/CVERecord?id=CVE-2023-52667 Référence CVE CVE-2023-52669 https://www.cve.org/CVERecord?id=CVE-2023-52669 Référence CVE CVE-2023-52675 https://www.cve.org/CVERecord?id=CVE-2023-52675 Référence CVE CVE-2023-52686 https://www.cve.org/CVERecord?id=CVE-2023-52686 Référence CVE CVE-2023-52700 https://www.cve.org/CVERecord?id=CVE-2023-52700 Référence CVE CVE-2023-52703 https://www.cve.org/CVERecord?id=CVE-2023-52703 Référence CVE CVE-2023-52781 https://www.cve.org/CVERecord?id=CVE-2023-52781 Référence CVE CVE-2023-52813 https://www.cve.org/CVERecord?id=CVE-2023-52813 Référence CVE CVE-2023-52835 https://www.cve.org/CVERecord?id=CVE-2023-52835 Référence CVE CVE-2023-52877 https://www.cve.org/CVERecord?id=CVE-2023-52877 Référence CVE CVE-2023-52878 https://www.cve.org/CVERecord?id=CVE-2023-52878 Référence CVE CVE-2023-52881 https://www.cve.org/CVERecord?id=CVE-2023-52881 Référence CVE CVE-2023-6349 https://www.cve.org/CVERecord?id=CVE-2023-6349 Référence CVE CVE-2024-22195 https://www.cve.org/CVERecord?id=CVE-2024-22195 Référence CVE CVE-2024-22354 https://www.cve.org/CVERecord?id=CVE-2024-22354 Référence CVE CVE-2024-23944 https://www.cve.org/CVERecord?id=CV

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

d?id=CVE-2023-52615 Référence CVE CVE-2023-52626 https://www.cve.org/CVERecord?id=CVE-2023-52626 Référence CVE CVE-2023-52667 https://www.cve.org/CVERecord?id=CVE-2023-52667 Référence CVE CVE-2023-52669 https://www.cve.org/CVERecord?id=CVE-2023-52669 Référence CVE CVE-2023-52675 https://www.cve.org/CVERecord?id=CVE-2023-52675 Référence CVE CVE-2023-52686 https://www.cve.org/CVERecord?id=CVE-2023-52686 Référence CVE CVE-2023-52700 https://www.cve.org/CVERecord?id=CVE-2023-52700 Référence CVE CVE-2023-52703 https://www.cve.org/CVERecord?id=CVE-2023-52703 Référence CVE CVE-2023-52781 https://www.cve.org/CVERecord?id=CVE-2023-52781 Référence CVE CVE-2023-52813 https://www.cve.org/CVERecord?id=CVE-2023-52813 Référence CVE CVE-2023-52835 https://www.cve.org/CVERecord?id=CVE-2023-52835 Référence CVE CVE-2023-52877 https://www.cve.org/CVERecord?id=CVE-2023-52877 Référence CVE CVE-2023-52878 https://www.cve.org/CVERecord?id=CVE-2023-52878 Référence CVE CVE-2023-52881 https://www.cve.org/CVERecord?id=CVE-2023-52881 Référence CVE CVE-2023-6004 https://www.cve.org/CVERecord?id=CVE-2023-6004 Référence CVE CVE-2023-6240 https://www.cve.org/CVERecord?id=CVE-2023-6240 Référence CVE CVE-2023-6597 https://www.cve.org/CVERecord?id=CVE-2023-6597 Référence CVE CVE-2023-6918 https://www.cve.org/CVERecord?id=CVE-202

Official advisory ↗
CERT-FR · French · CERTFR-2024-AVI-0720Multiples vulnérabilités dans IBM QRadar SIEM

d?id=CVE-2023-52615 Référence CVE CVE-2023-52626 https://www.cve.org/CVERecord?id=CVE-2023-52626 Référence CVE CVE-2023-52667 https://www.cve.org/CVERecord?id=CVE-2023-52667 Référence CVE CVE-2023-52669 https://www.cve.org/CVERecord?id=CVE-2023-52669 Référence CVE CVE-2023-52675 https://www.cve.org/CVERecord?id=CVE-2023-52675 Référence CVE CVE-2023-52686 https://www.cve.org/CVERecord?id=CVE-2023-52686 Référence CVE CVE-2023-52700 https://www.cve.org/CVERecord?id=CVE-2023-52700 Référence CVE CVE-2023-52703 https://www.cve.org/CVERecord?id=CVE-2023-52703 Référence CVE CVE-2023-52781 https://www.cve.org/CVERecord?id=CVE-2023-52781 Référence CVE CVE-2023-52813 https://www.cve.org/CVERecord?id=CVE-2023-52813 Référence CVE CVE-2023-52835 https://www.cve.org/CVERecord?id=CVE-2023-52835 Référence CVE CVE-2023-52877 https://www.cve.org/CVERecord?id=CVE-2023-52877 Référence CVE CVE-2023-52878 https://www.cve.org/CVERecord?id=CVE-2023-52878 Référence CVE CVE-2023-52881 https://www.cve.org/CVERecord?id=CVE-2023-52881 Référence CVE CVE-2023-7008 https://www.cve.org/CVERecord?id=CVE-2023-7008 Référence CVE CVE-2024-1048 https://www.cve.org/CVERecord?id=CVE-2024-1048 Référence CVE CVE-2024-22365 https://www.cve.org/CVERecord?id=CVE-2024-22365 Référence CVE CVE-2024-26583 https://www.cve.org/CVERecord?id=CVE-

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

d?id=CVE-2023-52804 Référence CVE CVE-2023-52805 https://www.cve.org/CVERecord?id=CVE-2023-52805 Référence CVE CVE-2023-52806 https://www.cve.org/CVERecord?id=CVE-2023-52806 Référence CVE CVE-2023-52807 https://www.cve.org/CVERecord?id=CVE-2023-52807 Référence CVE CVE-2023-52808 https://www.cve.org/CVERecord?id=CVE-2023-52808 Référence CVE CVE-2023-52809 https://www.cve.org/CVERecord?id=CVE-2023-52809 Référence CVE CVE-2023-52810 https://www.cve.org/CVERecord?id=CVE-2023-52810 Référence CVE CVE-2023-52811 https://www.cve.org/CVERecord?id=CVE-2023-52811 Référence CVE CVE-2023-52812 https://www.cve.org/CVERecord?id=CVE-2023-52812 Référence CVE CVE-2023-52813 https://www.cve.org/CVERecord?id=CVE-2023-52813 Référence CVE CVE-2023-52814 https://www.cve.org/CVERecord?id=CVE-2023-52814 Référence CVE CVE-2023-52815 https://www.cve.org/CVERecord?id=CVE-2023-52815 Référence CVE CVE-2023-52816 https://www.cve.org/CVERecord?id=CVE-2023-52816 Référence CVE CVE-2023-52817 https://www.cve.org/CVERecord?id=CVE-2023-52817 Référence CVE CVE-2023-52818 https://www.cve.org/CVERecord?id=CVE-2023-52818 Référence CVE CVE-2023-52819 https://www.cve.org/CVERecord?id=CVE-2023-52819 Référence CVE CVE-2023-52821 https://www.cve.org/CVERecord?id=CVE-2023-52821 Référence CVE CVE-2023-52825 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2023-52804 Référence CVE CVE-2023-52805 https://www.cve.org/CVERecord?id=CVE-2023-52805 Référence CVE CVE-2023-52806 https://www.cve.org/CVERecord?id=CVE-2023-52806 Référence CVE CVE-2023-52807 https://www.cve.org/CVERecord?id=CVE-2023-52807 Référence CVE CVE-2023-52808 https://www.cve.org/CVERecord?id=CVE-2023-52808 Référence CVE CVE-2023-52809 https://www.cve.org/CVERecord?id=CVE-2023-52809 Référence CVE CVE-2023-52810 https://www.cve.org/CVERecord?id=CVE-2023-52810 Référence CVE CVE-2023-52811 https://www.cve.org/CVERecord?id=CVE-2023-52811 Référence CVE CVE-2023-52812 https://www.cve.org/CVERecord?id=CVE-2023-52812 Référence CVE CVE-2023-52813 https://www.cve.org/CVERecord?id=CVE-2023-52813 Référence CVE CVE-2023-52814 https://www.cve.org/CVERecord?id=CVE-2023-52814 Référence CVE CVE-2023-52815 https://www.cve.org/CVERecord?id=CVE-2023-52815 Référence CVE CVE-2023-52816 https://www.cve.org/CVERecord?id=CVE-2023-52816 Référence CVE CVE-2023-52817 https://www.cve.org/CVERecord?id=CVE-2023-52817 Référence CVE CVE-2023-52818 https://www.cve.org/CVERecord?id=CVE-2023-52818 Référence CVE CVE-2023-52819 https://www.cve.org/CVERecord?id=CVE-2023-52819 Référence CVE CVE-2023-52821 https://www.cve.org/CVERecord?id=CVE-2023-52821 Référence CVE CVE-2023-52825 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2023-52804 Référence CVE CVE-2023-52805 https://www.cve.org/CVERecord?id=CVE-2023-52805 Référence CVE CVE-2023-52806 https://www.cve.org/CVERecord?id=CVE-2023-52806 Référence CVE CVE-2023-52807 https://www.cve.org/CVERecord?id=CVE-2023-52807 Référence CVE CVE-2023-52808 https://www.cve.org/CVERecord?id=CVE-2023-52808 Référence CVE CVE-2023-52809 https://www.cve.org/CVERecord?id=CVE-2023-52809 Référence CVE CVE-2023-52810 https://www.cve.org/CVERecord?id=CVE-2023-52810 Référence CVE CVE-2023-52811 https://www.cve.org/CVERecord?id=CVE-2023-52811 Référence CVE CVE-2023-52812 https://www.cve.org/CVERecord?id=CVE-2023-52812 Référence CVE CVE-2023-52813 https://www.cve.org/CVERecord?id=CVE-2023-52813 Référence CVE CVE-2023-52814 https://www.cve.org/CVERecord?id=CVE-2023-52814 Référence CVE CVE-2023-52815 https://www.cve.org/CVERecord?id=CVE-2023-52815 Référence CVE CVE-2023-52816 https://www.cve.org/CVERecord?id=CVE-2023-52816 Référence CVE CVE-2023-52817 https://www.cve.org/CVERecord?id=CVE-2023-52817 Référence CVE CVE-2023-52818 https://www.cve.org/CVERecord?id=CVE-2023-52818 Référence CVE CVE-2023-52819 https://www.cve.org/CVERecord?id=CVE-2023-52819 Référence CVE CVE-2023-52821 https://www.cve.org/CVERecord?id=CVE-2023-52821 Référence CVE CVE-2023-52825 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2023-52615 Référence CVE CVE-2023-52626 https://www.cve.org/CVERecord?id=CVE-2023-52626 Référence CVE CVE-2023-52667 https://www.cve.org/CVERecord?id=CVE-2023-52667 Référence CVE CVE-2023-52669 https://www.cve.org/CVERecord?id=CVE-2023-52669 Référence CVE CVE-2023-52675 https://www.cve.org/CVERecord?id=CVE-2023-52675 Référence CVE CVE-2023-52686 https://www.cve.org/CVERecord?id=CVE-2023-52686 Référence CVE CVE-2023-52700 https://www.cve.org/CVERecord?id=CVE-2023-52700 Référence CVE CVE-2023-52703 https://www.cve.org/CVERecord?id=CVE-2023-52703 Référence CVE CVE-2023-52781 https://www.cve.org/CVERecord?id=CVE-2023-52781 Référence CVE CVE-2023-52813 https://www.cve.org/CVERecord?id=CVE-2023-52813 Référence CVE CVE-2023-52835 https://www.cve.org/CVERecord?id=CVE-2023-52835 Référence CVE CVE-2023-52877 https://www.cve.org/CVERecord?id=CVE-2023-52877 Référence CVE CVE-2023-52878 https://www.cve.org/CVERecord?id=CVE-2023-52878 Référence CVE CVE-2023-52881 https://www.cve.org/CVERecord?id=CVE-2023-52881 Référence CVE CVE-2024-0193 https://www.cve.org/CVERecord?id=CVE-2024-0193 Référence CVE CVE-2024-26583 https://www.cve.org/CVERecord?id=CVE-2024-26583 Référence CVE CVE-2024-26584 https://www.cve.org/CVERecord?id=CVE-2024-26584 Référence CVE CVE-2024-26585 https://www.cve.org/CVERecord?id=CV

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2023-029829Linux の 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.34, 4.14.331 ≤ 4.14.*, 4.19.300 ≤ 4.19.*, 5.4.262 ≤ 5.4.*, 5.10.202 ≤ 5.10.*, 5.15.140 ≤ 5.15.*, 6.1.64 ≤ 6.1.*, 6.5.13 ≤ 6.5.*, 6.6.3 ≤ 6.6.*, 6.7 ≤ *
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 21 May 2024 · Last source change 11 May 2026, 19:33 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-59529
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceUnavailable
NVD statusNVD enriched

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-59529↗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-52813 · cve.blacktree.nl