CVE-2026-92483
In the Linux kernel, the following vulnerability has been resolved:
liveupdate: Remember FLB retrieve() status
LUO keeps track of successful retrieve attempts on an FLB. It does so to avoid multiple retrievals of the same FLB. Multiple retrievals cause problems because once the FLB is retrieved, the serialized data structures are likely freed and the FLB is likely in a very different state from what the code expects.
All this works well when retrieve succeeds. When it fails, luo_flb_retrieve_one() returns the error immediately, without ever storing anywhere that a retrieve was attempted or what its error code was. If the user attempts to retrieve another file registered with the same FLB, LUO will attempt to call the FLB's retrieve() callback again.
Leer descripción completaMostrar menos
The retry is problematic for much of the same reasons listed above. The FLB is likely in a very different state than what the retrieve logic normally expects (e.g. some KHO pages may have already been restored and freed).
There is no sane way of attempting the retrieve again. Remember the error retrieve returned and directly return it on a retry.
This is done by changing the retrieved bool to a retrieve_status integer. A value of 0 means retrieve was never attempted, a positive value means it succeeded, and a negative value means it failed and the error code is the value.
This is similar to commit f85b1c6af5bc ("liveupdate: luo_file: remember retrieve() status") which did the same for LUO files.
CVSS
NVD no ha asignado puntuación CVSS a esta CVE (habitual desde el cambio de política de abril de 2026).
Probabilidad de explotación (EPSS)
- Probabilidad de explotación en los próximos 30 días: 0.22%
- Percentil entre todas las CVEs puntuadas: 11
- Fecha de la puntuación: 6/10/2026
EPSS (Exploit Prediction Scoring System, de FIRST) estima la probabilidad de que una vulnerabilidad sea explotada en 30 días. Complementa a CVSS (impacto) y a CISA KEV (explotación confirmada).
Tecnologías afectadas (1)
⚠ Inferidas por IA a partir de la descripción — NVD aún no ha analizado esta CVE; no son CPE verificados.
Referencias
JSON original (NVD)
Mostrar
{
"id": "CVE-2026-92483",
"cveTags": [],
"metrics": {},
"affected": [
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"affectedData": [
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"product": "Linux",
"versions": [
{
"status": "affected",
"version": "cab056f2aae7250af50e503b81a80dfc567a1acd",
"lessThan": "908f3ea3f050b865c5c2d8c1da566185a4a3efc0",
"versionType": "git"
},
{
"status": "affected",
"version": "cab056f2aae7250af50e503b81a80dfc567a1acd",
"lessThan": "5c4a03afcb21783987ffc64562b76ddd5a21b12b",
"versionType": "git"
}
],
"programFiles": [
"include/linux/liveupdate.h",
"kernel/liveupdate/luo_flb.c"
],
"defaultStatus": "unaffected"
},
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"product": "Linux",
"versions": [
{
"status": "affected",
"version": "7.0"
},
{
"status": "unaffected",
"version": "0",
"lessThan": "7.0",
"versionType": "semver"
},
{
"status": "unaffected",
"version": "7.2.6",
"versionType": "semver",
"lessThanOrEqual": "7.2.*"
},
{
"status": "unaffected",
"version": "7.3-rc1",
"versionType": "original_commit_for_fix",
"lessThanOrEqual": "*"
}
],
"programFiles": [
"include/linux/liveupdate.h",
"kernel/liveupdate/luo_flb.c"
],
"defaultStatus": "affected"
}
]
}
],
"published": "2026-09-17T17:17:50.373",
"references": [
{
"url": "https://git.kernel.org/stable/c/5c4a03afcb21783987ffc64562b76ddd5a21b12b",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/908f3ea3f050b865c5c2d8c1da566185a4a3efc0",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}
],
"vulnStatus": "Received",
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nliveupdate: Remember FLB retrieve() status\n\nLUO keeps track of successful retrieve attempts on an FLB. It does so\nto avoid multiple retrievals of the same FLB. Multiple retrievals cause\nproblems because once the FLB is retrieved, the serialized data\nstructures are likely freed and the FLB is likely in a very different\nstate from what the code expects.\n\nAll this works well when retrieve succeeds. When it fails,\nluo_flb_retrieve_one() returns the error immediately, without ever\nstoring anywhere that a retrieve was attempted or what its error code\nwas. If the user attempts to retrieve another file registered with the\nsame FLB, LUO will attempt to call the FLB's retrieve() callback again.\n\nThe retry is problematic for much of the same reasons listed above. The\nFLB is likely in a very different state than what the retrieve logic\nnormally expects (e.g. some KHO pages may have already been restored and\nfreed).\n\nThere is no sane way of attempting the retrieve again. Remember the\nerror retrieve returned and directly return it on a retry.\n\nThis is done by changing the retrieved bool to a retrieve_status\ninteger. A value of 0 means retrieve was never attempted, a positive\nvalue means it succeeded, and a negative value means it failed and the\nerror code is the value.\n\nThis is similar to commit f85b1c6af5bc (\"liveupdate: luo_file: remember\nretrieve() status\") which did the same for LUO files."
}
],
"lastModified": "2026-09-17T17:17:50.373",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}