CVE-2022-48882: net/mlx5e: Fix macsec possible null dereference when updating MAC security entity (SecY)
In the Linux kernel, the following vulnerability has been resolved:
net/mlx5e: Fix macsec possible null dereference when updating MAC security entity (SecY)
Upon updating MAC security entity (SecY) in hw offload path, the macsec
security association (SA) initialization routine is called. In case of
extended packet number (epn) is enabled the salt and ssci attributes are
retrieved using the MACsec driver rx_sa context which is unavailable when
updating a SecY property such as encoding-sa hence the null dereference.
Fix by using the provided SA to set those attributes.
Security readout for executives and security teams
Plain-English summary
This is a Linux kernel driver flaw in the mlx5e MACsec hardware offload path. A specific MACsec configuration update can hit a null pointer when extended packet numbers are enabled. The available sources do not provide CVSS, exploitation evidence, or business-impact detail.
Executive priority
Treat this as a targeted Linux kernel maintenance issue, not a broad emergency based on current evidence. Raise priority for environments relying on Mellanox mlx5e MACsec hardware offload, because a kernel null dereference can affect availability.
Technical view
The bug occurs when updating a MACsec SecY property, such as encoding-sa, in the mlx5e hardware offload path. The SA initialization routine reads salt and SSCI from an unavailable RX SA context when EPN is enabled. The kernel fix uses the provided SA instead.
Likely exposure
Likely limited to Linux systems using mlx5e-capable network hardware with MACsec hardware offload and EPN enabled. Source metadata identifies Linux as affected and includes 6.1, 6.1.7, and 6.2 version data, but downstream distribution exposure is not shown.
Exploitation context
No cited source or KEV entry indicates active exploitation. The source bundle only describes a kernel null dereference during a MACsec SecY update path. Practical exploitability, privilege requirements, and remote reachability are not established in the provided evidence.
Researcher notes
Evidence is sparse: no CVSS, CWE, exploit report, or detailed threat model is provided. Analysis should focus on validating reachable mlx5e MACsec offload configurations and mapping the upstream stable commits to distribution kernels or vendor appliance firmware.
Mitigation direction
Review vendor kernel advisories for your distribution and appliance images.
Prioritize kernel updates containing the referenced stable fixes.
Inventory systems using mlx5e NICs with MACsec hardware offload.
Assess whether MACsec EPN is enabled on exposed Linux systems.
If patching is delayed, consult vendor guidance before changing MACsec offload settings.
Validation and detection
Check running kernel versions against vendor advisories and stable backports.
Identify hosts with mlx5e drivers and MACsec hardware offload configured.
Review MACsec configuration for EPN and SecY update workflows.
Confirm patched kernels include the referenced stable commits.
Monitor kernel logs for mlx5e or MACsec null dereference crashes.
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-48882 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.