CVE-2022-50040: net: dsa: sja1105: fix buffer overflow in sja1105_setup_devlink_regions()
In the Linux kernel, the following vulnerability has been resolved:
net: dsa: sja1105: fix buffer overflow in sja1105_setup_devlink_regions()
If an error occurs in dsa_devlink_region_create(), then 'priv->regions'
array will be accessed by negative index '-1'.
Found by Linux Verification Center (linuxtesting.org) with SVACE.
Security readout for executives and security teams
Plain-English summary
CVE-2022-50040 is a Linux kernel flaw in the sja1105 network switch driver. An error path can access an internal array with index -1, creating a buffer overflow risk. The source bundle does not provide CVSS, impact scope, exploitability details, or evidence of active exploitation.
Executive priority
Track as a targeted kernel maintenance issue, not an emergency based on current evidence. Prioritize affected embedded or networking assets, especially custom kernels, because the record confirms a buffer overflow class bug but lacks severity and exploitation data.
Technical view
The issue is in sja1105_setup_devlink_regions(). If dsa_devlink_region_create() fails, priv->regions may be accessed using negative index -1. The Linux kernel marked this resolved through stable commits. The available record names Linux kernel versions as affected, but does not describe attacker prerequisites or runtime reachability.
Likely exposure
Exposure is most likely limited to Linux systems that include and use the net/dsa/sja1105 driver. This commonly matters more for appliances, embedded Linux, or networking platforms using that driver than for general servers where it is absent or unused. Confirm against actual kernel configuration and vendor kernel lineage.
Exploitation context
The bundle says KEV is false and gives no cited evidence of active exploitation. It also does not provide exploit prerequisites, local versus remote reachability, or proof-of-concept status. Treat exploitability as unproven from the provided evidence.
Researcher notes
Key uncertainty is reachability. The record identifies a specific negative-index error path but does not document triggering conditions, privilege requirements, or impact beyond buffer overflow. Analysis should focus on driver presence, devlink region setup paths, and whether downstream kernels carry one of the stable fixes.
Mitigation direction
Update to a vendor kernel containing the referenced stable fixes.
Backport the stable patch if maintaining a custom kernel tree.
Check distribution or device-vendor guidance for exact fixed builds.
Prioritize systems where the sja1105 driver is built, loaded, or required.
Validation and detection
Inventory kernel versions and custom kernel branches against the CVE record.
Check whether the sja1105 driver is enabled or loaded on affected assets.
Verify the fix exists in sja1105_setup_devlink_regions().
Confirm vendor advisories map your deployed kernel to a fixed release.
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-50040 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.
0CVSS vectors
3Timeline events
0ADP providers
5Source links
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
CVE publishedCVE Program
The CVE record was published.
Jun 18, 2025, 11:01 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.