FKIE_CVE-2023-54225
Vulnerability from fkie_nvd - Published: 2025-12-30 13:16 - Updated: 2026-10-28 19:10
Severity
Summary
In the Linux kernel, the following vulnerability has been resolved:
net: ipa: only reset hashed tables when supported
Last year, the code that manages GSI channel transactions switched
from using spinlock-protected linked lists to using indexes into the
ring buffer used for a channel. Recently, Google reported seeing
transaction reference count underflows occasionally during shutdown.
Doug Anderson found a way to reproduce the issue reliably, and
bisected the issue to the commit that eliminated the linked lists
and the lock. The root cause was ultimately determined to be
related to unused transactions being committed as part of the modem
shutdown cleanup activity. Unused transactions are not normally
expected (except in error cases).
The modem uses some ranges of IPA-resident memory, and whenever it
shuts down we zero those ranges. In ipa_filter_reset_table() a
transaction is allocated to zero modem filter table entries. If
hashing is not supported, hashed table memory should not be zeroed.
But currently nothing prevents that, and the result is an unused
transaction. Something similar occurs when we zero routing table
entries for the modem.
By preventing any attempt to clear hashed tables when hashing is not
supported, the reference count underflow is avoided in this case.
Note that there likely remains an issue with properly freeing unused
transactions (if they occur due to errors). This patch addresses
only the underflows that Google originally reported.
References
Impacted products
| Vendor | Product | Version |
|---|
{
"affected": [
{
"affectedData": [
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"drivers/net/ipa/ipa_table.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "50c24f0c940728792c8bdf65c1eaf6b91b3b0dcd",
"status": "affected",
"version": "d338ae28d8a866c57fcac38f3d77bcc1d1702d19",
"versionType": "git"
},
{
"lessThan": "c00af3a818cc573e10100cc6770f0e47befa1fa4",
"status": "affected",
"version": "d338ae28d8a866c57fcac38f3d77bcc1d1702d19",
"versionType": "git"
},
{
"lessThan": "e11ec2b868af2b351c6c1e2e50eb711cc5423a10",
"status": "affected",
"version": "d338ae28d8a866c57fcac38f3d77bcc1d1702d19",
"versionType": "git"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"drivers/net/ipa/ipa_table.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"status": "affected",
"version": "6.1"
},
{
"lessThan": "6.1",
"status": "unaffected",
"version": "0",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.1.*",
"status": "unaffected",
"version": "6.1.45",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.4.*",
"status": "unaffected",
"version": "6.4.8",
"versionType": "semver"
},
{
"lessThanOrEqual": "*",
"status": "unaffected",
"version": "6.5",
"versionType": "original_commit_for_fix"
}
]
}
],
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}
],
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nnet: ipa: only reset hashed tables when supported\n\nLast year, the code that manages GSI channel transactions switched\nfrom using spinlock-protected linked lists to using indexes into the\nring buffer used for a channel. Recently, Google reported seeing\ntransaction reference count underflows occasionally during shutdown.\n\nDoug Anderson found a way to reproduce the issue reliably, and\nbisected the issue to the commit that eliminated the linked lists\nand the lock. The root cause was ultimately determined to be\nrelated to unused transactions being committed as part of the modem\nshutdown cleanup activity. Unused transactions are not normally\nexpected (except in error cases).\n\nThe modem uses some ranges of IPA-resident memory, and whenever it\nshuts down we zero those ranges. In ipa_filter_reset_table() a\ntransaction is allocated to zero modem filter table entries. If\nhashing is not supported, hashed table memory should not be zeroed.\nBut currently nothing prevents that, and the result is an unused\ntransaction. Something similar occurs when we zero routing table\nentries for the modem.\n\nBy preventing any attempt to clear hashed tables when hashing is not\nsupported, the reference count underflow is avoided in this case.\n\nNote that there likely remains an issue with properly freeing unused\ntransactions (if they occur due to errors). This patch addresses\nonly the underflows that Google originally reported."
},
{
"lang": "es",
"value": "En el kernel de Linux, la siguiente vulnerabilidad ha sido resuelta:\n\nnet: ipa: solo restablecer tablas hash cuando sea compatible\n\nEl a\u00f1o pasado, el c\u00f3digo que gestiona las transacciones del canal GSI cambi\u00f3 de usar listas enlazadas protegidas por spinlock a usar \u00edndices en el b\u00fafer circular utilizado para un canal. Recientemente, Google inform\u00f3 haber visto desbordamientos negativos del contador de referencias de transacciones ocasionalmente durante el apagado.\n\nDoug Anderson encontr\u00f3 una manera de reproducir el problema de forma fiable, y realiz\u00f3 una b\u00fasqueda binaria del problema hasta el commit que elimin\u00f3 las listas enlazadas y el bloqueo. La causa ra\u00edz finalmente se determin\u00f3 que estaba relacionada con transacciones no utilizadas que se estaban confirmando como parte de la actividad de limpieza del apagado del m\u00f3dem. Las transacciones no utilizadas no se esperan normalmente (excepto en casos de error).\n\nEl m\u00f3dem utiliza algunos rangos de memoria residente en IPA, y cada vez que se apaga ponemos a cero esos rangos. En ipa_filter_reset_table() se asigna una transacci\u00f3n para poner a cero las entradas de la tabla de filtros del m\u00f3dem. Si el hashing no es compatible, la memoria de la tabla hash no deber\u00eda ponerse a cero. Pero actualmente nada lo impide, y el resultado es una transacci\u00f3n no utilizada. Algo similar ocurre cuando ponemos a cero las entradas de la tabla de enrutamiento para el m\u00f3dem.\n\nAl evitar cualquier intento de borrar tablas hash cuando el hashing no es compatible, se evita el desbordamiento negativo del contador de referencias en este caso.\n\nTenga en cuenta que probablemente a\u00fan queda un problema con la liberaci\u00f3n adecuada de transacciones no utilizadas (si ocurren debido a errores). Este parche aborda solo los desbordamientos negativos que Google inform\u00f3 originalmente."
}
],
"id": "CVE-2023-54225",
"lastModified": "2026-10-28T19:10:00.193",
"metrics": {},
"published": "2025-12-30T13:16:10.877",
"references": [
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/50c24f0c940728792c8bdf65c1eaf6b91b3b0dcd"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/c00af3a818cc573e10100cc6770f0e47befa1fa4"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/e11ec2b868af2b351c6c1e2e50eb711cc5423a10"
}
],
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"vulnStatus": "Deferred"
}
Loading…
Loading…
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.
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.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
Loading timeline…
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.