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

block/rq_qos: protect rq_qos apis with a new lock

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 10 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityHighOperational priority:Medium, lowered one band.downgradedsince 5 Aug 2026

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • Exploitation requires an existing local or physical foothold with privileges.
  • EPSS is 0.18% 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 10 structured product or package states 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.

13 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 10 affected package states 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.4.4-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourcelinuxAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.4.4-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.4.4-1Debian Security Tracker ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azure-6.11Affected, 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
Ubuntu 24.04 LTSnoble · standard archivelinux-gcp-6.11Affected, 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
Ubuntu 24.04 LTSnoble · standard archivelinux-hwe-6.11Affected, 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
Ubuntu 24.04 LTSnoble · standard archivelinux-lowlatency-hwe-6.11Affected, 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
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidia-6.11Affected, 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
Ubuntu 24.04 LTSnoble · standard archivelinux-oem-6.11Affected, 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
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
Ubuntu 24.04 LTSnoble · standard archivelinux-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
Ubuntu 24.04 LTSnoble · standard archivelinux-riscvAffected, 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-53823 · CSAF 2.0 · revision 30 · interimSUSE Product Security TeamCVE-2023-53823
82 known affected

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

  • cluster-md-kmp-default as component of SUSE Linux Enterprise High Performance Computing 15 SP5-ESPOS
  • dlm-kmp-default as component of SUSE Linux Enterprise High Performance Computing 15 SP5-ESPOS
  • gfs2-kmp-default as component of SUSE Linux Enterprise High Performance Computing 15 SP5-ESPOS
  • kernel-default as component of SUSE Linux Enterprise High Performance Computing 15 SP5-ESPOS
  • kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP5-ESPOS
  • kernel-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP5-ESPOS
  • kernel-macros as component of SUSE Linux Enterprise High Performance Computing 15 SP5-ESPOS
  • kernel-source as component of SUSE Linux Enterprise High Performance Computing 15 SP5-ESPOS
  • ocfs2-kmp-default as component of SUSE Linux Enterprise High Performance Computing 15 SP5-ESPOS
  • cluster-md-kmp-default as component of SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS
  • dlm-kmp-default as component of SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS
  • gfs2-kmp-default as component of SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS
Summary
In the Linux kernel, the following vulnerability has been resolved: block/rq_qos: protect rq_qos apis with a new lock commit 50e34d78815e ("block: disable the elevator int del_gendisk") move rq_qos_exit() from disk_release() to del_gendisk(), this will introduce some problems: 1) If rq_qos_add() is triggered by enabling iocost/iolatency through cgroupfs, then it can concurrent with del_gendisk(), it's not safe to write 'q->rq_qos' concurrently. 2) Activate cgroup policy that is relied on rq_qos will call rq_qos_add() and blkcg_activate_policy(), and if rq_qos_exit() is called in the middle, null-ptr-dereference will be triggered in blkcg_activate_policy(). 3) blkg_conf_open_bdev() can call blkdev_get_no_open() first to find the disk, then if rq_qos_exit() from del_gendisk() is done before rq_qos_add(), then memory will be leaked. This patch add a new disk level mutex 'rq_qos_mutex': 1) The lock will protect rq_qos_exit() directly. 2) For wbt that doesn't relied on blk-cgroup, rq_qos_add() can only be called from disk initialization for now because wbt can't be destructed until rq_qos_exit(), so it's safe not to protect wbt for now. Hoever, in case that rq_qos dynamically destruction is supported in the furture, this patch also protect rq_qos_add() from wbt_init() directly, this is enough because blk-sysfs already synchronize writers with disk removal. 3) For iocost and iolatency, in order to synchronize disk removal and cgroup configuration, the lock is held after blkdev_get_no_open() from blkg_conf_open_bdev(), and is released in blkg_conf_exit(). In order to fix the above memory leak, disk_live() is checked after holding the new lock.
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-60173

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 10 structured product or package states 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: block/rq_qos: protect rq_qos apis with a new lock commit 50e34d78815e ("block: disable the elevator int del_gendisk") move rq_qos_exit() from disk_release() to del_gendisk(), this will introduce some problems: 1) If rq_qos_add() is triggered by enabling iocost/iolatency through cgroupfs, then it can concurrent with del_gendisk(), it's not safe to write 'q->rq_qos' concurrently. 2) Activate cgroup policy that is relied on rq_qos will call rq_qos_add() and blkcg_activate_policy(), and if rq_qos_exit() is called in the middle, null-ptr-dereference will be triggered in blkcg_activate_policy(). 3) blkg_conf_open_bdev() can call blkdev_get_no_open() first to find the disk, then if rq_qos_exit() from del_gendisk() is done before rq_qos_add(), then memory will be leaked. This patch add a new disk level mutex 'rq_qos_mutex': 1) The lock will protect rq_qos_exit() directly. 2) For wbt that doesn't relied on blk-cgroup, rq_qos_add() can only be called from disk initialization for now because wbt can't be destructed until rq_qos_exit(), so it's safe not to protect wbt for now. Hoever, in case that rq_qos dynamically destruction is supported in the furture, this patch also protect rq_qos_add() from wbt_init() directly, this is enough because blk-sysfs already synchronize writers with disk removal. 3) For iocost and iolatency, in order to synchronize disk removal and cgroup configuration, the lock is held after blkdev_get_no_open() from blkg_conf_open_bdev(), and is released in blkg_conf_exit(). In order to fix the above memory leak, disk_live() is checked after holding the new lock.

