AEGLIX vulnerability intelligence
CVE-2026-43323
MEDIUM · CVSS 5.5 · Analyzed
Published: 2026-05-08 · Updated: 2026-11-11 · Source: NVD
Stored catalog record
Source record retrieved 2026-11-11T22:14:36.357475+00:00. Scheduled imports handle updates; this page does not assert that the provider was queried just now.
Continue your research
Connect this record to stored reporting, reviewed campaign mentions and source-domain investigation. These are research leads, not inferred attack relationships.
Open CVE research in Investigate · Find Arsenal listings referencing this CVE
Vulnerability overview
In the Linux kernel, the following vulnerability has been resolved: sched/fair: Fix zero_vruntime tracking fix John reported that stress-ng-yield could make his machine unhappy and managed to bisect it to commit b3d99f43c72b ("sched/fair: Fix zero_vruntime tracking"). The combination of yield and that commit was specific enough to hypothesize the following scenario: Suppose we have 2 runnable tasks, both doing yield. Then one will be eligible and one will not be, because the average position must be in between these two entities. Therefore, the runnable task will be eligible, and be promoted a full slice (all the tasks do is yield after all). This causes it to jump over the other task and now the other task is eligible and current is no longer. So we schedule. Since we are runnable, there is no {de,en}queue. All we have is the __{en,de}queue_entity() from {put_prev,set_next}_task(). But per the fingered commit, those two no longer move zero_vruntime. All that moves zero_vruntime are tick and full {de,en}queue. This means, that if the two tasks playing leapfrog can reach the critical speed to reach the overflow point inside one tick's worth of time, we're up a creek. Additionally, when multiple cgroups are involved, there is no guarantee the tick will in fact hit every cgroup in a timely manner. Statistically speaking it will, but that same statistics does not rule out the possibility of one cgroup not getting a tick for a significant amount of time -- however unlikely. Therefore, just like with the yield() case, force an update at the end of every slice. This ensures the update is never more than a single slice behind and the whole thing is within 2 lag bounds as per the comment on entity_key().
Patch review priority
Assess exposure and vendor guidance
- No higher-priority signal is available in the current stored evidence.
FIRST EPSS: 0.12% · percentile 2.0 · score date 2026-11-18.
EPSS estimates probability of exploitation in the next 30 days. It does not measure your exposure or prove exploitation. The elevated threshold is 10%; CISA KEV takes precedence. About FIRST EPSS ↗
Severity and scoring
- CVSS score
- 5.5 · MEDIUM
- CVSS version
- 3.1
- CVSS vector
- CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
- Weaknesses
- NVD-CWE-noinfo
CVSS measures technical severity; it does not establish whether this vulnerability is being exploited in your environment.
Known exploitation and remediation
Not listed in the CISA catalog retrieved for this record. This does not establish that exploitation has not occurred.
Verify affected versions and patch availability in the vendor advisory before making changes.
Affected products and versions
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
From (inclusive): 6.12.78
Before (exclusive): 6.12.81
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
From (inclusive): 6.18.17
Before (exclusive): 6.18.22
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
From (inclusive): 6.19.7
Before (exclusive): 6.19.12
These are NVD CPE applicability entries. Some products depend on configuration conditions; consult the official record to confirm applicability.
Advisories and references
- https://git.kernel.org/stable/c/1319ea57529e131822bab56bf417c8edc2db9ae8
Patch
- https://git.kernel.org/stable/c/87573883c30f1a8555ff720836bb6ea231058539
Patch
- https://git.kernel.org/stable/c/c089147074ed96ff4330739a0559394c19a3dfc8
Patch
- https://git.kernel.org/stable/c/fb61ffb3fb30a161eb5404c27fc7635e275beafd
Patch