GHSA-HR4W-PHGX-2F52
Vulnerability from github – Published: 2025-12-24 12:30 – Updated: 2025-12-24 12:30In the Linux kernel, the following vulnerability has been resolved:
wifi: iwlwifi: fix iwl_mvm_max_amsdu_size() for MLO
For MLO, we cannot use vif->bss_conf.chandef.chan->band, since that will lead to a NULL-ptr dereference as bss_conf isn't used. However, in case of real MLO, we also need to take both LMACs into account if they exist, since the station might be active on both LMACs at the same time.
{
"affected": [],
"aliases": [
"CVE-2023-54029"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2025-12-24T11:15:55Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\nwifi: iwlwifi: fix iwl_mvm_max_amsdu_size() for MLO\n\nFor MLO, we cannot use vif-\u003ebss_conf.chandef.chan-\u003eband, since\nthat will lead to a NULL-ptr dereference as bss_conf isn\u0027t used.\nHowever, in case of real MLO, we also need to take both LMACs\ninto account if they exist, since the station might be active\non both LMACs at the same time.",
"id": "GHSA-hr4w-phgx-2f52",
"modified": "2025-12-24T12:30:28Z",
"published": "2025-12-24T12:30:28Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2023-54029"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/4489aa868bc6343afdaf5ef324af5b1f64962b25"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/63e2d06adf6b0842132ba89efdf8fada5f7ff1ac"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/b2bc600cced23762d4e97db8989b18772145604f"
}
],
"schema_version": "1.4.0",
"severity": []
}
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
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.