What

In the Linux kernel, the following vulnerability has been resolved: block/rq_qos: protect rq_qos apis with a new lock commit 50e34d78815e ("block: disable the elevator int del_gendisk") move rq_qos_exit() from disk_release() to del_gendisk(), this will introduce some problems: 1) If rq_qos_add() is triggered by enabling iocost/iolatency through cgroupfs, then it can concurrent with del_gendisk(), it's not safe to write 'q->rq_qos' concurrently. 2) Activate cgroup policy that is relied on rq_qos will call rq_qos_add() and blkcg_activate_policy(), and if rq_qos_exit() is called in the middle, null-ptr-dereference will be triggered in blkcg_activate_policy(). 3) blkg_conf_open_bdev() can call blkdev_get_no_open() first to find the disk, then if rq_qos_exit() from del_gendisk() is done before rq_qos_add(), then memory will be leaked. This patch add a new disk level mutex 'rq_qos_mutex': 1) The lock will protect rq_qos_exit() directly. 2) For wbt that doesn't relied on blk-cgroup, rq_qos_add() can only be called from disk initialization for now because wbt can't be destructed until rq_qos_exit(), so it's safe not to protect wbt for now. Hoever, in case that rq_qos dynamically destruction is supported in the furture, this patch also protect rq_qos_add() from wbt_init() directly, this is enough because blk-sysfs already synchronize writers with disk removal. 3) For iocost and iolatency, in order to synchronize disk removal and cgroup configuration, the lock is held after blkdev_get_no_open() from blkg_conf_open_bdev(), and is released in blkg_conf_exit(). In order to fix the above memory leak, disk_live() is checked after holding the new lock.

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: block/rq_qos: protect rq_qos apis with a new lock commit 50e34d78815e ("block: disable the elevator int del_gendisk") move rq_qos_exit() from disk_release() to del_gendisk(), this will introduce some problems: 1) If rq_qos_add() is triggered by enabling iocost/iolatency through cgroupfs, then it can concurrent with del_gendisk(), it's not safe to write 'q->rq_qos' concurrently. 2) Activate cgroup policy that is relied on rq_qos will call rq_qos_add() and blkcg_activate_policy(), and if rq_qos_exit() is called in the middle, null-ptr-dereference will be triggered in blkcg_activate_policy(). 3) blkg_conf_open_bdev() can call blkdev_get_no_open() first to find the disk, then if rq_qos_exit() from del_gendisk() is done before rq_qos_add(), then memory will be leaked. This patch add a new disk level mutex 'rq_qos_mutex': 1) The lock will protect rq_qos_exit() directly. 2) For wbt that doesn't relied on blk-cgroup, rq_qos_add() can only be called from disk initialization for now because wbt can't be destructed until rq_qos_exit(), so it's safe not to protect wbt for now. Hoever, in case that rq_qos dynamically destruction is supported in the furture, this patch also protect rq_qos_add() from wbt_init() directly, this is enough because blk-sysfs already synchronize writers with disk removal. 3) For iocost and iolatency, in order to synchronize disk removal and cgroup configuration, the lock is held after blkdev_get_no_open() from blkg_conf_open_bdev(), and is released in blkg_conf_exit(). In order to fix the above memory leak, disk_live() is checked after holding the new lock.

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: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.
A

