CVE-2023-52461: drm/sched: Fix bounds limiting when given a malformed entity
In the Linux kernel, the following vulnerability has been resolved:
drm/sched: Fix bounds limiting when given a malformed entity
If we're given a malformed entity in drm_sched_entity_init()--shouldn't
happen, but we verify--with out-of-bounds priority value, we set it to an
allowed value. Fix the expression which sets this limit.
Security readout for executives and security teams
Plain-English summary
CVE-2023-52461 is a Linux kernel DRM scheduler flaw involving incorrect bounds handling for malformed scheduling entities. The stated impact is limited confidentiality exposure, with no integrity or availability impact in the supplied CVSS data. It is not listed as KEV, and the supplied sources do not show active exploitation.
Executive priority
Treat this as a routine but real kernel maintenance item. It does not currently warrant emergency response based on the supplied evidence, but affected Linux fleets should be patched through normal security update processes.
Technical view
The issue is in drm_sched_entity_init(), where an out-of-bounds priority value from a malformed entity should be clamped to an allowed value. The fix corrects the expression used for this limit. The source bundle identifies Linux kernel versions around 6.7/6.8 as affected, but distro backports require vendor confirmation.
Likely exposure
Exposure is likely limited to systems running affected Linux kernel builds that include the vulnerable DRM scheduler code. The source lists Linux kernel 6.7-era versions and fixed stable commits, but exact exposure depends on distribution packaging and backports.
Exploitation context
The CVSS vector indicates network reachability, low complexity, no privileges, and low confidentiality impact. However, the supplied sources do not describe a public exploit, exploitation method, or active exploitation. KEV status is false.
Researcher notes
Source detail is sparse. The record describes a bounds-limiting fix in DRM scheduler entity initialization, but does not provide CWE mapping, exploit details, or operational preconditions. Validate against exact kernel source, vendor advisories, and backported package metadata.
Mitigation direction
Apply Linux kernel stable updates containing the referenced fixes.
Check distribution security advisories for CVE-2023-52461 backport status.
Prioritize internet-facing or multi-tenant Linux systems running affected kernels.
If patching is delayed, follow vendor guidance for compensating controls.
Validation and detection
Inventory running Linux kernel versions across servers and endpoints.
Confirm whether vendor kernel packages include the referenced stable commits.
Check vulnerability scanner results for CVE-2023-52461 after patching.
Review kernel package changelogs for explicit CVE or commit references.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2023-52461 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.