FKIE_CVE-2026-64248
Vulnerability from fkie_nvd - Published: 2026-07-24 16:16 - Updated: 2026-11-08 16:10| Vendor | Product | Version | |
|---|---|---|---|
| linux | linux_kernel | * | |
| linux | linux_kernel | * | |
| linux | linux_kernel | * | |
| linux | linux_kernel | * | |
| linux | linux_kernel | * | |
| linux | linux_kernel | * | |
| linux | linux_kernel | 7.1 | |
| linux | linux_kernel | 7.1 | |
| linux | linux_kernel | 7.1 | |
| linux | linux_kernel | 7.1 | |
| linux | linux_kernel | 7.1 |
{
"affected": [
{
"affectedData": [
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"arch/mips/kernel/smp.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "f8a1ef884013dc99f712d3eb75624c7cd3fd94f6",
"status": "affected",
"version": "2dc79362302922cb18f35e262712b5e58de65442",
"versionType": "git"
},
{
"lessThan": "e1919d026706544cb6e7251ec06e908edd6f34ee",
"status": "affected",
"version": "eef4f71b46a9929ac33e968538c9dd5d96a02460",
"versionType": "git"
},
{
"lessThan": "6eda71977ee11c222f8ad4cae4d18d50448e56f4",
"status": "affected",
"version": "684a78183c54c23e70d1cba320f7fc184604210b",
"versionType": "git"
},
{
"lessThan": "f9b57a0015c241274651f4b36627f56b1b5a8651",
"status": "affected",
"version": "18c0456ea2615b1a743a6db739c74411c3b42bc6",
"versionType": "git"
},
{
"lessThan": "9fef09df42df55ab819b285ea892e0fc1b95a9c4",
"status": "affected",
"version": "91840be8f710370607f949a627e070896faeddb8",
"versionType": "git"
},
{
"lessThan": "9f3f3bdc6d9dac1a5a8262ee7ad0f2ff1527a7e7",
"status": "affected",
"version": "91840be8f710370607f949a627e070896faeddb8",
"versionType": "git"
},
{
"status": "affected",
"version": "81b582784518196eff1050212a046bc29d3a05dd",
"versionType": "git"
},
{
"lessThan": "6.1.178",
"status": "affected",
"version": "6.1.175",
"versionType": "semver"
},
{
"lessThan": "6.6.145",
"status": "affected",
"version": "6.6.142",
"versionType": "semver"
},
{
"lessThan": "6.12.95",
"status": "affected",
"version": "6.12.92",
"versionType": "semver"
},
{
"lessThan": "6.18.38",
"status": "affected",
"version": "6.18.34",
"versionType": "semver"
},
{
"lessThan": "7.1",
"status": "affected",
"version": "7.0.11",
"versionType": "semver"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"arch/mips/kernel/smp.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"status": "affected",
"version": "7.1"
},
{
"lessThan": "7.1",
"status": "unaffected",
"version": "0",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.1.*",
"status": "unaffected",
"version": "6.1.178",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.6.*",
"status": "unaffected",
"version": "6.6.145",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.12.*",
"status": "unaffected",
"version": "6.12.95",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.18.*",
"status": "unaffected",
"version": "6.18.38",
"versionType": "semver"
},
{
"lessThanOrEqual": "7.1.*",
"status": "unaffected",
"version": "7.1.3",
"versionType": "semver"
},
{
"lessThanOrEqual": "*",
"status": "unaffected",
"version": "7.2",
"versionType": "original_commit_for_fix"
}
]
}
],
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}
],
"configurations": [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"matchCriteriaId": "6476CFBE-7300-465C-8DBA-620D3D005F5A",
"versionEndExcluding": "6.1.178",
"versionStartIncluding": "6.1.175",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"matchCriteriaId": "D144D922-9AD2-409A-85E8-D8620FC3CA68",
"versionEndExcluding": "6.6.145",
"versionStartIncluding": "6.6.142",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"matchCriteriaId": "2E4368C8-9FF7-4CC0-87A3-C707FFF4C1C0",
"versionEndExcluding": "6.12.95",
"versionStartIncluding": "6.12.92",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"matchCriteriaId": "756FA43D-0AB4-4F32-87FC-8C7552758B86",
"versionEndExcluding": "6.18.38",
"versionStartIncluding": "6.18.34",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"matchCriteriaId": "F099E30C-99C7-4E28-BFFA-57D8DCD36E9B",
"versionEndExcluding": "7.1",
"versionStartIncluding": "7.0.11",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"matchCriteriaId": "45BB622E-915E-4013-B2C5-D455CDA9D2DD",
"versionEndExcluding": "7.1.3",
"versionStartIncluding": "7.1.1",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:7.1:-:*:*:*:*:*:*",
"matchCriteriaId": "42591D75-4648-4AF0-B193-8AE633EFFACF",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:7.1:rc4:*:*:*:*:*:*",
"matchCriteriaId": "E5910A9D-F60A-409A-B486-FE66BFEBA9B9",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:7.1:rc5:*:*:*:*:*:*",
"matchCriteriaId": "81DFF19E-9CF8-49C6-8C36-1E4038622933",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:7.1:rc6:*:*:*:*:*:*",
"matchCriteriaId": "B0E8FC71-3952-444C-83E9-718DBBBEC615",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:7.1:rc7:*:*:*:*:*:*",
"matchCriteriaId": "1039E95A-8CC3-4C88-8FF9-5C08EEB861C9",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
]
}
],
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nMIPS: smp: report dying CPU to RCU in stop_this_cpu()\n\nsmp_send_stop() parks all secondary CPUs in stop_this_cpu(). The function\nmarks the CPU offline for the scheduler via set_cpu_online(false) but\nnever informs RCU, so RCU keeps expecting a quiescent state from CPUs\nthat are now spinning forever with interrupts disabled.\n\nAs long as nothing waits for an RCU grace period after smp_send_stop()\nthis is harmless, which is why it went unnoticed. Since commit\n91840be8f710 (\"irq_work: Fix use-after-free in irq_work_single() on PREEMPT_RT\")\nhowever, irq_work_sync() calls synchronize_rcu() on architectures without\nan irq_work self-IPI, i.e. where arch_irq_work_has_interrupt() returns\nfalse. That is the asm-generic default used by MIPS. Any irq_work_sync()\nissued in the reboot/shutdown path after smp_send_stop() then blocks on\na grace period that can never complete, hanging the reboot:\n\n WARNING: CPU: 0 PID: 15 at kernel/irq_work.c:144 irq_work_queue_on\n ...\n rcu: INFO: rcu_sched detected stalls on CPUs/tasks:\n rcu: Offline CPU 1 blocking current GP.\n rcu: Offline CPU 2 blocking current GP.\n rcu: Offline CPU 3 blocking current GP.\n\nThis issue was noticed on several Realtek MIPS switch SoCs (MIPS\ninterAptiv) and came up during kernel bump downstream in OpenWrt from\n6.18.33 to 6.18.34, after the backport of the patch to the 6.18 stable\nbranch. The patch also has been backported all the way back to 6.1.\n\nCall rcutree_report_cpu_dead() once interrupts are disabled, mirroring the\ngeneric CPU-hotplug offline path, so RCU stops waiting on the parked CPUs\nand grace periods can still complete. MIPS shuts down all CPUs here\nwithout going through the CPU-hotplug mechanism, so this report is not\notherwise issued. Reporting a dying CPU to RCU outside the regular hotplug\noffline path is not unprecedented: arm64 does the same in cpu_die_early().\nThere it is an exception for a CPU that was coming online and is aborting\nbringup, rather than the default shutdown action as on MIPS."
},
{
"lang": "es",
"value": "En el kernel de Linux, la siguiente vulnerabilidad ha sido resuelta:\n\nMIPS: smp: informar CPU moribunda a RCU en stop_this_cpu()\n\nsmp_send_stop() estaciona todas las CPUs secundarias en stop_this_cpu(). La funci\u00f3n marca la CPU como fuera de l\u00ednea para el planificador a trav\u00e9s de set_cpu_online(false) pero nunca informa a RCU, por lo que RCU sigue esperando un estado de reposo de las CPUs que ahora est\u00e1n girando indefinidamente con las interrupciones deshabilitadas.\n\nMientras nada espere un per\u00edodo de gracia de RCU despu\u00e9s de smp_send_stop(), esto es inofensivo, raz\u00f3n por la cual pas\u00f3 desapercibido. Sin embargo, desde el commit 91840be8f710 (\u2019irq_work: Fix use-after-free in irq_work_single() on PREEMPT_RT\u2019), irq_work_sync() llama a synchronize_rcu() en arquitecturas sin un auto-IPI de irq_work, es decir, donde arch_irq_work_has_interrupt() devuelve falso. Ese es el valor predeterminado asm-generic utilizado por MIPS. Cualquier irq_work_sync() emitido en la ruta de reinicio/apagado despu\u00e9s de smp_send_stop() se bloquea entonces en un per\u00edodo de gracia que nunca puede completarse, colgando el reinicio:\n\n ADVERTENCIA: CPU: 0 PID: 15 en kernel/irq_work.c:144 irq_work_queue_on\n ...\n rcu: INFO: rcu_sched detect\u00f3 bloqueos en CPUs/tareas:\n rcu: CPU 1 fuera de l\u00ednea bloqueando GP actual.\n rcu: CPU 2 fuera de l\u00ednea bloqueando GP actual.\n rcu: CPU 3 fuera de l\u00ednea bloqueando GP actual.\n\nEste problema fue notado en varios SoCs de switch MIPS de Realtek (MIPS interAptiv) y surgi\u00f3 durante la actualizaci\u00f3n del kernel en OpenWrt de 6.18.33 a 6.18.34, despu\u00e9s del backport del parche a la rama estable 6.18. El parche tambi\u00e9n ha sido backporteado hasta la versi\u00f3n 6.1.\n\nLlamar a rcutree_report_cpu_dead() una vez que las interrupciones est\u00e9n deshabilitadas, reflejando la ruta gen\u00e9rica de desconexi\u00f3n de CPU-hotplug, para que RCU deje de esperar en las CPUs estacionadas y los per\u00edodos de gracia a\u00fan puedan completarse. MIPS apaga todas las CPUs aqu\u00ed sin pasar por el mecanismo de CPU-hotplug, por lo que este informe no se emite de otra manera. Informar una CPU moribunda a RCU fuera de la ruta regular de desconexi\u00f3n de hotplug no tiene precedentes: arm64 hace lo mismo en cpu_die_early(). All\u00ed es una excepci\u00f3n para una CPU que estaba entrando en l\u00ednea y est\u00e1 abortando el inicio, en lugar de la acci\u00f3n de apagado predeterminada como en MIPS."
}
],
"id": "CVE-2026-64248",
"lastModified": "2026-11-08T16:10:00.183",
"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"
}
]
},
"published": "2026-07-24T16:16:54.280",
"references": [
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"tags": [
"Patch"
],
"url": "https://git.kernel.org/stable/c/6eda71977ee11c222f8ad4cae4d18d50448e56f4"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"tags": [
"Patch"
],
"url": "https://git.kernel.org/stable/c/9f3f3bdc6d9dac1a5a8262ee7ad0f2ff1527a7e7"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"tags": [
"Patch"
],
"url": "https://git.kernel.org/stable/c/9fef09df42df55ab819b285ea892e0fc1b95a9c4"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"tags": [
"Patch"
],
"url": "https://git.kernel.org/stable/c/e1919d026706544cb6e7251ec06e908edd6f34ee"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"tags": [
"Patch"
],
"url": "https://git.kernel.org/stable/c/f8a1ef884013dc99f712d3eb75624c7cd3fd94f6"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"tags": [
"Patch"
],
"url": "https://git.kernel.org/stable/c/f9b57a0015c241274651f4b36627f56b1b5a8651"
}
],
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"vulnStatus": "Analyzed",
"weaknesses": [
{
"description": [
{
"lang": "en",
"value": "NVD-CWE-noinfo"
}
],
"source": "nvd@nist.gov",
"type": "Primary"
}
]
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
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.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
How durations are calculated
Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.
Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.
Loading timeline…
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.
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.