CVE-2022-48957: dpaa2-switch: Fix memory leak in dpaa2_switch_acl_entry_add() and dpaa2_switch_acl_entry_remove()
In the Linux kernel, the following vulnerability has been resolved:
dpaa2-switch: Fix memory leak in dpaa2_switch_acl_entry_add() and dpaa2_switch_acl_entry_remove()
The cmd_buff needs to be freed when error happened in
dpaa2_switch_acl_entry_add() and dpaa2_switch_acl_entry_remove().
Security readout for executives and security teams
Plain-English summary
This is a Linux kernel memory leak in the dpaa2-switch driver. When ACL entry add or remove operations hit an error, allocated command memory may not be freed. Business impact is likely resource exhaustion risk on affected systems, but the source bundle provides no CVSS score or active exploitation evidence.
Executive priority
Treat this as targeted patch hygiene, not an emergency, unless DPAA2 switching is business-critical in your environment. Prioritize affected network or embedded Linux assets once vendor-fixed kernels are available. Escalate if memory pressure or ACL management failures are observed.
Technical view
The flaw is in dpaa2_switch_acl_entry_add() and dpaa2_switch_acl_entry_remove(). The cmd_buff allocation was not freed on error paths, creating a kernel memory leak. The issue is documented as resolved by Linux stable commits referenced in the CVE source bundle.
Likely exposure
Exposure appears limited to Linux systems using affected kernels and the dpaa2-switch driver path, especially environments that rely on DPAA2 switch ACL management. The bundle lists affected Linux versions but does not provide CPEs, distributions, hardware scope, or downstream package mapping.
Exploitation context
The source bundle does not show KEV listing, public exploitation, exploit maturity, or weaponized use. The likely security concern is memory/resource exhaustion if the vulnerable error paths can be repeatedly reached, but practical exploitability is not established by the provided sources.
Researcher notes
The record lacks CVSS, CWE, CPEs, distro package data, and exploit evidence. Analysis should focus on the dpaa2-switch ACL error paths and whether downstream kernels include the stable commits. Avoid broad Linux exposure claims without confirming driver presence and vendor backports.
Mitigation direction
Update to a vendor-supported kernel containing the referenced stable fixes.
Prioritize systems using dpaa2-switch or DPAA2 switch ACL functionality.
Check distribution advisories for backported fixes and package names.
If patching is delayed, request vendor guidance; no temporary workaround is provided.
Monitor affected systems for unusual kernel memory growth or networking instability.
Validation and detection
Inventory Linux kernel versions across exposed and embedded systems.
Identify hosts where dpaa2-switch is built, loaded, or required.
Confirm kernel packages include the referenced stable fix commits.
Review vendor advisories for downstream fixed package versions.
Check operational logs for repeated ACL management failures.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2022-48957 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.