Official authority intelligence

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

BSI · German · WID-SEC-2025-2765Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service

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

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20251210Security Bulletin 10 Dec 2025

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 10 Dec 2025, published on 10 December 2025. Open the linked bulletin for the product, severity and reference information published in that issue.

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

d?id=CVE-2023-53802 Référence CVE CVE-2023-53807 https://www.cve.org/CVERecord?id=CVE-2023-53807 Référence CVE CVE-2023-53808 https://www.cve.org/CVERecord?id=CVE-2023-53808 Référence CVE CVE-2023-53813 https://www.cve.org/CVERecord?id=CVE-2023-53813 Référence CVE CVE-2023-53815 https://www.cve.org/CVERecord?id=CVE-2023-53815 Référence CVE CVE-2023-53816 https://www.cve.org/CVERecord?id=CVE-2023-53816 Référence CVE CVE-2023-53817 https://www.cve.org/CVERecord?id=CVE-2023-53817 Référence CVE CVE-2023-53819 https://www.cve.org/CVERecord?id=CVE-2023-53819 Référence CVE CVE-2023-53821 https://www.cve.org/CVERecord?id=CVE-2023-53821 Référence CVE CVE-2023-53823 https://www.cve.org/CVERecord?id=CVE-2023-53823 Référence CVE CVE-2023-53825 https://www.cve.org/CVERecord?id=CVE-2023-53825 Référence CVE CVE-2023-53827 https://www.cve.org/CVERecord?id=CVE-2023-53827 Référence CVE CVE-2023-53828 https://www.cve.org/CVERecord?id=CVE-2023-53828 Référence CVE CVE-2023-53831 https://www.cve.org/CVERecord?id=CVE-2023-53831 Référence CVE CVE-2023-53834 https://www.cve.org/CVERecord?id=CVE-2023-53834 Référence CVE CVE-2023-53836 https://www.cve.org/CVERecord?id=CVE-2023-53836 Référence CVE CVE-2023-53839 https://www.cve.org/CVERecord?id=CVE-2023-53839 Référence CVE CVE-2023-53841 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2023-53795 Référence CVE CVE-2023-53797 https://www.cve.org/CVERecord?id=CVE-2023-53797 Référence CVE CVE-2023-53799 https://www.cve.org/CVERecord?id=CVE-2023-53799 Référence CVE CVE-2023-53807 https://www.cve.org/CVERecord?id=CVE-2023-53807 Référence CVE CVE-2023-53808 https://www.cve.org/CVERecord?id=CVE-2023-53808 Référence CVE CVE-2023-53813 https://www.cve.org/CVERecord?id=CVE-2023-53813 Référence CVE CVE-2023-53815 https://www.cve.org/CVERecord?id=CVE-2023-53815 Référence CVE CVE-2023-53819 https://www.cve.org/CVERecord?id=CVE-2023-53819 Référence CVE CVE-2023-53821 https://www.cve.org/CVERecord?id=CVE-2023-53821 Référence CVE CVE-2023-53823 https://www.cve.org/CVERecord?id=CVE-2023-53823 Référence CVE CVE-2023-53825 https://www.cve.org/CVERecord?id=CVE-2023-53825 Référence CVE CVE-2023-53828 https://www.cve.org/CVERecord?id=CVE-2023-53828 Référence CVE CVE-2023-53831 https://www.cve.org/CVERecord?id=CVE-2023-53831 Référence CVE CVE-2023-53834 https://www.cve.org/CVERecord?id=CVE-2023-53834 Référence CVE CVE-2023-53836 https://www.cve.org/CVERecord?id=CVE-2023-53836 Référence CVE CVE-2023-53839 https://www.cve.org/CVERecord?id=CVE-2023-53839 Référence CVE CVE-2023-53841 https://www.cve.org/CVERecord?id=CVE-2023-53841 Référence CVE CVE-2023-53842 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2023-53808 Référence CVE CVE-2023-53811 https://www.cve.org/CVERecord?id=CVE-2023-53811 Référence CVE CVE-2023-53813 https://www.cve.org/CVERecord?id=CVE-2023-53813 Référence CVE CVE-2023-53814 https://www.cve.org/CVERecord?id=CVE-2023-53814 Référence CVE CVE-2023-53815 https://www.cve.org/CVERecord?id=CVE-2023-53815 Référence CVE CVE-2023-53818 https://www.cve.org/CVERecord?id=CVE-2023-53818 Référence CVE CVE-2023-53819 https://www.cve.org/CVERecord?id=CVE-2023-53819 Référence CVE CVE-2023-53820 https://www.cve.org/CVERecord?id=CVE-2023-53820 Référence CVE CVE-2023-53821 https://www.cve.org/CVERecord?id=CVE-2023-53821 Référence CVE CVE-2023-53823 https://www.cve.org/CVERecord?id=CVE-2023-53823 Référence CVE CVE-2023-53825 https://www.cve.org/CVERecord?id=CVE-2023-53825 Référence CVE CVE-2023-53827 https://www.cve.org/CVERecord?id=CVE-2023-53827 Référence CVE CVE-2023-53828 https://www.cve.org/CVERecord?id=CVE-2023-53828 Référence CVE CVE-2023-53830 https://www.cve.org/CVERecord?id=CVE-2023-53830 Référence CVE CVE-2023-53831 https://www.cve.org/CVERecord?id=CVE-2023-53831 Référence CVE CVE-2023-53832 https://www.cve.org/CVERecord?id=CVE-2023-53832 Référence CVE CVE-2023-53834 https://www.cve.org/CVERecord?id=CVE-2023-53834 Référence CVE CVE-2023-53836 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2023-53811 Référence CVE CVE-2023-53813 https://www.cve.org/CVERecord?id=CVE-2023-53813 Référence CVE CVE-2023-53814 https://www.cve.org/CVERecord?id=CVE-2023-53814 Référence CVE CVE-2023-53815 https://www.cve.org/CVERecord?id=CVE-2023-53815 Référence CVE CVE-2023-53816 https://www.cve.org/CVERecord?id=CVE-2023-53816 Référence CVE CVE-2023-53818 https://www.cve.org/CVERecord?id=CVE-2023-53818 Référence CVE CVE-2023-53819 https://www.cve.org/CVERecord?id=CVE-2023-53819 Référence CVE CVE-2023-53820 https://www.cve.org/CVERecord?id=CVE-2023-53820 Référence CVE CVE-2023-53821 https://www.cve.org/CVERecord?id=CVE-2023-53821 Référence CVE CVE-2023-53823 https://www.cve.org/CVERecord?id=CVE-2023-53823 Référence CVE CVE-2023-53825 https://www.cve.org/CVERecord?id=CVE-2023-53825 Référence CVE CVE-2023-53827 https://www.cve.org/CVERecord?id=CVE-2023-53827 Référence CVE CVE-2023-53828 https://www.cve.org/CVERecord?id=CVE-2023-53828 Référence CVE CVE-2023-53830 https://www.cve.org/CVERecord?id=CVE-2023-53830 Référence CVE CVE-2023-53831 https://www.cve.org/CVERecord?id=CVE-2023-53831 Référence CVE CVE-2023-53832 https://www.cve.org/CVERecord?id=CVE-2023-53832 Référence CVE CVE-2023-53833 https://www.cve.org/CVERecord?id=CVE-2023-53833 Référence CVE CVE-2023-53834 https://www.cve.org/CVERecord?id=

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.19, 6.4.4 ≤ 6.4.*, 6.5 ≤ *
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 9 Dec 2025 · Last source change 5 Aug 2026, 09:16 UTC · CWE not yet assigned

CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2023-60173
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceUnavailable
NVD statusNVD not scheduled

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-60173↗Vendor CSAF · SUSE Product Security Team↗CVE authority or vendor 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-53823 · cve.blacktree.nl