CVE-2026-43323 (GCVE-0-2026-43323)
Vulnerability from cvelistv5 – Published: 2026-05-08 13:31 – Updated: 2026-11-06 15:42
VLAI
EPSS
VEX
Title
sched/fair: Fix zero_vruntime tracking fix
Summary
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().
Severity
No CVSS data available.
SSVC
Exploitation: none
Automatable: no
Technical Impact: partial
CISA Coordinator · CISA-ADP (v2.0.3)
Decision recorded 2026-11-06 15:35 UTC
Assigner
References
Impacted products
2 products
| Vendor | Product | Version | |
|---|---|---|---|
| Linux | Linux |
Affected:
d2fc2dcfce47a56ffd414783003cc966c742c8a9 , < c089147074ed96ff4330739a0559394c19a3dfc8
(git)
Affected: 99673934a89febe664e704550216638dcb2336a8 , < 87573883c30f1a8555ff720836bb6ea231058539 (git) Affected: 978d4fe59665c13db692ba96839f9c52d69f13f3 , < fb61ffb3fb30a161eb5404c27fc7635e275beafd (git) Affected: b3d99f43c72b56cf7a104a364e7fb34b0702828b , < 1319ea57529e131822bab56bf417c8edc2db9ae8 (git) |
|
| Linux | Linux |
Affected:
6.12.78 , < 6.12.81
(semver)
Affected: 6.18.17 , < 6.18.22 (semver) Affected: 6.19.7 , < 6.19.12 (semver) |
{
"containers": {
"adp": [
{
"metrics": [
{
"other": {
"content": {
"id": "CVE-2026-43323",
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "no"
},
{
"Technical Impact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-11-06T15:35:42.794523Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2026-11-06T15:42:49.004Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"kernel/sched/fair.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "c089147074ed96ff4330739a0559394c19a3dfc8",
"status": "affected",
"version": "d2fc2dcfce47a56ffd414783003cc966c742c8a9",
"versionType": "git"
},
{
"lessThan": "87573883c30f1a8555ff720836bb6ea231058539",
"status": "affected",
"version": "99673934a89febe664e704550216638dcb2336a8",
"versionType": "git"
},
{
"lessThan": "fb61ffb3fb30a161eb5404c27fc7635e275beafd",
"status": "affected",
"version": "978d4fe59665c13db692ba96839f9c52d69f13f3",
"versionType": "git"
},
{
"lessThan": "1319ea57529e131822bab56bf417c8edc2db9ae8",
"status": "affected",
"version": "b3d99f43c72b56cf7a104a364e7fb34b0702828b",
"versionType": "git"
}
]
},
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"kernel/sched/fair.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "6.12.81",
"status": "affected",
"version": "6.12.78",
"versionType": "semver"
},
{
"lessThan": "6.18.22",
"status": "affected",
"version": "6.18.17",
"versionType": "semver"
},
{
"lessThan": "6.19.12",
"status": "affected",
"version": "6.19.7",
"versionType": "semver"
}
]
}
],
"cpeApplicability": [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.12.81",
"versionStartIncluding": "6.12.78",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.18.22",
"versionStartIncluding": "6.18.17",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.19.12",
"versionStartIncluding": "6.19.7",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
]
}
],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nsched/fair: Fix zero_vruntime tracking fix\n\nJohn reported that stress-ng-yield could make his machine unhappy and\nmanaged to bisect it to commit b3d99f43c72b (\"sched/fair: Fix\nzero_vruntime tracking\").\n\nThe combination of yield and that commit was specific enough to\nhypothesize the following scenario:\n\nSuppose we have 2 runnable tasks, both doing yield. Then one will be\neligible and one will not be, because the average position must be in\nbetween these two entities.\n\nTherefore, the runnable task will be eligible, and be promoted a full\nslice (all the tasks do is yield after all). This causes it to jump over\nthe other task and now the other task is eligible and current is no\nlonger. So we schedule.\n\nSince we are runnable, there is no {de,en}queue. All we have is the\n__{en,de}queue_entity() from {put_prev,set_next}_task(). But per the\nfingered commit, those two no longer move zero_vruntime.\n\nAll that moves zero_vruntime are tick and full {de,en}queue.\n\nThis means, that if the two tasks playing leapfrog can reach the\ncritical speed to reach the overflow point inside one tick\u0027s worth of\ntime, we\u0027re up a creek.\n\nAdditionally, when multiple cgroups are involved, there is no guarantee\nthe tick will in fact hit every cgroup in a timely manner. Statistically\nspeaking it will, but that same statistics does not rule out the\npossibility of one cgroup not getting a tick for a significant amount of\ntime -- however unlikely.\n\nTherefore, just like with the yield() case, force an update at the end\nof every slice. This ensures the update is never more than a single\nslice behind and the whole thing is within 2 lag bounds as per the\ncomment on entity_key()."
}
],
"providerMetadata": {
"dateUpdated": "2026-05-11T22:22:20.507Z",
"orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"shortName": "Linux"
},
"references": [
{
"url": "https://git.kernel.org/stable/c/c089147074ed96ff4330739a0559394c19a3dfc8"
},
{
"url": "https://git.kernel.org/stable/c/87573883c30f1a8555ff720836bb6ea231058539"
},
{
"url": "https://git.kernel.org/stable/c/fb61ffb3fb30a161eb5404c27fc7635e275beafd"
},
{
"url": "https://git.kernel.org/stable/c/1319ea57529e131822bab56bf417c8edc2db9ae8"
}
],
"title": "sched/fair: Fix zero_vruntime tracking fix",
"x_generator": {
"engine": "bippy-1.2.0"
}
}
},
"cveMetadata": {
"assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"assignerShortName": "Linux",
"cveId": "CVE-2026-43323",
"datePublished": "2026-05-08T13:31:08.188Z",
"dateReserved": "2026-05-01T14:12:56.001Z",
"dateUpdated": "2026-11-06T15:42:49.004Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2",
"vulnerability-lookup:meta": {
"epss": {
"cve": "CVE-2026-43323",
"date": "2026-11-16",
"epss": "0.00122",
"percentile": "0.0201"
},
"nvd": {
"cve": {
"affected": [
{
"affectedData": [
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"kernel/sched/fair.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "c089147074ed96ff4330739a0559394c19a3dfc8",
"status": "affected",
"version": "d2fc2dcfce47a56ffd414783003cc966c742c8a9",
"versionType": "git"
},
{
"lessThan": "87573883c30f1a8555ff720836bb6ea231058539",
"status": "affected",
"version": "99673934a89febe664e704550216638dcb2336a8",
"versionType": "git"
},
{
"lessThan": "fb61ffb3fb30a161eb5404c27fc7635e275beafd",
"status": "affected",
"version": "978d4fe59665c13db692ba96839f9c52d69f13f3",
"versionType": "git"
},
{
"lessThan": "1319ea57529e131822bab56bf417c8edc2db9ae8",
"status": "affected",
"version": "b3d99f43c72b56cf7a104a364e7fb34b0702828b",
"versionType": "git"
}
]
},
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"kernel/sched/fair.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "6.12.81",
"status": "affected",
"version": "6.12.78",
"versionType": "semver"
},
{
"lessThan": "6.18.22",
"status": "affected",
"version": "6.18.17",
"versionType": "semver"
},
{
"lessThan": "6.19.12",
"status": "affected",
"version": "6.19.7",
"versionType": "semver"
}
]
}
],
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}
],
"configurations": [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"matchCriteriaId": "3567D859-58AE-4093-AF8D-4FAF8C4F6486",
"versionEndExcluding": "6.12.81",
"versionStartIncluding": "6.12.78",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"matchCriteriaId": "3453DC21-7215-4DEF-AA80-3E40542E64E4",
"versionEndExcluding": "6.18.22",
"versionStartIncluding": "6.18.17",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"matchCriteriaId": "F9B925B8-9C64-4FC6-A4EF-B7840F1F1889",
"versionEndExcluding": "6.19.12",
"versionStartIncluding": "6.19.7",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
]
}
],
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nsched/fair: Fix zero_vruntime tracking fix\n\nJohn reported that stress-ng-yield could make his machine unhappy and\nmanaged to bisect it to commit b3d99f43c72b (\"sched/fair: Fix\nzero_vruntime tracking\").\n\nThe combination of yield and that commit was specific enough to\nhypothesize the following scenario:\n\nSuppose we have 2 runnable tasks, both doing yield. Then one will be\neligible and one will not be, because the average position must be in\nbetween these two entities.\n\nTherefore, the runnable task will be eligible, and be promoted a full\nslice (all the tasks do is yield after all). This causes it to jump over\nthe other task and now the other task is eligible and current is no\nlonger. So we schedule.\n\nSince we are runnable, there is no {de,en}queue. All we have is the\n__{en,de}queue_entity() from {put_prev,set_next}_task(). But per the\nfingered commit, those two no longer move zero_vruntime.\n\nAll that moves zero_vruntime are tick and full {de,en}queue.\n\nThis means, that if the two tasks playing leapfrog can reach the\ncritical speed to reach the overflow point inside one tick\u0027s worth of\ntime, we\u0027re up a creek.\n\nAdditionally, when multiple cgroups are involved, there is no guarantee\nthe tick will in fact hit every cgroup in a timely manner. Statistically\nspeaking it will, but that same statistics does not rule out the\npossibility of one cgroup not getting a tick for a significant amount of\ntime -- however unlikely.\n\nTherefore, just like with the yield() case, force an update at the end\nof every slice. This ensures the update is never more than a single\nslice behind and the whole thing is within 2 lag bounds as per the\ncomment on entity_key()."
},
{
"lang": "es",
"value": "En el kernel de Linux, la siguiente vulnerabilidad ha sido resuelta:\n\nsched/fair: Correcci\u00f3n del seguimiento de zero_vruntime\n\nJohn inform\u00f3 que stress-ng-yield pod\u00eda hacer que su m\u00e1quina funcionara mal y logr\u00f3 identificar la causa hasta el commit b3d99f43c72b (\u2019sched/fair: Fix zero_vruntime tracking\u2019).\n\nLa combinaci\u00f3n de yield y ese commit fue lo suficientemente espec\u00edfica como para hipotetizar el siguiente escenario:\n\nSupongamos que tenemos 2 tareas ejecutables, ambas haciendo yield. Entonces una ser\u00e1 elegible y la otra no, porque la posici\u00f3n promedio debe estar entre estas dos entidades.\n\nPor lo tanto, la tarea ejecutable ser\u00e1 elegible y ser\u00e1 promovida una porci\u00f3n completa (despu\u00e9s de todo, todo lo que hacen las tareas es yield). Esto hace que salte sobre la otra tarea y ahora la otra tarea es elegible y la actual ya no lo es. As\u00ed que planificamos.\n\nDado que somos ejecutables, no hay {de,en}queue. Todo lo que tenemos es el __{en,de}queue_entity() de {put_prev,set_next}_task(). Pero seg\u00fan el commit se\u00f1alado, esos dos ya no mueven zero_vruntime.\n\nTodo lo que mueve zero_vruntime son el tick y el {de,en}queue completo.\n\nEsto significa que, si las dos tareas que juegan a la rayuela pueden alcanzar la velocidad cr\u00edtica para llegar al punto de desbordamiento dentro del tiempo de un tick, estamos en un aprieto.\n\nAdem\u00e1s, cuando hay m\u00faltiples cgroups involucrados, no hay garant\u00eda de que el tick realmente llegue a cada cgroup de manera oportuna. Estad\u00edsticamente hablando, lo har\u00e1, pero esas mismas estad\u00edsticas no descartan la posibilidad de que un cgroup no reciba un tick durante una cantidad significativa de tiempo, por improbable que sea.\n\nPor lo tanto, al igual que con el caso de yield(), fuerza una actualizaci\u00f3n al final de cada porci\u00f3n. Esto asegura que la actualizaci\u00f3n nunca est\u00e9 m\u00e1s de una sola porci\u00f3n atrasada y que todo est\u00e9 dentro de los 2 l\u00edmites de retraso seg\u00fan el comentario en entity_key()."
}
],
"id": "CVE-2026-43323",
"lastModified": "2026-11-11T20:10:00.273",
"metrics": {
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "LOCAL",
"availabilityImpact": "HIGH",
"baseScore": 5.5,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"privilegesRequired": "LOW",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H",
"version": "3.1"
},
"exploitabilityScore": 1.8,
"impactScore": 3.6,
"source": "nvd@nist.gov",
"type": "Primary"
}
],
"ssvcV203": [
{
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"ssvcData": {
"id": "CVE-2026-43323",
"options": [
{
"exploitation": "none"
},
{
"automatable": "no"
},
{
"technicalImpact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-11-06T15:35:42.794523Z",
"version": "2.0.3"
}
}
]
},
"published": "2026-05-08T14:16:40.947",
"references": [
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"tags": [
"Patch"
],
"url": "https://git.kernel.org/stable/c/1319ea57529e131822bab56bf417c8edc2db9ae8"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"tags": [
"Patch"
],
"url": "https://git.kernel.org/stable/c/87573883c30f1a8555ff720836bb6ea231058539"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"tags": [
"Patch"
],
"url": "https://git.kernel.org/stable/c/c089147074ed96ff4330739a0559394c19a3dfc8"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"tags": [
"Patch"
],
"url": "https://git.kernel.org/stable/c/fb61ffb3fb30a161eb5404c27fc7635e275beafd"
}
],
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"vulnStatus": "Analyzed",
"weaknesses": [
{
"description": [
{
"lang": "en",
"value": "NVD-CWE-noinfo"
}
],
"source": "nvd@nist.gov",
"type": "Primary"
}
]
}
},
"redhat_vex": {
"aggregate_severity": "Moderate",
"current_release_date": "2026-11-07T04:43:42+00:00",
"cve": "CVE-2026-43323",
"id": "CVE-2026-43323",
"initial_release_date": "2026-05-08T00:00:00+00:00",
"product_status:known_affected": "186",
"product_status:known_not_affected": "14",
"source": "Red Hat CSAF VEX",
"status": "final",
"title": "kernel: sched/fair: Fix zero_vruntime tracking fix",
"url": "https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-43323.json",
"version": "3"
},
"suse_vex": {
"aggregate_severity": "moderate",
"current_release_date": "2026-11-07T02:18:13Z",
"cve": "CVE-2026-43323",
"id": "CVE-2026-43323",
"initial_release_date": "2026-05-13T03:35:24Z",
"product_status:known_not_affected": "385",
"product_status:recommended": "58",
"source": "SUSE CSAF VEX",
"status": "interim",
"title": "SUSE CVE CVE-2026-43323",
"url": "https://ftp.suse.com/pub/projects/security/csaf-vex/2026/cve-2026-43323.json",
"version": "5"
},
"vulnrichment": {
"containers": {
"adp": [
{
"metrics": [
{
"other": {
"content": {
"id": "CVE-2026-43323",
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "no"
},
{
"Technical Impact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-11-06T15:35:42.794523Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2026-11-06T15:35:44.255Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"kernel/sched/fair.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "c089147074ed96ff4330739a0559394c19a3dfc8",
"status": "affected",
"version": "d2fc2dcfce47a56ffd414783003cc966c742c8a9",
"versionType": "git"
},
{
"lessThan": "87573883c30f1a8555ff720836bb6ea231058539",
"status": "affected",
"version": "99673934a89febe664e704550216638dcb2336a8",
"versionType": "git"
},
{
"lessThan": "fb61ffb3fb30a161eb5404c27fc7635e275beafd",
"status": "affected",
"version": "978d4fe59665c13db692ba96839f9c52d69f13f3",
"versionType": "git"
},
{
"lessThan": "1319ea57529e131822bab56bf417c8edc2db9ae8",
"status": "affected",
"version": "b3d99f43c72b56cf7a104a364e7fb34b0702828b",
"versionType": "git"
}
]
},
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"kernel/sched/fair.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "6.12.81",
"status": "affected",
"version": "6.12.78",
"versionType": "semver"
},
{
"lessThan": "6.18.22",
"status": "affected",
"version": "6.18.17",
"versionType": "semver"
},
{
"lessThan": "6.19.12",
"status": "affected",
"version": "6.19.7",
"versionType": "semver"
}
]
}
],
"cpeApplicability": [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.12.81",
"versionStartIncluding": "6.12.78",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.18.22",
"versionStartIncluding": "6.18.17",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.19.12",
"versionStartIncluding": "6.19.7",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
]
}
],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nsched/fair: Fix zero_vruntime tracking fix\n\nJohn reported that stress-ng-yield could make his machine unhappy and\nmanaged to bisect it to commit b3d99f43c72b (\"sched/fair: Fix\nzero_vruntime tracking\").\n\nThe combination of yield and that commit was specific enough to\nhypothesize the following scenario:\n\nSuppose we have 2 runnable tasks, both doing yield. Then one will be\neligible and one will not be, because the average position must be in\nbetween these two entities.\n\nTherefore, the runnable task will be eligible, and be promoted a full\nslice (all the tasks do is yield after all). This causes it to jump over\nthe other task and now the other task is eligible and current is no\nlonger. So we schedule.\n\nSince we are runnable, there is no {de,en}queue. All we have is the\n__{en,de}queue_entity() from {put_prev,set_next}_task(). But per the\nfingered commit, those two no longer move zero_vruntime.\n\nAll that moves zero_vruntime are tick and full {de,en}queue.\n\nThis means, that if the two tasks playing leapfrog can reach the\ncritical speed to reach the overflow point inside one tick\u0027s worth of\ntime, we\u0027re up a creek.\n\nAdditionally, when multiple cgroups are involved, there is no guarantee\nthe tick will in fact hit every cgroup in a timely manner. Statistically\nspeaking it will, but that same statistics does not rule out the\npossibility of one cgroup not getting a tick for a significant amount of\ntime -- however unlikely.\n\nTherefore, just like with the yield() case, force an update at the end\nof every slice. This ensures the update is never more than a single\nslice behind and the whole thing is within 2 lag bounds as per the\ncomment on entity_key()."
}
],
"providerMetadata": {
"dateUpdated": "2026-05-11T22:22:20.507Z",
"orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"shortName": "Linux"
},
"references": [
{
"url": "https://git.kernel.org/stable/c/c089147074ed96ff4330739a0559394c19a3dfc8"
},
{
"url": "https://git.kernel.org/stable/c/87573883c30f1a8555ff720836bb6ea231058539"
},
{
"url": "https://git.kernel.org/stable/c/fb61ffb3fb30a161eb5404c27fc7635e275beafd"
},
{
"url": "https://git.kernel.org/stable/c/1319ea57529e131822bab56bf417c8edc2db9ae8"
}
],
"title": "sched/fair: Fix zero_vruntime tracking fix",
"x_generator": {
"engine": "bippy-1.2.0"
}
}
},
"cveMetadata": {
"assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"assignerShortName": "Linux",
"cveId": "CVE-2026-43323",
"datePublished": "2026-05-08T13:31:08.188Z",
"dateReserved": "2026-05-01T14:12:56.001Z",
"dateUpdated": "2026-11-06T15:42:49.004Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
}
}
Loading…
Loading…
Experimental. This forecast is provided for visualization only and may change without notice. Do not use it for operational decisions.
Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Loading…
Loading…
The MITRE ATT&CK techniques below are AI-generated suggestions, inferred from the description of the
vulnerability by the CIRCL/vulnerability-attack-technique-classification-roberta-base
model, served locally by ML-Gateway.
They have not been verified by an analyst and are provided for guidance only.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Loading…
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.
Loading…