Security readout for executives and security teams
Plain-English summary
A Linux scheduler flaw can trigger an internal warning when the NEXT_BUDDY behavior is enabled. The supplied CVSS assessment indicates potentially serious confidentiality, integrity, and availability consequences, but the sources do not describe a demonstrated attack or specific business impact. Exploitation requires local, low-privileged access and high complexity.
Executive priority
Treat as a high-priority kernel maintenance issue, especially on shared or locally accessible systems. Promptly establish exposure and schedule vendor-supported updates. Emergency response is not supported by the current evidence because active exploitation is unconfirmed and exploitation is rated high complexity.
Technical view
The fair scheduler could retain or assign a next-buddy entity while that entity was in delayed-dequeue state, violating an invariant in pick_next_entity(). The kernel fix moves clear_buddies() before delayed-dequeue handling and prevents delayed entities from becoming the next buddy. The supplied record scores this CVSS 3.1 at 7.0.
Likely exposure
Potential exposure is limited to Linux kernel versions marked affected in the supplied record, including listed 6.12-series and 6.13 entries. Exact range semantics and distribution backports are unclear. Risk requires local access and may depend on NEXT_BUDDY-related scheduler behavior, so validate deployed vendor kernels individually.
Exploitation context
The CVSS vector indicates local access, high attack complexity, low privileges, and no user interaction. CISA KEV status is false, and the supplied sources provide no evidence of active exploitation or a public exploit. The practical path from the reported scheduler warning to the assessed confidentiality, integrity, and availability impacts is not documented.
Researcher notes
The record identifies an invariant failure involving next-buddy selection and delayed dequeue. Two upstream stable commits are provided, but the bundle does not include a CWE, reproducer, affected-configuration details, distribution mappings, or evidence connecting the warning to reliable security impact. Avoid inferring exploitability beyond the supplied CVSS vector.
Mitigation direction
- Apply a vendor-supported kernel containing the referenced upstream stable fixes.
- Check distribution security advisories for backported fixes and exact affected package versions.
- Prioritize multi-user systems where untrusted users can obtain local accounts.
- Use normal maintenance and rollback procedures when deploying the kernel update.
Validation and detection
- Inventory running kernel versions across Linux hosts and compare them with vendor advisories.
- Confirm whether each vendor kernel includes either referenced stable fix or an equivalent backport.
- After updating, verify hosts booted into the corrected kernel.
- Review kernel logs for scheduler warnings associated with pick_next_entity().
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-2024-49573 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
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.
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H15.9LinuxVulnerability scoring details
Base CVSS 3.1 score
7HighVector: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
Source materials
- CVE List V5 sourceCVE List V5
- https://git.kernel.org/stable/c/5dbe6816c49197677a5ecce749bd99929da147daCVE reference, Linux
- https://git.kernel.org/stable/c/493afbd187c4c9cc1642792c0d9ba400c3d6d90dCVE reference, Linux
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.